diff --git a/docs/plans/2026-10-12_runs-list-damaged-record.md b/docs/plans/2026-10-12_runs-list-damaged-record.md index e9c7b7697..fb9da9773 100644 --- a/docs/plans/2026-10-12_runs-list-damaged-record.md +++ b/docs/plans/2026-10-12_runs-list-damaged-record.md @@ -32,7 +32,8 @@ evidence is in `agents/rocko/work/queue-56/BUILD.md` and `out/`. The - `packages/runs/src/runs.mjs`, only if the fix sits in `listRunRecords` - `packages/runs/tests/` -- `packages/runs/README.md`, the table of damaged records only +- `packages/runs/README.md`, the "How mosaic-task.mjs uses it" + section only: the table of damaged records and the paragraph above it - `agents/rocko/work/queue-/` ### What ships @@ -45,7 +46,11 @@ evidence is in `agents/rocko/work/queue-56/BUILD.md` and `out/`. The `listRunRecords`, and says why in the packet. If it sits in `listRunRecords`, `show` and every other caller must print what they print today for a well-formed record. -- The README table gets a row for an object with wrong field types. +- The README table gets a row for an object with wrong field types, and + the paragraph above the table names that case among the conditions, + so it no longer claims identical output for a root that has one. + (Amended 2026-10-12 after Rocko's round 1 note: the paragraph was + outside the first version's scope and its claim became false.) - Tests: `{}`; a numeric `status`; a `null` `taskId`; a damaged run between two good ones, with both good lines byte-identical to today's output. Mutants that drop each check survive on the base and are