Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1The kickoff-table plan has three finished PRs left, and the merge rung is yours. (1) propflowai #6915 — makes the Phases-card drift guard real: it currently hardcodes its own copy of phase_table.PHASES, so it reds if the CARD drifts but stays green forever if phase_table.py itself moves; also replaces a hand-written 'we ran a control' comment with an executable one. Test-and-fixture only, CI green, draft + hold-for-review. (2) agent-smith #370 — the twin that cross-reads #6915's pin and asserts it equals phase_table.PHASES/ROW_STATES; perturbing phase_table.py alone now reds it. Test-only, lint-test pass, draft. MUST merge after #6915 or it has no file to read. (3) agent-smith #371 — the step-3 cutover: the kickoff post becomes one line + one /agents link and the Slack phase-table render path is DELETED. Patch-gated (task-watch-pointer-only-v1) and proven against a REAL pre-cutover Temporal history: with the gate removed that specimen strands with [TMPRL1100] at the recorded smith_slack_send, so the gate is doing work. lint-test + adversarial pass, CLEAN, auto-merge off. Three caveats you should have: #371's only bot review (19:06Z) is OLDER than its current head (19:18Z), so nobody has reviewed what you would merge; the cutover ADDS one thing rather than only deleting, because the old table footer was the only Slack surface carrying 'Blocked on you'; and only ONE task-watch execution remains in Temporal retention, so there is no independent second specimen.
In plain terms. Smith's kickoff post in Slack can now shrink to one line plus a link, with the big phase table living on the agents page instead of being pasted into the thread. Three finished changes do that, and also repair a drift guard that had quietly stopped being able to notice when the phase list changes. Merging them means kickoffs get short and the table lives in one place; leaving them means Smith keeps pasting the table into Slack and the guard stays half-blind.
Fable recommends: Merge all three in order: #6915, then #370, then #371 (cutover last) All three are the remainder of the plan you already approved, and the cutover carries the strongest replay evidence this repo has produced: a real pre-change history that STRANDS when the gate is removed, which is exactly what #274 lacked when it wedged every live OperatorTaskWorkflow. The drift pair is test-only and closes a guard that cannot currently fail in the direction it checks. Order is load-bearing: #6915 before #370, and the cutover last because it deletes the old surface only after the replacement is live on /agents. If the stale review on #371 bothers you, option 2 splits it off cleanly. Tried first, unsuccessfully: Two fable-decide rounds were run and BOTH resolved rather than deferring, so neither is admissible as raise evidence and this field carries them instead. Receipt f58bd333b: Gera's earlier 'merge all three, in order' answer is EXHAUSTED by the three PRs he named — a broad yes does not extend to specific diffs no human has read. Receipt fab35e44e: hold #6915/#370 until a human reads them — it read both diffs, called them good and low-risk, and said quality was never the question, authority was. Both rounds held under reversal. Fable did not give up; it concluded twice that this rung is yours, which is why this block exists rather than a self-merge.