Development record
Three ADRs end with leaked agent tool-call closing tags committed into the durable record: a literal </content> line then </invoke>
Three ADRs end with leaked agent tool-call closing tags committed into the durable record: a literal </content> line then </invoke>
Evidence
.abcd/development/decisions/adrs/0011-spec-terminology-rename.md:85-86.abcd/development/decisions/adrs/0013-fn38-memory-single-writer-and-write-lint.md:78-79.abcd/development/decisions/adrs/0020-manifest-version-lockstep.md:188-189
Each file ends with two literal byte lines </content> then </invoke> (confirmed via cat -A; not a code fence, not a render artefact). A tree-wide sweep for </content>/</invoke> across .abcd/ returns exactly these three pairs. record-lint exits 0 — ungated.
Adversarial verdict
CONFIRMED (substantive). Refuter read the file bytes and git history: leaked tool-call scaffolding, no legitimate reason, not prior art (distinct from iss-49 record cosmetics, iss-179 adr-6 citations). Fix: delete the two trailing lines from each file.
Frontmatter
| id | iss-373 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-373-three-adrs-end-with-leaked-agent-tool.md
open on GitHub ↗ · commit history ↗
mentions3
- dcn-26082000000000052026-08-20 — bughunt round 3 (branch bughunt-a/round-3): captured twelve findings (iss-360..iss-369, plus two renumbered to iss-373/iss-374 after round 2's own collision re-mint landed inside this round's block — the week's fourth collision,
- iss-49record cosmetics batch: an orphaned .gitkeep; two verbatim doctrine blocks duplicated in the record; the ACKNOWLEDGEMENTS ccpm entry was added retroactively against its own same-change rule; the brief lacks a one-page arc42 crosswalk and an open-questions precedence line; 05-personas.md should be rewritten role-first with personas.json as the roster source of truth. Low individual impact; batched so the cleanup pass has one handle. Detector: none warranted beyond the existing lints — this is the residue after detector-shaped clusters were extracted, fixed directly per the fix-the-detector one-off bound.
- iss-179adr-29 and adr-25 still narrate adr-6 in prose, but adr-6 is in no store and is absent from all git history (the ADR set landed in one import commit; 0004/0006/0008/0014-0018 were never migrated, and every one but 0006 is accounted for by a successor's supersedes). adr-29 states in its own body that adr-6's decision stands and that adr-29 does not supersede it, so the supersession vocabulary cannot record it and neither ADR body should be rewritten to paper over it. iss-39 closed the machine-readable half (the two related_adrs entries, and the two brief pages that cited it). The surviving prose sites are adr-29 lines 24, 39, 43, 56, 60, 63, 71 and adr-25 lines 51, 80; adr-29's line 43 in particular still says it "links to ADR-6" now that the frontmatter link is gone, which is the residual made legible rather than hidden.