Neil cb29f42c1e test(runtime): pin the store subscription the reconciled loop can leak ...

The retention suite that `reconcile three branches' handle-gap verdict rules
into one loop` replaced carried an assertion the split suites did not: the
store subscription is held for exactly as long as something needs it.

Measured before writing it, because half of it was already covered:

  RETAIN direction -- drop the verdict term from `stopStoreSubscriptionIfIdle`
  so a verdict with no waiter behind it loses the subscription its drain needs:
  already caught, 2 failures in host-mirror-handle-gap-landed-handle.test.ts.

  RELEASE direction -- never release the subscription at all: caught by
  NOTHING. That mutation passes all 272 tests across the 33 other handle-gap
  and session-tabs suites. A leaked subscription rescans every parked pane on
  every store write for the life of the session and nothing notices.

So this is for the release direction. The retain cases ride along because both
halves of one invariant belong in one file, not because they were missing.
That term is also precisely what the reconcile moved -- it now counts verdicts
as well as waiters -- so it is the part of this map most likely to drift again.

Asserted with a spy on useAppStore.subscribe rather than a new test-only
export: whether the module is subscribed is already observable at the store
boundary, and the production surface should not grow just to say so.

2026-09-11 01:17:15 -07:00

..

src

test(runtime): pin the store subscription the reconciled loop can leak

2026-09-11 01:17:15 -07:00

index.html

fix(macos): prevent stale UI surfaces after wake (#11226)

2026-07-28 16:37:13 -07:00

popout.html

fix(macos): prevent stale UI surfaces after wake (#11226)

2026-07-28 16:37:13 -07:00

web-index.html

…