@ggui-ai/iframe-runtime 0.1.0-rc.3 → 0.2.0-alpha.1

package/dist/status-dom.d.ts

@@ -1,72 +1,77 @@
 /**
- * In-iframe status DOM. Extracted from `runtime.ts` in B3b so the
- * channel-client handlers can import the `setStatus` + status-refs
- * helpers without a circular dep on the runtime module (which imports
- * the handlers for registration at boot).
+ * In-iframe runtime status surface.
  *
- * Operators see the boot state at a glance; failures land here with a
- * prefix that makes them grep-able in dev consoles.
+ * Used to inject a visible `<div data-ggui-status>` banner ("Initializing
+ * renderer…", "Connected", etc.) into the iframe body alongside the
+ * user-rendered React tree. End users saw it as a stray label above
+ * their UI — production-unfriendly. As of the displayMode-divergence
+ * close-out we route status transitions to `console.log` and inject ONLY
+ * the React mount-target div (no banner, no list-item placeholder text).
  *
- * The status DOM is a `<div data-ggui-status>` + `<ul data-ggui-stack>`
- * pair built once at boot and reused for the iframe's lifetime. The
- * `data-ggui-status` attribute carries a {@link StatusKind} value so
- * operator stylesheets + e2e specs can pin assertions against the
- * narrow union rather than reading the text content.
+ * Post-stack-removal (2026-05-27): the iframe holds exactly one mounted
+ * render for its lifetime. The `setConnectedStatus` helper no longer takes
+ * a stack-model arg — there's nothing to count — and the placeholder
+ * `<li data-ggui-stack-item>` render path is gone.
+ *
+ * The exported names (`setStatus`, `setConnectedStatus`, `StatusRefs`)
+ * are preserved so the channel handlers + runtime keep their import
+ * shape.
  */
-import type { StackModel } from './stack.js';
 /**
- * Closed union of values the `data-ggui-status` attribute carries.
+ * Closed union of values the iframe's status surface carries. Kept on
+ * the runtime side as the canonical state vocabulary even though it no
+ * longer surfaces visibly.
  *
- *   - `idle` — initial state before any boot IO. Default text reads
- *     "Initializing renderer…"; set by {@link ensureStatusDom}.
- *   - `initializing` — same as `idle` (legacy alias kept for the rare
- *     external CSS hook in `e2e/`).
+ *   - `idle` — initial state before any boot IO.
+ *   - `initializing` — legacy alias for `idle`.
  *   - `connecting` — ui/initialize fired or WS handshake in flight.
  *   - `connected` — first ack landed + every subsequent successful
- *     push. Text shows the live stack count.
- *   - `reconnecting` — WS dropped; the reconnect ladder is running.
- *   - `disconnected` — terminal close + ladder exhausted, or a graceful
- *     stop. Authors may layer reload UX here.
- *   - `upgrade-required` — version handshake failed; operator should
- *     upgrade the client.
- *   - `error` — every other failure (ui/initialize, bootstrap parse,
- *     WS handshake non-version).
+ *     push.
+ *   - `reconnecting` — WS dropped; reconnect ladder running.
+ *   - `disconnected` — terminal close + ladder exhausted.
+ *   - `upgrade-required` — version handshake failed.
+ *   - `error` — every other failure.
  *
- * Closed at this layer; new values require a code change here PLUS
- * any e2e specs / CSS that pattern-match against the attribute.
+ * Surfaces on `console.log` prefixed `[ggui:<state>]`; consumers
+ * (operators, e2e specs) MAY install a `console.log` interceptor or
+ * read `notifyParent('ggui:bootstrap-failed', …)` for failure paths.
  */
 export type StatusKind = 'idle' | 'initializing' | 'connecting' | 'connected' | 'reconnecting' | 'disconnected' | 'upgrade-required' | 'error';
 /**
- * Refs handed back from {@link ensureStatusDom}. Stays narrow (two
- * elements) so the channel handlers can close over them without
- * pulling other runtime state.
+ * Refs handed back from {@link ensureStatusDom}. `status` is a detached
+ * element kept for backward compatibility with channel handlers that
+ * still pass `refs.status` through; it is NEVER appended to the
+ * document, so production iframes carry no diagnostic banner. `stack`
+ * is the React mount target — appended to `document.body` so renderer
+ * wiring has a container.
  */
 export interface StatusRefs {
     readonly status: HTMLElement;
     readonly stack: HTMLElement;
 }
 /**
- * Build the minimum viable status DOM the runtime owns. Adopters can
- * style via the `data-ggui-status` / `data-ggui-stack` attributes; the
- * bundle ships zero CSS so hosts see only the structure.
+ * Build the React mount target. Reuses pre-existing `[data-ggui-stack]`
+ * if the shell already wrote one (cf. `buildSelfContainedShell`); else
+ * creates a fresh `<ul data-ggui-stack>` and appends it to `<body>`.
+ * The companion `status` element is created detached and never
+ * appended — consumers that still pass it through `StatusRefs` see no
+ * visible effect.
+ *
+ * The `<ul>` element name is preserved (legacy from the stack-of-N
+ * placeholder render path) but only ever holds a single React mount
+ * subtree post-stack-removal.
  */
 export declare function ensureStatusDom(doc: Document): StatusRefs;
 /**
- * Set the status text + the `data-ggui-status` attribute. Centralised
- * so every caller stays consistent across the runtime + the channel
- * handlers (push handler keeps the count fresh on every fold).
+ * Log a status transition. The element is mutated for backward compat
+ * (some tests still hold a `refs.status` reference), but production
+ * users never see it because the element is detached from `document`.
  */
 export declare function setStatus(refs: StatusRefs, text: string, state: StatusKind): void;
 /**
- * Convenience — render the `connected (N items)` status line based on
- * the current stack model size. Used by the push handler on every
- * successful upsert + by the boot sequence on first ack.
- */
-export declare function setConnectedStatus(refs: StatusRefs, model: StackModel): void;
-/**
- * Re-render the stack DOM into the placeholder element. Wraps the
- * standalone {@link renderStackInto} so callers can pass refs + model
- * without unpacking; the standalone export stays for the legacy
- * callers that have only the bare element in scope.
+ * Log the "connected" transition. Post-stack-removal the iframe always
+ * holds exactly one item; the message stays bare ("Connected.") since
+ * there's no count to surface. Consumers (devtools, e2e specs
+ * intercepting `console.log`) get a stable string on every push.
  */
-export declare function refreshStackDom(refs: StatusRefs, model: StackModel): void;
+export declare function setConnectedStatus(refs: StatusRefs): void;

package/dist/status-dom.js

@@ -1,51 +1,68 @@
-import { renderStackInto } from './stack.js';
 /**
- * Build the minimum viable status DOM the runtime owns. Adopters can
- * style via the `data-ggui-status` / `data-ggui-stack` attributes; the
- * bundle ships zero CSS so hosts see only the structure.
+ * In-iframe runtime status surface.
+ *
+ * Used to inject a visible `<div data-ggui-status>` banner ("Initializing
+ * renderer…", "Connected", etc.) into the iframe body alongside the
+ * user-rendered React tree. End users saw it as a stray label above
+ * their UI — production-unfriendly. As of the displayMode-divergence
+ * close-out we route status transitions to `console.log` and inject ONLY
+ * the React mount-target div (no banner, no list-item placeholder text).
+ *
+ * Post-stack-removal (2026-05-27): the iframe holds exactly one mounted
+ * render for its lifetime. The `setConnectedStatus` helper no longer takes
+ * a stack-model arg — there's nothing to count — and the placeholder
+ * `<li data-ggui-stack-item>` render path is gone.
+ *
+ * The exported names (`setStatus`, `setConnectedStatus`, `StatusRefs`)
+ * are preserved so the channel handlers + runtime keep their import
+ * shape.
+ */
+/**
+ * Build the React mount target. Reuses pre-existing `[data-ggui-stack]`
+ * if the shell already wrote one (cf. `buildSelfContainedShell`); else
+ * creates a fresh `<ul data-ggui-stack>` and appends it to `<body>`.
+ * The companion `status` element is created detached and never
+ * appended — consumers that still pass it through `StatusRefs` see no
+ * visible effect.
+ *
+ * The `<ul>` element name is preserved (legacy from the stack-of-N
+ * placeholder render path) but only ever holds a single React mount
+ * subtree post-stack-removal.
  */
 export function ensureStatusDom(doc) {
-    // Reuse pre-existing nodes if the thin shell wrote them — lets the
-    // shell inline a status line if it wants to.
-    const existingStatus = doc.querySelector('[data-ggui-status]');
     const existingStack = doc.querySelector('[data-ggui-stack]');
-    if (existingStatus !== null && existingStack !== null) {
-        return { status: existingStatus, stack: existingStack };
-    }
-    const root = doc.body;
+    const stack = existingStack ??
+        (() => {
+            const el = doc.createElement('ul');
+            el.setAttribute('data-ggui-stack', '');
+            doc.body.appendChild(el);
+            return el;
+        })();
+    // Detached placeholder so legacy `setStatus(refs, …)` calls have
+    // somewhere to write without touching the visible DOM. `aria-hidden`
+    // + zero size belt-and-braces in case any path appends it later.
     const status = doc.createElement('div');
     status.setAttribute('data-ggui-status', 'idle');
-    status.textContent = 'Initializing renderer…';
-    const stack = doc.createElement('ul');
-    stack.setAttribute('data-ggui-stack', '');
-    root.appendChild(status);
-    root.appendChild(stack);
+    status.setAttribute('aria-hidden', 'true');
     return { status, stack };
 }
 /**
- * Set the status text + the `data-ggui-status` attribute. Centralised
- * so every caller stays consistent across the runtime + the channel
- * handlers (push handler keeps the count fresh on every fold).
+ * Log a status transition. The element is mutated for backward compat
+ * (some tests still hold a `refs.status` reference), but production
+ * users never see it because the element is detached from `document`.
  */
 export function setStatus(refs, text, state) {
     refs.status.textContent = text;
     refs.status.setAttribute('data-ggui-status', state);
+    // eslint-disable-next-line no-console
+    console.log(`[ggui:${state}]`, text);
 }
 /**
- * Convenience — render the `connected (N items)` status line based on
- * the current stack model size. Used by the push handler on every
- * successful upsert + by the boot sequence on first ack.
- */
-export function setConnectedStatus(refs, model) {
-    const size = model.size();
-    setStatus(refs, `Connected (${size} item${size === 1 ? '' : 's'}).`, 'connected');
-}
-/**
- * Re-render the stack DOM into the placeholder element. Wraps the
- * standalone {@link renderStackInto} so callers can pass refs + model
- * without unpacking; the standalone export stays for the legacy
- * callers that have only the bare element in scope.
+ * Log the "connected" transition. Post-stack-removal the iframe always
+ * holds exactly one item; the message stays bare ("Connected.") since
+ * there's no count to surface. Consumers (devtools, e2e specs
+ * intercepting `console.log`) get a stable string on every push.
  */
-export function refreshStackDom(refs, model) {
-    renderStackInto(refs.stack, model);
+export function setConnectedStatus(refs) {
+    setStatus(refs, 'Connected.', 'connected');
 }

package/dist/system-cards/NoCredentialsCard.d.ts

@@ -1,7 +1,7 @@
 /**
  * No-credentials system card.
  *
- * Rendered when the server processed a `ggui_push` for a session whose
+ * Rendered when the server processed a `ggui_render` for a session whose
  * LLM credentials are missing or unresolvable. The user needs to open
  * the server's `/settings` page in a real browser tab to paste an API
  * key.

package/dist/system-cards/NoCredentialsCard.js

@@ -2,7 +2,7 @@ import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 /**
  * No-credentials system card.
  *
- * Rendered when the server processed a `ggui_push` for a session whose
+ * Rendered when the server processed a `ggui_render` for a session whose
  * LLM credentials are missing or unresolvable. The user needs to open
  * the server's `/settings` page in a real browser tab to paste an API
  * key.

package/dist/system-cards/ProtocolProbeCard.js

@@ -211,7 +211,7 @@ function defaultParams(method) {
                         intent: 'probe-click',
                         data: { note: 'hello from the protocol probe' },
                     },
-                    sessionId: 'probe-session',
+                    renderId: 'probe-render',
                     appId: 'probe-app',
                     actionId: '00000000', // overwritten in onClick with real FNV-1a
                     firedAt: new Date().toISOString(),
@@ -312,7 +312,7 @@ function ProbeButtonRow({ method, description, call, }) {
                 const args = params
                     .arguments ?? {};
                 // New gesture-envelope shape (SPEC §4.6): `{kind, payload,
-                // sessionId, appId, actionId, firedAt}`. For Pattern β the
+                // renderId, appId, actionId, firedAt}`. For Pattern β the
                 // `payload` carries `{intent, data}`.
                 const payload = args['payload'] ?? {};
                 const intent = String(payload['intent'] ?? '?');

package/dist/system-cards/index.d.ts

@@ -1,10 +1,10 @@
 /**
  * System-card registry.
  *
- * Central mapping from `SystemStackItem.kind` (a stable wire string)
+ * Central mapping from `SystemRender.kind` (a stable wire string)
  * to a real React component bundled inside the iframe-runtime. The
  * runtime's self-contained boot path looks up the kind here when it
- * sees a stack item with `type: 'system'`. Unknown kinds fall through
+ * sees a render with `type: 'system'`. Unknown kinds fall through
  * to {@link UnknownSystemCard} so an old runtime + new server still
  * surfaces something visible (vs. a blank iframe).
  *
@@ -13,7 +13,7 @@
  *   1. Author `MyNewCard.tsx` in this directory.
  *   2. Add an entry to {@link SYSTEM_CARD_REGISTRY} below.
  *   3. (Optional) Add the new kind string to
- *      `SystemStackItemKind` in `@ggui-ai/protocol` for IDE autocomplete.
+ *      `SystemRenderKind` in `@ggui-ai/protocol` for IDE autocomplete.
  */
 import * as React from 'react';
 import { NoCredentialsCard, type NoCredentialsCardProps } from './NoCredentialsCard.js';
@@ -28,7 +28,7 @@ import { ProtocolProbeCard, type ProtocolProbeCardProps } from './ProtocolProbeC
 export type SystemCardComponent = React.ComponentType<Record<string, unknown>>;
 /**
  * Registered system-card kinds. Keep keys aligned with
- * `SystemStackItemKind` in `@ggui-ai/protocol` so wire + bundle stay
+ * `SystemRenderKind` in `@ggui-ai/protocol` so wire + bundle stay
  * in sync. New kinds added without a registry entry render as
  * {@link UnknownSystemCard}.
  */

package/dist/system-cards/index.js

@@ -1,10 +1,10 @@
 /**
  * System-card registry.
  *
- * Central mapping from `SystemStackItem.kind` (a stable wire string)
+ * Central mapping from `SystemRender.kind` (a stable wire string)
  * to a real React component bundled inside the iframe-runtime. The
  * runtime's self-contained boot path looks up the kind here when it
- * sees a stack item with `type: 'system'`. Unknown kinds fall through
+ * sees a render with `type: 'system'`. Unknown kinds fall through
  * to {@link UnknownSystemCard} so an old runtime + new server still
  * surfaces something visible (vs. a blank iframe).
  *
@@ -13,7 +13,7 @@
  *   1. Author `MyNewCard.tsx` in this directory.
  *   2. Add an entry to {@link SYSTEM_CARD_REGISTRY} below.
  *   3. (Optional) Add the new kind string to
- *      `SystemStackItemKind` in `@ggui-ai/protocol` for IDE autocomplete.
+ *      `SystemRenderKind` in `@ggui-ai/protocol` for IDE autocomplete.
  */
 import * as React from 'react';
 import { ThemeProvider, lightTheme, darkTheme } from '@ggui-ai/design/themes';
@@ -64,7 +64,7 @@ function UnknownSystemCard({ kind, props, }) {
 }
 /**
  * Registered system-card kinds. Keep keys aligned with
- * `SystemStackItemKind` in `@ggui-ai/protocol` so wire + bundle stay
+ * `SystemRenderKind` in `@ggui-ai/protocol` so wire + bundle stay
  * in sync. New kinds added without a registry entry render as
  * {@link UnknownSystemCard}.
  */

package/dist/types.d.ts

@@ -2,22 +2,57 @@
  * Internal types shared across the `@ggui-ai/iframe-runtime` runtime.
  *
  * These shapes describe the renderer's INTERNAL contracts — the
- * bootstrap-parse outcome union + the renderer-host postMessage
- * frames. The wire shapes consumed FROM the network
- * (`SubscribePayload`, `AckPayload`, `WebSocketMessage`,
- * `GguiBootstrapMeta`) come from `@ggui-ai/protocol` and are imported
- * as `type` only so esbuild emits no runtime require for the protocol
- * package — the bundle stays self-contained.
+ * slice-parse outcome union + the renderer-host postMessage frames.
+ * The wire shapes consumed FROM the network (`SubscribePayload`,
+ * `AckPayload`, `WebSocketMessage`, `McpAppAiGguiRenderMeta`) come from
+ * `@ggui-ai/protocol` and are imported as `type` only so esbuild
+ * emits no runtime require for the protocol package — the bundle
+ * stays self-contained.
  *
- * Post-B3b: the WS lifecycle lives inside `@ggui-ai/channel-client`'s
+ * Post-B3b: the WS lifecycle lives inside `@ggui-ai/live-channel`'s
  * `WSTransport`; the renderer no longer maintains its own manager
  * class. The `RendererWebSocketManagerOptions` type that pre-B3b
  * declared the manager's constructor bag has been retired.
  */
-import type { GguiBootstrapMeta } from '@ggui-ai/protocol/integrations/mcp-apps';
-import type { HostContextProjection } from '@ggui-ai/protocol';
+import type { McpAppAiGguiRenderMeta } from '@ggui-ai/protocol/integrations/mcp-apps';
+import type { HostContextProjection, ComponentRender, SystemRender } from '@ggui-ai/protocol';
 /**
- * Why a bootstrap parse can fail. Closed union — every value is a
+ * Post-Phase-B alias kept for ergonomic call sites — the wire-side
+ * `McpAppAiGguiRenderMeta` is the single source of truth, and the
+ * "validated" qualifier is a no-op now (no nested-optional-session
+ * narrowing left after the slice merge). Future callers SHOULD prefer
+ * `McpAppAiGguiRenderMeta` directly; the alias persists so the rename
+ * sweep can land incrementally without churn at every call site.
+ */
+export type ValidatedMcpAppAiGguiMeta = McpAppAiGguiRenderMeta;
+/**
+ * The four server-assigned ledger fields on every wire-delivered
+ * {@link Render}. They're stamped by the server's per-render event
+ * ledger — NOT derivable from the inline `__GGUI_META__` bootstrap.
+ */
+type RenderLedgerFields = 'eventSequence' | 'createdAt' | 'lastActivityAt' | 'expiresAt';
+/**
+ * The mount surface's INPUT contract — what `mountRender` / `applyRender`
+ * accept. It is a {@link Render} minus the four server-assigned ledger
+ * fields ({@link RenderLedgerFields}), so the runtime can mount the
+ * compiled component (or system card) carried inline by the resource
+ * shell BEFORE the authoritative wire `Render` arrives over the WS.
+ *
+ * A full `Render` is assignable to `RenderSeedInput` (it carries every
+ * field plus the ledger), so the WS-ack reconcile path passes a real
+ * `Render` here unchanged; the inline-seed path passes the projection
+ * built by `buildRenderSeedInput`. We do NOT fabricate the ledger fields
+ * (Strict-Typing-First / no-type-laundering) — the first ack replaces
+ * the seed with the authoritative `Render`.
+ *
+ * Carries the SAME contract-spec fields a full `ComponentRender` does
+ * (`propsSpec` / `streamSpec` / `actionSpec`), as `undefined` on a
+ * seed — so the channel handlers that read those after the
+ * `type !== 'mcpApps' && type !== 'system'` narrowing stay type-clean.
+ */
+export type RenderSeedInput = Omit<ComponentRender, RenderLedgerFields> | Omit<SystemRender, RenderLedgerFields>;
+/**
+ * Why a slice-meta parse can fail. Closed union — every value is a
  * canonical reason the renderer surfaces to the host via postMessage.
  *
  * This set is intentionally narrow — it covers only parse-time
@@ -28,42 +63,43 @@ import type { HostContextProjection } from '@ggui-ai/protocol';
  *   - `MISSING_TOOL_OUTPUT` — host echoed `ui/initialize` without a
  *     `result.toolOutput` object at all.
  *   - `MISSING_META_GGUI_BOOTSTRAP` — `result.toolOutput` exists but
- *     `_meta.ggui.bootstrap` is absent. The on-wire synonym is
- *     `BOOTSTRAP_META_MISSING`.
- *   - `MALFORMED_BOOTSTRAP` — `_meta.ggui.bootstrap` is present but
- *     missing one of the four required string fields (`wsUrl`,
- *     `token`, `sessionId`, `appId`) — i.e. it doesn't satisfy
- *     `GguiBootstrapMeta`.
- *   - `EXPIRED_BOOTSTRAP` — `expiresAt` is set and parses to a
- *     timestamp in the past. UX sugar; servers reject expired tokens
- *     anyway, but we skip the round-trip when the proof is on hand.
+ *     `_meta["ai.ggui/render"]` is absent. The on-wire synonym is
+ *     `BOOTSTRAP_META_MISSING`. (Name retained pre-R4 for the
+ *     observability + host-postMessage protocol; cosmetic rename is
+ *     deferred.)
+ *   - `MALFORMED_BOOTSTRAP` — slice is present but fails business
+ *     rules (no live mode and no static content, mode discriminators
+ *     mutually exclusive, structural rejection by the combiner).
+ *   - `EXPIRED_BOOTSTRAP` — `expiresAt` parses to a timestamp in the
+ *     past AND there's no static content to degrade to.
  */
-export type BootstrapParseFailureReason = 'MISSING_TOOL_OUTPUT' | 'MISSING_META_GGUI_BOOTSTRAP' | 'MALFORMED_BOOTSTRAP' | 'EXPIRED_BOOTSTRAP';
+export type McpAppAiGguiMetaParseFailureReason = 'MISSING_TOOL_OUTPUT' | 'MISSING_META_GGUI_BOOTSTRAP' | 'MALFORMED_BOOTSTRAP' | 'EXPIRED_BOOTSTRAP';
 /**
- * Result of a bootstrap-meta extraction attempt. Discriminated on
- * `ok` so call sites get exhaustive narrowing without a typed-error
- * class — keeps the renderer's runtime cost tiny (no class metadata
- * in the bundle).
+ * Result of a slice-meta extraction attempt. Discriminated on `ok`
+ * so call sites get exhaustive narrowing without a typed-error class
+ * — keeps the renderer's runtime cost tiny (no class metadata in the
+ * bundle).
  *
- * widening: the `ok: true` arm now also carries
- * an optional `hostContext: HostContextProjection`. When the bootstrap
- * is extracted from the `ui/initialize` response (Reading-A path), the
- * parser opportunistically projects the surrounding `McpUiHostContext`
- * into this field so the runtime can:
+ * The `ok: true` arm carries the validated {@link McpAppAiGguiRenderMeta}
+ * slice and optionally a `hostContext: HostContextProjection`. When the
+ * meta is extracted from the `ui/initialize` response (Reading-A path),
+ * the parser opportunistically projects the surrounding
+ * `McpUiHostContext` into this field so the runtime can:
  *   - drive canvas-mode display-mode escalation
  *   - echo to the server (live-channel `host_context_observed` envelope)
  *   - feed the agent on next handshake/consume
  *
  * Capture is best-effort: a malformed `HostContext` never blocks the
- * bootstrap parse. Absent for the other extraction paths
- * (`__GGUI_BOOTSTRAP__` global, `ui/notifications/tool-result`) — those
+ * slice parse. Absent for the other extraction paths
+ * (`__GGUI_META__` global, `ui/notifications/tool-result`) — those
  * envelopes don't carry HostContext.
  */
-export type BootstrapParseResult = {
+export type McpAppAiGguiMetaParseResult = {
     readonly ok: true;
-    readonly bootstrap: GguiBootstrapMeta;
+    readonly meta: McpAppAiGguiRenderMeta;
     readonly hostContext?: HostContextProjection;
 } | {
     readonly ok: false;
-    readonly reason: BootstrapParseFailureReason;
+    readonly reason: McpAppAiGguiMetaParseFailureReason;
 };
+export {};

package/dist/types.js

@@ -1,3 +1,3 @@
 export {};
 // `RendererWebSocketManagerOptions` retired in B3b — the WS lifecycle
-// moved to `@ggui-ai/channel-client`'s `WSTransport`.
+// moved to `@ggui-ai/live-channel`'s `WSTransport`.

package/dist/validation.d.ts

@@ -62,8 +62,8 @@ export interface RendererValidatorContext {
 export declare function validateOutboundActionEnvelope(actionSpec: ActionSpec | undefined, envelope: ActionEnvelope): ValidationResult;
 /**
  * Validate an inbound stream-channel delivery before applying it to
- * stack-item state. Known reserved channels (`_ggui:*`) validate even
- * when the target stack item has no declared `streamSpec` — the
+ * render state. Known reserved channels (`_ggui:*`) validate even
+ * when the target render has no declared `streamSpec` — the
  * payload shape is server-owned; user channels stay permissive without
  * a contract.
  */

package/dist/validation.js

@@ -70,8 +70,8 @@ export function validateOutboundActionEnvelope(actionSpec, envelope) {
 }
 /**
  * Validate an inbound stream-channel delivery before applying it to
- * stack-item state. Known reserved channels (`_ggui:*`) validate even
- * when the target stack item has no declared `streamSpec` — the
+ * render state. Known reserved channels (`_ggui:*`) validate even
+ * when the target render has no declared `streamSpec` — the
  * payload shape is server-owned; user channels stay permissive without
  * a contract.
  */