Originally created by: lodar
dev3 (CHANNELS=none) filed a manual gate correctly. It pinged no one. Board said blocked, the filer was told the gate was filed, and it only surfaced because dev3 messaged its lead out of band.
Measured on the live board: every gate from an agent WITH a channel had gate_pinged_at stamped within a second of need_asked_at; the one from the agent WITHOUT a channel had it NULL.
DIVE-1243 already added an org-lead fallback for exactly this case. It has never once fired. It probed the lead's channel by readability (-r access.json), and every agent's channel dir is 0700 with access.json 0600 — a sibling agent can never read a peer's pairing state. Permission-denied was indistinguishable from unpaired, so the fallback read the entire fleet as unpaired, logged no lead channel either, and returned 0.
_task_agent_paired — probe paired-ness independently of readability (group-readable connector token + a bare -d on the channel dir; the parent .../channels is 0755). That split is the whole fix: unreachable must fail loudly, reachable-but-unreadable must be delivered by someone with the privilege to read it._task_escalation_chain — walk reports_to UP the whole chart (depth-capped, cycle-guarded), not one hop. The alert names the original filer, since it lands on the manager's bot and would otherwise read as the manager's own gate.task gate-escalate <ident> (root-only, undocumented) — re-send an already-filed, still-pending gate from a privileged context. Agents reach it via their existing NOPASSWD sudo entry; the path is hardcoded to /usr/local/bin/5dive because sudoers grants that exact path. The raw human nonce crosses on stdin, never argv.task need restores the pre-gate status, clears every need_* field, and fails naming the cause. A gate nobody can answer is worse than a refused one.access.json is readable), and a gate with NO delivery receipt is retried at 15 min instead of the full hour.Filed as agent-dev3 against the real board:
todo;gate-delivery result=ok chat=… message_id=… detail=confirmed Bot API send, gate_pinged_at stamped. A real human received a gate filed by a channel-less agent.20 new assertions in tests/gate_channelless_escalation_unit.sh; gate_delivery_receipt_unit, heartbeat_gate_renag_unit, heartbeat_gate_escalate_unit, gate_t2_routed_escalate_unit, gate_notify_log_observable_unit all pass.
DIVE-1926 was not permanently invisible: the 1h re-nag delivered it at 07:10 through created_by=main. The permanent case is a gate on a task the channel-less agent created itself — then created_by and assignee are both unpaired and the re-nag loops forever. Both are covered.
FIVE_VERSION is 0.15.5. Main landed 0.15.4 (PR [#156]) mid-build and this branch had also claimed 0.15.4; rebased onto da303e9 and renumbered. DIVE-1938 check re-run by hand at push time: no other open PR claims a version, so 0.15.5 is free.
🤖 Generated with Claude Code
Ticket changed by: lodar