Hey, thanks for the thought, that’s a solid observation. 76 beforeShellExecution events with zero lifecycle events is a really good negative control: the system looks healthy, but it’s dropping exactly the events a workflow might rely on.
The idea of a fail-closed startup probe when start or stop receipts are missing, and using monotonic event IDs to tell “there were no subagents” apart from a gap in the stream, sounds like a good direction for hook observability.
On this thread: the transient state where all subagent hooks go quiet while beforeShellExecution from the same hooks.json keeps working isn’t reproducible on-demand yet, so we’re actively looking at diagnostics like yours. Separately, the background subagentStop is an issue we’re already tracking: `subagentStop` never fires for background subagents; documented `summary` / `modified_files` / `agent_transcript_path` missing or null
If you have an instrumented case where you can catch this, I’d love the details: Request ID, generation_id, and the contents of Output > Hooks at the time of the failure.