source-control(babysit-prs): SKILL.md step 9 cross-reference to loop.md §5.3 is imprecise after #504's cadence-mapping table landed

[kyle-sexton]

Lane: work-2 · Category: improvement (docs polish) · Source: claude-review bot finding on PR #652 (#504), 2026-07-20.

Triggering example

SKILL.md step 9 reads: 'Schedule the next wake from the snapshot's recommended_cadence (reference/cadence.md); the static ladder in reference/loop.md §5.3 is the Python-free degrade.'

After #504's fix landed (PR #652), loop.md §5.3 now houses BOTH the engine-backed recommended_cadence→delaySeconds mapping table AND the pre-existing Python-free degrade ladder. Step 9's phrasing still technically works (it correctly points to loop.md §5.3 for the degrade ladder) but doesn't surface that §5.3 is also where the engine-backed mapping now lives — a reader following step 9 might go to cadence.md first looking for the seconds mapping, when it's actually in loop.md §5.3.

Observed vs expected

Observed: step 9's cross-reference phrasing predates #504's change and doesn't reflect that both the mapping table and the degrade ladder now live in the same section.

Expected (reviewer's suggested wording): 'Schedule the next wake using the mapping table in loop.md §5.3 (engine-backed) or the static degrade ladder in the same section (Python-free).'

Category

improvement — cosmetic/clarity only, not a functional bug (the existing cross-reference is still navigable, per the reviewer's own assessment). Deferred out of PR #652 to keep that PR scoped to the mapping-table fix itself.

Related

Found during the post-green review pass on PR #652 (closes #504).

Work-class: C2 (mechanical) — attended triage 2026-07-23, operator-ratified. 🤖

[kyle-sexton]

This was generated by AI during triage.

Triage (T1 — routed ready)

Cosmetic cross-reference wording fix, zero design decision — reviewer's suggested replacement wording for SKILL.md step 9 is already given verbatim in the issue body: "Schedule the next wake using the mapping table in loop.md §5.3 (engine-backed) or the static degrade ladder in the same section (Python-free)."

[kyle-sexton]

Folded into the rolling paper-cut sweep #657 per the v11 intake throttle (paper-cuts batch as sweep lines, consequence findings stay standalone). Content preserved as a checklist line there; this closure is the fold, not a wontfix. [Control tower, triage-audit execution 2026-07-20; operator veto window]

[kyle-sexton]

Flagging (babysit lane, 2026-07-20): this issue's own body says "After #504's fix landed (PR #652)..." but PR #652 has not merged — it's still OPEN, and as of this comment its mergeability just flipped from computing to a real CONFLICTING state against main. This issue was closed COMPLETED on the assumption that #652 had already landed, which wasn't true at close time.

Not reopening this myself (outside this lane's action set — issue state changes are a human/authoring-lane call), just flagging the mismatch for whoever's tracking it: if loop.md §5.3 still needs the cross-reference fix this issue described, it isn't done yet until #652 actually merges.

[kyle-sexton]

This was generated by AI during triage.

Reactivated (triage lane — #657 sweep-conversion, rule 8h). This issue was administratively FOLDED-closed into #657 under the v11 intake throttle — not fixed: it still carries status: ready, and no PR closed it (closedByPullRequestsReferences: []). Restoring it to the ready frontier as its own dispatchable work-item, rather than filing a duplicate (its fully-specified content already lives here). Its #657 fold-line is checked off with a pointer back to this issue.