Why, and what was tried
The session raising this recommends: Merge it
All automated checks pass on the final version and the 4th review found nothing blocking. Blast radius: it reads ONE stuck-message queue, sends only messages whose tag starts with the approved name to ONE destination, then deletes them from the stuck queue. Everything else is put back untouched (hidden at most an hour if the run dies). It cannot touch other queues, change or print a message, is capped at 100 moves by default (1000 max) and 5 minutes of reading, and one approval runs once. Worst case: one message in both queues, named and held an hour so it is never sent twice. Each real use still needs your Go or Trinity's approval. Small follow-up after merge: copy the run's counts into the record people read afterwards. This also widens the 'one call per operation' rule in ADR-0075; I will add that amendment line.
Tried first, unsuccessfully: Fable receipt fc4952940 RESOLVED that this merge is Gera's own decision, and its recommendation was to raise exactly this block: HOW_TO_ADD in prod_write.py and agentflow ADR-0075 say Gera reviews every new production operation, and this PR widens ADR-0075's one-call wording. Not a Fable decline; a Fable ruling that routes to Gera. Earlier ruling fa5807bb9 capped review at round 4.
fe283b3d is parked on this.