@solidjs/web 2.0.0-beta.22 → 2.0.0-beta.24

package/types/server-functions/client.d.ts

@@ -81,6 +81,30 @@ export interface ServerFunctionsClientConfig {
    * ```
    */
   prepareRequest?: PrepareRequestHook;
+  /**
+   * Response-side integration seam — the client mirror of the handler's
+   * `transformResult`. `handle(response, ctx)` sees every response before
+   * the transport decodes it; returning anything but undefined resolves the
+   * call with that value. `capture(info)` runs synchronously at the call
+   * site (before any await) and its return arrives as `ctx.context`, so
+   * ambient per-call state (e.g. a reactive owner) survives to response
+   * time. See `createServerComponentHandler` in frame-transport for the
+   * canonical implementation.
+   */
+  responseHandler?: {
+    capture?(info: { id: string; meta: unknown }): unknown;
+    handle(
+      response: Response,
+      ctx: { id: string; meta: unknown; args: unknown[]; context: unknown }
+    ): unknown;
+  };
+  /**
+   * Encoder for argument lists JSON can't carry faithfully. JSON-safe args
+   * always go as plain JSON (no codec in the bundle); anything else throws
+   * unless this is set. Installed by `enableRichArguments()` from the
+   * rich-args entry — set directly only for custom wire encodings.
+   */
+  serializeArgs?(args: unknown[]): string | Promise<string>;
 }
 
 /**

package/types/server-functions/server.d.ts

@@ -102,6 +102,23 @@ export interface ServerFunctionsServerConfig {
    * router); per-handler `collectFlightData` options override it.
    */
   collectFlightData?: CollectFlightDataHook;
+  /**
+   * Server-wide default for the handler's `transformResult` (same contract
+   * — see `HandleServerFunctionRequestOptions`); a per-request option
+   * overrides it. Registering it here makes result policies (e.g. frames'
+   * `frameTransformResult`) work through generic dispatchers that call
+   * `handleServerFunctionRequest(request)` with no options.
+   */
+  transformResult?(
+    event: ServerFunctionEvent,
+    result: unknown,
+    context: { instance: string | null; request: Request; thrown?: boolean }
+  ): unknown | ResponseEnvelope | Promise<unknown | ResponseEnvelope>;
+  /**
+   * The in-process mirror of `transformResult` for direct (same-server)
+   * calls during document SSR — e.g. frames' `frameTransformDirectResult`.
+   */
+  transformDirectResult?(value: unknown, options: { id: string }): unknown;
   /**
    * Endpoint the HTTP handler is mounted on, used for the `url` of SSR'd
    * references (e.g. form actions) — must match the client configuration.

package/types/server-functions/shared.d.ts

@@ -369,3 +369,20 @@ export function decodeResponse<T = unknown>(
   response: Response,
   codecOptions?: JSONCodecOptions
 ): Promise<T | undefined>;
+
+/**
+ * Frame one payload for the server-function wire: a `;0x<len32>;` length
+ * prefix followed by the utf-8 data. Both transports (server-function
+ * responses and frame streams) share this framing.
+ */
+export function createChunk(data: string): Uint8Array;
+
+/**
+ * Incremental decoder for `createChunk` framing over a byte stream: `next()`
+ * yields one complete payload string per call (async-iterator result shape),
+ * buffering partial frames internally until their length prefix is satisfied.
+ */
+export class ChunkReader {
+  constructor(stream: ReadableStream<Uint8Array>);
+  next(): Promise<{ done: boolean; value: string | undefined }>;
+}

package/types/server.d.ts

@@ -212,6 +212,8 @@ export function setAttributeNS(node: Element, namespace: string, name: string, v
 export function registerElementClaim(handler: (element: Element) => void): () => void;
 /** Server no-op: returns `node` unchanged. Claims never fire during SSR. */
 export function claimElement<T extends Element>(node: T): T;
+/** Server no-op: returns `root` unchanged. Claims never fire during SSR. */
+export function claimElementTree<T extends Node>(root: T): T;
 
 /** @deprecated not supported on the server side */
 export function addEvent(node: Element, name: string, handler: () => void, delegate: boolean): void;

package/types-cjs/client.d.cts

@@ -84,6 +84,14 @@ export function registerElementClaim(handler: (element: Element) => void): () =>
  * Emitted by the compiler at element creation; idempotent by contract.
  */
 export function claimElement<T extends Element>(node: T): T;
+/**
+ * Sweep-claim every navigation-relevant element (`a[href]`, `form[action]`)
+ * in `root` — the subtree equivalent of the per-element `claimElement`
+ * compiled output emits, for content that becomes live DOM without compiled
+ * creation code (frame streams, adopted SSR ranges). Dormant without a
+ * registered consumer.
+ */
+export function claimElementTree<T extends Node>(root: T): T;
 export function className(node: Element, value: JSX.ClassValue, prev?: JSX.ClassValue): void;
 export function setProperty(node: Element, name: string, value: any): void;
 export function setStyleProperty(node: Element, name: string, value: any): void;

package/types-cjs/core.d.cts

@@ -1,3 +1,4 @@
-export { getOwner, runWithOwner, createComponent, createRoot as root, sharedConfig, untrack, merge as mergeProps, flatten, ssrHandleError, ssrScope } from "solid-js";
+export { getOwner, runWithOwner, createComponent, createRoot as root, sharedConfig, untrack, merge as mergeProps, flatten, ssrHandleError, ssrScope, NoHydration, Hydration } from "solid-js";
 export declare const effect: (fn: any, effectFn: any, options: any) => void;
 export declare const memo: (fn: any) => import("solid-js").SourceAccessor<any>;
+export declare const runWithHydrationScope: (id: any, fn: any) => unknown;

package/types-cjs/frames/client.d.cts

@@ -0,0 +1,53 @@
+/**
+ * @solidjs/web/frames — client half. Consume frame streams into live DOM
+ * boundaries. There is deliberately no server-component API here beyond
+ * `installServerComponents()`: `dynamic` + server functions IS the client
+ * surface — a server-function call whose response is a frame stream
+ * resolves with a stable per-call-site component.
+ *
+ * Copied next to the runtime's frame d.ts files at publish (see
+ * types:copy-frames), so the relative imports below resolve in-place.
+ */
+export {
+  createFrame,
+  createFrameHost,
+  createFrameInsertable,
+  FRAME_APPLIED_EVENT
+} from "./frame-client.cjs";
+export type {
+  Frame,
+  FrameChunk,
+  FrameHost,
+  FrameHostOptions,
+  FrameOptions,
+  FrameWrite,
+  Slot,
+  SlotContext
+} from "./frame-client.cjs";
+export {
+  FRAME_STREAM_HEADER,
+  applyFrameResponse,
+  isFrameStreamResponse,
+  createServerComponentHandler
+} from "./frame-transport.cjs";
+export { createJSONDataTable } from "./serializer.cjs";
+export type { JSONDataTable } from "./serializer.cjs";
+
+import type { FrameHost } from "./frame-client.cjs";
+
+/**
+ * The app-wide frame host (created on first use): one chunk router, with
+ * codec data tables rotated per response — deserializer cross-reference
+ * space is stream-scoped by contract.
+ */
+export function getFrameHost(): FrameHost;
+
+/**
+ * Installs the server-component transport policy on the server-function
+ * client: boundary identity derives from the reactive owner captured at the
+ * call site, frame-stream responses resolve to stable per-call-site
+ * components, and document-SSR boundaries adopt their server-rendered
+ * ranges. Call once in the client entry (the package is sideEffects:false —
+ * a bare import would be tree-shaken); call again to rebind a custom host.
+ */
+export function installServerComponents(host?: FrameHost): void;

package/types-cjs/frames/frame-client.d.cts

@@ -0,0 +1,222 @@
+/**
+ * Client frame runtime — the consumer side of a frame stream. A frame
+ * renders server-owned content into a DOM boundary from a resident keyed
+ * record store: chunks are writes, not events, so application is
+ * prerequisite-driven and order-independent. Client-owned slot ranges
+ * inside the boundary are preserved across server updates — the
+ * version is a stale-guard only ("policy A"): newer content morphs in
+ * place, and teardown is `dispose()`, never a version bump.
+ */
+
+/** One transport chunk of a frame stream, addressed by frame `id`. */
+export type FrameChunk =
+  | { type: "start"; id: string; version: number }
+  | { type: "html"; id: string; version: number; html: string }
+  | { type: "fragment"; id: string; version: number; key: string; html: string }
+  | {
+      type: "reveal";
+      id: string;
+      version: number;
+      keys: string[];
+      waitForStyles?: boolean;
+      fallback?: boolean;
+    }
+  | {
+      type: "data";
+      id: string;
+      version: number;
+      key?: string;
+      node?: unknown;
+      initial?: boolean;
+      /** Eval-style hydration script — only when produced with the hydration serializer. */
+      payload?: string;
+    }
+  | {
+      type: "assets";
+      id: string;
+      version: number;
+      key: string;
+      modules?: string[];
+      styles?: string[];
+      inlineStyles?: { id: string; content?: string; attrs?: Record<string, string> }[];
+    }
+  | { type: "slot"; id: string; version: number; key: string; args: Record<string, unknown> }
+  | { type: "template"; id: string; version: number; key: string; html: string; fields: string[] }
+  | {
+      type: "block";
+      id: string;
+      version: number;
+      key: string;
+      template: string;
+      values: unknown[];
+    }
+  | { type: "complete"; id: string; version: number }
+  | { type: "error"; id: string; version: number; key?: string; error: unknown };
+
+/**
+ * Maps a wire chunk onto resident-store record writes. `data` chunks map to
+ * no records — they are response-scoped and the host applies them through
+ * its data hook.
+ */
+export function chunkToRecords(chunk: FrameChunk): Record<string, unknown>;
+
+/**
+ * One store write applied to a frame: `r` maps record keys to values
+ * (`chunkToRecords` produces these from wire chunks) and `version` is the
+ * stream stamp — an older version than the frame's current one is ignored.
+ */
+export interface FrameWrite {
+  version: number;
+  r: Record<string, unknown>;
+}
+
+/** Context passed to a slot callback. */
+export interface SlotContext {
+  /**
+   * True only for the hydration-attach invocation of an adopted
+   * document-SSR range — the one call a consumer may answer with a claim
+   * (`existing` IS the server-rendered output for these args). Unset on
+   * stream-driven re-calls: those must render for real, or content the
+   * re-call displaced (e.g. `{$frame}` region ranges) is dropped.
+   */
+  adopted?: boolean;
+  /**
+   * Register cleanup for when this occurrence's range is removed from the
+   * server content, or the owning frame is disposed.
+   */
+  onCleanup(fn: () => void): void;
+  /**
+   * The range's current interior — server-rendered client content on an
+   * adopted document-SSR boot, or the previous output on a re-call. A
+   * framework binding hydrates onto it and returns `undefined` to claim it
+   * in place (zero DOM mutation).
+   */
+  existing: ChildNode[];
+}
+
+/**
+ * Client content for a server-declared slot. Direct-insert occurrences
+ * call it with empty props; render-prop occurrences pass the occurrence's
+ * resolved args (primitives literal, `{$ref}` data resolved through the
+ * host, `{$frame}` regions as marker-range fragments). Return nodes to fill
+ * the range, or `undefined` to claim `ctx.existing` untouched.
+ */
+export type Slot = (props: Record<string, unknown>, ctx: SlotContext) => Node | Node[] | undefined;
+
+export interface Frame {
+  /** Merge a write into the store and flush (morph/reveal/slot sync). */
+  apply(write: FrameWrite): void;
+  /** The active version, or undefined before the first apply. */
+  readonly version: number | undefined;
+  /** Read-only view of the resident record store. */
+  readonly store: Readonly<Record<string, unknown>>;
+  /** The stream's error record, if an `error` chunk arrived. */
+  readonly error: unknown;
+  /** Whether the named fragment has been revealed into the boundary. */
+  isRevealed(segment: string): boolean;
+  /** Tear down: slot cleanups cascade, later chunks are ignored. Idempotent. */
+  dispose(): void;
+}
+
+/**
+ * Routes a flat stream of addressed chunks to frames by id, buffering chunks
+ * for frames that have not registered yet (only the newest version's chunks
+ * are kept). `data` chunks are response-scoped and go to `applyData`.
+ *
+ * An id may have several frames (the same server component mounted more
+ * than once): chunks fan out to all of them, and a frame registering after
+ * delivery is seeded from a sibling's store.
+ */
+export interface FrameHost {
+  register(id: string, frame: Frame): void;
+  /** Remove one frame (or all frames of the id when `frame` is omitted). */
+  unregister(id: string, frame?: Frame): void;
+  apply(chunk: FrameChunk): void;
+  /** The first registered frame under the id, if any. */
+  get(id: string): Frame | undefined;
+  serialize(value: unknown): { $ref: string };
+  /** `frameId` is the resolving frame's id — route to its stream's table. */
+  resolve(ref: { $ref: string }, frameId?: string): unknown;
+}
+
+/**
+ * The bubbling DOM event (`"frame:applied"`) a frame dispatches from its
+ * parent element whenever server content lands in the document — root
+ * materialize/morph, segment reveal, fallback materialization — with
+ * `detail: { id, version, reason }`. One document-level listener sees every
+ * boundary (nested region frames dispatch too); use it to re-apply
+ * client-owned decorations on server-owned markup (router affordance
+ * reflection, e.g. `aria-current`) without a MutationObserver.
+ */
+export const FRAME_APPLIED_EVENT: "frame:applied";
+
+/** Options for `createFrameHost`. */
+export interface FrameHostOptions {
+  /**
+   * Backs `{$ref}` slot args (typically a codec data table's `resolve`).
+   * `frameId` identifies the resolving frame — data tables are
+   * response-scoped, so multi-stream hosts route by it (nested region ids
+   * prefix-match their root).
+   */
+  resolve?(ref: { $ref: string }, frameId?: string): unknown;
+  /** Test/host-side counterpart of `resolve`. */
+  serialize?(value: unknown): { $ref: string };
+  /**
+   * Receives each `data` chunk whole. Wire a codec table:
+   * `applyData: c => table.apply(c)` (see `createJSONDataTable`).
+   */
+  applyData?(chunk: Extract<FrameChunk, { type: "data" }>): void;
+}
+
+export function createFrameHost(options?: FrameHostOptions): FrameHost;
+
+/** Options for `createFrame` / `createFrameInsertable`. */
+export interface FrameOptions {
+  /** Register with this host under `id`, receiving routed/buffered chunks. */
+  host?: FrameHost;
+  id?: string;
+  /** Client content keyed by prop name (occurrences resolve by prop). */
+  slots?: Record<string, Slot>;
+  /**
+   * Adopt existing server-rendered DOM: the first apply morphs against it,
+   * and slots sync immediately (hydration attach) — a document-SSR boot
+   * needs no chunk.
+   */
+  adopt?: boolean;
+  /** Called after each apply flush (tests/telemetry). */
+  onApply?(info: { version: number; reason: "materialize" | "morph" | "reveal" }): void;
+  /**
+   * Wraps element-claim sweeps (`a[href]`/`form[action]` in materialized
+   * server content — and only those) so claim consumers register their
+   * per-element cleanup against the boundary's reactive owner, e.g.
+   * `fn => runWithOwner(owner, fn)`. Nested region frames inherit it.
+   * Without it, sweeps run under whatever owner is current (none, for
+   * streamed chunks).
+   */
+  ownerScope?<T>(fn: () => T): T;
+}
+
+/** A frame rendering into an element boundary. */
+export function createFrame(boundary: Element, options?: FrameOptions): Frame;
+
+/**
+ * A branded frame-insertable value: the client runtime's `insert` recognizes
+ * it (registered `$$FRAME` symbol) and calls the mount handler the value
+ * carries — a comment range is established at the insertion point and a
+ * host-registered frame binds to it. One static mount per value; lifecycle
+ * belongs to the creator via `dispose()` (register it with your owner's
+ * cleanup).
+ */
+export function createFrameInsertable(options: FrameOptions): {
+  readonly frame: Frame | null;
+  dispose(): void;
+};
+
+/**
+ * Binds a frame to an EXISTING marker range — the document-SSR adoption
+ * path: the page already holds the server-rendered boundary between
+ * `frame:<id>:start`/`:end` comments; the frame constructed over it treats
+ * that content as its own (first stream morphs rather than materializes)
+ * and slots sync immediately, claiming their server-rendered DOM.
+ */
+export function adoptFrameRange(start: Comment, end: Comment, options?: FrameOptions): Frame;

package/types-cjs/frames/frame-sink.d.cts

@@ -0,0 +1,145 @@
+import { FrameChunk } from "./frame-client.cjs";
+
+/** Addresses a frame stream: the boundary id and this response's version. */
+export interface FrameAddress {
+  id: string;
+  version: number;
+}
+
+/**
+ * The emission surface `renderToStream` routes through when producing a
+ * frame stream instead of a document (see the `sink` render option). Each
+ * method emits transport-agnostic chunks; `emit` is the envelope boundary.
+ * @internal Compiler/renderer wiring — use `renderToFrameStream` or
+ * `renderServerComponent` instead.
+ */
+export function createFrameSink(
+  emit: (chunk: FrameChunk) => void,
+  frame: FrameAddress
+): Record<string, (...args: any[]) => void>;
+
+/** Options shared by the frame producers. */
+export interface FrameStreamOptions {
+  /** Boundary address; defaults to `{ id: "", version: 1 }`. */
+  frame?: { id?: string; version?: number };
+  /** Remaining `renderToStream` options (plugins, onError, manifest, ...). */
+  [key: string]: unknown;
+}
+
+/** A produced frame stream: pipe chunks, or await the collected array. */
+export interface FrameStream extends PromiseLike<FrameChunk[]> {
+  pipe(writable: { write(chunk: FrameChunk): void; end?(): void }): void;
+}
+
+/**
+ * Render to a FrameChunk stream: the same render core as `renderToStream`
+ * with emission swapped to the frame sink and the document writable replaced
+ * by a chunk envelope (`start` up front, `complete` at stream end). Data
+ * records default to the keyed JSON codec (decode with
+ * `createJSONDataTable`).
+ */
+export function renderToFrameStream(code: () => unknown, options?: FrameStreamOptions): FrameStream;
+
+/**
+ * Render a **server component** — a `props => JSX` function, typically
+ * returned from a server function — to a FrameChunk stream. `props` is a
+ * slot-props proxy, not data:
+ *
+ * - reading a prop as a child emits a marker range the client fills;
+ * - calling a prop as a render function emits a `slot` chunk for a fresh
+ *   occurrence (a primitive `$key` arg names it, so client state follows the
+ *   entity across responses — the slot-level analogue of For's `keyed`
+ *   function; positional otherwise, which is the right default for most
+ *   flows);
+ * - primitive args ride the chunk; server JSX args stream as nested regions
+ *   (`{$frame}` — html once, never data); other values serialize as `{$ref}`
+ *   data records with referential dedupe.
+ *
+ * The props a *client* passes never reach the server — server inputs are the
+ * function's arguments.
+ */
+export function renderServerComponent(
+  component: (props: Record<string, any>) => unknown,
+  options?: FrameStreamOptions
+): FrameStream;
+
+/**
+ * The slot props proxy used by `renderServerComponent`. Every key
+ * virtually exists (`in` is always true — a prop is a position the client
+ * may fill), enumeration is empty by design, and serialization goes through
+ * the live render context, so it must only be used during the frame's
+ * render.
+ * @internal Exposed for framework bindings composing their own producers.
+ */
+export function createSlotProps(
+  sink: ReturnType<typeof createFrameSink>,
+  frame: FrameAddress
+): Record<string, any>;
+
+/**
+ * A server component as an HTTP Response: the chunk stream framed with the
+ * server-function wire convention, tagged `X-Frame-Stream: <frame id>` for
+ * the client and `X-Content-Raw` so the server-function handler forwards it
+ * untouched. `init` (headers/status, e.g. from a `respond()` envelope)
+ * merges in; the frame tags win on conflict.
+ */
+export function serverComponentResponse(
+  component: (props: Record<string, any>) => unknown,
+  options?: FrameStreamOptions,
+  init?: { headers?: HeadersInit; status?: number }
+): Response;
+
+/**
+ * The server-component convention as a `transformResult` policy for
+ * `handleServerFunctionRequest`: a function result — or a `respond()`
+ * envelope whose value is a function — becomes a frame-stream Response,
+ * with the frame id defaulting to the server function's id so repeat calls
+ * target the same client boundary. Everything else passes through.
+ *
+ * @example
+ * ```ts
+ * handleServerFunctionRequest(request, {
+ *   transformResult: frameTransformResult,
+ *   provideEvent
+ * });
+ * ```
+ */
+export function frameTransformResult(event: unknown, result: unknown): unknown;
+
+// === Document SSR (t = 0) ===
+
+/**
+ * Document-mode slot props — the t = 0 counterpart of
+ * `createSlotProps`: the server component renders INLINE in the
+ * document and the client's real props render server-side inside its
+ * positions (the one hydration-time exception), wrapped in the same marker
+ * dialect the chunk producer emits so the adopting client binds slots and
+ * regions onto the server-rendered ranges.
+ */
+export function createDocumentSlotProps(
+  clientProps: Record<string, unknown>,
+  frameId: string
+): Record<string, unknown>;
+
+/**
+ * The in-process mirror of `frameTransformResult` for DOCUMENT SSR: install
+ * as `configureServerFunctionsServer({ transformDirectResult })` and a
+ * direct (same-process) server-function result that is a function comes back
+ * as an inline-renderable server component (frame markers + document
+ * slot props). Non-function results pass through.
+ */
+export function frameTransformDirectResult<T>(value: T, options: { id: string }): T;
+
+/**
+ * Seroval plugin for the hydration serializer: writes an inline server
+ * component as a stable per-function-id placeholder reference
+ * (`self._$SC.r(id)`) instead of meeting an unserializable function.
+ */
+export const ServerComponentPlugin: unknown;
+
+/**
+ * Inline bootstrap for the document shell: installs the `self._$SC`
+ * placeholder registry the hydration references resolve through; the client
+ * upgrades it via `installServerComponents()`.
+ */
+export const SERVER_COMPONENT_BOOTSTRAP: string;

package/types-cjs/frames/frame-transport.d.cts

@@ -0,0 +1,106 @@
+import { FrameChunk, FrameHost } from "./frame-client.cjs";
+
+/**
+ * Header tagging a Response as a frame stream; its value is the producing
+ * frame's id. Frame-owned wire contract — deliberately not a server-function
+ * `BodyFormat` entry, since the body is frame chunks, not a serialized value.
+ */
+export const FRAME_STREAM_HEADER: "X-Frame-Stream";
+
+/** Whether a fetch Response carries a frame stream. */
+export function isFrameStreamResponse(response: Response): boolean;
+
+/** Options for `applyFrameResponse`. */
+export interface ApplyFrameResponseOptions {
+  /**
+   * Remap the producer's root frame id onto a local one — the id your
+   * insertable/frame registered under — so navigations to the same boundary
+   * reuse the same frame regardless of what the server called it. Boundary
+   * identity belongs to the client.
+   */
+  as?: string;
+  /**
+   * Restamp every chunk of the response with this version (one response IS
+   * one version). Versions belong to the client too: the producer cannot
+   * know how many streams a boundary has consumed, so pass the Nth-response
+   * counter to make policy A's stale-guard real across navigations.
+   */
+  version?: number;
+}
+
+/**
+ * Reads a frame-stream Response to completion, applying every chunk to
+ * `host`. Chunks are length-prefixed JSON over the server-function wire
+ * framing. Resolves with the id the chunks were applied under once the
+ * stream ends; rejects on a malformed or errored stream.
+ *
+ * @example
+ * ```ts
+ * const response = await getStory(id); // frame-tagged server function result
+ * if (isFrameStreamResponse(response)) {
+ *   await applyFrameResponse(response, host, { as: "story-pane" });
+ * }
+ * ```
+ */
+export function applyFrameResponse(
+  response: Response,
+  host: FrameHost,
+  options?: ApplyFrameResponseOptions
+): Promise<string>;
+
+/** Options for `createServerComponentHandler`. */
+export interface ServerComponentHandlerOptions<C = unknown> {
+  host: FrameHost;
+  /**
+   * Builds the framework's mountable component for a boundary. Invoked once
+   * per boundary and cached; every mount of the returned component is its
+   * own frame instance under the boundary id (multi-mount fans out).
+   */
+  component(frameId: string): C;
+  /**
+   * Runs synchronously at each server-function call site (before any
+   * await); its return is the call's ambient identity — e.g. Solid's
+   * `getOwner`. Calls sharing a captured context share one boundary.
+   */
+  capture?(info: { id: string; meta: unknown }): unknown;
+  /**
+   * A new response is about to stream into a boundary: rotate
+   * response-scoped state (codec data tables) here. `version` is the
+   * client-owned stream counter the chunks will be stamped with.
+   */
+  onStream?(frameId: string, version: number, response: Response): void;
+  /**
+   * Document-SSR adoption: given a boundary id the page already carries
+   * (server-rendered between `frame:<id>` markers), return the component
+   * that adopts that range — or `undefined` to stream normally. Consulted
+   * once per boundary, before any fetch.
+   */
+  documentComponent?(frameId: string): C | undefined;
+  /**
+   * Answer a call SYNCHRONOUSLY before any request is made (t = 0 local
+   * answers — e.g. a boundary the document already carries). Returning a
+   * non-undefined value resolves the call with it; a hydrating consumer
+   * never observes a pending beat.
+   */
+  intercept?(info: { id: string; meta: unknown; args: unknown[] }): C | undefined;
+}
+
+/**
+ * The client mirror of `frameTransformResult`, shaped for the server-function
+ * client's `responseHandler` seam: frame-stream responses resolve the call
+ * with a **stable component** instead of data, so an equals-gated consumer
+ * (Solid's `dynamic`) never remounts across refetches — the response streams
+ * into the boundary underneath as the only observable effect.
+ *
+ * Boundary identity is derived, never declared: contexts captured per call
+ * key a WeakMap of boundaries (dying with their call sites); ownerless calls
+ * fall back to one boundary per function id.
+ */
+export function createServerComponentHandler<C>(options: ServerComponentHandlerOptions<C>): {
+  capture?(info: { id: string; meta: unknown }): unknown;
+  intercept?(info: { id: string; meta: unknown; args: unknown[] }): C | undefined;
+  handle(
+    response: Response,
+    ctx: { id: string; meta: unknown; args: unknown[]; context: unknown }
+  ): C | undefined;
+};