solidjs / solid / 37516791413

76%

main: 89%

push

github

frames: A0 correctness pass — S-flush, C3 hold, C5 data scope, C12 report, rulings (#3837)

* fix(web/frames): the address is an async source — one landing per bound address, one response per store (S-flush)

A0 (SCs are rendered data): a frame is one async value outward. The mount's
covering <Loading> now pends on the bound address's FIRST FLUSH — content or
error — through `FrameHost.landing(address)`, read per bound address through a
fresh node (frames-rulings 1.5, 1.6 (i)): a switch is a new question on the
source, the superseded address's late writes release nothing, an unrevealed
boundary stays on its fallback and a revealed one holds. The two hand-rolled
shell gates (`boundaryComponent`'s arm/release/settle/setGate and
`adoptBoundary`'s twin), `followAddress`'s re-arm and frameless waiter, and
`onApply`-as-release go. An unstaged response announces itself to the host at
its header (`start`), so the address reads "in flight" from the header to the
landing.

The store is one response's (1.4 full; 2.1/2.2): a version bump or rebind
replaces the store wholesale — root, segments, slot records, the error — so a
byte-identical root under a new version still applies as the new version's
(C7 c), a held record leaves with the response that carried it (C6 a1, b2),
and `argsEquivalent`/`clearStreamRecords` delete; the mount's `#slotArgs`
value compare is what preserves occurrence state. The host keeps the latest
landed version as `shown` so a mount opened mid-flight seeds the committed
value (holds-latest) and the landing fans out as the version's whole set.

The occurrence's name decides its class: a called occurrence (`prop#n`) found
without its record waits for it — never evaluated argless (C18 ×3 flip; the
#2968 poll stays as the document face's re-sync trigger, scoped to called
occurrences) — and a bare occurrence is direct-insert. A reveal is an apply
(2.3, interim): the document face's reveal cascade syncs the adopting frame,
so a direct-insert rang... (continued)

654 of 932 branches covered (70.17%)

Branch coverage included in aggregate %.

1 of 3 new or added lines in 1 file covered. (33.33%)

964 of 1199 relevant lines covered (80.4%)

28.17 hits per line