capture has no way to record comments or updates on an existing issue -- issues are create-once records whose only later mutations are status transitions, so triage evidence, corrections and new reproductions accumulate in conversation or unsanctioned hand-edits instead of the ledger; add a capture followup verb appending timestamped redacted body sections under the ledger lock, and give the schema's unwritten related_issues field its writer via a --relates flag (same schema-grows-a-writer precedent as resolved_by); design sketch persisted at .abcd/.work.local/scratch/review-2026-08-24/design-capture-followup.md review 2026-08-24

capture has no way to record comments or updates on an existing issue -- issues are create-once records whose only later mutations are status transitions, so triage evidence, corrections and new reproductions accumulate in conversation or unsanctioned hand-edits instead of the ledger; add a capture followup verb appending timestamped redacted body sections under the ledger lock, and give the schema's unwritten related_issues field its writer via a --relates flag (same schema-grows-a-writer precedent as resolved_by); design sketch persisted at .abcd/.work.local/scratch/review-2026-08-24/design-capture-followup.md review 2026-08-24

Remedy grounds (2026-09-29)

Why: an appended, dated section keeps the one-file-per-record ledger and its folder-as-status signal intact. SOTA check: git-bug stores a bug as an append-only log of operations (comment added, comment edited) compiled into the current state, never rewriting earlier ones (https://github.com/git-bug/git-bug/blob/trunk/doc/design/data-model.md, read 2026-09-29); the appended section is that model's file-per-record form. Rejected: a separate comments file per issue, which is a second record per id and splits the status signal.