docs(phase-32.2): update tracking after wave 4

This commit is contained in:
Jakub Zych
2026-11-21 02:31:05 +01:00
parent 7a39fda957
commit 75f45933b8

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:** 4/5 plans executed
**Plans:** 5/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.
@@ -1733,7 +1733,7 @@ Plans:
- [x] 32.2-04-PLAN.md — sm-grzybyfunkcjonalne-app wiring, local MCP OAuth proof, DEPLOY.md
**Wave 4** *(blocked on Wave 3 completion)*
- [ ] 32.2-05-PLAN.md — Unit tests, regressions and release checkpoint
- [x] 32.2-05-PLAN.md — Unit tests, regressions and release checkpoint
### Phase 32.1: MCP OAuth for plugin apps: declared scopes, MCP subject on context, per-client MCP consent (INSERTED)