solid

Ported onto L2 (2026-10-04) The PR was authored against the pre-L2 core. The branch was rebuilt in place on (now ): the PR's semantics re-implemented on the hold model, nothing pre-L2 revived. The pre-L2 head is kept as tag (). Spec: (D1–D11, §6 "On L2", §8.3, §10 review brief). The model on L2 Clamp = the commit-#0 loading window. () wraps the memo's compute: every answered pass re-opens , registers an async-shaped result through itself, and keeps the window open only for a flight still in the air. Readers are served the committed value ('s serve branch); no , never , so no frame observes it and no transaction is blocked by it (D1; never sees it). A sync-resolved thenable never opens a flight (A10). Verdict = an mark whose scope is the flight. marks + wakes the verdict readers; the mark drops in ahead of the landing's write (, as clears a plain memo's pending ahead of it) so the readers the write re-runs read the landing as final; follows A19 unchanged (D4). The seam sweep (, riding ) closes what no landing reports (a rejected flight, a dead node) and re-opens a window a commit closed under a newer question. "Never leads" = the seam's own hold decision. A flight asked inside a flush is queued as a pending node of that flush with nothing staged ( → ); a parking flush holds it (), its landing re-enters the hold (A34 (1)), a committing flush sweeps it ('s close is gated on a staged value). Inside an action the flight is the action's work and never delays it. Boundary. `createDeferred = createMemountilrefreshunansweredFlightGlobalQueue._slotDerivecountd1 = createDeferredm1 = createMemo(async){}countd1m1:execm1:doned1m1d1recomputem1m1m1:done(0)m1signaldeferredm1m1fix(createDeferred): a re-ask over a held landing keeps it…signals(createDeferred): a lagging question is not an answer…CONFIG_DEFERREDm1()createDeferred@solidjs/signalssolid-jscreateDeferred(compute, options?)createMemoloadingValuecreateMemocreateDeferredcommitPendingNode_loadingGlobalQueue._deferredLandedGlobalQueue._slotDeriveaffects.tsunmarkonSeamCONFIG_DEFERRED = 1 loadingValuerefresh(d)until(...)untilcreateMemopackages/signals/docs/create-deferred.mdtests/createDeferred.test.tscreateDeferred@solidjs/signalscreateMemocreateDeferredsolid-jscreateMemocreateMemocreateDeferredcommitPendingNodepackages/signals/src/core/deferred.tsoptimistic.tsverdict.ts_loading = trueloadingValueisPendingaffects()markWalkactiveAffectsMarksrefreshuntilread()yield until(...)recomputeREACTIVE_REASKfinallycommitPendingNodeGlobalQueue._deferredLanded?.commitPendingNodeasyncWritenextSize-Exception:handleAsyncMockPromiseisPendingpackages/signalscreateDeferred.test.tspackages/solidpackages/webtsc -p tsconfig.build.jsonRULES-INDEX.mdscripts/sizeorigin/next`.

Describe the bug Your Example Website or App Standalone source, one-command setup and README. Steps to Reproduce the Bug or Issue The test mounts Feedback in the persistent Router shell, navigates to unresolved lazy route children, waits 400 ms, then releases the route promise. The README also supplies a one-command clean setup and a next-tag switch. Expected behavior The status indicator appears beside the old page at the old URL. It remains absent although routing is true and the timer fires. Release commits the new page normally. Platform Solid rc.15 and next e3716454129f; Router next.39 / HEAD 4a1685ec8f1a; Bun 1.4.2, system Chrome; development and production. Additional context With Router next.30 fixed, Solid rc.13 passes and rc.14 first fails. Compiler rc.13/rc.14 swaps follow the runtime. Router next.39 and built Router HEAD also reproduce. Related #3884 concerns supersession timing rather than this single-navigation feedback failure. Tested hand-rolled transitions without Router pass; the exact runtime trigger remains unisolated.