DISCLOSURE: 860c3df contains two items its message does not name
Correcting the record rather than rewriting it, on the steward's instruction.
860c3df is titled "Build records for PENDING-172 and PENDING-173". Its 65
insertions are two authors' work:
MINE ### PENDING-172 — BUILD RECORD
### PENDING-173 — BUILD RECORD
NOT MINE ## PENDING-176 — Every PDF routes to V-SCAN by file extension…
## PENDING-177 — The runbook's PDF recipe selects a backend…
176 and 177 were written by a second interactive session (davidglidden-93,
pid 56861) doing chamber-library PDF work, and were sitting uncommitted in
PENDING.md when I staged it. `git add PENDING.md` is a whole-file act, so
another session's uncommitted work in the shared register is annexed silently.
They now carry my commit message, my Co-Authored-By and my Claude-Session
trailer, and git will report that permanently. Their content is unaltered and
nothing was lost; the attribution is what is wrong.
Cause, and it is mine: I staged a shared governance register without reading
`git diff --cached` first. This is a third form of PENDING-104's class — not a
corrupted read (ADDENDUM 1) and not an interleaved write (ADDENDUM 2), but
commit-boundary annexation, which leaves the file byte-correct and the record
misattributed. Nothing detects it; today's new parked-worker control cannot,
because an ordinary interactive session has no job directory.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wn9mxsFjHJkzYjuDdrtxwp
This commit is contained in:
co-authored by
Claude Opus 5
parent
860c3df6fd
commit
7578f5a675