docs(08): finalize oauth plans after final checker pass

.planning/STATE.md

@@ -2,14 +2,14 @@
 gsd_state_version: 1.0
 milestone: v1.0
 milestone_name: milestone
-status: planning
+status: executing
 stopped_at: Phase 8 UI-SPEC approved
-last_updated: "2026-09-23T10:52:49.807Z"
-last_activity: 2026-09-23
+last_updated: "2026-09-23T16:42:33.535Z"
+last_activity: 2026-09-23 -- Phase 08 planning complete
 progress:
   total_phases: 15
   completed_phases: 7
-  total_plans: 45
+  total_plans: 55
   completed_plans: 45
   percent: 47
 ---
@@ -27,8 +27,8 @@ See: .planning/PROJECT.md (updated 2026-09-16)
 
 Phase: 08
 Plan: Not started
-Status: Ready to plan
-Last activity: 2026-09-23
+Status: Ready to execute
+Last activity: 2026-09-23 -- Phase 08 planning complete
 
 Progress: [██████████] 100%
 
@@ -214,7 +214,7 @@ None yet.
 
 ### Blockers/Concerns
 
-- Phase 8 (OAuth2.1) needs a pre-planning check of `wavepath.org/plugins/golem15/oauthserver` to resolve whether `ClientCredentialsStorage`/`TokenExchangeStorage` are needed — flagged in research/SUMMARY.md Gaps, unresolved.
+- ~~Phase 8 (OAuth2.1) pre-planning check of the PHP OAuth server for `ClientCredentialsStorage`/`TokenExchangeStorage`~~ — resolved 2026-09-23 during Phase 8 discussion/research: the PHP server is hand-rolled and supports only `authorization_code`/`refresh_token`, so neither interface is needed (see 08-CONTEXT.md, 08-RESEARCH.md).
 - Phase 9 (admin schema pipeline / relation manager) is the least-precedented design surface in the research — plan with `--research-phase`.
 - Phase 11 (River dual-driver split) is documented but unverified against a real build — plan with `--research-phase` and budget a timed-latency test.