From 75f45933b8f0a15cc221f3bdb9083084a3a24c23 Mon Sep 17 00:00:00 2001 From: Jakub Zych Date: Sat, 21 Nov 2026 02:31:05 +0100 Subject: [PATCH] docs(phase-32.2): update tracking after wave 4 --- .planning/ROADMAP.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.planning/ROADMAP.md b/.planning/ROADMAP.md index 34f0b453..60c5b9c1 100644 --- a/.planning/ROADMAP.md +++ b/.planning/ROADMAP.md @@ -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)