The reset fired BackendAccessRevokedEvent inside a plain GORM
transaction, where lagoon.AfterCommit refuses to run, so a listener's
after-commit work (sm-oauthserver-plugin's revoked MCPSubjectChanged
events that end MCP sessions) never ran for this D-13 site.
TestBackendAccessRevokedEvent now asserts the after-commit callback runs
once for a committed reset and not for a vetoed one.
- cabana: BackendAccessRevokedEvent with reasons deleted, deactivated,
password_changed, password_set, password_reset and permissions, fired
synchronously inside the save's transaction; a listener error rolls back
- fired on admin delete, deactivate, a password set by another admin, an own
password change, admin:reset-password, a role/permissions/superuser change
and a role's permission change (every holder); MCPSubjectChanged unchanged
- role delete fires nothing (refused while the role has holders); no sign
out everywhere action exists
- smoke test TestBackendAccessRevokedSmoke (Postgres)
- migrate, migrate:rollback and deferred:purge gain --pretend and --force;
they and queue:clear confirm only in production on an interactive
terminal, so deploys over SSH proceed as before
- result lines: Applied N migrations, Rolled back <id> of <plugin>,
Cleared N jobs from <queue>
- --json for migrate:status, key:generate, route:list, admin:token:create,
admin:token:list, admin:token:scopes and websockets:health; -q keeps the
key and the token
- hints for an empty DSN, an unreachable database, an invalid app.key, a
missing uploads bucket and an application binary run below its root
- flare and websockets:health return bonfire.Reported after printing
- long help and examples for every application command, greeter:hello and
blog:publish; cmd/summer TestCommandsDocumented fails on any gap