Problem
idd-verify's external-writes collector (#315) partitions the audit-trail records by the issue whose comments/body carry them. A write recorded under issue A's ### Sister Concerns Filed / ### Linked-Context Siblings Filed that actually landed ON issue B (e.g. a comment posted to B) therefore shows up only in the --- #A --- block, while the --- #B --- block says "no audit-trail record found … treat the blast radius as unconfirmed". Observed in PsychQuant/che-apple-mail-mcp PR #407 verify R3 (finding R3-20): the record of the comment posted on #333 lived under #404's block; #333's block claimed no record. A reviewer reading only #333's partition is told the opposite of what the file itself knows.
Type
enhancement (verify tooling; report accuracy)
Expected
When an audit-trail entry names a target issue that is also in REFD_ISSUES (e.g. #333 inside a row of #404's sister table), the collector cross-lists that entry under the target issue's block too (or emits "recorded under #404, targets #333"). "No record found" should be emitted only when no ref'd issue's records mention the issue at all.
Context
Problem
idd-verify's external-writes collector (#315) partitions the audit-trail records by the issue whose comments/body carry them. A write recorded under issue A's### Sister Concerns Filed/### Linked-Context Siblings Filedthat actually landed ON issue B (e.g. a comment posted to B) therefore shows up only in the--- #A ---block, while the--- #B ---block says "no audit-trail record found … treat the blast radius as unconfirmed". Observed inPsychQuant/che-apple-mail-mcpPR #407 verify R3 (finding R3-20): the record of the comment posted on #333 lived under #404's block; #333's block claimed no record. A reviewer reading only #333's partition is told the opposite of what the file itself knows.Type
enhancement (verify tooling; report accuracy)
Expected
When an audit-trail entry names a target issue that is also in
REFD_ISSUES(e.g.#333inside a row of #404's sister table), the collector cross-lists that entry under the target issue's block too (or emits "recorded under #404, targets #333"). "No record found" should be emitted only when no ref'd issue's records mention the issue at all.Context
skills/idd-verify/SKILL.md(collect_external_writes, per-issue loop).