The deactivate lifecycle fired BackendAccessRevokedEvent with actionDB's Unscoped session, so a listener's Delete through ev.Tx was a hard delete only for that reason. It now passes the save's transaction like every other site.
fireBackendAccessRevoked refuses a nil tx before any listener runs, and the Administrators and Roles update hooks fail closed (like the delete hook) when the save carries no transaction, instead of firing with whatever TxFromContext answered.
pier now resolves only the empty subject (frontend user grant) and pact.MCPGrantSubjectBackend; any other value is ErrUnauthorized and never reaches the linked-administrator lookup.
Add wristband.CheckConsentPath (additive, for hosts to call at boot) and make Authorize answer 500 before storing a pending request while the configured path fails it, so the handoff can never leave the issuer's origin.
A request naming only offline_access now gets Options.DefaultScopes (when set) plus offline access instead of a pending request with zero data scopes. The read fallback is only used when the server accepts read; otherwise the request is refused with invalid_scope (RFC 6749 3.3).
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.
- ConnectView.test.ts: every C1 state, the * rule, no auto-allow, Allow and
Deny bodies through window.location.assign, forbidden schemes, switch
account, 401/404 handling, focus and the profile fallback
- router, LoginView and AccountContributions tests extended for /connect,
the login hint and item rows (null items unchanged, empty block, :title
confirm, 404 item_gone, 409 action_stale)
- AccountContributions renders a section's items as list rows (title,
subtitle, meta joined with ' · ') with one button per item action, or
the dashed empty block; sections without items render as before
- item actions confirm with :title filled as text, post to
/account/contribution-items/{name}/{item}/actions/{action}, reload and
focus the section heading; 404 toasts item_gone and reloads
- myaccount.items_empty, item_gone, item_action_named in en and pl
- docs/backend/admin-spa.md: the /connect screen and My account item rows
- Loading skeleton (aria-busy, no buttons), Expired (404 or no request,
no call), Load error with Try again, No grantable scope (Deny only),
Returning with the continue link for http(s) redirects
- 422 shows scopes_required under the scopes; 5xx, network, 400 and a
javascript:/data:/vbscript: redirect show decide_failed; ticks kept
- 401 hands over to expireSession; focus follows the state heading
- Use another account: logout() without the router, then login with the
/connect?request= redirect
- LoginView shows mcp_connect.login_hint when the redirect is /connect
- /connect route without shell and without public, so login round-trips back
- ConnectView ready state: client mark, fact box, catalog-order scope picker
with the token-dialog * rule, Stay connected, Deny and Allow
- Allow/Deny POST /mcp/consent/{request}; the browser leaves through
window.location.assign after refusing javascript:, data: and vbscript:
- MCPConsent, MCPConsentDecision and AccountItem type aliases
- backend::lang.mcp_connect copy in en and pl; connect page title
- smoke test: ticks, POST body, assign called, router never used
- 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)
- pact: AccountContribution.Items/ItemActions/ItemsEmpty, AccountItem,
AccountItemAction, AccountItemActionInput, ErrAccountItemNotFound
- cabana: the list sends items (null without Items), permitted item actions
and the empty line; boot refuses item actions without Items
- cabana: POST {api}/account/contribution-items/{name}/{item}/actions/{action}
runs only for an item the administrator's own Items listed, in a transaction
(path outside /account/contributions/ to avoid a ServeMux overlap)
- swag views; admin.json and schema.d.ts regenerated; route inventories
- pact: MCPGrant.Subject with MCPGrantSubjectBackend, MCPSubject.ScopeLimited
- pier: a backend-subject grant resolves straight to a scope-limited backend
subject bound to oauth:backend:<client>:<admin>, no link lookup, no ceiling
- pier: the backend guard scope-limits ScopeLimited subjects like g15_ tokens
- wristband: Options.ConsentPath and Options.DefaultScopes; defaults unchanged
- smoke tests TestBackendSubjectSmoke (Postgres) and TestConsentPathSmoke
Five plans in four waves: framework seams, admin SPA consent route and plugin backend mode in parallel, app wiring with a local proof, then unit tests and the release checkpoint. Research open questions marked resolved.
- flare: send region run by TestDocsNotifyReply against a loopback TLS push
service; blogSubscriptions and the publish-source region run by
TestDocsSubscriptionSource on a Postgres container (skips under -short)
- kiosk: write, newest and client regions run by TestDocsWriteManifest (a
copy of the literal fixture), ExampleVersionsResponse and
TestDocsBlogReleases (httptest registry); the CheckT fence reuses
TestPluginManifest
- lagoon: new open region run by TestDocsOpenFromApp (DocsDSN added to
export_docs_test.go); the model, create-post, on-database, publish and
migrations fences reuse the Database pages' targets
- cooler: ExampleFromApp and the articlesController purge declarations;
AllowExport run by TestDocsAllowExport on miniredis
- diary: blogLog and ExampleFor; the generated main's run function, run by
TestDocsRun in a temp directory with diary.Reset on cleanup
- festival: PostPublished/ExampleBus_Fire and PostFormExtended/Collected/
ExampleBus_Collect, with a TestDocsDeclarations for Collected
- fetchguard: fetch region run by TestDocsFetchImage (loopback refused as
private_ip), client region run by TestDocsSyncItems on a stub transport
- cabana: the hand-written controller fence points at Post, PostsController
and BlogPlugin declarations; TestDocsDeclarations now calls each of them
- compass: mailSettings and ExampleOpen; the YAML block matches the
directory ExampleOpen writes
- conga: job, dispatch and progress fences reuse the Jobs page targets; new
reindex and worker regions run in TestDocsDispatch (Docker), and the
schedule fence is FeedPlugin.Schedule, checked by TestDocsSchedule
- backpack: Greeter and ExampleApp_Publish replace the whole-file fence
- beachcomber: Post's Searchable methods plus a new SearchIndexSchema, a
Plugin.Boot that installs the gate, and the existing gate/search regions
- boardwalk: new example_test.go; the mount region runs in ExampleHandler
- bonfire: importPostsCommand and acmeMain (the binary's main as a function
returning the exit code), run by ExampleExecute; ExampleCatalog_Has
- bouncer: users/FindByID and ExampleNewJWTGuard; RefreshRoute run by
TestDocsRefreshRoute on a production compass config
- the Usage fence becomes two src= references to ExampleRender and
ExamplePurify, filled by summer docs:sync
- the Phase 11.1 SC4 acceptance scan now allows top-level src= fences
in module READMEs (nested ones are still refused) and expects the
api/<name> pages to caption them like docs/ pages
- checkSnippets compares top-level src= fences of module READMEs like
docs/ pages; the README src= refusal is gone
- Sync also rewrites drifted src= fences in modules/<name>/README.md,
still all-or-nothing across pages and READMEs
- fenceAnnotator captions top-level src= fences on every page
- the snippet-readme-src planted violation now plants a drifted README
fence instead of the old refusal
- utilities.md, README.md and CLAUDE.md describe src= in module READMEs