Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1PR #5675 removes a duplicate @canonical docblock left on MachineGradeCitation (types.ts) when two concurrent fixes for today's red main both merged 6 minutes apart. Comment-only, -7 lines, 0 failing checks. It sits behind a hold-for-review label that the task's standing constraints forbid me from dropping — and dropping it re-arms auto-merge, which is the merge rung. Merge it, or close it and leave the duplicate on main?
In plain terms. Two sessions fixed this morning's broken build at the same time and both fixes landed, so the code now carries the same explanatory note twice, in two voices. Nothing is broken — the build has been green all afternoon with the duplicate sitting there. A small cleanup is written and ready; it only touches a comment. Merging it costs you a click. Skipping it leaves a trap for whoever tightens that check later, because the check's own name says there should be exactly one note.
Fable recommends: Drop hold-for-review on #5675 so it auto-merges — removes the duplicate Nothing is broken today — five consecutive green push:main runs with the duplicate present — but the guard only tolerates it because entity-classification.drift.test.ts:296 boolean-tests /@canonical\b/, while that same test is NAMED 'carries exactly one of @canonical or @derived'. Anyone tightening it to count occurrences re-reds main on this exact spot. The fix is already written, green, and keeps the first-landed block; closing it entrenches a latent trap in a load-bearing contract file to save one click. Tried first, unsuccessfully: receipt fa8c02bd0 — RESOLVED, held under reversal (high/high). Fable read both PRs and origin/main's types.ts, confirmed the duplicate at ~583 and ~604, and made the latent-red-main argument above. It resolved leave-open-vs-close in favour of leave-open; the merge rung itself is yours, which is why this is here.
1af80f47 (adopted from 245cddd5) is parked on this.