feat(solo): fold chats quiet for 72 hours into Inactive - #3186

…es (#3442)

## Why

Two browser journeys fail intermittently in CI for the same underlying
reason. Both jump the page clock far enough to expire the live stream's
heartbeat, and the stream restart that follows was not accounted for.

| Test | Sightings |
|---|---|
| `agent-outcomes.spec.mjs`, "a remote failure shares its expandable
history and preserves its message anchor" | WebKit 1/18, Browser
journeys: [10 Nov,
main](https://github.com/block/buzz-app/actions/runs/42923245792/job/130206998334),
[10 Nov,
PR](https://github.com/block/buzz-app/actions/runs/42920092542/job/130193154955),
[11 Nov,
PR](https://github.com/block/buzz-app/actions/runs/43110752944/job/130826317616),
[11 Nov,
main](https://github.com/block/buzz-app/actions/runs/42952461094/job/130300041605)
|
| `relay-recovery.spec.mjs`, "relay reads recover automatically after
the network returns" | WebKit 5/18, Browser journeys: [10 Nov, PR,
passed on
re-run](https://github.com/block/buzz-app/actions/runs/42918607668/job/130187892464)
|

## Root cause

The live broker stream arms a 45 s heartbeat on the page clock. The
broker's 15 s keepalive runs on real time. A page-clock jump longer than
45 s therefore always expires the heartbeat, and the page aborts and
restarts its stream. `presence.spec.mjs` already records this hazard.

**`agent-outcomes`** pauses the page clock, freezes wall time, and runs
120 s of browser time. Two failures follow from the restart:

- In three of the four jobs the test published its signed replies before
the restarted stream had re-issued a channel REQ. The policy relay
rejected the publish with "event must traverse an explicit production
channel REQ". In each trace the publish came about 0.9 s after the clock
resumed, and the new stream opened 0.2 to 0.4 s later.
- In the fourth job (11 Nov, main) the 120 s jump took 85.6 s of real
time instead of the usual 4 to 12 s. The still-frozen wall clock drifted
more than 60 s from the broker, so read-state signing answered 400.

**`relay-recovery`** fast-forwards the page clock 30 s twice. The second
jump expires the heartbeat. In the same jump, session recovery's
scheduled retry posts `/stream-retry` with the old stream id. The broker
has already handled the stream close and answers 404 "Live stream no
longer available". The app drops the error for a superseded generation,
but the browser still logs "Failed to load resource … 404". The fixture
only excused retired-stream 404s for `/stream-observer` and
`/stream-priority`, so the unexplained-console-error check failed the
test. The trace shows the fast-forward, the 404 ten milliseconds later,
and the new stream 0.7 s after that.

Neither is a product defect. The restart only happens under a fake-clock
jump, and the app already ignores the late control response.

## Fix

- **`agent-outcomes.spec.mjs`**: re-anchor the page wall clock to real
time right after resuming, so signed read-state events follow the
broker's clock again. Then poll for the primary/alpha route before
publishing, mirroring the readiness wait the test already does at
startup.
- **`fixture.mjs`**: widen the retired-stream 404 match to the six
broker control routes that answer 404 once a stream is retired:
observer, priority, retry, interests, artifact-sync and
artifact-sync-close. The exact `retiredStreams.has(streamId)` guard
stays, so a 404 for a live or unknown stream still fails. Presence
controls answer 200 for a missing stream and stay out of the list.

No timeouts, retries or assertions were relaxed. No browser cases were
added or removed.

## Evidence

Local runs on Linux, WebKit, `bin/pnpm test:browser:ci --project webkit
--no-deps --workers=1 --repeat-each=8 --reporter=list`.

| Scope | Result |
|---|---|
| `agent-outcomes.spec.mjs -g "a remote failure shares"` | 8/8 passed,
17.8 to 20.2 s each |
| `relay-recovery.spec.mjs relay-refusal.spec.mjs -g "relay reads
recover automatically\|an upload is the first request"` | 16/16 passed |

## Not reproduced, not run

- The late `/stream-retry` 404 did not reproduce locally. No retired
controls were recorded in the local evidence, so the widened fixture
branch is only exercised under CI timing. The Flake check lane on this
PR is the real test of it.
- The unchanged `agent-outcomes` test also passed 8/8 locally, with two
or three stream restarts during each jump. The local run guards against
regression rather than reproducing the CI ordering.
- The read-state re-anchor addresses a failure seen once, when the jump
ran unusually slowly. That slowness was not reproduced.
- Chromium was not run for these two changes.
- No human has tested this yet, so `buzz-review-completed` is not set.

## Overlap with open PRs

Several open PRs also edit `tests/browser/fixture.mjs` (for example
#3332, #3239, #3186 and #3093). None touches the retired-stream match,
and a trial merge of each against this change is clean.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Signed-off-by: mtoohey <[email protected]>
Signed-off-by: Matt Toohey <[email protected]>
Co-authored-by: Claude Fable 5.1 <[email protected]>