busy-nudge: de-gate from humanincdw + cover lane-context 1:1 asks
Elazar 2026-07-13: agents sit idle for hours waiting on replies. Two defects in runBusyNudgeCheck (hub.mjs:5253): (1) global 'if(!humanInCdw)return' kills ALL nudges when humanincdw=false — fix: delete it, per-row skip only recipient==Elazar&&!humanInCdw (d27c0c9 does this). (2) stmtBusyNudgeCandidates (hub.mjs:1998) requires origin_aro IS NULL, so nudge NEVER fired for lane-context 1:1 DMs — which is where rule-18 puts nearly all execution traffic and where Elazar's idle agents were. Fix: drop 'origin_aro IS NULL', KEEP 'recipient NOT LIKE aro:%' (still exclude room fan-outs; only 1:1 asks). Requires: re-run the 5 cases + a lane-context-ask case + MEASURE boot-burst on live-DB copy (all previously-suppressed lane asks in last 3600s could fire at once); if burst large, add boot-grace. coder implements, audit reviews, PM bounces.
Questions
Activity
-
Live v2.39.14: busy-nudge de-gated from humanincdw (per-row skip only recipient=Elazar&&!humanincdw) + widened to lane-context 1:1 asks via messages.fanout column (fanout=0), fan-out/multi-DM never nudge. Boot burst max 8/337 sim boots. Audit CLEAR ddcb666.