docs(phase-32.2): update tracking after plan 32.2-02

This commit is contained in:
Jakub Zych
2026-11-21 00:59:08 +01:00
parent 44a39ff250
commit 26af5f9549

View File

@@ -1712,7 +1712,7 @@ Plans:
**Requirements**: TBD
**Depends on:** Phase 32.1 (MCP OAuth for plugin apps), Phase 19.7 (generic MCP module)
**Repos:** `summercms.go`, `sm-oauthserver-plugin`, `sm-grzybyfunkcjonalne-app`
**Plans:** 1/5 plans executed
**Plans:** 2/5 plans executed
**Success Criteria** (what must be TRUE):
1. With the backend-subject mode on, `/oauth/mcp/authorize` recognises a signed-in administrator from the cabana cookie session, sends an anonymous browser through the admin login and back, and shows a server-rendered, branded consent page; the issued grant carries the administrator (`BackendUserID`) and no frontend user. With the mode off (the default), every existing flow and test of `sm-oauthserver-plugin` and sm-bm-app passes unchanged.
@@ -1726,7 +1726,7 @@ Plans:
- [x] 32.2-01-PLAN.md — Framework seams: pact backend grant and consent provider, wristband handoff, pier scope limit, cabana consent endpoint, revoke event, account items
**Wave 2** *(blocked on Wave 1 completion)*
- [ ] 32.2-02-PLAN.md — Admin SPA consent route, switch account, account items, openapi and dist
- [x] 32.2-02-PLAN.md — Admin SPA consent route, switch account, account items, openapi and dist
- [ ] 32.2-03-PLAN.md — sm-oauthserver-plugin backend mode: config, migration, store, verifier, consent provider, revocation, My account, connections screen
**Wave 3** *(blocked on Wave 2 completion)*