Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. When Clara's review step holds a work order back from AppFolio (say, the tenant had already asked for a human), should a person editing or approving that work order release the hold, or should it stay held for good? Today the hold is not written on the work order at all, so other screens still show it as 'not sent yet' and Clara re-reviews it every time the conversation wakes up; either choice fixes that, they differ only in whether a person can send it later.
The full question, as raised
Follow-up to PR #23228 (false 'stranded mirror' page): when the judge refuses to ship a work order to AppFolio, should the refusal be written onto the WorkOrder row as a sync status ('withheld', pointing at the WO_JUDGMENT# row) so hasPendingSyncWork and every 'unsynced' reader (drain probe, wo-progress.ts tenant promise, atlas mirror-health, admin queue/kill-all/unsynced count) agree it is held on purpose and the re-judge loop ends — and if so, does a staff edit/approve release it?
Why, and what was tried
The session raising this recommends: Mark it held on purpose; a staff edit or approval releases it Same shape as the prior instance (#21328/#21330, guest cards: a structural park reason on the row, read by every reader). A release-on-edit door matters because the judge is a model: a wrong refusal must be recoverable by a person, not a permanent silent strand. Changes what staff see on the progress page, so it needs Fede's read before it merges. Tried first, unsuccessfully: Read hasPendingSyncWork (src/lib/maintenance/work-orders/pending-sync.ts) and its readers on origin/main: wo-progress.ts, atlas mirror-health, queue/kill-all/admin routes read 'unsynced' directly. The judge prompt lists duplicates and cancelled WOs as refusal grounds; this refusal was 'tenant asked for a human', so there is also an upstream question of why intake filed a WO on an escalated thread. Fable chose the row-state fix with a release door; the permanence question and the customer-visible wording are a founder's call.