Neil a6a50769bf fix(notifications): restore the blocked-child waiting state on non-Stop lead events ...

The lead-Stop gate revert (84880f2711) dropped the effective-state read from
the local lead path entirely, not just from the Stop case. That regressed a
separate contract: a child blocked on a permission prompt no longer held the
pane at `waiting` when the lead kept working, so the pane read `working` and
the user never saw what it was blocked on.

Restore the read, but AFTER the roster reap rather than before it. Post-reap,
a lead Stop sees an empty roster and still reports `done`, which is what
agent-hooks/server.ts requires; only non-Stop events observe live children.
The pre-reap `leadStopWithLiveSubagents` flag is unchanged and still carries
the "children were live at Stop" signal for the notification gate.

Both orderings are now pinned by tests: reading pre-reap breaks the Stop
contract, dropping the read breaks the blocked-child contract.

2026-07-26 20:43:56 -07:00

..

cli

fix(runtime): report the effective ask timeout so a clamped wait isn't misreported (#10550)

2026-07-25 05:42:05 -07:00

main

fix(notifications): gate the Codex lead-Stop banner without downgrading its state

2026-07-26 19:04:25 -07:00

preload

fix(crash-reporting): record exact V8 heap sizes, not Blink's quantized ones (#10683)

2026-07-25 22:54:20 -07:00

relay

fix(agent-hooks): install OpenCode status plugin into the WSL guest so status works over WSL (#10328)

2026-07-25 02:30:59 -07:00

renderer

fix(notifications): gate remote Codex lead Stops too

2026-07-26 19:07:23 -07:00

shared

fix(notifications): restore the blocked-child waiting state on non-Stop lead events

2026-07-26 20:43:56 -07:00

types

…