What
Two commits are ready on claude/session-provenance-tracking-3ykzr4:
adac8e2 — the burndown kit: burndown/queue.json (a selection over the Desk board, not a second backlog), six per-stage agent prompt templates (scout / work / verify-A / verify-B / fix / final), and burndown/RUNBOOK.md.8415075 — the 2026-09-03 run archive: 13 patch sets with their reports, scout assessments, all 36 adversarial verdicts, and TICKETS-TO-FILE.md.
122 files, +10,693.
Why this repo
burndown/RUNBOOK.md places the kit at bounded-systems/.github/burndown/, and the nightly trigger it describes clones this repo and fails closed if burndown/ is absent.
Provenance
The run happened in a Cowork session with no repos attached and no push credentials, so it filed zero issues and pushed nothing. The work was carried out as two exported patches and applied with git am. Both commits carry a Claude-Session: trailer naming the producing session; the trailers survived the transfer, the commit SHAs did not (they were rewritten onto a new parent). That asymmetry is the argument for the trailer over the SHA.
Checks
node --test .claude/*.test.mjs — 326 pass, 0 failnode --test *.test.mjs — 282 pass, 0 fail- Applies clean to
af649d8; tree contents byte-identical to the exported archive (diff -r)
- Public-safety scan: no
.github-private references, no token- or key-shaped strings
Why this issue exists
pr-claim requires a PR to name an open, claimed issue in its own repo. Cross-repo naming will not satisfy it here. The archive documents a run whose stated ceiling was exactly this gate — so the record is now blocked by the mechanism it describes, which is the honest place for it to sit.
The PR will say Closes #N against this issue.
What
Two commits are ready on
claude/session-provenance-tracking-3ykzr4:adac8e2— the burndown kit:burndown/queue.json(a selection over the Desk board, not a second backlog), six per-stage agent prompt templates (scout / work / verify-A / verify-B / fix / final), andburndown/RUNBOOK.md.8415075— the 2026-09-03 run archive: 13 patch sets with their reports, scout assessments, all 36 adversarial verdicts, andTICKETS-TO-FILE.md.122 files, +10,693.
Why this repo
burndown/RUNBOOK.mdplaces the kit atbounded-systems/.github/burndown/, and the nightly trigger it describes clones this repo and fails closed ifburndown/is absent.Provenance
The run happened in a Cowork session with no repos attached and no push credentials, so it filed zero issues and pushed nothing. The work was carried out as two exported patches and applied with
git am. Both commits carry aClaude-Session:trailer naming the producing session; the trailers survived the transfer, the commit SHAs did not (they were rewritten onto a new parent). That asymmetry is the argument for the trailer over the SHA.Checks
node --test .claude/*.test.mjs— 326 pass, 0 failnode --test *.test.mjs— 282 pass, 0 failaf649d8; tree contents byte-identical to the exported archive (diff -r).github-privatereferences, no token- or key-shaped stringsWhy this issue exists
pr-claimrequires a PR to name an open, claimed issue in its own repo. Cross-repo naming will not satisfy it here. The archive documents a run whose stated ceiling was exactly this gate — so the record is now blocked by the mechanism it describes, which is the honest place for it to sit.The PR will say
Closes #Nagainst this issue.