You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fff1615
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix(signals): a lane holds through a boundary showing content (F6) (#3811)
A boundary output that forwards its tree's pending (CONFIG_REDERIVE, status exactly pending) is now a frame reader of the lane in blockedBy's one hop, so a Loading showing content no longer lets the lane release past it. An output that has never committed holds nothing. Rulings recorded in SPEC-ASYNC-SEMANTICS.md (A18 amendment and the never-committed clause); three #3331 pins re-pinned, the F6 pin flipped to passing.
No size caps change: +20 B minified on every signals bundle is within the #3821 allowance.
Co-authored-by: Claude via Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
A lane now holds through a `Loading` boundary showing content: a boundary output forwarding its tree's pending counts as a frame reader, so `latest()` no longer reveals beside the boundary's stale content (A33). An output that never committed — a mount the frame has not revealed — holds nothing. A corrected guess that never showed is void at the correction: untracked reads return the committed value (A18 amendment, 2026-10-05).
0 commit comments