docs: add phase 9 stale-verification debug note, phase dir placeholders and 11.1 state

.planning/debug/phase9-verification-stale-loop.md

@@ -0,0 +1,53 @@
+---
+status: diagnosed
+trigger: "I already did that execute 9 like 3 times and gsd-progress still talks about it, wtf"
+created: 2026-09-28T00:00:00+02:00
+updated: 2026-09-28T14:31:00+02:00
+---
+
+## Current Focus
+
+hypothesis: Confirmed — Phase 10.2 relocated the Phase 9 implementation packages under modules/, while 09-VERIFICATION.md still declares the old locations as covered inputs.
+test: Compared every declared path with the checkout and traced representative missing entries through git rename history.
+expecting: The missing paths were renamed in the Phase 10.2 commit, proving an invalidated Phase 9 report rather than a timestamp/digest instability.
+next_action: Diagnose-only complete; regenerate 09-VERIFICATION.md through the stale re-verification path so its covered_files list names current modules/ paths.
+bug_class: bohrbug
+reasoning_checkpoint: null
+tdd_checkpoint: null
+
+## Symptoms
+
+expected: Running execute-phase for Phase 9 refreshes its canonical verification report so gsd-progress stops routing back to Phase 9.
+actual: Phase 9 remains marked stale after execute-phase has been run approximately three times.
+errors: No separate error message; gsd-progress repeatedly reports stale verification and recommends Phase 9 again.
+reproduction: Run execute-phase for Phase 9, then run gsd-progress and observe Phase 9 is still stale.
+started: Repeated in the current 2026-09-28 workflow; whether an earlier run ever remained stable is unknown.
+
+## Eliminated
+
+## Evidence
+
+- timestamp: 2026-09-28T14:20:00+02:00
+  checked: Phase 9 verification report, current git HEAD, and working-tree status
+  found: 09-VERIFICATION.md was written at 00:10Z with covered_digest v2:sha256:510b91f54dea0918569d267a7aba22fcf879ad69899aa6e2033677a68a84de41, while current HEAD is cc584e9 at 14:13+02. The report covers many framework source/test files as well as Phase 9 plans and summaries. The worktree has only planning/session state and unrelated untracked files; no covered source files are presently modified.
+  implication: The stale state is deterministic and likely arises from a mismatch between the report's recorded snapshot and its currently computed snapshot, not from an uncommitted covered-file edit.
+- timestamp: 2026-09-28T14:23:00+02:00
+  checked: gsd-core verification.status implementation and Phase 9 status
+  found: verification.status returns stale for the actual phase directory. Reports with covered_files plus covered_digest use only a content digest; computeCoveredDigest returns null if any declared path is absent, unreadable, non-regular, or escapes projectRoot, and readVerificationStatus treats that as stale. The fingerprint CLI returned its explicit failure message: a covered file is missing, unreadable, or escapes the project root.
+  implication: This is not a timestamp loop. A malformed or no-longer-valid declared covered path is a stronger, directly observed root-cause candidate.
+- timestamp: 2026-09-28T14:27:00+02:00
+  checked: Every Phase 9 covered_files entry against the current checkout
+  found: 42 of 71 declared paths are not files, including bouncer/*.go, cabana/*.go, lagoon/*.go, pact/capabilities.go, phrasebook/translator.go, and surf/router.go. The Phase 9 report's covered fingerprint cannot be computed as a result. Every currently present Phase 9 PLAN and SUMMARY is declared, so the failure is not an omitted phase artifact.
+  implication: Any re-run that leaves this declaration unchanged is guaranteed to be stale. The defect is a now-invalid path list, not the report's time or a newly added Phase 9 artifact.
+- timestamp: 2026-09-28T14:31:00+02:00
+  checked: Git rename history and the execute-phase stale-reverification workflow
+  found: Commit 5e50b16 at 2026-09-28T02:21:02+02:00, refactor(10.2-01): nest framework packages under modules, renamed the missing Phase 9 paths (for example cabana/auth.go → modules/cabana/auth.go and bouncer/audience_test.go → modules/bouncer/audience_test.go). The report remains from before that refactor: its mtime is 00:02+02 and its last committed change is 7ac75b9 at 00:03+02. The execute-phase stale route is explicitly supposed to re-dispatch the verifier and regenerate the digest.
+  implication: Phase 10.2 invalidated Phase 9's content snapshot. Until a verifier run writes a replacement report with the modules/ paths, verification.status deterministically returns stale; a retry that does not alter this report has not completed that regeneration step.
+
+## Resolution
+
+root_cause: Commit 5e50b16 (Phase 10.2) moved 42 Phase 9-covered framework files from top-level package paths to modules/ paths, but 09-VERIFICATION.md still fingerprints the removed top-level paths. computeCoveredDigest fails closed on the first missing covered input, so verification.status always returns stale. The report was never regenerated after that refactor (it remains at its 00:02/00:03 timestamp).
+fix: Re-run/recover the Phase 9 stale re-verification until it actually rewrites 09-VERIFICATION.md with a fresh covered_files list using modules/... paths and a matching v2 digest; then rerun verification.status.
+verification: Reproduced status=stale against the real Phase 9 directory; Phase 9 fingerprint command fails explicitly; enumerated 42 missing inputs; git rename history maps representative missing inputs to modules/... in 5e50b16; report timestamp predates that commit.
+oracle_type: 
+files_changed: []

.planning/phases/10.1-runtime-admin-extension-point/.gitkeep

@@ -0,0 +1 @@
+

.planning/phases/10.2-nest-framework-packages-under-modules-and-write-run-docs/.gitkeep

@@ -0,0 +1 @@
+

.planning/state.json

@@ -61,7 +61,7 @@
     {
       "number": "11.1",
       "name": "SummerCMS documentation for humans and AI agents",
-      "status": "pending"
+      "status": "in_progress"
     },
     {
       "number": "11.2",
@@ -92,7 +92,7 @@
   "next": {
     "command": "/gsd:progress --next",
     "label": "Advance to the next step (verify)",
-    "reason": "Phase 11 of 19 · ready to verify"
+    "reason": "Phase 11.1 of 19 · ready to verify"
   },
-  "updated_at": "2026-09-30T19:09:22.774Z"
+  "updated_at": "2026-10-01T06:58:29.408Z"
 }