Turn 1 of the docs design wrapped three good layouts around invented
content — a bench.toml, a brew-installed CLI, "lanes", a handoff rule
engine, port 7331, PAS-411 cards. None of it exists. Turn 2 holds all
three layouts and replaces every word, label and code block with the
product AGENTS.md, README.md and manager/core/.env.example describe.
1b Dockside — hero terminal is the real install one-liner, the real
first-run questions and the real board.py startup lines on 26071.
The six doors are install, the five stages, agents on the board,
PRs & review, team mode, the three-layer law.
1a Harbour — the article is "Claiming a card": what each move writes
to **Assignee:**, the two local/.env keys that turn it on, and the
board: <n> → <stage> (<name>) commit it makes.
1c Logbook — the CLI reference is now a settings reference, with
BOARD_SYNC as the shown key and the board's own activity log (real
event strings from sync.py, agents.py and github.py) in the pinned
console.
The design project's write path needs an interactive permission grant,
which a headless run cannot answer, so the finished file lands here as
reference/bench-docs-design-turn2.dc.html for a human to upload as
"Bench Docs.dc.html". The card scoped itself to the design project with
no repo files changed; this one file is the deviation, and a git rm
undoes it once the upload has happened.
Everything core from cicero-pas's .task-manager, with instance data
reduced to skeleton: empty stage directories, the task template, empty
local/ scaffolding, and a README covering install (clone into
.task-manager/, vendored on purpose) and update (update.sh replaces core
wholesale; local/ and tasks/ survive).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
istos