tldr-experts 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -1,5 +1,999 @@
 # Changelog
 
+## 0.3.1 — 2026-08-31
+
+**Unattended mode.** Twelve of the entries below are one feature: a run a **host session**
+drives end to end, and a gate an **agent** may close over a check it wrote down. `attended_by: host`
+stops the framework spawning on a run at all; `economy: host-tokens` stops a ceiling that is not
+dollars from buying a metered spawn; the dispatch-notes slot gives the host the one place to add
+what the bundle cannot know; `next --prepare/--commit --review` makes the Build reviewer the
+second delegable role, so one review is done once; the `fixlist` verdict gives a review that
+SIGNS somewhere to put its findings, for one bounded round that costs no attempt;
+`gates_policy: agent` closes a gate on the seven auto conditions **plus** a boundary check, a
+budget-event check and a validated evidence note, and falls through to a person on a question, a
+moved ceiling, work nobody scoped, or its own refusal — rendered as a decision card rather than
+a dashboard. Three smaller pieces stop a turn being wasted before it starts: `preconditions:`
+on a stage, a story branch fast-forwarded onto its epic before dispatch, and a budget brake that
+counts the work that is LEFT rather than the price the stage was written at. Two measurements
+from 2026-08-30 are the whole argument: **$9.95** of spawns that died on caps a Plan agent had
+priced in host tokens, and a framework reviewer that spawned beside a host already reading the
+same diff. New chapter: `docs/guide/10-unattended-mode.md`. Every part is additive — a run with
+none of these behaves byte-identically to the release before them.
+
+### Added
+
+- **A story branch that has fallen behind its epic is fast-forwarded before a developer is
+  dispatched onto it.** Measured 2026-08-30 on `260830-tenancy-identity-customers`: S3 was
+  reopened, `story reopen` keeps its branch by design, and that branch still sat at the S1-era
+  epic tip while the epic had since gained S2 and S5. S3's handlers needed S2's contract, so a
+  dispatch on that base would not have compiled. The host fast-forwarded by hand before
+  dispatching. That is the one case this automates.
+
+  ```
+  · S3: fast-forwarded `story/260830-tenancy/S3` to `epic/tenancy` — 2 commit(s), b5a2474 → ae9c8dd
+  ```
+  - **Where.** Inside `openStory`, which is the one place a story worktree is opened, and only
+    on the two openings that are about to put a DEVELOPER on the branch: the headless pipeline
+    and `tldrx next --prepare`. The review openings (`--prepare --review`, `--commit --review`,
+    an errored review re-run) and `--commit` measure nothing and move nothing — a fast-forward
+    there would drag other stories' commits onto a branch whose whole meaning is "what this
+    story built", for a base nobody is about to compile against.
+  - **The requeue case, which fires far more often than the reopen one.** A `changes` verdict
+    merges the story into its epic and then hands it a second attempt; before this, attempt 2
+    was dispatched onto attempt 1's base. It now starts on the current epic tip.
+  - **A diverged branch is warned about, never resolved.** Commits on both sides is the second
+    live case — a dead spawn's partial commit on a stale base, where no fast-forward existed
+    and the host preserved the partial on a backup branch and re-pointed the story branch by
+    hand. Which of two histories survives is a decision, so the framework does not make it: it
+    names both counts, both shas, and the two options, changes nothing, and lets the dispatch
+    proceed on the old base — saying, in as many words, which base that is.
+  - **A dirty worktree is left alone**, whatever the topology says. It is the operator's.
+  - **Never a rebase.** Rewriting a branch a developer has already committed to is the class of
+    move the run-id-in-branch-name fix (2026-08-29 audit §B) exists to prevent. The only write
+    is `git merge --ff-only`, which refuses rather than inventing a merge commit. Measured
+    2026-08-31 against a real repository, which is what the design asked to verify before
+    building: blocked by a file in the way it exits non-zero and leaves HEAD and the file
+    exactly as they were — atomic-or-nothing, so a failed fast-forward needs no repair, only a
+    line saying it did not happen.
+  - **`story.base_fastforwarded`** joins the closed §2.9 event set — the only event in it that
+    records tldrx moving a ref. It carries `story`, `repo`, `branch`, `base`, `from`, `to` and
+    `commits`, `tldrx replay` narrates it, and it is appended ONLY when the ref actually moved:
+    a divergent or dirty branch produces a warning and no event, because nothing happened.
+  - **An up-to-date branch is silent** and emits nothing, so a run with nothing to say about
+    its bases is what it was before.
+  - `tldrx story reopen` is unchanged: it still runs no git command, spends nothing and touches
+    no branch. The detection belongs where a worktree is being opened anyway and where the
+    operator is about to dispatch.
+
+- **Decision cards — the shape an interrupt takes when a run stops for a person.** Measured
+  2026-08-30: an unattended run stopped on two owner questions, and the host did NOT show the
+  owner the dashboard or the `2 open question(s) in 01-what/questions.md` line the framework
+  actually prints. It hand-composed, in chat, the question, the options and a recommendation
+  with one line of why. The owner answered both in seconds. The card is what made the
+  interrupt cheap; hand-composing it is what the framework was making the host pay for.
+
+  ```
+  DECISION — 260830-tenancy · 01-what/what
+  Q2 · Should an existing customer's tenant be inferred or asked for?
+    Why asked: no tenant column on the customer aggregate [src: absent:api:src/.../Customer.cs]
+    A) infer from the invoice email domain — no new UI, wrong for resellers
+    B) ask once at first login — one screen, correct for everyone
+    C) other — write it below
+  Recommends B — one screen, correct for everyone [src: 01-what/handoff.md:22]
+    tldrx answer Q2 "…" --run 260830-tenancy
+  ```
+  - **Pure rendering of things that already exist.** The question, its `Why asked:` line and
+    its lettered options come out of `questions.md` through the **§2.7 parser** — the
+    questions grammar is not touched, and a block the parser cannot read does not appear on a
+    card any more than it appears anywhere else. The `Recommends` line comes out of the
+    evidence note's optional `recommend: [{q, option, why, src}]` array, which the evidence
+    grammar already validates.
+  - **A question with no recommendation gets no line.** Never a manufactured one and never a
+    placeholder: the whole value of that line is that an agent stood behind it with a
+    citation.
+  - **One renderer, three surfaces.** `tldrx run auto --gate-agent` at the stop;
+    `tldrx next`'s agent-gate fallthrough, where the card is **appended** to the fallthrough
+    list so nothing that reads those lines today loses a byte; and `tldrx status`, where a run
+    waiting on answers now shows the card rather than `open questions: Q1, Q2`.
+  - **A card per fallthrough kind.** Budget and boundary get their own card over the same
+    frame — the measured fact, then the commands (`widen the scope …` / `approve` / `reject`
+    for a boundary; the phase's two numbers plus `budget show` for a budget event) — and every
+    other reason an agent gate fell through is carried as one gate card naming its reasons.
+  - **`--gate-agent` is rendering only.** It does not upgrade any stage to
+    `gates_policy: agent`: a run keeps the policy it was opened with, and a flag that could
+    raise one at stop time would make the frozen policy decorative. On an
+    `attended_by: host` run it changes nothing — `run auto` is still refused at exit `1`
+    before the event log is opened, and nothing spawns.
+  - **Nothing else moves.** `tldrx answer`, `questions.md`, the live dashboard and every exit
+    code are unchanged, and `run auto` without the flag prints exactly the block it always did.
+- **The budget brake counts the work that is LEFT, not the price the stage was written at.**
+  Measured 2026-08-31 on `260830-tenancy-identity-customers`: four of seven stories done, one
+  mid-attempt-2, two blocked, and the entire remaining metered cost a developer share and a
+  reviewer floor — **$2.50**. The brake compared the phase's remaining dollars against
+  `stage.budget_usd`, **$18.00**, a number written before a single story ran and never
+  revised. It refused the stage twice and the host ran `budget raise --take-from` twice, for
+  money nothing was going to spend.
+
+  For a Build stage with a plan on disk, `tldrx next`'s refusal, the `budget-gate` hook and
+  `tldrx budget show`'s `est.` column now all use one figure computed by one function: `Σ`
+  over the unsettled stories of the caps the executor would actually hand out — the
+  `03-plan/budget.yml` price through the same scale/share arithmetic, the developer and
+  reviewer shares, the `$1.00` reviewer floor, and the attempts each story has left.
+  - **The refusal shows its arithmetic**: `remaining work: S4 dev $1.50 + reviewer $1.00 =
+    $2.50`, under a line naming how many stories are done and what the stage's static
+    estimate was. A number an operator cannot take apart is one they cannot argue with, and
+    `$18.00` cited nothing.
+  - **`blocked` costs $0.00**, and the blocked ids are named rather than quietly dropped: the
+    executor dispatches a blocked story only after `tldrx story reopen`, which is a human
+    decision and which legitimately raises the figure again.
+  - **A story at `review` has already paid the developer turn under review.** Only a `changes`
+    verdict buys another one.
+  - **Under `economy: host-tokens` the developer turns are $0.00** — the host session pays for
+    them — while the reviewer floors stay, because outside attended mode `reviewAndSettle`
+    still spawns a metered reviewer and that floor is real money.
+  - **It can only NARROW.** The figure is capped at `stage.budget_usd`, so this brake can
+    never refuse more often than it did before; the reviewer floor can otherwise lift a naive
+    sum past the ceiling. Asserted in both directions, across a spread of plan shapes, because
+    a brake that loosened by accident is the failure to fear here.
+  - **`budget.blocked` gains `estimate_basis: plan|static`** and, on the plan basis,
+    `static_estimate_usd`, `stories_done` and `stories_total`.
+  - **With no plan on disk, and outside Build, every path is byte-identical**, wording
+    included: the estimate is `budget_usd` and the message still reads `the stage estimate
+    is $X`.
+
+- **`preconditions:` on a stage — the check that runs before the money does.** A stage may
+  declare operational facts that must hold before it is worth dispatching at all:
+
+  ```yaml
+  preconditions:
+    - {id: docker, repo: api, command: "docker compose ps", expect_exit: 0}
+  ```
+
+  The grounding is measured, 2026-08-30: before dispatching a Build story the host checked
+  the Docker daemon and the .NET SDK **by hand**, because a story has two attempts, an agent
+  cannot debug its way out of a daemon that is down, and the whole turn would have been spent
+  proving it. That check took about a second and protected an attempt worth dollars.
+  - **Same allowlist rule as a `cmd` check and a story's `` ```dod `` block — and now literally the
+    same function.** Only a command byte-equal to one `.tldrx/workspace.yml` declares runs,
+    argv-split, never through a shell. The comparison and both refusal sentences moved to
+    `schemas/commandAllowlist.ts`, so the three sites can no longer drift into three readings
+    of one rule. It is enforced **at load**: a stage naming an undeclared command never
+    becomes a runnable stage, so `tldrx run new` over it refuses too.
+  - **Red ⇒ refused, exit `2`, having spent nothing.** The id and the command's own exit code
+    are named, the stage is left exactly where it was (`ready`), no bundle is written and
+    nothing is spawned. The list stops at the first red one.
+  - **`--prepare` runs them no less than headless** — a bundle written for a host whose Docker
+    is down is the same wasted attempt as a spawn into one. `--commit` never runs them: it
+    settles a turn that already happened.
+  - **Every run is on the record**: one `check.passed` / `check.failed` event with
+    `kind: precondition`, carrying the repo, the command, the exit code and the duration, and
+    one operator line — `· precondition: docker compose ps → exit 0 (1.2s)`.
+  - **A stage that declares none is byte-identical**: no event, no line, no shipped stage file
+    changed. `[assumption]` — per stage, not per story; a per-story precondition is a real
+    want and is deliberately not designed here.
+- **The `fixlist` verdict, its artifact and its router — the review that SIGNS and still has
+  findings.** Measured 2026-08-31, driving `260830-tenancy-identity-customers` by hand: the
+  reviewer signed story S5 — every acceptance criterion met, zero scope violations — and in the
+  same breath named three real correctness/security defects the criteria never covered (a
+  concurrent double-confirm minting two sessions, a non-atomic confirm, a false security comment
+  beside a non-constant-time compare). S1 and S3 went the same way that night. Binary
+  `approve`/`changes` has nowhere to put those: `approve` throws them away, `changes` spends the
+  story's one requeue on a diff nobody faulted. So all three loops were run in chat — number the
+  findings, decide fix-now vs defer-with-log, route them to the author, re-verify — and none of
+  it reached a file. This is that loop, as a verdict and an artifact.
+  - **`fixlist` settles the story at `review` and spends NO attempt.** The requeue counter counts
+    verdicts that FAULTED the diff, and a signature is not one. `04-build/fixlist/<story>-<n>.md`
+    is written beside it by the EXECUTOR, never by the reviewer — which holds no write tool, the
+    same reason the review log is written there. Numbered `## <n> · <finding> [<severity>]`
+    sections, each with `Where:`, `Disposition:` and `Resolved:`.
+  - **A disposition ROUTES a finding; `Resolved:` CLOSES it.** Two questions, two fields, because
+    one field cannot answer the first once the second is true. `fix-now` · `defer-with-log` ·
+    `refuted` · `out-of-scope`, and **`refuted` must carry an `[src: …]`** in its `where` or
+    `detail`, through the §2.8 grammar and the §2.8 parser — a reviewer's verdict is a claim like
+    every other, and that night's host disproved one by grepping both sides before acting on it.
+    A fix list with an uncited `refuted` is refused whole and the verdict falls to `changes`.
+  - **The router: `tldrx next --prepare --fixlist <path>`.** The open findings land under
+    `## Fix list` in the DEVELOPER's prompt, numbered, with their `Do NOT` lines verbatim — a
+    bound the reviewer put on a fix is worth as much as the fix. `pending.json` gains
+    `fixlist: {path, round, findings, open}` and `resume_session`, the prior turn's `session_id`,
+    so the host can resume that sub-agent rather than pay to rebuild its context. **The framework
+    resumes nothing itself** — `spawnAgent` has no `--resume` — so the bundle carries the fix list
+    and the merged commit and hands the id back to the party that can act on it. Omit the flag and
+    the latest still-open round is carried by itself, the same courtesy `--prepare` already
+    extends to a story waiting on a review.
+  - **One round per story, and the second is refused out loud.** A free round that could be taken
+    twice is a story that never has to settle. A second `fixlist` is read as `changes` — which
+    costs the attempt the first one did not — the refusal names the round already on disk, and the
+    SECOND reviewer's prompt withdraws the verdict rather than offering one the executor would
+    then refuse. `story reopen` resets the count with every other one in the review ledger.
+  - **A story cannot settle `done` over an open `fix-now`.** An `approve` there settles `blocked`
+    and the reason names the file, the finding's number and its heading, plus the two ways to
+    close it. The check reads the FILE, not the envelope that produced it: the file is the state,
+    and a host closes a finding by writing `Resolved: yes` in it or re-routing its `Disposition:`.
+    That edit is the host's — §B.2's third role — because the author works in a story worktree of
+    another repo and its own prompt forbids writing outside it.
+  - **Fail-closed, unchanged and asserted.** A `verdict: "fixlist"` whose `fixlist[]` is missing,
+    empty or unreadable is `changes`, never a free round and never `approve`. Both economies reach
+    the same code: the host writes the envelope into the review bundle, or a spawned reviewer
+    returns it — `REVIEW_SCHEMA` gained the verdict and the optional array, and `parseReview`
+    narrows both.
+  - `defer-with-log` findings are appended to `retro.md`'s `## Build feedback` as the artifact is
+    written — the existing second writer with its existing verbatim dedup — so a deferred defect
+    reaches the owner through a channel that already exists rather than a new one.
+
+- **`tldrx next --prepare --review` / `--commit --review` — the reviewer is the second
+  delegable role.** A Build story has two sub-agents and only the developer was ever
+  delegable; the reviewer was the FRAMEWORK's spawn in both modes, which on a host-driven
+  run buys a second reading of a diff the host is already reading, and a bill nobody
+  budgeted. Now it rides the same handshake, one directory down:
+  `.agent/<stage>/<story>/review/{prompt.md,pending.json,result.json}` — nested so a
+  reviewer bundle can never be read as a developer one.
+  - **`--prepare --review` writes the bundle and spawns nothing.** `prompt.md` is what a
+    spawned reviewer would have been sent, from the same renderer. `pending.json` carries
+    `role: reviewer`, `result_schema` (the reviewer's `--json-schema` envelope, verbatim,
+    so the host needs no source to know the shape), and a `review:` block with the diff
+    command, the merged commit, the attempt and the **DoD results recovered from
+    `events.jsonl`** — the DoD is not re-run, and the prompt says so.
+  - **`--commit --review` settles it through the existing seam.** The envelope goes through
+    the same `parseReview` with the same fail-closed rule (unreadable ⇒ `changes`, never
+    `approve`) and the same `reviewAndSettle`: `approve` ⇒ `done` with its evidence,
+    `changes` ⇒ one requeue then `blocked`, `MAX_ATTEMPTS` and the requeue counter
+    untouched. A host that never writes `result.json` has produced no verdict and spends
+    no attempt.
+  - **The trail says whose review it was.** No `agent.spawned`; a `task.started` with
+    `role: reviewer, mode: prepare` instead. The `check: review` event carries
+    `source: host` (written only for a host review, so the spawned path's payload is
+    unchanged byte for byte), and the task row is `cost_usd: null, metered: false` unless
+    the envelope declares `cost_usd` / `tokens`.
+  - **On `attended_by: host` the framework never calls `spawnReviewer` at all.** Half B
+    merges the story and hands the review over, so a full attended story cycle emits zero
+    `agent.spawned`. Outside attended mode `--review` is opt-in and the headless reviewer
+    is unchanged.
+
+### Changed
+
+- **`tldrx next --prepare` on a story awaiting review now writes the reviewer bundle
+  instead of spawning a reviewer.** It used to spawn a metered one — which is the single
+  thing `--prepare` exists not to do. Measured 2026-08-31 on the live
+  `260830-tenancy-identity-customers`: story S3's reviewer died at its $1.00 cap, the
+  story parked at `review`, and the `--prepare` that was supposed to rescue it spawned a
+  replacement that a two-minute host timeout then killed mid-read. The story is still
+  parked at `review` afterwards, its attempt still unspent, and the verdict is the host's
+  to write. Headless `tldrx next` still re-runs the review by spawning, unchanged.
+- **`tldrx next`'s `attended_by: host` refusal names `--commit --review`** when the stage
+  is holding a reviewer bundle. It named `--commit`, which is the wrong half: that door
+  reads the DEVELOPER's `result.json` and re-runs a pipeline that has already merged.
+- **`--discard-pending` bins the reviewer bundle too**, alongside the developer bundles it
+  already binned — a stale review `result.json` would otherwise be read by the next
+  `--commit --review` as a verdict on work it never saw.
+
+- **`tldrx init` says what it is doing while it does it** — a live line per step, in the
+  same `--ui scene|compact|plain|off` view family as the agent progress view, on stderr.
+  It used to print NOTHING until it was finished. Measured 2026-08-30 on a five-repo
+  workspace: **36.0 s of total silence** with the default `--provider auto` against
+  **1.3 s** with `--provider static` — so ~97% of the wait is `graphify update` running
+  once per repo inside `buildMap`, and the command looked hung for all of it.
+  - **Ten steps announce themselves**: detecting repos, building the code map, writing
+    `workspace.yml`, planning the interview, seeding experts, reading conventions, writing
+    `process.yml`/`facts.yml`, `init-questions.md`, `init-handoff.md`, and the `.gitignore`
+    + `CLAUDE.md` blocks. `--mcp` adds an eleventh, because it health-checks every server.
+  - **The slow ones name the repo they are inside.** `detecting repos` reports each repo
+    with its stack, confidence and default branch as detection finishes it; the map step
+    reports `<repo> — 6 documents via graphify` per repo. The wait is now legible instead
+    of merely long.
+  - **A terminal gets a spinner, colour and an in-place rewrite; a pipe gets plain lines.**
+    A finished step is printed once and never touched again, so it survives in scrollback
+    after the command exits — a step list is a HISTORY, not a picture of a moment, which is
+    why this is not `ui/driver.ts` with a different renderer. In `plain` a step still open
+    after 5 s says `still <label> — 12 s`, because there is no spinner there to prove the
+    process is alive.
+  - **A schoolhouse** (`core/ui/campus.ts`) is painted above the steps in `scene` mode,
+    drawn in the same hand as the classroom the agent view renders — `init` is the survey
+    that happens before the school opens.
+  - **`--quiet`** turns the live view off and keeps the report. **`--ui <mode>`** works on
+    `init` exactly as it does on `next`, `run auto` and `expert train`, and a bad value is
+    a usage error raised before any work is done.
+- **`core/ui/color.ts`** — the framework's first ANSI palette, resolved per STREAM rather
+  than per process. `tldrx init > report.txt` on a terminal has a piped stdout and a TTY
+  stderr: the live lines are still worth colouring and the file must still be plain text.
+  `palette(false)` is the identity for every ink, so a renderer never branches on colour
+  and the uncoloured path stays byte-for-byte deterministic in a test. `FORCE_COLOR` beats
+  `NO_COLOR` beats `CI` beats the stream.
+
+- **The dispatch-notes slot** — `.agent/<stage>/dispatch-notes.md`, and for a Build story
+  `.agent/<stage>/<story>/dispatch-notes.md`: the one place a HOST can add context to a
+  prompt the framework generated. Measured over one full run of
+  `260830-tenancy-identity-customers`, 2026-08-30, EVERY stage needed host-added context the
+  bundle lacked — a deferred decision at What, non-inlined seed docs and a staleness warning
+  at How, the owner's answers at Plan, "Docker is up" at Build — and the host had exactly two
+  places to put any of it, neither of which is one: `stage.md` is the framework's file,
+  shared by every run of that workflow, and an edit to `prompt.md` is thrown away by the next
+  `--prepare`.
+  - **Rendered under `## Dispatch notes`, between `## Inputs` and `## Previous attempt`.**
+    Behind the expert blocks on purpose: the slot is the most volatile thing in the document
+    — a human writes it between one cycle and the next — and a per-cycle file ahead of the
+    largest stable section would pay the cache-WRITE price on every stage. The same position
+    in the Build developer prompt, directly under `## Inputs`, because that is where the
+    brief ends and `## Investigate` step 1 tells the developer the files above ARE the brief.
+  - **Absent ⇒ nothing changes, byte for byte.** No section, no `dispatch_notes` key in
+    `pending.json`, `0 B` in the context ledger. Asserted by adding the file, re-preparing,
+    removing it, re-preparing, and comparing the two prompts byte for byte.
+  - **Capped at 8 KB, and never free.** The stage's file and the story's file feed ONE slot,
+    spent stage-file-first, so neither can quietly double the budget; the overflow is named
+    in the prompt, on stdout, and in `pending.json`
+    (`dispatch_notes: {bytes, truncated, max_bytes, sources[]}`). The rendered section's
+    bytes are charged to the context ledger and count against `prompt_max_bytes` like
+    everything else — asserted with a ceiling the prompt clears without notes and breaks
+    with them. The byte cut never splits a character in half.
+  - **Context, never configuration.** The framework does not parse it, does not substitute
+    `{{placeholders}}` in it, does not require `[src: …]` tokens on it, and it cannot change
+    a declared input, an output, a check or a cap. The section says all of that to the
+    sub-agent in its own preamble, because a note that reads like an instruction is otherwise
+    indistinguishable from the stage's own rules.
+  - **Survives `--discard-pending`.** The flag bins `pending.json`, `result.json` and
+    `result.raw.json`; the notes are an INPUT to the rendering that is about to be redone,
+    not an output of the one being binned.
+  - **Per-cycle scratch, deliberately.** `.agent/` is gitignored, and that is the whole
+    point: a caveat that must outlive the cycle is a FACT, and `.tldrx/memory/facts.yml` is
+    the durable channel that already reaches every prompt with attribution behind it. Two
+    durable channels for the same thing would make neither authoritative.
+- **`attended_by: host` — a run a host session drives, that the framework never spawns on.**
+  One optional top-level key in `run.yml`, set at creation with `tldrx run new --attended-by host`
+  or flipped later with `tldrx run attend host` / `tldrx run attend --none`. The finding it is
+  built for is one sentence of field notes from 2026-08-30: a bare `tldrx next` on a Build stage
+  runs the WHOLE remaining headless pipeline — every wave, every story, as paid spawns — when the
+  host wanted one re-review. Six of six of those spawns then died on `Reached maximum budget` at
+  caps a Plan agent had authored assuming host-billed sub-agents. $9.95, nothing delivered. The
+  affordance was missing at the RUN level: `--prepare`/`--commit` is a decision per invocation,
+  and nothing on the run could say "this one is being driven by a host session".
+  - **A bare `tldrx next` exits `4` and names the exact command** the stage is waiting for —
+    `--prepare` when it is ready, `--commit` when a bundle is already out. Four, not two: the run
+    is not refusing the work, it is waiting on the host to take a turn, which is the same shape as
+    waiting at a gate and the code `run auto` already stops cleanly on. The refusal is the first
+    thing in `runStage` — ahead of the budget gate, ahead of reading an input, ahead of assembling
+    a prompt — so nothing is billed and nothing is written.
+  - **`--dry-run` is refused with it, and the message says why.** `--dry-run` is `mode: headless`:
+    it spawns a real sub-agent and the turn is billed, and only the non-handoff FILES are reverted
+    afterwards. That is measured, not read — one `agent.spawned`, one `agent.result`, the cost on
+    the ledger. The CLI reference said "Spawns nothing, writes nothing" and a comment in
+    `next.ts` said the same; both were wrong and both are corrected here.
+  - **`tldrx run auto` is refused at exit `1`**, before the event log is opened, so nothing is
+    written. A loop whose whole job is calling `next` headless has nothing to do on a run where
+    `next` headless is a refusal.
+  - **Three layers, because "nothing spawns" is a promise about money.** `runNext` refuses; every
+    executor (`build`, `watch`) refuses a headless context with `refused: true`, so the stage goes
+    back to `ready` rather than being marked failed; and `spawnAgent` itself throws while an
+    attended run is in flight. The third is what makes "no run path can reach a spawn" a property
+    rather than a claim about three `if`s — a fourth call site is always one merge away.
+  - **`tldrx run attend` is deliberately small**: it sets one field, appends one `run.attended`
+    event carrying the new value and the old, and touches no stage, no output, no branch and no
+    money. `--none` REMOVES the key rather than blanking it, because `attended_by: null` is not a
+    legal value. A direction is required and never guessed (exit `1`); setting what is already set
+    appends nothing, since a decision nobody made does not belong in the log; a `done` or
+    `cancelled` run is refused (exit `2`).
+  - **`tldrx run status` prints `attended: host`** and the status line gains an `att` marker
+    beside `auto:N` / `stale:N`, leading them because it is the one that changes what `tldrx next`
+    will do. `--json` gains `attended_by`, appended after `unmetered_tasks` so every existing key
+    keeps its position.
+  - **Additive, and asserted as such.** Absent — which is every run.yml written before this — the
+    framework may spawn and every path is what it was: the two-stage headless fixture's event
+    sequence is asserted against the one captured from `main` at `dae1d07`, event for event, and
+    an ordinary run.yml never mentions the key. A value the reader does not understand is a schema
+    error rather than a silent downgrade to "spawn anyway"; `requireKeys` ignores unknown top-level
+    keys, so an older binary reading a run.yml with `attended_by` still validates it — but it will
+    DROP the key on its next save, since `emitRunYaml` only writes what it knows.
+  - Out of scope on purpose: `tldrx expert train` and `tldrx seed triage --propose` spawn outside a
+    run and are untouched. `attended_by` is a property of a run.
+- **`economy: metered-usd | host-tokens` on `budget.yml`** — a price gets a currency, and a
+  headless spawn under a ceiling that is not money is refused before it spends. Measured
+  2026-08-30 on `260830-tenancy-identity-customers`: the Plan agent priced the run assuming
+  HOST-billed sub-agents — turns the host session pays for, which this process never meters
+  and which are ~free to the run — and the executor then enforced those figures as dollar
+  ceilings on METERED spawns. Six spawns of six died on `Reached maximum budget`, each
+  having spent real money to get there: **$9.95**, for nothing. The money model was a single
+  scalar with no unit on it and no way to say *"this number is not dollars."*
+  - **One optional key, three places**: the run level of `budget.yml`, any `phases[]` entry
+    of it (which overrides the run), and the root of `03-plan/budget.yml`, so a Plan agent
+    can say which economy it was pricing in. Resolution is phase-then-run.
+  - **`tldrx next` refuses a headless spawn on a `host-tokens` phase — exit 2, above prompt
+    assembly, before a byte is written or a cent is spent.** The message names the number,
+    the unit, and both ways out (`tldrx next --prepare`, or re-label and re-price the
+    phase). `--prepare` / `--commit` are untouched: the in-session handshake is exactly
+    where a host-billed turn belongs.
+  - **The two are never converted into one another.** There is no exchange rate here and
+    inventing one would be a guess about a price. The budget-gate hook does not deny on such
+    a phase (there is no dollar ceiling to enforce, and it says so on stderr), the auto
+    gate's money condition reads `n/a (host-tokens economy)` rather than comparing a spend
+    in dollars to a ceiling in tokens, and `tldrx run estimate` prices the stage in TOKENS
+    with no dollar figure at all.
+  - **A `03-plan/budget.yml` priced in `host-tokens` contributes no story caps.** Its
+    numbers are not dollars, so the Build executor falls back to the uniform share it used
+    before plan prices were read at all — and says so on stderr, through the advisory seam
+    that already existed for an unusable plan budget.
+  - **An unknown value is REFUSED, never defaulted to dollars** — a unit nothing here
+    understands is not one it may quietly read as money. An empty `economy:` key, and an
+    absent one, both mean `metered-usd`.
+  - **`tldrx budget raise` no longer erases what it rewrites past.** The label round-trips
+    through the same emitter the raise goes through; a raise that dropped it would turn a
+    token budget back into dollars silently, from the one command an operator reaches for
+    when a ceiling binds.
+  - **Absent label ⇒ byte-identical behaviour**, asserted: an unlabelled `budget.yml` emits
+    no `economy:` line, an unlabelled headless stage still spawns, and every existing budget
+    test passes untouched.
+
+- **`tldrx story reopen <id> --note "<why>"`** — one Build story, given another run of
+  developer attempts, by a person. The third verb of the family that landed 2026-08-30 and
+  the only one a HUMAN signs: the other two stop the machine reading a transport failure
+  as a judgement, and this one is for when the machine read the run correctly and the
+  owner disagrees. Found on `260830-tenancy-identity-customers`, where story S3 sat
+  `blocked` after two GENUINE `changes` verdicts (its developers ran and committed nothing;
+  both reviewers correctly refused an empty diff) — no rescue applied and none should have,
+  but S3 gates wave 3 and the owner had decided it ships. The only reopening verb was
+  `tldrx reject --stage`, which acts on a STAGE, and hand-editing `run.yml` or a story file
+  is forbidden by design.
+  - **The note is required** — a reopen with no reason is not actionable — and one
+    `story.reopened` is appended carrying the actor, the note, the status the story came
+    from, its wave, and how many verdicts the closed run of attempts consumed.
+  - **The story goes back to `todo` and its attempt counter restarts at 1 of 2.** Nothing
+    is erased to make that true: `story.reopened` is a RESET BOUNDARY that
+    `readReviewLedger` reads, so verdicts before it stop counting while every event stays
+    in `events.jsonl` for `replay`, `cost` and `retro`. The full reset is the honest
+    choice precisely because the history survives it — "you get two more turns" is what
+    overruling a block means, and a half-reset would be a number nobody could explain from
+    the record.
+  - **It runs no agent, spends nothing, deletes nothing and refunds nothing.** The story's
+    BRANCH is what carries the last developer's commits forward and it is untouched; the
+    worktree is left exactly as the build left it (kept at `review`, already removed for a
+    `blocked` story) and is reopened from the branch when the next turn needs it.
+  - **It does not make the stage runnable, and does not pretend to.** Sending a stage back
+    is `reject`'s own signed decision, so the output names the command that fits where the
+    Build stage actually is: `tldrx next` when it is ready, `tldrx reject --note` at a
+    pending gate, `tldrx reject --stage` over a signed one.
+  - Refuses with exit 2, saying why: an id the plan does not have (naming the ones it
+    does); a `done` story, because undoing finished work is a decision about the stage and
+    belongs to `reject --stage`; a `todo` story, which is already pending; and a missing
+    `--note`. An unknown run id is still exit 3.
+  - `tldrx replay` narrates it (`story S3 REOPENED by alan — back to \`todo\` from
+    \`blocked\` — "…"`), and the Build stage says so in one line, with the note, when it
+    picks the story up. A reopened story is byte-identical on disk to a never-started one,
+    and a narrative that showed two `changes` verdicts and then a third developer turn with
+    nothing in between would read as the framework losing count.
+- **`--parallel <n>` on `tldrx next` and `tldrx run auto`** — how many stories of ONE
+  build wave run at once. `waves.yml` already puts every dependency in an earlier wave, so
+  a wave's stories are independent by construction. Also settable per scope as
+  `build: {parallel: N}` at the top of a workflow, or per stage as `parallel:` in
+  `stage.yml`; the flag beats the workflow, which beats the stage file. **The default is 1
+  and at 1 the executor takes exactly the path it always did** — verified byte-identical on
+  the event sequence against `main`, not asserted. Above 1 the wave runs in two halves:
+  developer + DoD + commit concurrently, then merge + reviewer serially in the wave's
+  LISTED order, so the epic branch reads the same whatever order the machine finished in.
+  The reviewer half is serial for a reason and not only the merge: a reviewer reads
+  `git diff <epic>...<story>`, whose merge base moves every time another story merges into
+  that epic. A red story does not cancel its siblings, but the wave ends `failed` and the
+  next wave does not start. Ctrl-C/SIGTERM kills every live child, not the first.
+  Budgets are untouched: the stage ceiling was already divided by
+  `stories x attempts x (developer + reviewer)`, so N at once costs what N in a row cost.
+- The live view gives each running story its own column — `S1 reading … · S2 $ dotnet
+  test …` — in the scene, the compact one-liner and `--ui plain`. A lane leaves the line
+  when its sub-agent finishes. With nothing parallel the view is what it always was.
+
+- **`gates_policy: agent` — a gate an agent may close, over a check it wrote down.** The third
+  answer to "who closes a gate", beside `human` (waits) and `auto` (the harness signs when seven
+  measured conditions hold). Measured 2026-08-30 on `260830-tenancy-identity-customers`: the host
+  ran a defined checklist at every gate and typed it into `approve --note "<free text>"`, where
+  nothing validated it, `replay` could not render it, and `run.yml` recorded a person's name for a
+  check a sub-agent had made. The evidence note (above) was the artefact; this is the gate.
+  - **Strictly stronger than an auto gate, never a cheaper one.** Three things, not one: every
+    one of the seven `auto` conditions unchanged and unweakened (including the `boundary`
+    condition landed alongside it), PLUS no budget decision in this stage's window, PLUS an
+    evidence note that parses, sources every bullet, and whose verdict is `sign`.
+  - **The budget requirement is an EVENT, not an arithmetic.** A `budget.raised` or
+    `budget.blocked` in `events.jsonl` at or after the stage's `started_at` falls the gate to a
+    person even when the spend is comfortably under the ceiling. Condition 3 already compares
+    numbers; what it cannot see is that somebody *raised* the ceiling to let this stage through,
+    and a decision made to unblock a stage may not then be signed off by the machine that was
+    blocked. Asserted in both directions on one fixture: the same gate closes without the event
+    and falls through with it, with nothing else changed.
+  - **The same door, so the trail reads the same.** A closing agent gate goes through `approve`:
+    the checks are re-run off disk, `gate.by` records the note's `by:`, one ordinary
+    `gate.approved` is appended, and the cursor advances. `AUTO_GATE_ACTOR` is untouched —
+    `by: auto` still means "the facilitator closed it with no note but its own conditions".
+  - **The note is COPIED into the run tree**, at `<phase>/gate-evidence/<stage>.md`, and that
+    copy is what `gate.evidence.path` points at. `.agent/` is gitignored by spec §1, and a gate
+    whose evidence lives only in a gitignored directory is a gate nobody can audit from a clone.
+    A copy, not a move: the scratch original stays where the agent left it.
+  - **Four fallthroughs are named in their own right**, because a person's next move differs for
+    each: `questions` (a decision nobody has made), `budget-event` (a ceiling somebody moved),
+    `boundary` (work nobody scoped) and `refusal` (the note's verdict is `refuse` or
+    `sign-with-fixlist` — the agent doing its job, not failing at it). Any other failing condition
+    reports as `condition`, a missing or broken note as `evidence`. Each is tested in isolation:
+    a report that fired three at once would not answer "which of these stopped it", which is the
+    first question anybody asks.
+  - **`tldrx approve --as-agent [--evidence <path>]`** is the same decision taken by hand, and it
+    splits the two refusals apart by exit code. **Exit 2** is "this note is broken" — fix the
+    file, nothing was signed. **Exit 4** is "a person decides": the note parsed perfectly and its
+    verdict is not `sign`. **Exit 1** is `--as-agent` on a stage whose policy is not `agent`: a
+    run keeps the policy it was opened with, and a flag that could upgrade one at approve time
+    would make the frozen policy decorative.
+  - **A person may always overrule it.** A plain `tldrx approve` on an agent-gated stage works
+    exactly as it does anywhere else, is recorded as the person, and writes no `evidence` key. An
+    agent gate is one an agent MAY close, never one a person may not.
+  - **`tldrx replay` renders the check**, not just the signature: who signed, how many files they
+    read, how many citations they spot-checked and what those resolved to, how many touched paths
+    they audited and how many were outside the surface, and the path to the note. Rendered from
+    the note's FRONT MATTER and from `run.yml` — never from its prose, which would change the
+    narrative every time somebody rephrased a sentence. A note that has gone missing is SAID to
+    be missing rather than invented, and the counts `run.yml` recorded still stand.
+  - **`--gates` gains a qualified form**: `--gates plan:agent,build:agent`. A bare entry still
+    means `human`, so every invocation anybody has already typed means exactly what it meant. An
+    unknown policy is its own usage error, distinct from an unknown stage.
+  - **Additive, and asserted as such.** No shipped scope uses `agent`; it arrives via
+    `--gates`, or a fork's own workflow file, and never by default. An absent `gates_policy`
+    entry still reads as `human`. A gate with no `evidence` emits no key at all, so every
+    `run.yml` written before this round-trips byte-for-byte through a save — asserted by
+    comparing the emitter's output against the file on disk. The gate mapping never rejected an
+    unknown key (measured against the reader that predates this), so a `run.yml` carrying
+    `gate.evidence` still validates on an older binary; a `gates_policy` naming `agent` there
+    fails loudly instead, which is the right failure — a policy the reader does not understand is
+    not one it may downgrade to "sign it anyway".
+  - **The emitter had to be extended, not worked around.** `emitRunYaml`'s `gate()` wrote exactly
+    five keys as a flow mapping, so a sixth held in memory would have been dropped, silently, by
+    the next save. 47 new tests.
+
+- **The gate evidence note** — `.agent/<stage>/evidence.md`, plus `tldrx gate template` to
+  write the blank form. This is the artefact half of the `agent` gate (design §A): a third
+  answer to "who closes a gate", between `human` (waits) and `auto` (the harness signs when
+  seven measured conditions hold). Measured 2026-08-30 on
+  `260830-tenancy-identity-customers`: the host ran a defined checklist at every gate and
+  typed `approve --note "<evidence>"` by hand, into a free-text field where nothing validated
+  it and `replay` could not render it. There was no value meaning *"an agent checked it,
+  showed its work, and is accountable for the check"*, so there was nowhere to put the check.
+  - **Front matter is the machine half, the body is the human half** — the §2.13 story
+    pattern, reused rather than reinvented. Required keys: `version gate role by at verdict
+    read citations touches diff_vs_stories`; `caveats` and `recommend` are optional and
+    default to `[]`. Four H2 sections in order — `Read` · `Citations checked` ·
+    `Touches audited` · `Verdict` — each with at least one list item.
+  - **Every bullet goes through the EXISTING §2.8 resolver.** Not a second grammar and not a
+    second checker: `srcToken.ts` tokenizes and resolves, and the section rule is
+    `handoff.ts`'s, lifted into a shared `validateSections` that `validateHandoff` now calls
+    too. Two readers of "is this bullet sourced" drift, and the looser one would win the
+    argument at exactly the moment a gate is being signed. A checklist whose own claims are
+    unsourced is what `claim-sources` exists to refuse, and an evidence note is a claim about
+    a claim.
+  - **`unverified` REFUSES here, unlike in a handoff.** A citation nothing could check does
+    not fail a stage (spec §2.8) but it is precisely what stops an AUTO gate closing (spec
+    §5, condition 5). An agent gate is strictly stronger than an auto gate, never a cheaper
+    one, so a `doc:` URL nothing in the workspace names cannot be what a signature rests on.
+  - **Seven refusals, each with its own message and its own `kind`**, so a caller routes on
+    the reason rather than on a string: unreadable or incomplete front matter · a missing
+    section or one holding only prose · a bullet with no `src` token or one that does not
+    resolve · `sampled > of` or `resolved + refuted > sampled` · `sampled: 0` with citations
+    on record · a verdict that is not `sign` · a `gate:` naming a stage other than the one at
+    the cursor. `verdict` is the kind that means "a person decides" rather than "this note is
+    broken" — `sign-with-fixlist` and `refuse` fall to a human by design, and the verdict
+    space is three because a reviewer can meet every acceptance criterion and still have
+    found three real defects nobody wrote a criterion for.
+  - **`tldrx gate template` fills what a tool can COUNT and leaves every judgement blank**:
+    the gate at the cursor, the time, how many citations the §2.8 resolver found across the
+    stage's declared outputs (patterns like `03-plan/stories/<id>.md` included), and how many
+    touched paths the plan declares. The blank form deliberately does not validate — a
+    template that parsed clean out of the box would be a signature nobody had to earn — and
+    it writes no `[src: …]` anywhere, the same rule `questions lint --fix` follows. It spends
+    nothing, spawns nothing, approves nothing and moves no cursor; an evidence note already on
+    disk is left alone (exit `2`) unless `--force` says otherwise.
+  - `validateEvidence(text, srcContext, {gate})` is the function `approve --as-agent` will
+    call before it records anything. Nothing in this change signs a gate, reads a
+    `gates_policy`, or writes into the run tree: the artefact layer lands first, on purpose.
+
+- **Auto-gate condition 7, `boundary` — the stage stayed inside the surface the run declared.**
+  The other six ask whether the artefact is sound and whether the work finished. None of them
+  asks the question a reviewer asks first: *is this the work we scoped?* Measured 2026-08-30
+  on `260830-tenancy-identity-customers` — the host ran this check BY HAND at every gate,
+  because the framework ran it nowhere ("touches outside What boundary is NOT checked
+  anywhere"), and that run's own S3 review surfaced the shape it was worried about: a
+  Platform-layer file edited by a module story.
+  - **The surface** is the union of every `file:`-kind `[src: …]` citation in
+    `01-what/handoff.md` and `02-how/handoff.md`, and every `touches:` entry of every story
+    under `03-plan/stories/` — or of `04-build/implicit-plan.yml` when the scope skipped Plan.
+    A directory entry covers everything beneath it, which is how a story declares the files it
+    is about to create and the forced companions (a lockfile, a generated client) that come
+    with them. The citation half reuses `citedRepoPaths`, the derivation the implicit plan
+    already builds `touches:` from — the same §2.8 tokenizer, not a second one.
+  - **The measurement** is `git diff --name-only <default_branch>...<epic_branch>`, once per
+    repo the plan's epics name, through the Build phase's existing git seam. Nothing is
+    checked out, fetched or written, and the epic's own `branch:` is what is diffed — the ref
+    `openStory` actually cut, not one re-derived here.
+  - **Offending paths are NAMED**, up to eight then `+N more`, prefixed with their repo:
+    `boundary=2 changed path(s), 1 outside the surface: app:platform/Auth.cs; work outside the
+    declared surface is a boundary change — a human decides whether to widen the scope`.
+    "1 path outside the surface" is not something anybody can act on.
+  - **A human may still approve over it**, and that is the whole point: widening a boundary is
+    a decision, and the framework has no basis for making it. Work nobody scoped is often the
+    right work.
+  - **It never refuses on an absence.** Outside Build, with no epic branch cut yet, with no
+    repo on disk, with no plan, or on a run whose What cited no repo path at all, it is `n/a`
+    **with the reason in the note** — a condition that could not measure must not report that
+    it measured zero. Same shape as condition 6's `n/a (not a build stage)`.
+  - **`tldrx-work/`, `.tldrx/` and `.agent/` are excluded from BOTH sides**, through the same
+    `isStatePath` filter the implicit-plan derivation already applies. A handoff cites the
+    run's own state as evidence, and in a `root_is_repo: true` workspace the state sits inside
+    the product repo — neither is a boundary question.
+  - **A bare citation widens the surface rather than shrinking it.** `file := [repo ":"] path
+    ":" line` makes the repo prefix optional, and `citedRepoPaths` skips the bare form because
+    it feeds a developer prompt, where a wrong guess puts another repo's file in front of an
+    agent. Here the risk is inverted — an unattributable citation would manufacture a false
+    refusal — so a bare path is admitted to every repo's surface. A check that refuses wrongly
+    is a check that gets turned off.
+
+### Changed
+
+- **The init report is coloured and carries a roll-up.** Repo names, confidence
+  (green/yellow/red), the counts and the `created`/`kept` verbs are inked, and a new
+  `files N written · N created · N kept` line answers "how much of this run was
+  regenerated, how much is new, and how much was mine and left alone" without reading the
+  per-file list. `stripAnsi(coloured) === uncoloured`, asserted.
+- `detectWorkspace` and `buildMap` take optional progress callbacks. Both default to
+  doing nothing, so `tldrx map` and every other existing caller behave exactly as before.
+- `tldrx init` now writes progress bytes to stderr like every other long-running command,
+  so the two `build.test.ts` cases that spawn it to exercise the node seam pass `--quiet`.
+  Their `stderr === ""` assertion is how a REAL warning gets noticed, and it still is.
+- **`tldrx cost` is organised by ECONOMY, and prints no grand total.** `STAGE · ECONOMY ·
+  MEASURED · DECLARED`, one footer per economy, and a third line for attempts that reported
+  neither — no row spans both columns and nothing adds a dollar to a token. A footer that
+  printed `$1.70` under a run which had also burned 1.5M host tokens is the sentence the
+  label exists to stop. `--json` carries `economy` on every stage row and the set of
+  economies on the run. Attempt lines are unchanged, all four token counters included, and a
+  declared `--tokens` figure past a million now reads `~1.2M` rather than `~1200.0k`.
+
+- `tldrx doctor` prints where the framework's own files are: a `framework <path>` line
+  naming the installed package that ships `stages/`, `workflows/` and `templates/`, and
+  saying that a project's overrides live in `.tldrx/stages/` and `.tldrx/workflows/`. The
+  `/tldrx` skill says the same in two lines. Measured 2026-08-30: a real session spent
+  1m22s on `find / -name build -type d -path "*stages*"` because nothing printed it.
+
+### Fixed
+
+- **A rejected knowledge file gets ONE repair round before the money is thrown away.**
+  Measured 2026-08-30 on `~/scavtopia`: `tldrx expert train dotnet-stack --area dotnet --mode
+  light` spent **$1.69**, the trainer wrote `knowledge/dotnet.md.partial`, and the validator
+  refused it for **two** bullets that asserted an execution (`exit 0`) and cited a file line.
+  The file went to `dotnet.rejected.md`, nothing reached `competencies.yml`, the status did not
+  move — $1.69 for zero evidence, over a mistake the checker could name in one line and the
+  writer could have fixed in one edit. `expert train` now hands those exact problems back to the
+  same trainer for one more turn before anything is quarantined.
+  - **A fresh spawn carrying the ORIGINAL prompt**, not a resumed session: `spawnAgent` has no
+    `--resume` and the session id is captured for the ledger only. Appending to the original
+    prompt is what keeps the repair possible at all — the citations to be fixed point into files
+    that were inlined in that prompt and nowhere else — and the byte-identical prefix reads the
+    cache the first turn paid to create. The appended `# REPAIR ROUND` section carries the
+    numbered verdict, the rejected file with a line-number gutter whose numbers are the `L<n>`
+    numbers in the verdict, and the reminder that deleting an offending bullet is a legal fix.
+  - **One round, and the gate does not move.** The repaired file goes through the same
+    `parseKnowledgeFile`, same shape, same scope. A second failure rejects exactly as the first
+    used to, quarantines the same way, and returns the same exit `5`. An unsourced claim still
+    cannot become evidence; it has simply been told once that it is unsourced.
+  - **Paid out of `--max-usd`, never on top of it.** The repair turn's ceiling is
+    `min(this sub-agent's share, whatever is left of the run's ceiling)`. Below the `$0.25`
+    floor it does not spawn and says so — a cold `claude -p` that dies on
+    `error_max_budget_usd` before its first reply costs money and produces nothing.
+  - **The operator is told while it happens**, so an extra sub-agent never spends silently:
+    `repairing: 3 problem(s) sent back to the trainer — one round, $0.31 of the ceiling left`,
+    then either `repaired: the second file validates` or `the repaired file does not validate
+    either (2 problem(s)) — one round is all there is`. Both turns land in `training.jsonl`; the
+    repair as `task: "code:repair"`, `repair: true`, with the number of problems it was sent.
+  - Not on `--commit`: there the sub-agent belongs to the host session and this process spawned
+    nothing, so repairing is running `--commit` again. Not for a file that was never written —
+    there is no verdict to send back.
+
+- **The execution-claim rule is now TAUGHT, with an example and a counter-example.** The same
+  $1.69 run is the evidence that stating it once in a paragraph does not work. Both training
+  prompts — the spawned one and `--print-prompt` — now give the four literal shapes the checker
+  looks for (`exit <n>`, `<n>/<n> passed`, `build is green`, and the bare word `measured` in the
+  sentence itself), one conforming line, one refused line, and why the refused one is refused: a
+  `workspace.yml` line DECLARES a command and is not a record of running it. Two further gaps
+  closed: **not making the claim** is named as the other legal answer (the trainer that failed
+  had no command in reach of the sentence it was writing, so "run it and cite it" was not
+  actionable), and the `(measured)` **annotation** is explicitly exempted — §2.3 asks for it on
+  every bullet, `\bmeasured\b` is one of the patterns, and nothing had ever told a writer that
+  `claimCheck` strips the annotation before it looks. The runs-mode prompt never stated the rule
+  at all, though the validator has always applied it to both files; it does now.
+
+- **`duplicate src` is documented as non-fatal, and the rejection report stops implying
+  otherwise.** It always was a warning — one call site, one `severity: "warning"`, one validation
+  path for both shapes — but the report did not say which lines were fatal and the headline
+  counted warnings as problems, so the same $1.69 run read as "3 problems" when only 2 rejected
+  it and the third was a duplicate that costs one bullet its evidence row. `describeKnowledgeIssues`
+  now lists errors first, prefixes warnings with `warning:` exactly as `knowledgeWarnings` does,
+  and the headline counts errors only (new `knowledgeErrors`). The reason it is a warning is
+  recorded where the message is emitted: "earns no second row" is a statement about scoring, not
+  about honesty, and throwing away every other finding in a file over a repeated citation is not
+  rigour.
+
+- **A developer that FAILED is no longer recorded as a consumed attempt.** The
+  developer-side sibling of the reviewer fix below, found by the same run on 2026-08-30.
+  Five developer spawns on `260830-tenancy-identity-customers` died with
+  `Reached maximum budget ($0.30 | $0.40 | $0.50 | $0.90 | $1.50)` before delivering
+  anything the pipeline could see, and every one was settled as the story `blocked` —
+  terminal in-run — so six of seven stories were reported as tried and failed when five of
+  them had never been tried. A failed developer spawn now puts the story back at the status
+  it held BEFORE the attempt (`todo`, or `review` when a reviewer had asked for changes),
+  keeps its worktree, spends no attempt, and stops the in-process loop rather than buying
+  the same error twice. Its `check.failed` carries `check: "developer"`,
+  `status: "error"` and the error verbatim as `detail`; the review log, the operator line
+  and `retro.md` all say the developer **FAILED**, never that anything was reviewed. The
+  next `tldrx next` — headless or `--prepare` — offers the story again as a fresh developer
+  run at the **same attempt number**. A developer that RAN and produced work its DoD faulted
+  is a different thing entirely and still blocks, unchanged, as do two `changes` verdicts.
+- **Runs recorded by the old code pick those stories back up.** A `blocked` story whose last
+  attempt recorded no commit, no check of any kind and no reviewer — the only trace the old
+  code left, the error itself having gone to `run.yml` alone — is read as the errored spawn
+  it was and offered again, with `S2 was blocked by a developer that FAILED (…) — that was
+  never an attempt, so it is offered again`. It is paired with the story's own plan, because
+  a story with an empty dod block blocks with exactly the same event shape and that block is
+  a plan bug. Measured read-only against the live run: `tldrx next --prepare` now offers
+  **S2** and, after it, S5, S4, S6 and S7 — while S3, which was blocked by two genuine
+  `changes` verdicts, stays blocked.
+- **The auto gate will not sign a Build stage whose stories are not all `done`.** Its five
+  conditions were all about the ARTEFACT — citations, questions, money, status — and none of
+  them looked at what the stage was for. On the live run all five held while six of seven
+  stories sat `blocked` and the epic branch carried one story's work, and the gate signed the
+  stage, then signed it again after a human revoked it. A sixth condition now reads the story
+  statuses where they live, refuses with `stories=1 of 7 done — S2:blocked, S3:blocked, …`
+  and falls through to the human gate. A person may still approve over blocked stories —
+  what is worth shipping is their judgement — and outside the Build phase the condition is
+  measured as `n/a` and always holds.
+- **A merge that moved nothing is no longer called "merged".** `git merge --no-ff` of a
+  branch that is already an ancestor exits 0 and says "Already up to date", and the handoff's
+  Gate section rendered that as landed work: on the live run it read
+  `(S1, S3, S5, S4, S7 merged)` when the epic tip carried only S1's commits. The executor now
+  counts what the merge is about to move BEFORE it moves it — afterwards it cannot, because a
+  merged branch is an ancestor either way — and the Gate line, the story Finding and the
+  review log all say “added nothing — identical to `epic/x`” for a count of zero.
+- **A reviewer that FAILED is no longer recorded as a reviewer that asked for changes.**
+  Found live 2026-08-30 by the first `feature`-scope run to reach Build: the headless
+  reviewer of a 39-file, +1879-line story was given $0.26, died mid-read with
+  `Reached maximum budget ($0.26)`, and the executor wrote that transport error down as
+  `verdict: "changes"`. That single line spent the story's one requeue, sent a fresh
+  developer at code nobody had faulted, and would have blocked the story after a second
+  reviewer hit the same wall — with **zero review ever performed**. A failed reviewer now
+  settles the story at `review` with `verdict: "error"`: the attempt counter is untouched
+  (only a real verdict spends it), the `check.failed` event carries the error as its
+  `detail` plus `verdict: "error"` so no ledger counts it as changes-requested, and every
+  operator-facing line, the review log and `retro.md` all say the reviewer **FAILED**.
+  Fail-closed is unchanged — an unfinished review is still never an approval. Inventing the
+  verdict is what stopped.
+- **`tldrx next` on a story whose review errored re-runs only the REVIEW.** The diff is
+  already committed and merged and its DoD went green, so there is nothing for a developer
+  to redo. Both doors do it: the headless path and `tldrx next --prepare`, which used to
+  hand the host session a full "attempt 2" developer bundle. The commit and the DoD results
+  come back out of `events.jsonl`, so the resumed reviewer sees the same proof the first one
+  did — including on the live run, where a `task.started` for the attempt that was never owed
+  sits AFTER the DoD it did not run, and must not erase it. Runs recorded by the OLD code resume too — a `verdict: "changes"` whose `detail` is
+  one of the framework's own transport errors is read as the failure it was, including a
+  story already left at `in_progress` by a wrongly-prepared attempt 2.
+- **The Build executor reads `03-plan/budget.yml`.** The Plan writes a per-story price map,
+  the Plan gate validates it, and until now **nothing read it**: the executor split its
+  stage into equal shares, so the story priced at $4.75 and the one priced at $0.75 both got
+  $1.03. A priced story now gets `price / (attempts x (developer + reviewer))` as its
+  developer ceiling and a quarter of that as its reviewer's; an unpriced one keeps the
+  uniform share; prices adding up to more than the stage are scaled down proportionally. A
+  `budget.yml` that will not parse or validate is an advisory on stderr, never a refused
+  build.
+- **A reviewer is never given less than $1.00.** Whatever the arithmetic says, clamped by
+  what the stage has left and by `per_agent_max_usd`. A reviewer that cannot finish reading
+  the diff approves nothing and blocks nothing — it converts the entire developer turn
+  beside it into a story stuck at `review`, which is what $0.26 did on 2026-08-30.
+- **`tldrx cost` no longer prints `0 in · 0 out · 0 cache write · 0 cache read` for a turn
+  the host declared tokens for.** `tldrx next --commit --tokens 342527` writes that number
+  onto the task row and the `agent.result` payload, and the cost view ignored it. It now
+  renders as `~342.5k declared (host session)`, kept apart from the four measured counters
+  rather than folded into them: nobody measured those, and four zeroes claim the turn used
+  no tokens.
+- **A stage whose declared outputs are a SHAPE no longer fails while the files sit next to
+  the error.** Found live 2026-08-30 by the first `feature`-scope run to reach Plan: the
+  stage wrote `03-plan/epics/E1.md` and `03-plan/stories/S1.md`..`S7.md`, and
+  `tldrx next --commit` refused it with "`03-plan/epics/<epic>.md` was declared as an output
+  but does not exist on disk; `03-plan/stories/<id>.md` was declared as an output but does
+  not exist on disk". Plan cannot name its outputs — it does not know how many stories there
+  will be until it has written them — so `stage.yml` declares the shape, and every
+  filesystem call was asking `existsSync` about a path with a literal `<id>` in it.
+  A declared path holding an angle-bracket token is now a **pattern**: it matches any file
+  in that directory with the pattern's fixed prefix and suffix, resolved against the run dir
+  and then the workspace root, in the same "first base wins" order everything else uses.
+  The fix is in `paths.ts`, at the seam, not in the validator: `present`/`missing` count a
+  pattern by its matches (so a stage taking `stories/<id>.md` as an INPUT gets past the gap
+  check), the prompt is handed the concrete files rather than the shape, the previous-attempt
+  inline shows every one of them, and `--dry-run` reverts each file it matched and names it.
+  `{repo}` expansion is untouched and still runs first, so `{repo}` and a token compose.
+  Plain paths behave exactly as before, down to the wording of their failure.
+- A pattern output that matches nothing now fails honestly — "`03-plan/stories/<id>.md` was
+  declared as an output but **no file matches it on disk**", rather than claiming a file
+  nobody ever named was looked for and not found. Its `sections:` contract binds **every**
+  matched file, and the failure names the concrete file that broke it, not the shape.
+- **`tldrx run estimate` prices cache traffic, which is where the money actually goes.**
+  Measured 2026-08-30 on a real workspace: a What stage was estimated at **$0.33** and the
+  one comparable real attempt cost **$1.70** — **5x**. That attempt's ledger says why: 56
+  input · 29.0k output · **166.3k cache write** · **3,747.1k cache read**. The estimate
+  multiplied input and output only, so it was adding up the two columns the money was not in.
+  Both cache counters had been on every `agent.result` since wave N and `modelPrices.ts` had
+  carried the multipliers the whole time — nothing needed new data, only arithmetic that used
+  it. The estimate now prices four terms: measured prompt tokens at the input rate, plus the
+  **median** cache write (**1.25x** input), cache read (**0.1x** input) and output of past
+  attempts at the same stage id, falling back to attempts at any stage and **naming which
+  sample it used**. It prints the breakdown —
+  `input ~189 · cache write ~166k · cache read ~3,747k · output ~29k → ~$1.46` — and keeps
+  saying "ESTIMATE" in words. With no history the old behaviour stands (it refuses to guess
+  the output half) and it now says `cache traffic not modelled — first attempt of this kind`
+  rather than pricing a silent zero. The input and cache-write terms overlap on a cold first
+  turn, so a first attempt leans high; that is stated in the output's own honesty line, not
+  corrected away.
+- **`tldrx cost` shows the cache write / cache read columns on every attempt line**, not only
+  on stage and run totals, and no longer hides them on a stage that ran once — previously an
+  attempt line carried cost, task and model and nothing about where the money went.
+
+- **tldrx state survives the project's own `.gitignore` rules, and `doctor` detects a rule
+  that shadows it.** Found by a real user 2026-08-30: their repo carried the stock .NET
+  `[Ll]og/` ignore, which swallowed `tldrx-work/<run>/04-build/log/S1.md` — the Build phase's
+  per-story review log, which spec §1 marks committed and the handoff cites as
+  `[src: 04-build/log/<id>.md:1]`. Nothing errored; the file was written, `git status` stayed
+  quiet, and a teammate's clone never got it. `init`'s managed block only ever ADDED ignores,
+  so any pre-existing project rule (`log/`, `docs/`, a `*.yml` in a subdir) could hide state
+  and nothing noticed. The block now opens with `!tldrx-work/`, `!tldrx-work/**`, `!.tldrx/`
+  and `!.tldrx/**` — the bare pair and the `**` pair are both needed, because gitignore cannot
+  re-include a file whose parent directory is excluded — and the framework's own ignores follow
+  AFTER them, since a later pattern wins. Measured with `git check-ignore -v` against a repo
+  carrying `[Ll]og/`, not asserted from memory: the story log comes back not-ignored while the
+  product's `Logs/build.log`, `tldrx-work/*/.lock` and `.tldrx/cache/` stay ignored. Re-running
+  `init` upgrades a block written before this in place, markers and neighbouring rules kept.
+- **`tldrx doctor` now says when a rule outside that block is still hiding state.** It runs
+  `git check-ignore --verbose --no-index -z` over four paths that must be tracked — the newest
+  run's `run.yml` and `events.jsonl`, a synthetic `04-build/log/` probe, and
+  `.tldrx/memory/facts.yml` — and prints each offender with the rule's own `file:line:pattern`,
+  so a `.git/info/exclude` or a nested `.gitignore` is named too. A warning: it never moves the
+  exit code, which is about the tools this machine has. `--json` gains `gitignoreShadow`, where
+  `null` means no workspace was scanned rather than nothing found.
+- **The `## Inputs` preamble no longer claims files the budget dropped.** Measured on a
+  real Build prompt, 2026-08-30: 9 of 15 declared inputs were inlined, the other 6 carried
+  "It exists on disk; do not guess at its content" — and the preamble above them still read
+  "Their full content is inlined below, so there is nothing to open and nothing else to
+  find." The two documents the run existed to edit were among the six. The preamble is now
+  conditional in every prompt that has one (stage prompts and the developer prompt share one
+  renderer): with everything inlined it is the sentence it always was; with anything dropped
+  it is `Inlined below: <n> of <m> declared inputs.` followed by "The rest exist on disk —
+  READ them at the listed paths before relying on them; do not guess: <list>".
+- **A touched path the story's worktree cannot read is flagged as such.** The developer works
+  in a worktree of the story branch, so a path that exists in the repo but is not committed
+  at that branch is unreadable there — and `existsSync(worktree/path)` called it a file the
+  story creates. Build now asks git (`git cat-file -e <branch>:<path>`) and marks it `NOT in
+  this worktree — its content is only what the handoff quotes`, plus one stderr line per
+  path: `warning: input <path> is not committed, so the story worktree cannot read it`. A
+  path that exists nowhere is still "does not exist yet — this story creates it".
+- **The story's own goal wins the developer prompt's inline budget.** `touches` was spent in
+  list order, so on that same run `AGENTS.md` — cited once in passing — was inlined whole
+  and the two documents the goal named were in the dropped tail. Touched paths the story's
+  `goal`, acceptance criteria, test plan or title NAME now sort first into the 64 KB; a brief
+  that names nothing changes no order at all.
+- **The developer is told to run an acceptance criterion's embedded pattern BEFORE it
+  edits.** Found on a real run's second Build of 2026-08-30: a derived criterion carried a
+  literal grep (`` Pending `DECISIONS-NEEDED.md` # ``, backticks included) and the markers
+  it was meant to count had been written three different ways, so it reported 0 against two
+  files that still held five real markers — the in-session driver only caught it by
+  measuring the inventory by hand. The developer prompt's `## Investigate` list now carries
+  the rule verbatim: validate the pattern against the current tree first; a criterion that
+  reports zero while the goal says the work exists is broken, so measure the real inventory,
+  use THAT as the completion test, and record the discrepancy in the handoff. The criterion
+  text itself stays data the story may not edit. `stages/build/stage.md` says so too.
+- **The implicit story no longer `touches` tldrx's own state.** `touches` is derived from
+  every repo path the What handoff cites, and a handoff cites state as evidence: measured
+  2026-08-30, 13 touched paths of which three were `run.yml`, a `.tldrx/triage/**/split.yml`
+  and a `.agent/**/prompt.md`. The developer prompt inlines every touched path and calls a
+  change outside `touches` a plan deviation, so those three read as permission to rewrite
+  the run's own bookkeeping. Anything with `tldrx-work`, `.tldrx` or `.agent` as a path
+  segment is now dropped from `touches` and recorded in `notes:` as `excluded <path> from
+  touches: tldrx state is never story-writable`. Product documents are untouched.
+- **A document your answer settles now joins the implicit story's `touches`.** Measured on a
+  real run, 2026-08-30: the run existed to settle six ADRs, the owner answered all six, and
+  the one thing the story could not edit was `ADR-D013-DELIVERY-ZONE-GEOMETRY.md` — the What
+  handoff never cited the file, `touches` is built from what the handoff cites, and the
+  developer prompt says a change outside `touches` is a plan deviation. The plan's own
+  `notes:` said so: "F010 settle no touched document". Build now reads the mapping rule
+  backwards as well — a file whose name carries a decision key (`ADR-D013-*.md`,
+  `decision-7.md`) that a fact of this run names is added, searched for beside the
+  already-touched files first and then across the repo, under the same ≤24 cap — and writes
+  `added <path> to touches: settled by F<n>` into `notes:`. A document no fact names is
+  never added.
+- **The developer gets the WHOLE answer.** `.tldrx/memory/facts.yml` capped a fact at 300
+  chars and `captureAnswers` writes one as `"<question> — <answer>"`, so on that same run all
+  six answers were cut and four lost the clause naming the ADR they settle — including the
+  words "Accepts ADR-D009 as written." The cap is now 2000 (spec §2.5; the bound only moved
+  outwards, so every facts.yml already on disk stays valid), a cut fact ends in ` …` and
+  carries `truncated: true`, `01-what/questions.md` is a declared input of the implicit story
+  and is inlined into the prompt, and each apply-bullet quotes the full `[Answer]:` text and
+  cites both the fact and the line it came from: `[src: F010; 01-what/questions.md:82]`.
+- **The implicit story's goal is the work, not the What's stale scoping.** With answered facts
+  the `goal:` list holds nothing but the apply-bullets, and the What handoff's Decisions move
+  to a `context:` list rendered under `## Context (from the What stage)` — after the objective,
+  labelled background, explicitly not a task. Before this, a run opened to get six decisions
+  answered told its developer, as its stated goal, "Out of scope: selecting an answer on the
+  owner's behalf … every relevant ADR is status `proposed`". The plan note now names the facts
+  the story is for (`… applies the run's answered decisions (F005–F010) …`). With no answers
+  nothing moves: the What's decisions are still the goal.
+- **`tldrx next --prepare --discard-pending` re-derives an implicit plan**, instead of
+  re-rendering the same story. The flag was handled only for stages with no executor, so on
+  Build it did nothing at all: `04-build/implicit-plan.yml` is written once and read forever
+  after, and re-preparing could not pick up a fix. It now bins the bundle's `pending.json`,
+  `result.json` and `result.raw.json`, derives the plan again from the handoff and the answers
+  as they stand, and prepares a fresh bundle — reusing this run's own epic branch and story
+  worktree rather than re-cutting or refusing them. It refuses to rewind a plan something has
+  been built off (recorded evidence, a settled story, or a commit on `story/<run>/S1` beyond
+  the epic) and prints which of those stopped it.
+- **The dirty-tree check ignores tldrx's own state (`tldrx-work/`, `.tldrx/`).** In a
+  `root_is_repo: true` workspace the framework's state lives INSIDE the product repo, so
+  Build refused the files it had just written itself. Measured 2026-08-30: `tldrx next
+  --prepare 260830-decisions-gate` exited 2 with `repo \`aparece-v2\` has 4 uncommitted
+  change(s) on \`main\``, and all four were tldrx's — `run.yml` and `events.jsonl` (rewritten
+  on every `next`), `.lock` (the run lock) and `04-build/` (the implicit plan written seconds
+  earlier). A user's uncommitted answers under `tldrx-work/` blocked it the same way, though
+  those are committed on the user's cadence, not as a precondition of Build. Product dirt
+  still refuses exactly as before — same message, same fix — and the message now lists only
+  product paths; when the only dirt was state, one line says how many files were excused. A
+  story commit excludes the same two paths by pathspec: a story worktree is a checkout of the
+  same repo, so `git add -A` could otherwise sweep the run folder into the diff a reviewer
+  reads (measured: it did). Multi-repo workspaces, whose state is a sibling of the repos
+  rather than inside them, are untouched.
+- **A scope that skips the Plan phase can Build.** `docs`, `hotfix`, `performance`,
+  `prototype` and `security-patch` all list `build` in `stages:` and `plan` in `skips:`, and
+  every one of them was a dead end: `stages/build/stage.yml` declares `03-plan/waves.yml` as
+  an input and the executor's first act was to load `03-plan/`, so a real `docs` run parked
+  at `04-build (ready)` could only fail its own Build stage with `03-plan/ does not
+  validate — stories/: the Plan wrote no stories`. Build now writes the one story that
+  decision implies into `04-build/implicit-plan.yml`, deterministically and with no model
+  involved: title from `run.yml`, `goal` from `01-what/handoff.md` § Decisions verbatim
+  (`[src: …]` tokens kept), `acceptance` from `01-what/success-metrics.md`, `touches` from
+  the repo paths that handoff CITES and that exist (≤24, first-cited order, a citation with
+  no repo prefix skipped rather than guessed at), `dod` from the commands `workspace.yml`
+  declares for the roles the scope calls for, and `budget_usd` from the Build stage ceiling.
+  A real `03-plan/` always wins. `tldrx next` prints one line naming the reason, and
+  `tldrx run status` prints `plan: implicit (scope skips Plan)` so a synthesised plan never
+  reads like one a person approved. The plan carries the work **forward**: bullets whose
+  subject is the What stage's own deliverable are dropped on five literal signals
+  (`questions.md`, `### Q`, an `01-what/` path, a question id, the run's-questions
+  vocabulary) with every drop and its signal recorded in the story's `notes:`, every
+  live fact stamped with this run adds
+  `Apply <fact> to the touched files [src: F<n>]` to `goal`, and `acceptance` gains a check
+  that each document one of those facts settles — the fact's text mentions that file's ADR
+  id or decision number — no longer reads `Status: proposed`. A mapping that cannot be
+  derived is reported in the story's `notes:` and falls back to "apply every listed fact;
+  leave a one-line note per file saying which fact changed it", never to a guess. A fact
+  cut at §2.5's 300-char cap is matched against the full `[Answer]:` behind it in
+  `01-what/questions.md`: measured on a real run, `captureAnswers` had sliced the ADR
+  clause off four of six facts, so 2 of 6 mapped on the stored text and 6 of 6 map with
+  the answer. The grep in that criterion is complete or names `notes:` wholesale — a
+  `(+1 more)` inside a command is something a person pastes and reads wrong. The
+  developer prompt states plainly that Plan was skipped and this story applies the run's
+  answered decisions.
+- **`skips:` in a workflow is read rather than decorative.** The schema declared the key and
+  the loader dropped it, so nothing could tell "the Plan phase has not run yet" from "no Plan
+  phase was ever going to run" — a distinction that cannot be made from disk, since both look
+  like an absent `03-plan/`. `WorkflowPreset.skips` now carries it down to `StageSpec`.
+- **A DoD command is looked up by its `workspace.yml` KEY, not by matching the command text.**
+  Measured on a real .NET workspace: `lint: dotnet format --verify-no-changes` has no "lint"
+  anywhere in the string, so a text match silently found nothing and would have handed a docs
+  run an empty Definition of Done. `WorkspaceContext.commandRoles` keeps the keys.
+- Build's declared `03-plan/…` inputs are treated as satisfied when the scope skips Plan, and
+  **only** those: every other missing input is still exit 1.
+
+### Verified, not changed
+
+- **The walk already skips vendored and generated trees**, and always did: `SKIPPED_DIRS`
+  in `detect/walk.ts` covers `node_modules`, `dist`, `build`, `out`, `bin`, `obj`,
+  `target`, `.venv`, `Pods`, `.next`, `.expo`, `coverage` and more, plus every
+  dot-directory below the root, and it is honoured by `walkFiles` (so by `countCodeFiles`
+  and `readSourceTree`) and by `findRepos`. There are now tests that say so: a fixture with
+  a `.ts` file planted in each of those trees, and a real git repo inside `node_modules`
+  that must not be reported as a workspace member. The slow part of `init` was never the
+  walk — it is `graphify update`, once per repo.
+
 ## 0.3.0 — 2026-08-30
 
 Every measurement below was taken on a real workspace on 2026-08-29 unless another date is