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.
Five code paths treat a failed or empty membership lookup as proof the person is NOT a vendor, so an unclear read is admitted as a lead. Keep admitting, hold, or make unclear its own outcome? Today admitting can market to a vendor and page a technician in the quiet hours he set; holding can delay a real lead when the database hiccups. Over 21 days of real traffic the lookup failed zero times, with 23 blocked lines as the positive control that the sweep ran; whether the blank-id path is reachable in production is NOT established. A pinned test states a role-lookup error must never drop a genuine lead, so changing direction overturns it on purpose.
281c6038 is parked on this.
Two read-only checks need a person to run them, and both are the last step before work that already merged can prove it worked. (1) THE PARKED-MAIL REPLAY, 30-day window. The reader merged tonight (#19932): it walks a month of binned inbound mail and scores each one with the production emergency-word classifier, so we can finally say how often an emailed gas report was silently thrown away. Every production read is refused in the unattended lane that built it, so the run needs an attended seat. Until it runs, the gate on the held gas-report fix (#19816) cannot be met: its own authorising rulings require a replay covering parked mail before merge. (2) THE BLAST-RADIUS CENSUS on the nightly eval's old sender. The forward hole is closed (#19938 merged: the nightly now refuses to send as that number), so this is purely historical: the bench handyman line is also a contact phone on an ACTIVE vendor record at a real customer, and the nightly injected as it run after run for as long as that was true. Did anything land on, or get attributed to, that real customer's vendor record, and is any of it still there? That row's own DONE MEANS asks for these counts; a lane was named for them and never delivered them, and I searched 9,870 task directories with a positive control to confirm they exist nowhere. BOTH ARE READ-ONLY. Cleanup, if the census finds residue, is a separate act with its own approval under the prod-data rule. THIS SUPERSEDES b92036747, whose own next step was 'someone checks a month of binned mail first': its ruling was build the reader, measure, then ship, the build is now done, so this block carries its measure step.
281c6038 is parked on this.
PR 19836 carries the hold-for-review label. The fence applied it because the title began 'docs(', and the retitle to 'chore(' withdrew that claim — but the release notice never self-releases on that path, so the hold strands the fix indefinitely unless a person acts. The diff is 28 added lines in one file, ALL inside a single docblock: re-measured 2026-10-15 from the patch at head 24be3309190, which is still the current head, and ZERO added lines are executable. Dropping the label is a founder act by the fence's own contract ('Released by: a founder, in one click'), and the decider ruling explicitly does not authorise an agent to do it. Two separate verdicts: 'the condition is met' and 'merge it' — on red checks it merges nothing.
281c6038 is parked on this.