@abide/abide 0.58.0 → 0.100.0

package/src/lib/ui/dom/tryBlock.ts

@@ -1,263 +0,0 @@
-import { effect } from '../effect.ts'
-import { AsyncCellError } from '../runtime/AsyncCellError.ts'
-import { CURRENT_BOUNDARY } from '../runtime/CURRENT_BOUNDARY.ts'
-import { claimMarker } from '../runtime/claimMarker.ts'
-import { OWNER } from '../runtime/OWNER.ts'
-import { RENDER } from '../runtime/RENDER.ts'
-import { SuspenseSignal } from '../runtime/SuspenseSignal.ts'
-import { scopeGroup } from '../runtime/scopeGroup.ts'
-import type { Boundary } from '../runtime/types/Boundary.ts'
-import type { State } from '../runtime/types/State.ts'
-import { state } from '../state.ts'
-import { anchoredBranch } from './anchoredBranch.ts'
-import { discardAndRebuild } from './discardAndRebuild.ts'
-
-/*
-Reactive error boundary — the runtime for `<template try>` (ADR-0019 D3). Unlike the old
-synchronous render-once version it is render-MANY and reactive both directions: it catches
-a build throw AND an initial reactive-read throw (as before) AND — the headline capability
-— a throw from a LATER re-run, where an async error lives (an async cell that rejects after
-mount, read via a throwing peek → `AsyncCellError`).
-
-Each branch's content lives in a `[`…`]`-bracketed RANGE (the model `when`/`await`/`each`
-share) parked before an anchor, so a swap detaches one unit and builds the other. The
-guarded branch builds under an ambient `CURRENT_BOUNDARY` so every effect created inside
-associates with this boundary (`boundaryFor`); when such an effect throws on a re-run the
-scheduler (`flushEffects.drain`) calls `boundary.handle(error)` — which swaps to the catch
-branch. No `renderCatch` (no `<template catch>`) means no boundary is installed, so a later
-throw propagates to the nearest ENCLOSING `{#try}` unchanged, and an initial throw rethrows.
-
-Keep-the-watch: the terminal alternative would dispose the guarded scope on throw, killing
-the only subscription to the failing cell — the boundary would go deaf to recovery. So the
-throw carries the originating cell (`AsyncCellError.cell`); on catching an async-cell error
-the boundary subscribes to that cell's lifecycle and, when it recovers (error→value via a
-`refresh()` or a dep change), rebuilds the guarded content fresh — one rebuild, then
-fine-grained. On catch→catch (a fresh error while still failing) the catch branch rebuilds
-with the new error (the codegen catch binding is a plain local, so the error passes by
-value; in-place `err` update is a v2 refinement).
-
-Hydration claims the SSR boundary (`<!--abide:try:N-->…<!--/abide:try:N-->`): the happy
-path adopts the guarded nodes in place and brackets them into a range (so the first swap
-detaches them like any later one); a throw discards the server nodes and builds the catch
-fresh.
-*/
-// @documentation plumbing
-export function tryBlock(
-    parent: Node,
-    id: string,
-    renderTry: (parent: Node) => void,
-    renderCatch?: (parent: Node, error: State<unknown>) => void,
-    before: Node | null = null,
-): void {
-    const hydration = RENDER.hydration
-    /* The live branch's scope, registered with the owner so it disposes on owner teardown —
-       not only when a swap detaches it. */
-    const group = scopeGroup()
-    /* Only a block WITH a catch branch installs a boundary: with no catch it cannot handle a
-       throw, so its guarded effects must inherit the ENCLOSING boundary (a nested throw then
-       propagates outward) and an initial throw rethrows. */
-    const hasCatch = renderCatch !== undefined
-    /* The single active branch mounted before an anchor — owns `active`/`detach`/`place`/
-       adopt-strand guard (shared with `awaitBlock`); this block keeps its bespoke boundary
-       recovery. */
-    const branch = anchoredBranch(parent, group)
-    /* The keep-the-watch subscription on the throwing cell, live while the catch branch is
-       shown (async-cell errors only); disposed on recover / swap / teardown. */
-    let watchDispose: (() => void) | undefined
-    /* Which branch is mounted, and the reactive error cell the catch branch reads. A
-       catch→catch (a fresh error while still failing) WRITES this cell — the `err` binding
-       re-runs in place, no rebuild — mirroring how `awaitBlock` updates its then-value cell. */
-    let activeKind: 'try' | 'catch' | undefined
-    let errorCell: State<unknown> | undefined
-
-    const boundary: Boundary = { handle: (error) => showCatch(error) }
-
-    const disposeWatch = (): void => {
-        if (watchDispose !== undefined) {
-            watchDispose()
-            watchDispose = undefined
-        }
-    }
-
-    /* Install this boundary as the ambient one around the guarded branch's build (passed as
-       `place`'s `wrapBuild`) so its effects associate for later-throw routing; the catch branch
-       builds WITHOUT it, so a throw in catch content propagates to the enclosing boundary rather
-       than back to this one. */
-    const withBoundary = (run: () => void): void => {
-        const previousBoundary = CURRENT_BOUNDARY.current
-        CURRENT_BOUNDARY.current = boundary
-        try {
-            run()
-        } finally {
-            CURRENT_BOUNDARY.current = previousBoundary
-        }
-    }
-
-    /* Build (or rebuild) the guarded branch. A SYNCHRONOUS throw during the build — an
-       initial reactive-read throw or a plain build throw — falls to the catch branch (or
-       rethrows with no catch, preserving the old boundary's semantics). Later-run throws
-       arrive via `boundary.handle` instead. */
-    const showTry = (): void => {
-        disposeWatch()
-        try {
-            branch.place((host) => renderTry(host), hasCatch ? withBoundary : undefined)
-            activeKind = 'try'
-            errorCell = undefined
-        } catch (error) {
-            /* A `SuspenseSignal` is "value pending", not an error, and must NEVER render `{:catch}`
-               (ADR-0042 D3, mirroring `flushEffects`, which refuses to route it to a boundary) — that
-               would flash the author's catch during loading and, since `rewatch` only arms on an
-               `AsyncCellError`, stick there forever. Every reading region withholds its own suspend
-               locally (post-ADR-0042 the `{#await}`/`{#each await}` subjects included), so this is
-               unreachable in a compiled template; rethrow defensively rather than mislabel it. */
-            if (error instanceof SuspenseSignal) {
-                throw error
-            }
-            if (!hasCatch) {
-                throw error
-            }
-            showCatch(error)
-        }
-    }
-
-    /* Swap to the catch branch. A catch→catch (a fresh error while the catch branch is
-       already mounted) updates the reactive `err` cell IN PLACE — the binding re-runs, no
-       rebuild, focus/scroll inside the catch branch survive. Otherwise (try→catch, or the
-       initial throw) it builds the catch branch fresh around a new error cell. Either way it
-       keeps a watch on the throwing async cell so a recovery re-arms the guarded branch. */
-    const showCatch = (error: unknown): void => {
-        if (activeKind === 'catch' && errorCell !== undefined) {
-            errorCell.value = error
-            rewatch(error)
-            return
-        }
-        const cell = state<unknown>(error)
-        errorCell = cell
-        branch.place((host) => (renderCatch as NonNullable<typeof renderCatch>)(host, cell))
-        activeKind = 'catch'
-        rewatch(error)
-    }
-
-    /* (Re)subscribe the keep-the-watch to whatever cell threw this time. Only a reactive
-       async-cell error carries a source to watch; a plain render bug is terminal in v1 (a bug
-       is not a data state that self-heals). */
-    const rewatch = (error: unknown): void => {
-        disposeWatch()
-        if (error instanceof AsyncCellError) {
-            watchCell(error.cell)
-        }
-    }
-
-    /* Subscribe to the throwing cell's lifecycle. On recovery (its error clears or a value
-       arrives — error→value via `refresh()` or a dep change) rebuild the guarded branch
-       fresh; on a fresh error while still failing, rebuild catch with the new error. Created
-       OUTSIDE this boundary and the owner (it must not route its own reads here and must not
-       double-register), tracked in the group so it disposes with the block. */
-    const watchCell = (cell: AsyncCellError['cell']): void => {
-        const previousBoundary = CURRENT_BOUNDARY.current
-        const previousOwner = OWNER.current
-        CURRENT_BOUNDARY.current = undefined
-        OWNER.current = undefined
-        let firstRun = true
-        let dispose: () => void
-        try {
-            dispose = effect(() => {
-                const cellError = cell.error()
-                const value = cell.peek()
-                /* The first run only subscribes — the cell is still in its error state that
-                   drove us here, so acting on it would immediately re-arm. */
-                if (firstRun) {
-                    firstRun = false
-                    return
-                }
-                /* Recovered: rebuild guarded fresh. Still failing with a fresh error: rebuild
-                   catch with it. Either path disposes THIS watch first (safe: an effect fully
-                   unlinks itself, so its own end-of-run tracking trims nothing). */
-                if (cellError === undefined || value !== undefined) {
-                    showTry()
-                } else {
-                    showCatch(new AsyncCellError(cell, cellError))
-                }
-            })
-        } finally {
-            CURRENT_BOUNDARY.current = previousBoundary
-            OWNER.current = previousOwner
-        }
-        watchDispose = group.track(dispose)
-    }
-
-    if (hydration !== undefined) {
-        firstHydrate()
-        return
-    }
-    branch.parkAnchor(before)
-    showTry()
-
-    /* The first run when hydrating: claim the boundary's open marker, adopt the guarded
-       server nodes in place, then bracket them into a range so the first swap detaches them
-       like every later one. A guarded throw (the server rendered catch, or the client build
-       throws too) discards the boundary and builds the catch fresh. */
-    function firstHydrate(): void {
-        const cursor = hydration as NonNullable<typeof hydration>
-        const open = claimMarker(cursor, parent, `abide:try:${id} open marker`)
-        try {
-            adopt()
-        } catch (error) {
-            rebuildCold(open, error)
-        }
-    }
-
-    /* Adopt the guarded branch in place — the cursor already sits past the boundary open
-       (claiming it advanced): claim the server's `[` range-open marker, build the guarded
-       content (which claims its nodes) under the boundary, then claim the `]` range-close
-       and the boundary close, parking an anchor so a later swap detaches this range like
-       any other. A build throw disposes the partial scope and rethrows so `firstHydrate`
-       rebuilds cold. */
-    function adopt(): void {
-        const cursor = hydration as NonNullable<typeof hydration>
-        /* The server emits the `[ … ]` range inside the boundary — claim `[` as the live
-           range start, advancing the cursor to the first content node. */
-        const start = claimMarker(cursor, parent, `abide:try:${id} range-open marker`)
-        /* Install the boundary around the whole adopt (build + marker claims); the shared
-           strand-dispose guard in `adoptStrand` disposes the partial scope and rethrows on any
-           failure, and this `finally` restores the boundary before the rethrow reaches
-           `firstHydrate`. */
-        const previousBoundary = CURRENT_BOUNDARY.current
-        if (hasCatch) {
-            CURRENT_BOUNDARY.current = boundary
-        }
-        try {
-            branch.adoptStrand(
-                (host) => renderTry(host),
-                () => {
-                    const end = claimMarker(cursor, parent, `abide:try:${id} range-close marker`)
-                    const close = claimMarker(cursor, parent, `/abide:try:${id} close marker`)
-                    branch.parkAnchor(close)
-                    return { start, end }
-                },
-            )
-            activeKind = 'try'
-        } finally {
-            CURRENT_BOUNDARY.current = previousBoundary
-        }
-    }
-
-    /* Discard the SSR boundary and build the catch branch fresh in its place (hydration off).
-       No catch → rethrow (the throw surfaces past the boundary, as the sync version did). */
-    function rebuildCold(open: Node, error: unknown): void {
-        branch.detach()
-        discardAndRebuild(
-            hydration as NonNullable<typeof hydration>,
-            parent,
-            open,
-            `/abide:try:${id}`,
-            (after) => {
-                if (!hasCatch) {
-                    throw error
-                }
-                branch.parkAnchor(after)
-                showCatch(error)
-            },
-        )
-    }
-}

package/src/lib/ui/dom/types/EachRow.ts

@@ -1,21 +0,0 @@
-import type { State } from '../../runtime/types/State.ts'
-
-/* A live row in a keyed list: a content RANGE bounded by two comment markers (so a
-   row holds any content, not just one node), plus the disposer for the bindings
-   created in its ownership scope. `cell` holds the row's item as a reactive value, so a
-   re-key with a changed value (same key, new object) updates the row in place instead of
-   leaving it frozen. `indexCell` holds the row's reactive position, so a reorder repaints
-   its `index` binding in place without a rebuild. `pending` holds a freshly built row's
-   nodes in a fragment until first placement inserts them. */
-export type EachRow = {
-    start: Node
-    end: Node
-    dispose: () => void
-    cell: State<unknown>
-    indexCell: State<number>
-    pending?: DocumentFragment
-    /* The id of the last reconcile pass that saw this row's key in the source. A row
-       whose `gen` lags the current pass departed and is pruned — an int compare that
-       replaces a per-reconcile `Set` of present keys. */
-    gen?: number
-}

package/src/lib/ui/dom/types/SkeletonHoles.ts

@@ -1,10 +0,0 @@
-/* The holes a realized `skeleton` exposes for the build's attach code to wire up:
-   `el` the element holes (attribute/listener/bind nodes) in pre-order, `an` the anchor
-   holes (reactive text, control flow, components) in document order. Two arrays because
-   the element and anchor walks follow different traversal rules (`walkElementOrder` vs
-   `walkAnchorOrder`), so their indices are independent series — el[N] and an[N] are
-   unrelated holes, each numbered from 0 by its own walk. */
-export type SkeletonHoles = {
-    el: Element[]
-    an: Node[]
-}

package/src/lib/ui/dom/types/SwitchCase.ts

@@ -1,11 +0,0 @@
-/* One branch of a `switch`: `match` returns the value this case selects on
-   (undefined = the default branch); `render` builds the branch's content into the
-   parent (the block tracks it as a range between markers). `pending` (only on an
-   async `{#if}`/`{:elseif}` cond-chain branch) reports whether this branch's own
-   async condition is still loading — a true reading holds the whole chain here, so a
-   later branch never renders on a not-yet-known earlier condition. */
-export type SwitchCase = {
-    match: (() => unknown) | undefined
-    render: (parent: Node) => void
-    pending?: () => boolean
-}

package/src/lib/ui/dom/when.ts

@@ -1,58 +0,0 @@
-import { ELSE_SEGMENT, THEN_SEGMENT } from '../runtime/BRANCH_SEGMENT.ts'
-import { SuspenseSignal } from '../runtime/SuspenseSignal.ts'
-import { mountSwappableRange } from './mountSwappableRange.ts'
-
-/*
-Conditional binding — the runtime for `<template if>` (with optional `else`). The
-branch's content lives in a RANGE bounded by two comment markers, so a branch may
-hold anything — elements, components, text, nested control-flow, snippets — not
-just element roots. A 2-case swappable range tracks `condition()` and swaps the
-range's content on a truthy↔falsy flip (`render` truthy, `renderElse` falsy); an
-unchanged condition is a no-op. See `mountSwappableRange` for the shared
-hydrate/swap/teardown semantics.
-
-`isPending` (compiler-supplied only for a bare async subject) adds a third state: while
-it returns true the block renders NEITHER branch, so a still-loading promise never flashes
-its `{:else}` before settling — "pending" is not conflated with a settled falsy value. It is
-consulted first, so `condition()` (the throwing peek) runs only once the cell is no longer
-pending; an error then throws to the nearest `{#try}`.
-*/
-// @documentation plumbing
-export function when(
-    parent: Node,
-    condition: () => unknown,
-    render: (parent: Node) => void,
-    renderElse?: (parent: Node) => void,
-    before: Node | null = null,
-    isPending?: () => boolean,
-): void {
-    mountSwappableRange(
-        parent,
-        () => {
-            if (isPending?.() === true) {
-                return 'pending'
-            }
-            /* A blocking `await` cell embedded in the condition — a member access or compound the
-               whole-subject `isPending` gate doesn't cover (`{#if !sources.length}`, `{#if user &&
-               await load()}`) — throws a `SuspenseSignal` while pending (ADR-0042). Withhold the
-               block (render neither branch) until it settles, exactly as a bare async subject holds;
-               the read tracked its cell, so the swap effect re-runs on resolve. */
-            try {
-                /* The branch key doubles as the branch's render-path segment (see
-                   BRANCH_SEGMENT), so it is sourced from the shared alphabet SSR also emits. */
-                return condition() ? THEN_SEGMENT : ELSE_SEGMENT
-            } catch (signal) {
-                if (!(signal instanceof SuspenseSignal)) {
-                    throw signal
-                }
-                return 'pending'
-            }
-        },
-        (branch) =>
-            branch === THEN_SEGMENT ? render : branch === ELSE_SEGMENT ? renderElse : undefined,
-        before,
-        /* An async subject (compiler supplies `isPending`) can render a different branch on the
-           server than the pending client, so hydration must not adopt the SSR range in place. */
-        isPending !== undefined,
-    )
-}

package/src/lib/ui/dom/withScope.ts

@@ -1,37 +0,0 @@
-import { createScope } from '../createScope.ts'
-import { CURRENT_SCOPE } from '../runtime/CURRENT_SCOPE.ts'
-import { enterRenderPass } from '../runtime/enterRenderPass.ts'
-import { exitRenderPass } from '../runtime/exitRenderPass.ts'
-import type { Scope } from '../types/Scope.ts'
-
-/*
-The shared mount core every page/layout/component build path runs (`mount`, `hydrate`,
-`fillRange`, `mountRange`, `fillBoundary`). Establishes the layer's lexical scope nested
-under the current one in `awaiting` mode — so it adopts the model doc its first `doc()`
-creates — brackets a render pass — so its `await`/`try` block ids draw from the shared
-counter in SSR-stream order — runs `build`, then restores the previous scope (synchronous
-build, so the restore is exact). `build` returns its reactivity stopper (from `scope` or
-`fillBefore`), which the lexical scope ADOPTS (`own`) so the scope has a single teardown:
-the caller wraps its own DOM teardown (clear host vs clear range) around one
-`lexical.dispose()`, no longer composing a separate `stop()` at every site.
-*/
-export function withScope(build: () => () => void): { lexical: Scope } {
-    const parentScope = CURRENT_SCOPE.current
-    const lexical = createScope({}, parentScope, true)
-    enterRenderPass()
-    CURRENT_SCOPE.current = lexical
-    try {
-        lexical.own(build())
-    } catch (error) {
-        /* `build` threw before returning its stopper — e.g. a hydration desync in one of
-           several sibling blocks. `own` never ran, so nothing downstream will dispose this
-           lexical scope; tear it down here (its child scopes/effects created before the
-           throw) before rethrowing, rather than leaking a live, unreachable scope. */
-        lexical.dispose()
-        throw error
-    } finally {
-        exitRenderPass()
-        CURRENT_SCOPE.current = parentScope
-    }
-    return { lexical }
-}

package/src/lib/ui/dom/withSuspense.ts

@@ -1,22 +0,0 @@
-import { SuspenseSignal } from '../runtime/SuspenseSignal.ts'
-
-/*
-Runs `read`, returning `fallback` when it SUSPENDS — a pending blocking `await` read throws a
-`SuspenseSignal` (ADR-0042). The reading region shows `fallback` until the value resolves; the
-throwing read subscribed the enclosing effect to the cell, so the effect re-runs and fills in on
-settle. Any non-suspense error propagates unchanged (a real rejection still reaches `{#try}`). The
-single place the `instanceof SuspenseSignal` swallow lives for a value-returning bind, so the read
-sites (`each`, `watch`, …) share one definition rather than copying the try/catch. Text binds use
-the sibling `readTextOrSuspend` (fallback `''` with String coercion); an attribute leaves itself
-unset inline (a side effect, not a fallback value).
-*/
-export function withSuspense<T>(read: () => T, fallback: T): T {
-    try {
-        return read()
-    } catch (signal) {
-        if (!(signal instanceof SuspenseSignal)) {
-            throw signal
-        }
-        return fallback
-    }
-}

package/src/lib/ui/dom/writeCell.ts

@@ -1,22 +0,0 @@
-import { isAsyncCell } from '../../shared/isAsyncCell.ts'
-import type { AsyncState } from '../../shared/types/AsyncState.ts'
-
-/*
-Unified write for a `linked` reference the compiler lowers to `$$writeCell(NAME, value)`
-from an author assignment (`draft = x`, `draft += 1`, `draft++`). The read side is
-`$$readCell` — a call, so not an assignable target — which is why an assignment to a
-`linked` binding needs its own lowering. A `linked` cell is a writable `State` for a
-sync seed (write `.value`) or a writable `AsyncState` for an async/stream seed (write
-`.set(value)`, which latches until the next reseed); one write shape covers both, so
-codegen never branches on the seed kind. Returns `value` so the lowered assignment still
-evaluates to the written value in expression position (`a = b = draft = x`).
-*/
-// @documentation plumbing
-export function writeCell(cell: unknown, value: unknown): unknown {
-    if (isAsyncCell(cell)) {
-        ;(cell as AsyncState<unknown>).set(value)
-    } else {
-        ;(cell as { value: unknown }).value = value
-    }
-    return value
-}

package/src/lib/ui/effect.ts

@@ -1,24 +0,0 @@
-import { CURRENT_SCOPE } from './runtime/CURRENT_SCOPE.ts'
-import { createEffectNode } from './runtime/createEffectNode.ts'
-import { inScope } from './runtime/inScope.ts'
-import type { EffectResult } from './runtime/types/EffectResult.ts'
-
-/*
-Runs `fn` now, capturing every reactive cell it reads, then re-runs it whenever
-any of those change. `fn` may return a teardown — run before each re-run and on
-dispose — and may be async (its teardown then runs once the promise settles, but
-only the reads before its first `await` are tracked). Returns a dispose that runs
-the final teardown and detaches it from the graph. This is abide's from-scratch
-effect primitive: the open-on-first-read / close-on-last-reader lifecycle,
-grounded in abide's own reactive core. Imported and called bare
-(`import { effect } from '@abide/abide/ui/effect'`); the compiler resolves the import
-binding (alias-safe) and the SSR back-end strips the call (effects are client
-lifecycle). Generated binding code also calls it directly.
-*/
-// @documentation plumbing
-export function effect(fn: () => EffectResult): () => void {
-    /* Re-runs fire after the build, so pin the scope this effect was created under
-       (the dep-tracking observer is managed separately, so this can't disturb it). */
-    const captured = CURRENT_SCOPE.current
-    return createEffectNode(() => inScope(captured, fn))
-}

package/src/lib/ui/enterScope.ts

@@ -1,18 +0,0 @@
-import { createScope } from './createScope.ts'
-import { CURRENT_SCOPE } from './runtime/CURRENT_SCOPE.ts'
-import type { Scope } from './types/Scope.ts'
-
-/*
-Establishes a fresh lexical scope for an SSR render and returns the previous one
-to restore (see `exitScope`). The client gets its per-component scope from
-`mount`/`hydrate`; a server render has no mount, so its body brackets itself with
-`enterScope`/`exitScope` — each render (and each nested child render) owns an
-isolated scope, so `scope()` and `model` don't bleed across renders. Nests via the
-returned previous, like `mount`'s save/restore.
-*/
-// @documentation plumbing
-export function enterScope(): Scope | undefined {
-    const previous = CURRENT_SCOPE.current
-    CURRENT_SCOPE.current = createScope({}, previous, true)
-    return previous
-}

package/src/lib/ui/exitScope.ts

@@ -1,8 +0,0 @@
-import { CURRENT_SCOPE } from './runtime/CURRENT_SCOPE.ts'
-import type { Scope } from './types/Scope.ts'
-
-/* Restores the scope `enterScope` saved, closing an SSR render's scope. */
-// @documentation plumbing
-export function exitScope(previous: Scope | undefined): void {
-    CURRENT_SCOPE.current = previous
-}

package/src/lib/ui/finalizeStreamedChildren.ts

@@ -1,88 +0,0 @@
-import type { FlightPromise } from './flight.ts'
-import type { ResumeEntry } from './runtime/RESUME.ts'
-import type { SsrAwait, SsrRender } from './runtime/types/SsrRender.ts'
-
-/* One hoistable child render staged by generateSSR: the reserved index in its output array, the
-   array itself, the child's render-path (the streamed boundary id), and its in-flight render. */
-export type StagedChild = {
-    slot: number
-    out: string[]
-    id: string
-    flight: FlightPromise
-}
-
-/*
-The ADR-0039 WHEN-TO-STREAM decision, run once after a component's body walk (compileSSR emits
-`await $$finalizeStreamedChildren($childSlots, $awaits, $resume)` before the render returns). Each
-hoistable child was started as an isolated `$$flight` in the prefix and its output position RESERVED
-(an empty `$out` slot); here we fill that slot per child:
-
-- A flight that has already SETTLED (a synchronous / warm-cache child, or a fast read) inlines its
-  html into the reserved slot in the child's addressed `abide:c:CHILDPATH` boundary (ADR-0049) —
-  the same shape `generateSSR`'s non-hoistable inline path emits, so an all-fast page adopts and
-  recovers uniformly. Its awaits / resume merge exactly as the inline path did.
-- A flight settled REJECTED rethrows here — same as a rejecting inline await (500 before flush).
-- A still-PENDING flight (genuine I/O) STREAMS: the slot gets an empty `abide:await:CHILDPATH`
-  boundary, and an html-only SsrAwait is pushed so `renderToStream` flushes the shell now and streams
-  the child's fragment when it settles (its own nested awaits/resume compose through the same drain).
-
-Timing: one microtask drain settles every synchronous child; a single shared macrotask is paid ONLY
-if some child is still pending after that (a page whose children are all fast never reaches it), so
-the inline fast path costs one microtask and a genuinely-slow child — which was going to block the
-shell anyway — trades ~one tick for a progressively-flushed shell.
-*/
-// @documentation plumbing
-export async function finalizeStreamedChildren(
-    slots: StagedChild[],
-    awaits: SsrAwait[],
-    resume: Record<string, ResumeEntry>,
-): Promise<void> {
-    if (slots.length === 0) {
-        return
-    }
-    await Promise.resolve()
-    if (slots.some((staged) => !staged.flight.settled)) {
-        await new Promise<void>((resolve) => setTimeout(resolve, 0))
-    }
-    for (const staged of slots) {
-        if (staged.flight.settled && staged.flight.error === undefined) {
-            const rendered = staged.flight.value as SsrRender
-            /* Inline the settled html in the child's ADDRESSED boundary (ADR-0049) — the same
-               `abide:c:CHILDPATH` shape `generateSSR`'s non-hoistable path emits, so the client's
-               `mountChild` adopts a hoistable-settled and a non-hoistable child identically (it can't
-               know which the server chose) and either recovers at this boundary on a desync. */
-            staged.out[staged.slot] =
-                `<!--abide:c:${staged.id}-->${rendered.html}<!--/abide:c:${staged.id}-->`
-            mergeChildRender(rendered, awaits, resume)
-        } else if (staged.flight.settled) {
-            throw staged.flight.error
-        } else {
-            staged.out[staged.slot] =
-                `<!--abide:await:${staged.id}--><!--/abide:await:${staged.id}-->`
-            awaits.push({
-                id: staged.id,
-                htmlOnly: true,
-                promise: () => staged.flight,
-                // biome-ignore lint/suspicious/noThenProperty: `then` is the SsrAwait renderer callback the stream drain invokes explicitly with the resolved value — this object is stored in `awaits[]`, never awaited as a thenable
-                then: async (rendered) => {
-                    mergeChildRender(rendered as SsrRender, awaits, resume)
-                    return (rendered as SsrRender).html
-                },
-            })
-        }
-    }
-}
-
-/* Fold a child render's contribution (its nested awaits, its resume map) up into the parent's — the
-   single definition both the inlined-settled arm and the still-pending stream arm merge through, so
-   the two can never drift on what a child contributes upward. */
-function mergeChildRender(
-    rendered: SsrRender,
-    awaits: SsrAwait[],
-    resume: Record<string, ResumeEntry>,
-): void {
-    for (const nested of rendered.awaits) {
-        awaits.push(nested)
-    }
-    Object.assign(resume, rendered.resume)
-}

package/src/lib/ui/flight.ts

@@ -1,56 +0,0 @@
-/*
-Server-only flight-starter behind the SSR codegen's `$$flight` alias (ADR-0034). The
-SSR back-end hoists a *hoistable* await's promise into the synchronous render prefix as
-`const $flightN = $$flight(() => (<promise expr>))`, so the flight is already in-flight
-when the body walk reaches its blocking `await $flightN` / streaming `promise: () =>
-$flightN` — independent flights overlap instead of serializing (prefix → barrier → body
-→ drain). Server-only: the client build never emits `$$flight`, so it tree-shakes out of
-the browser bundle (like `$$settleAsyncCells`).
-
-Two behaviours the raw promise expression can't provide on its own:
-
-- A SYNCHRONOUS throw in the loader (before it returns a promise) is normalised to a
-  rejected promise, so a hoisted flight's throw still lands in the block's `{:catch}` /
-  500 path exactly as an inline `await (expr)` would — the expression no longer evaluates
-  inside the block's try/catch, so the thunk wrapper restores that reach.
-- The settledness `.then(onValue, onError)` below is itself a rejection handler attached
-  synchronously to `promise`, so a flight that rejects in the window before its real
-  consumer (the inline await / the `renderToStream` drain) attaches a handler is never a
-  Bun-fatal unhandled rejection — the `onError` branch never rethrows, so the block's
-  surface-rejection → 500 / catch-branch semantics are unchanged. Mirrors the inline
-  `.then(onValue, onError)` guard in `createAsyncCell`.
-*/
-// @documentation plumbing
-export function flight(thunk: () => unknown): FlightPromise {
-    let promise: Promise<unknown>
-    try {
-        promise = Promise.resolve(thunk())
-    } catch (error) {
-        promise = Promise.reject(error)
-    }
-    /* Synchronous settledness signal (ADR-0039): the post-walk `finalizeStreamedChildren` reads
-       `.settled` to decide inline-vs-stream — a child flight that already resolved by finalize time
-       inlines its html into the shell (byte-identical to today), a still-pending one streams. Its
-       `onError` branch doubles as the rejection keeper (see the header note): it marks `promise`
-       handled, so a pre-consumer rejection is never a Bun-fatal unhandled rejection. */
-    const flightPromise = promise as FlightPromise
-    flightPromise.settled = false
-    promise.then(
-        (value) => {
-            flightPromise.value = value
-            flightPromise.settled = true
-        },
-        (error) => {
-            flightPromise.error = error
-            flightPromise.settled = true
-        },
-    )
-    return flightPromise
-}
-
-/* A flight promise carrying a synchronous settledness snapshot for `finalizeStreamedChildren`. */
-export type FlightPromise = Promise<unknown> & {
-    settled: boolean
-    value?: unknown
-    error?: unknown
-}