iter gc.1: journal — append cadence-flow notes for skillsystem postmortem

docs/journals/2026-05-11-iter-gc.1.md

@@ -62,6 +62,33 @@ this iter.
   plan-template miscount, not an implementation bug. Surfaced as a
   cadence-flow signal to the Boss in the end-report.
 
+## Cadence-flow notes (for skillsystem postmortem)
+
+Two observations from the orchestrator's end-report, surfaced here
+for the Boss's future skillsystem-postmortem entry — NOT in scope
+for gc.1 itself:
+
+1. **Planner verify-step counts derived from offsets become stale
+   at plan-freeze time.** The §Step 2.4 and §F.2 miscount above is
+   one instance. The orchestrator suggested two fixes: (a) planner
+   re-runs grep counts against the current file state at
+   plan-freeze time, or (b) planner expresses such counts as
+   `≥ N` inequalities rather than exact-match equalities. The
+   latter is cheaper and survives subsequent edits to the same
+   file.
+
+2. **Markdown-only verbatim-content iters bottom out cleanly in the
+   spec-check + quality-check phases.** Zero review-loop fixups
+   landed this iter; all five tasks went DONE on first pass through
+   both phases. The spec-check phase effectively reduced to "is
+   the verbatim text from the plan in the diff?" and the
+   quality-check phase had little to flag beyond whitespace
+   hygiene. Both passes still ran (discipline preserved), but the
+   value they added was low. This is expected for verbatim-content
+   tasks and not a concern about the discipline itself — captured
+   here so it is not misread, in retrospect, as evidence that the
+   phases are too lenient.
+
 ## Known debt
 
 None.