solidjs / solid / 37692732689

76%

main: 89%

push

github

fix(signals): a staged read of a node born staged is not re-queued at the lane seam (#3882)

Since #3869, verdict-lane work that read a staging of the flush is
re-derived on the committed world while the frame stays parked
(`stagedReaders`, the lane seam). A node born into the parked frame has
no committed value: the re-run reads the same staging, registers again,
and the seam re-queues it every round until flush throws "Potential
Infinite Loop Detected" (semantic fuzzer, mount-under-hold: a
`latest()`-gated Show mounting a fresh Loading under an action hold,
29 cases across seeds 3289 and 91501).

`stagedRead` keeps REACTIVE_STAGED_READ for such a read but no longer
lists the pass for re-derivation. The frames return to pre-#3869's (the
content shows the held value while held; A29's fallback frame is still
open, pinned as test.fails).

Co-authored-by: Claude via Cursor <noreply@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

674 of 958 branches covered (70.35%)

Branch coverage included in aggregate %.

996 of 1227 relevant lines covered (81.17%)

28.57 hits per line