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.
1The fix that stops your decisions list counting already-answered questions as still waiting on you is ready and checked. It carries a do-not-merge tag its own author added to flag a concern, and that concern has now been fixed. Merging it also means restarting the two services that run this fleet. Merge and deploy now, or hold it until a person reads the code?
Fable recommends: Merge it and deploy now The do-not-merge tag was added by the session that wrote the fix, to flag its own worry, and that worry is now fixed and double-checked. After the first review I overruled its all-clear and sent three more problems back, including one where deleting half the fix left every check still passing. All 1008 checks pass and I broke the code myself twice to confirm they actually catch it. Undo is a two-minute revert. Tried first, unsuccessfully: Fable receipt f684da491 came back RESOLVED, recommending merge and deploy, and I am escalating anyway rather than acting on it. Two reasons. First, an operator never merges and never removes a do-not-merge tag somebody else placed - that rung is yours by rule, not by my level of confidence. Second, deploying restarts both live services, which is the named-risk exception in your own standing instruction to otherwise drive everything to merge without asking. Worth knowing: an earlier receipt faa26cc3d escalated this to you on almost the same facts, so Fable itself landed on both sides of the line - which is the signal that it sits on the line. Fable also named the precedent risk in its own words: clearing a do-not-merge tag on machine review alone, in a repo where that tag is the only merge gate there is.