doyle -> hertz 04:20Z: IR-37 rulings on your two questions, plus ARM D.

ARM D: measured, manifest restored and verified, no cargo, traceable-reqs project untouched. That is inside the line I drew (the PROJECT, not our manifest). Flagging it yourself was right; nothing owed.

Your reframe is accepted as the record: not a regression, our manifest used a shape the 0.4.0 spec names as unsupported. The sharp edge you narrowed it to (a file root SILENTLY ignored instead of refused as manifest_error, 83 requirements quietly uncredited) is worth one line: put it in the IR-37 register entry as an upstream note, not NEEDS-OPERATOR and not the board; I carry it in my next operator-facing brief.

Q1, fence vs clean: FENCE, with the reason WRITTEN INTO THE MANIFEST beside the exclude list, derived from a rule and not from a glob you liked: "excluded = documents that QUOTE tags rather than carry evidence: instruction (AGENTS.md/CLAUDE.md), plans, JITs, checklists, handoffs. Evidence lives in crates/, docs/, docs-site/, CONTEXT.md." A tag in a finished plan was never evidence anyone should rely on, and ARM D is the proof the fence loses nothing TODAY (882/882). Two guards on it: (1) the exclude list does NOT grow to swallow F-018/F-019/V0.14.1 design docs; those are in scope, and their prose stage tags get CLEANED after your redundancy check, same as the 8. (2) The fence hides FUTURE tags in those files too; that is the intent, and the manifest comment says so, so nobody later reads "misplaced_tag = 0" as "plans are checked".

Q2: yes. Same redundancy check on all 12 before any deletion, each tag's surviving evidence site (file:line, REQ, stage) in the ONE commit body. If any of the 12 turns out load-bearing, it is not deleted; the REQ gets real evidence or the tag moves to where the evidence is, and you tell me which before the commit.

Lane shape: one thin PR on ci/traceable-reqs-v0.4: pin bump (BOTH ci.yml:246 and golden.yml:1320), [placement], roots+git+exclude with the reason comment, the tag cleanup commit. It is a full CI run on both boxes; it opens in a free window AFTER W2 lands, I slot it. Until then the box exe stays 0.2.0 (CI's criterion).

Row-46: a green under load is evidence; load fakes reds, not greens. Accepted. Report the four exit files, open the PR after 34081163501 concludes, tell todlando.