Weekly cadence doc says Monday, deployment fires Sunday (and a plan-file gate contradiction)

[schmug]

Task

Two committed documents disagree with what actually runs, and one of the two disagreements changes behaviour. Fix both so a reader following the docs gets the deployed reality. After this, the weekly cadence in SKILL.md matches the deployed routine, and the tts-engine plan does not instruct a re-runner into a gate its own step refuses.

Context

Filed by concern triage from https://github.com/schmug/agent-notes/issues/25 and https://github.com/schmug/agent-notes/issues/23 (sessions 679e4e4e-67f8-40c3-b7ad-d7d72b2f5e3b and 19a020a7-e57a-4d6f-a1b0-ceb6bbaae4f4).

(1) The weekly cadence — causal, not cosmetic. skills/frontier-commits/SKILL.md:326 documents "Schedule Mondays 07:30 local (after the 06:15 snapshot)". The deployed frontier-commits-weekly scheduled task runs 0 9 * * 0 — Sunday 09:03. A Sunday fire always lands on the last day of its own ISO week, so every run collides with any episode hand-shipped earlier that week, whereas a Monday fire opens a fresh one. The 2026-09-06 run's already-shipped-this-week skip is a symptom of that drift, not only a clean test of the guard from #197.

Worth checking as part of this: six stories detected on 2026-09-06 (anthropics/fermats-last-theorem, openai/PrimeGaps186, openai/LongGapsBetweenPrimes, releases claude-code v2.1.263 and codex rust-v0.153.4, and anthropic-tokenizer-typescript ARCHIVED) went unmarked and now wait for the next run. They were called "not lost" on the strength of reading _appeared and the mention-once key scheme, never on a run proving they re-surface. Confirm they actually do.

(2) The tts-engine plan. docs/superpowers/plans/2026-09-04-tts-engine-registry.md on main sets its step-0 Surface Tension rehearsal manifest to the Ryan preset, which the plan's own Task 2 gate refuses on breeze (no presets). The executing session worked around it with voice=house and #206 landed, but the plan file was never corrected — #203 body was updated instead. A reader re-running Task 8 on breeze hits the refusal.

Reproduction

1. grep -n "07:30" skills/frontier-commits/SKILL.md → line 326, "Mondays 07:30 local".
2. Inspect the deployed frontier-commits-weekly scheduled task → 0 9 * * 0 (Sunday 09:03).
3. Read docs/superpowers/plans/2026-09-04-tts-engine-registry.md step 0 against its own Task 2 gate.

Expected: docs describe what runs.
Actual: the cadence is off by a day in the direction that causes collisions, and the plan's step 0 contradicts its Task 2.

Pointers

• skills/frontier-commits/SKILL.md:326 — the documented cadence.
• The deployed routine: ~/.claude/scheduled-tasks/frontier-commits-weekly/SKILL.md and its schedule registration.
• docs/superpowers/plans/2026-09-04-tts-engine-registry.md — step 0's rehearsal manifest and the Task 2 gate.
• The same-week guard this interacts with: Guard the weekly run against a same-ISO-week double ship #197
• skills/frontier-commits/fc_stories.py — _appeared and the mention-once key scheme, for the six-stories check.

Constraints

• Decide which one is right before editing. The doc and the deployment disagree; changing the doc to match a Sunday fire keeps the collision. The argument in the concern is that Monday is correct because it opens a fresh ISO week — if you agree, the deployment moves and the doc stays.
• Changing a deployed scheduled task is a live-behaviour change; state what you changed and why in the PR.
• The plan file is history-adjacent — correct step 0 in place, and note the correction rather than silently rewriting the plan's narrative.

Acceptance criteria

• skills/frontier-commits/SKILL.md:326 and the deployed frontier-commits-weekly schedule agree, with the chosen day justified in the PR.
• The chosen cadence opens a fresh ISO week rather than closing one, or the reason it doesn't matter is written down.
• docs/superpowers/plans/2026-09-04-tts-engine-registry.md step 0 no longer selects a preset its own Task 2 gate refuses on breeze.
• The six unmarked 2026-09-06 stories are confirmed to have surfaced in the following run (or the reason they didn't is filed).

Out of scope

The fc_snapshot.py partial-sweep reporting (filed separately), and the Breeze 500-char take ceiling.