solidjs / solid / 38123002633

78%

main: 89%

push

github

fix(signals): carve async toward the F/D rules; redo #3937, #3954, #3895 (#3977)

* fix(signals): a first load born under a hold holds it (column 2); drop _bornIn

A new async memo whose first pass reads a held value is held at creation,
like its sync twin (A29): its answer is the hold's, and the hold waits for
it. A fresh or re-armed boundary that catches the pass keeps it (#3540):
then the hold does not wait. This replaces #3881's _bornIn, which landed
the first answer into a live hold but never let the hold wait for it (the
direction rule's time half, withdrawn 2026-10-09).

- issue-3800-repro: a slower first load keeps the hold open; the action's
  hold waits for the pages read outside a boundary.
- direction-rule-probe: the three same-tick/in-flush shapes are no longer
  `it.fails` — they assert the wait.

Size (local, Rolldown): minified -22..-24 B on every scenario; core floor
7440 -> 7431 B br, hello world 9935 -> 9927 B br.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LVm3wseHt9wRTY8LfPiHmQ

* fix(signals): a probe alone does not hold

A verdict read (`isPending`, `latest`) registers its reader to re-derive at
the landing — the verdict flips there — without making it a holder of the
hold. A render effect holds when its read threw, or when, beside a probe, its
plain read of the flight was served the committed value (REACTIVE_FRAME_READ,
the stale reader; #3442 / A10). #3774 routed the probe's re-run through the
stale reader, which also made it a blocker, against its own stated intent
("a probe alone is neither").

Fixes a probe-only header keeping a same-source `Loading on` re-arm's
fallback off screen (the header's probe held `data`, so the content under
the boundary was served the committed value instead of throwing).

Re-pinned (only probes read the async, so nothing holds):
- optimistic-settle-verdicts #3409: after the revert each indicator clears
  with its own flight (7000 / 80... (continued)

746 of 1036 branches covered (72.01%)

Branch coverage included in aggregate %.

1079 of 1321 relevant lines covered (81.68%)

27.13 hits per line