@ggui-ai/protocol-conformance 0.2.0-alpha.4 → 0.3.0-rc.0

package/dist/fixtures/consume-buffer/action-payload-schema-violation.json

@@ -0,0 +1,37 @@
+{
+    "name": "action-payload-schema-violation",
+    "description": "A `data:submit` action naming a DECLARED action whose `data` violates the entry's declared payload schema is rejected at receipt: the server replies an `error` frame with code CONTRACT_VIOLATION (echoing the action's requestId) and the envelope is NOT appended to the consume buffer. Proves the payload-schema half of the declared-action contract (SPEC Section 4.6 receipt validation) — name-membership alone does not admit an action whose payload breaks the contract.",
+    "skipReason": null,
+    "setup": [
+        {
+            "type": "create-session",
+            "sessionId": "ck-schema-violation-1",
+            "actionSpec": {
+                "toggleTask": {
+                    "schema": {
+                        "type": "object",
+                        "properties": { "id": { "type": "string" } },
+                        "required": ["id"]
+                    }
+                }
+            }
+        }
+    ],
+    "inputEnvelope": {
+        "type": "action",
+        "requestId": "ck-schema-violation-1-req",
+        "payload": {
+            "sessionId": "ck-schema-violation-1",
+            "type": "data:submit",
+            "payload": {
+                "action": "toggleTask",
+                "data": { "id": 41 }
+            }
+        }
+    },
+    "expectedBehavior": {
+        "kind": "error-frame",
+        "code": "CONTRACT_VIOLATION",
+        "requestId": "ck-schema-violation-1-req"
+    }
+}

package/dist/fixtures/consume-buffer/index.d.ts

@@ -0,0 +1,6 @@
+import type { TestCase } from '../../types.js';
+/** All fixtures asserting consume-buffer action routing (SPEC
+ *  §nextStep-evolution single model + §4.4 contract enforcement +
+ *  §4.6 receipt validation). */
+export declare const consumeBufferFixtures: readonly TestCase[];
+//# sourceMappingURL=index.d.ts.map

package/dist/fixtures/consume-buffer/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/fixtures/consume-buffer/index.ts"],"names":[],"mappings":"AAkCA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE/C;;gCAEgC;AAChC,eAAO,MAAM,qBAAqB,EAAE,SAAS,QAAQ,EAIpD,CAAC"}

package/dist/fixtures/consume-buffer/index.js

@@ -0,0 +1,41 @@
+/**
+ * `consume-buffer` fixture sub-module.
+ *
+ * Exercises the single action-routing model's wire-observable half:
+ * every UI action lands as an event on the GguiSession's consume
+ * buffer, and the buffer append is provable on pure WS.
+ *
+ *   - `action-ack-sequence` — a declared action's ack frame carries
+ *     `payload.sequence`, the monotonic event sequence the append
+ *     assigned. Persistence proof.
+ *   - `undeclared-action-rejected` — a `data:submit` action absent
+ *     from the declared actionSpec replies an `error` frame with code
+ *     `CONTRACT_VIOLATION`; nothing is appended. Contract-gate proof,
+ *     name-membership half.
+ *   - `action-payload-schema-violation` — a `data:submit` action
+ *     naming a DECLARED entry whose `data` violates the entry's
+ *     declared payload schema replies the same `error` frame with
+ *     code `CONTRACT_VIOLATION`; nothing is appended. Contract-gate
+ *     proof, payload-schema half (SPEC §4.6 receipt validation).
+ *
+ * The retrieval half — the agent draining the buffer via
+ * `ggui_consume` — is an MCP tool call a WS-only runner cannot drive;
+ * that obligation belongs to an MCP-binding driver, not this catalog.
+ * Same declared-gap posture for the schema-validity meta-check on the
+ * DECLARED schema itself: a malformed authored schema is a fixture-
+ * authoring error the runner throws on (validating parse), while a
+ * malformed AGENT-authored schema on a live server is a `ggui_render`
+ * / `ggui_handshake` rejection (SPEC Section 7.9) outside this WS
+ * kit's observation window.
+ */
+import actionAckSequence from './action-ack-sequence.json' with { type: 'json' };
+import actionPayloadSchemaViolation from './action-payload-schema-violation.json' with { type: 'json' };
+import undeclaredActionRejected from './undeclared-action-rejected.json' with { type: 'json' };
+/** All fixtures asserting consume-buffer action routing (SPEC
+ *  §nextStep-evolution single model + §4.4 contract enforcement +
+ *  §4.6 receipt validation). */
+export const consumeBufferFixtures = [
+    actionAckSequence,
+    actionPayloadSchemaViolation,
+    undeclaredActionRejected,
+];

package/dist/fixtures/consume-buffer/undeclared-action-rejected.json

@@ -0,0 +1,29 @@
+{
+    "name": "undeclared-action-rejected",
+    "description": "A `data:submit` action whose name is absent from the GguiSession's declared actionSpec is rejected at the wire boundary: the server replies an `error` frame with code CONTRACT_VIOLATION (echoing the action's requestId) and the envelope is NOT appended to the consume buffer. Proves the declared-action contract gates persistence — undeclared actions never reach the agent.",
+    "skipReason": null,
+    "setup": [
+        {
+            "type": "create-session",
+            "sessionId": "ck-undeclared-action-1",
+            "actionSpec": { "toggleTask": {} }
+        }
+    ],
+    "inputEnvelope": {
+        "type": "action",
+        "requestId": "ck-undeclared-action-1-req",
+        "payload": {
+            "sessionId": "ck-undeclared-action-1",
+            "type": "data:submit",
+            "payload": {
+                "action": "doesNotExist",
+                "data": {}
+            }
+        }
+    },
+    "expectedBehavior": {
+        "kind": "error-frame",
+        "code": "CONTRACT_VIOLATION",
+        "requestId": "ck-undeclared-action-1-req"
+    }
+}

package/dist/fixtures/host-context/host-context-observed-persists.json

@@ -0,0 +1,34 @@
+{
+    "name": "host-context-observed-persists",
+    "description": "The iframe-runtime captures `McpUiHostContext` from the `ui/initialize` response, trims it IFRAME-SIDE to `HostContextProjection` (`projectHostContext` in `@ggui-ai/protocol` — `theme`/`styles` are deliberately not projection fields; they flow through ggui's theming pipeline), and echoes the projection via the `host_context_observed` Client→Server message. The server's obligation is purely stateful: persist `payload.hostContext` onto `GguiSession.hostContext` VERBATIM — the first-party handler patches the received projection as-is, with no server-side re-projection — so `ggui_handshake` / `ggui_consume` surface it to the agent on later turns. That is why this fixture's `expected` is exactly the projection it authors. There is no synchronous response frame, so a `no-op` (wire-silence) assertion would wrongly certify a server that drops the message; the kit grades the obligation by reading `hostContext` back through `ConformanceHost.readSessionField` after the observation window and deep-equalling it against `expected`. Hosts without that introspection seam SKIP — never a weakened pass.",
+    "skipReason": null,
+    "setup": [{ "type": "create-session", "sessionId": "ck-host-context-1" }],
+    "inputEnvelope": {
+        "type": "host_context_observed",
+        "payload": {
+            "sessionId": "ck-host-context-1",
+            "hostContext": {
+                "availableDisplayModes": ["inline", "fullscreen"],
+                "currentDisplayMode": "inline",
+                "containerDimensions": { "maxWidth": 480, "height": 320 },
+                "platform": "web",
+                "deviceCapabilities": { "touch": false, "hover": true },
+                "locale": "en-US",
+                "timeZone": "America/Los_Angeles"
+            }
+        }
+    },
+    "expectedBehavior": {
+        "kind": "session-state",
+        "field": "hostContext",
+        "expected": {
+            "availableDisplayModes": ["inline", "fullscreen"],
+            "currentDisplayMode": "inline",
+            "containerDimensions": { "maxWidth": 480, "height": 320 },
+            "platform": "web",
+            "deviceCapabilities": { "touch": false, "hover": true },
+            "locale": "en-US",
+            "timeZone": "America/Los_Angeles"
+        }
+    }
+}

package/dist/fixtures/host-context/index.d.ts

@@ -0,0 +1,5 @@
+import type { TestCase } from '../../types.js';
+/** All fixtures asserting host-context persistence
+ *  (`host_context_observed` → `GguiSession.hostContext`). */
+export declare const hostContextFixtures: readonly TestCase[];
+//# sourceMappingURL=index.d.ts.map

package/dist/fixtures/host-context/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/fixtures/host-context/index.ts"],"names":[],"mappings":"AAoCA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE/C;6DAC6D;AAC7D,eAAO,MAAM,mBAAmB,EAAE,SAAS,QAAQ,EAElD,CAAC"}

package/dist/fixtures/host-context/index.js

@@ -0,0 +1,40 @@
+/**
+ * `host-context` fixture sub-module.
+ *
+ * Exercises the host-context persistence obligation — the
+ * `host_context_observed` Client→Server live-channel message defined
+ * by `@ggui-ai/protocol` (`transport/websocket` union +
+ * `types/host-context`'s `HostContextObservedPayload`, whose contract
+ * is "server-side handler writes to `GguiSession.hostContext`"):
+ *
+ *   - `host-context-observed-persists` — the `HostContextProjection`
+ *     the iframe echoes after `ui/initialize` MUST land on
+ *     `GguiSession.hostContext` exactly as received (the projection /
+ *     trimming step is iframe-side, BEFORE emission; the first-party
+ *     server persists the received value verbatim, which is what the
+ *     fixture's `expected` pins). A stateful obligation with no
+ *     response frame — graded via the kit's session-state read-back
+ *     mechanism (`ConformanceHost.readSessionField`); hosts without
+ *     the introspection seam SKIP with a precise reason.
+ *
+ * Authoring note: the projection vocabulary is re-derived from the
+ * live `HostContextProjection` — `currentDisplayMode` (NOT the
+ * retired `displayMode` spelling) and NO `theme` field (theme flows
+ * through ggui's theming pipeline, not host context). The runner's
+ * input-envelope parser rejects unknown projection keys loudly, so a
+ * stale-vocabulary fixture is a fixture-authoring error, never a
+ * verdict on the implementation under test.
+ *
+ * Documentation-home note (declared, not hidden): the obligation's
+ * normative text lives in `@ggui-ai/protocol`'s type declarations;
+ * SPEC.md's §12.2 frame inventory does not yet list
+ * `host_context_observed`. Per the protocol-and-contract bar, that
+ * SPEC gap should close upstream — the wire type + persistence
+ * contract graded here are the shipping source of truth.
+ */
+import hostContextObservedPersists from './host-context-observed-persists.json' with { type: 'json' };
+/** All fixtures asserting host-context persistence
+ *  (`host_context_observed` → `GguiSession.hostContext`). */
+export const hostContextFixtures = [
+    hostContextObservedPersists,
+];

package/dist/fixtures/index.d.ts

@@ -20,11 +20,10 @@
  *
  * ## Current coverage
  *
- * Seven sub-modules with content (18 fixtures). Three additional
- * sub-modules (`data-contract`, `tool-name-uniqueness`,
- * `contract-error-payload`) are reserved for additive fixture
- * expansion and not yet materialized — adding fixtures there is a
- * kit minor version.
+ * Six sub-modules with content (12 fixtures). Additional sub-modules
+ * (`data-contract`, `tool-name-uniqueness`)
+ * are reserved for additive fixture expansion and not yet
+ * materialized — adding fixtures there is a kit minor version.
  *
  * ## What is NOT here — the gadget pure-function obligations
  *
@@ -36,13 +35,33 @@
  * caller-supplied function — there is no render, transport, or wire
  * frame to drive — so they do NOT belong in this behavioral fixture
  * catalog.
+ *
+ * ## What is NOT here — declared Path-A sequencing gap
+ *
+ * A `stream-delivery-roundtrip` fixture (an `emit-envelope`'d payload
+ * observed as a canonical `{type: 'data', payload: StreamEnvelope}`
+ * frame, graded by `stream-update`) is NOT authorable today without a
+ * false fail: the runner dispatches every setup directive BEFORE it
+ * opens the WebSocket and subscribes, and `emit-envelope` fans out to
+ * live subscribers only — a fresh, `fromSeq`-less subscribe replays
+ * nothing on declared channels (SPEC §12.2.1 invariant 1: "`fromSeq`
+ * absent always means empty replay"), so the setup-time emission is
+ * gone before the runner can observe it. The fixture's
+ * `inputEnvelope` cannot carry the emission either: an input envelope
+ * is by contract a Client→Server wire frame the runner sends on the
+ * transport, while emission is server-side (the agent's `ggui_emit`
+ * MCP tool) — routing a host directive through the wire-frame slot
+ * would conflate the two vocabularies. Honest grading needs either a
+ * post-subscribe host-directive phase (a runner-mechanism change) or
+ * an MCP-binding driver. Declared here rather than papered over with
+ * a fixture that fails conformant servers on sequencing alone.
  */
 export { bootstrapProtocolFixtures } from './bootstrap-protocol/index.js';
-export { observabilityEventsFixtures } from './observability-events/index.js';
-export { refreshSemanticsFixtures } from './refresh-semantics/index.js';
+export { consumeBufferFixtures } from './consume-buffer/index.js';
+export { hostContextFixtures } from './host-context/index.js';
 export { reservedChannelAuthorityFixtures } from './reserved-channel-authority/index.js';
 export { schemaVersionHandshakeFixtures } from './schema-version-handshake/index.js';
-export { wiredActionDispatchFixtures } from './wired-action-dispatch/index.js';
+export { subscribeTenancyFixtures } from './subscribe-tenancy/index.js';
 import type { TestCase } from '../types.js';
 /**
  * Contract slugs — match the sub-module directory names. The
@@ -50,7 +69,7 @@ import type { TestCase } from '../types.js';
  * Extensibly-closed via `(string & {})` so additive sub-modules
  * register without an API break.
  */
-export type ContractSlug = 'bootstrap-protocol' | 'observability-events' | 'refresh-semantics' | 'reserved-channel-authority' | 'schema-version-handshake' | 'wired-action-dispatch' | (string & {});
+export type ContractSlug = 'bootstrap-protocol' | 'consume-buffer' | 'host-context' | 'reserved-channel-authority' | 'schema-version-handshake' | 'subscribe-tenancy' | (string & {});
 /**
  * Every fixture the kit ships, grouped by the contract it exercises.
  * Order within each group matches the sub-module's `export` order.

package/dist/fixtures/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/fixtures/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsCG;AAEH,OAAO,EAAE,yBAAyB,EAAE,MAAM,+BAA+B,CAAC;AAC1E,OAAO,EAAE,2BAA2B,EAAE,MAAM,iCAAiC,CAAC;AAC9E,OAAO,EAAE,wBAAwB,EAAE,MAAM,8BAA8B,CAAC;AACxE,OAAO,EAAE,gCAAgC,EAAE,MAAM,uCAAuC,CAAC;AACzF,OAAO,EAAE,8BAA8B,EAAE,MAAM,qCAAqC,CAAC;AACrF,OAAO,EAAE,2BAA2B,EAAE,MAAM,kCAAkC,CAAC;AAE/E,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AAQ5C;;;;;GAKG;AACH,MAAM,MAAM,YAAY,GACpB,oBAAoB,GACpB,sBAAsB,GACtB,mBAAmB,GACnB,4BAA4B,GAC5B,0BAA0B,GAC1B,uBAAuB,GACvB,CAAC,MAAM,GAAG,EAAE,CAAC,CAAC;AAElB;;;;;;;GAOG;AACH,eAAO,MAAM,kBAAkB,EAAE,QAAQ,CAAC,MAAM,CAAC,YAAY,EAAE,SAAS,QAAQ,EAAE,CAAC,CAOlF,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,WAAW,EAAE,SAAS,QAAQ,EAGwB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/fixtures/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAyDG;AAEH,OAAO,EAAE,yBAAyB,EAAE,MAAM,+BAA+B,CAAC;AAC1E,OAAO,EAAE,qBAAqB,EAAE,MAAM,2BAA2B,CAAC;AAClE,OAAO,EAAE,mBAAmB,EAAE,MAAM,yBAAyB,CAAC;AAC9D,OAAO,EAAE,gCAAgC,EAAE,MAAM,uCAAuC,CAAC;AACzF,OAAO,EAAE,8BAA8B,EAAE,MAAM,qCAAqC,CAAC;AACrF,OAAO,EAAE,wBAAwB,EAAE,MAAM,8BAA8B,CAAC;AAExE,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AAQ5C;;;;;GAKG;AACH,MAAM,MAAM,YAAY,GACpB,oBAAoB,GACpB,gBAAgB,GAChB,cAAc,GACd,4BAA4B,GAC5B,0BAA0B,GAC1B,mBAAmB,GACnB,CAAC,MAAM,GAAG,EAAE,CAAC,CAAC;AAElB;;;;;;;GAOG;AACH,eAAO,MAAM,kBAAkB,EAAE,QAAQ,CAAC,MAAM,CAAC,YAAY,EAAE,SAAS,QAAQ,EAAE,CAAC,CAOlF,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,WAAW,EAAE,SAAS,QAAQ,EAGwB,CAAC"}

package/dist/fixtures/index.js

@@ -20,11 +20,10 @@
  *
  * ## Current coverage
  *
- * Seven sub-modules with content (18 fixtures). Three additional
- * sub-modules (`data-contract`, `tool-name-uniqueness`,
- * `contract-error-payload`) are reserved for additive fixture
- * expansion and not yet materialized — adding fixtures there is a
- * kit minor version.
+ * Six sub-modules with content (12 fixtures). Additional sub-modules
+ * (`data-contract`, `tool-name-uniqueness`)
+ * are reserved for additive fixture expansion and not yet
+ * materialized — adding fixtures there is a kit minor version.
  *
  * ## What is NOT here — the gadget pure-function obligations
  *
@@ -36,19 +35,39 @@
  * caller-supplied function — there is no render, transport, or wire
  * frame to drive — so they do NOT belong in this behavioral fixture
  * catalog.
+ *
+ * ## What is NOT here — declared Path-A sequencing gap
+ *
+ * A `stream-delivery-roundtrip` fixture (an `emit-envelope`'d payload
+ * observed as a canonical `{type: 'data', payload: StreamEnvelope}`
+ * frame, graded by `stream-update`) is NOT authorable today without a
+ * false fail: the runner dispatches every setup directive BEFORE it
+ * opens the WebSocket and subscribes, and `emit-envelope` fans out to
+ * live subscribers only — a fresh, `fromSeq`-less subscribe replays
+ * nothing on declared channels (SPEC §12.2.1 invariant 1: "`fromSeq`
+ * absent always means empty replay"), so the setup-time emission is
+ * gone before the runner can observe it. The fixture's
+ * `inputEnvelope` cannot carry the emission either: an input envelope
+ * is by contract a Client→Server wire frame the runner sends on the
+ * transport, while emission is server-side (the agent's `ggui_emit`
+ * MCP tool) — routing a host directive through the wire-frame slot
+ * would conflate the two vocabularies. Honest grading needs either a
+ * post-subscribe host-directive phase (a runner-mechanism change) or
+ * an MCP-binding driver. Declared here rather than papered over with
+ * a fixture that fails conformant servers on sequencing alone.
  */
 export { bootstrapProtocolFixtures } from './bootstrap-protocol/index.js';
-export { observabilityEventsFixtures } from './observability-events/index.js';
-export { refreshSemanticsFixtures } from './refresh-semantics/index.js';
+export { consumeBufferFixtures } from './consume-buffer/index.js';
+export { hostContextFixtures } from './host-context/index.js';
 export { reservedChannelAuthorityFixtures } from './reserved-channel-authority/index.js';
 export { schemaVersionHandshakeFixtures } from './schema-version-handshake/index.js';
-export { wiredActionDispatchFixtures } from './wired-action-dispatch/index.js';
+export { subscribeTenancyFixtures } from './subscribe-tenancy/index.js';
 import { bootstrapProtocolFixtures } from './bootstrap-protocol/index.js';
-import { observabilityEventsFixtures } from './observability-events/index.js';
-import { refreshSemanticsFixtures } from './refresh-semantics/index.js';
+import { consumeBufferFixtures } from './consume-buffer/index.js';
+import { hostContextFixtures } from './host-context/index.js';
 import { reservedChannelAuthorityFixtures } from './reserved-channel-authority/index.js';
 import { schemaVersionHandshakeFixtures } from './schema-version-handshake/index.js';
-import { wiredActionDispatchFixtures } from './wired-action-dispatch/index.js';
+import { subscribeTenancyFixtures } from './subscribe-tenancy/index.js';
 /**
  * Every fixture the kit ships, grouped by the contract it exercises.
  * Order within each group matches the sub-module's `export` order.
@@ -59,11 +78,11 @@ import { wiredActionDispatchFixtures } from './wired-action-dispatch/index.js';
  */
 export const fixturesByContract = {
     'bootstrap-protocol': bootstrapProtocolFixtures,
-    'observability-events': observabilityEventsFixtures,
-    'refresh-semantics': refreshSemanticsFixtures,
+    'consume-buffer': consumeBufferFixtures,
+    'host-context': hostContextFixtures,
     'reserved-channel-authority': reservedChannelAuthorityFixtures,
     'schema-version-handshake': schemaVersionHandshakeFixtures,
-    'wired-action-dispatch': wiredActionDispatchFixtures,
+    'subscribe-tenancy': subscribeTenancyFixtures,
 };
 /**
  * Every fixture flat, in deterministic lexicographic order by

package/dist/fixtures/reserved-channel-authority/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/fixtures/reserved-channel-authority/index.ts"],"names":[],"mappings":"AAiBA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE/C,qEAAqE;AACrE,eAAO,MAAM,gCAAgC,EAAE,SAAS,QAAQ,EAG/D,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/fixtures/reserved-channel-authority/index.ts"],"names":[],"mappings":"AA4BA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE/C,qEAAqE;AACrE,eAAO,MAAM,gCAAgC,EAAE,SAAS,QAAQ,EAE/D,CAAC"}

package/dist/fixtures/reserved-channel-authority/index.js

@@ -3,19 +3,29 @@
  *
  * Exercises the reserved-channel contract (SPEC §4.4 Reserved-channel
  * Authority):
- *   - Declared-channel schema violations surface as
- *     `_ggui:contract-error` envelopes with `SCHEMA_VIOLATION` code.
  *   - Channel-0 `props_update` round-trips deliver new props and the
  *     iframe DOM reflects the update.
  *
- * Both fixtures are `ConformanceHost`-gated — `stream-schema-
- * violation` drives via malformed-tool setup, `props-update-roundtrip`
- * via direct envelope dispatch.
+ * One fixture today (`props-update-roundtrip`), `ConformanceHost`-gated
+ * via direct envelope dispatch. Additional reserved-channel fixtures
+ * (declared-channel schema-violation rejection) land here as the
+ * family grows — a kit minor version.
+ *
+ * ## Declared gap — the namesake MUST is not WS-gradable
+ *
+ * SPEC §4.4's headline obligation — the server REJECTS agent-authored
+ * deliveries on `_ggui:*` reserved channels — cannot even be
+ * ATTEMPTED over the channel-3 WebSocket: the Client→Server frame
+ * vocabulary has no frame that authors a stream delivery (clients
+ * subscribe, dispatch actions, and echo observations; `data` frames
+ * are Server→Client only). Agent emission enters through the
+ * `ggui_emit` MCP tool, so both the violation and the rejection that
+ * grades it are observable only on the MCP binding. That fixture
+ * belongs to a future MCP-binding driver — the gap is declared here
+ * rather than faked with a frame the wire cannot carry.
  */
 import propsUpdateRoundtrip from './props-update-roundtrip.json' with { type: 'json' };
-import streamSchemaViolation from './stream-schema-violation.json' with { type: 'json' };
 /** All fixtures asserting reserved-channel authority (SPEC §4.4). */
 export const reservedChannelAuthorityFixtures = [
     propsUpdateRoundtrip,
-    streamSchemaViolation,
 ];

package/dist/fixtures/reserved-channel-authority/props-update-roundtrip.json

@@ -1,15 +1,15 @@
 {
     "name": "props-update-roundtrip",
-    "description": "Host delivers a `props_update` envelope on channel 0 with a new props payload. The iframe's DOM reflects the new props within `timeoutMs` — evidence on a stamped data-attribute. Proves the host -> iframe props channel is live-wired, complementing the wired-action (iframe -> host) path.",
+    "description": "Host delivers a `props_update` envelope on channel 0 with a new props payload. The iframe's DOM reflects the new props within `timeoutMs` — evidence on a stamped data-attribute. Proves the host -> iframe props channel is live, complementing the action-submit (iframe -> host) path.",
     "skipReason": null,
     "setup": [
-        { "type": "create-render", "renderId": "ck-props-update-1" },
+        { "type": "create-session", "sessionId": "ck-props-update-1" },
         {
             "type": "emit-envelope",
             "channel": "_ggui:props",
             "payload": {
                 "type": "props_update",
-                "renderId": "ck-props-update-1",
+                "sessionId": "ck-props-update-1",
                 "props": { "greeting": "initial" }
             }
         }
@@ -17,7 +17,7 @@
     "inputEnvelope": {
         "type": "props-update",
         "channel": 0,
-        "renderId": "ck-props-update-1",
+        "sessionId": "ck-props-update-1",
         "props": { "greeting": "updated-by-host" }
     },
     "expectedBehavior": {

package/dist/fixtures/schema-version-handshake/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/fixtures/schema-version-handshake/index.ts"],"names":[],"mappings":"AAgBA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE/C,yEAAyE;AACzE,eAAO,MAAM,8BAA8B,EAAE,SAAS,QAAQ,EAG7D,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/fixtures/schema-version-handshake/index.ts"],"names":[],"mappings":"AAwBA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE/C,yEAAyE;AACzE,eAAO,MAAM,8BAA8B,EAAE,SAAS,QAAQ,EAG7D,CAAC"}

package/dist/fixtures/schema-version-handshake/index.js

@@ -6,10 +6,18 @@
  *   - `UPGRADE_REQUIRED` error frame on mismatch per server's
  *     `versionPolicy` setting.
  *
- * Two fixtures; `version-match` is redundant-by-design with
- * `bootstrap-success` on today's harness but authored distinctly so
- * a `ConformanceHost` can expose the handshake as a discrete
- * assertion slot.
+ * Both fixtures declare `subscribe.supportedVersions: 'current'` —
+ * the runner resolves the sentinel to the kit's compiled
+ * `PROTOCOL_SCHEMA_VERSION`, so the catalog stays evergreen across
+ * protocol version bumps (no stale version literals). `version-match`
+ * grades BOTH halves of the happy path: the declared set is actually
+ * transmitted, and the ack must advertise `serverVersion` equal to
+ * the canonical (`expectedBehavior.serverVersion: 'current'`) — it is
+ * NOT redundant with `bootstrap-success`, whose ack assertion is
+ * versionless. `version-mismatch` grades the rejection half via the
+ * `server-version-override` directive: the same 'current' declaration
+ * excludes the override by construction, so only the override seam
+ * can produce the rejection.
  */
 import versionMatch from './version-match.json' with { type: 'json' };
 import versionMismatch from './version-mismatch.json' with { type: 'json' };

package/dist/fixtures/schema-version-handshake/version-match.json

@@ -1,15 +1,17 @@
 {
     "name": "version-match",
-    "description": "Happy-path version handshake: server advertises a schemaVersion the client supports (same as current canonical). Renderer completes the handshake without emitting `ggui:upgrade-required`. Baseline for `version-mismatch`'s negative assertion — proves the handshake path itself is observable.",
+    "description": "Happy-path version handshake (SPEC §12.2.2): the runner's subscribe DECLARES `supportedVersions` resolved from the 'current' sentinel (the kit's compiled canonical, evergreen across version bumps), the server's advertised schemaVersion is in the declared set, and the ack ADVERTISES `payload.serverVersion` equal to that canonical. Both halves are graded: an always-reject server fails on the error frame, and a versionless ack (legacy-pass-through, no `serverVersion`) fails the ack-field assertion — the handshake must be observable, not merely not-rejected. The runner-owned subscribe IS the probe (the inputEnvelope is descriptive, not dispatched). Baseline for `version-mismatch`'s negative assertion.",
     "skipReason": null,
-    "setup": [{ "type": "create-render", "renderId": "ck-version-match-1" }],
+    "setup": [{ "type": "create-session", "sessionId": "ck-version-match-1" }],
+    "subscribe": {
+        "supportedVersions": "current"
+    },
     "inputEnvelope": {
         "type": "handshake",
-        "renderId": "ck-version-match-1",
-        "clientAccepts": ["1.1"]
+        "sessionId": "ck-version-match-1"
     },
     "expectedBehavior": {
         "kind": "bootstrap-success",
-        "observabilitySequence": []
+        "serverVersion": "current"
     }
 }

package/dist/fixtures/schema-version-handshake/version-mismatch.json

@@ -1,25 +1,24 @@
 {
     "name": "version-mismatch",
-    "description": "Server advertises a protocol schemaVersion outside the client's accepted set. Renderer emits `{type:'ggui:upgrade-required', server, client}` to the parent host + a matching `ProtocolError{kind:'version'}`. Host SHOULD render an inline upgrade prompt — NOT treat this as a terminal failure.",
+    "description": "Rejection half of the version handshake (SPEC §12.2.2): the `server-version-override` directive makes the server advertise '99.99-unsupported' for this render, while the runner's subscribe declares `supportedVersions` resolved from the SAME 'current' sentinel as `version-match` — a set that excludes the override by construction (the override literal is never the canonical), so the rejection can only come from the override seam, never from the server's real version. Expected: an `error` frame with `payload.code === 'UPGRADE_REQUIRED'`. Servers on the default reject policy also close the connection; advisory-policy servers keep it open — both satisfy the frame assertion.",
     "skipReason": null,
     "setup": [
-        { "type": "create-render", "renderId": "ck-version-mismatch-1" },
+        { "type": "create-session", "sessionId": "ck-version-mismatch-1" },
         {
             "type": "server-version-override",
-            "renderId": "ck-version-mismatch-1",
+            "sessionId": "ck-version-mismatch-1",
             "advertiseVersion": "99.99-unsupported"
         }
     ],
+    "subscribe": {
+        "supportedVersions": "current"
+    },
     "inputEnvelope": {
-        "type": "render",
-        "renderId": "ck-version-mismatch-1",
-        "resource": {
-            "uri": "ui://ggui/render"
-        }
+        "type": "handshake",
+        "sessionId": "ck-version-mismatch-1"
     },
     "expectedBehavior": {
         "kind": "version-mismatch",
-        "serverVersion": "99.99-unsupported",
-        "clientAccepts": ["1.1"]
+        "serverVersion": "99.99-unsupported"
     }
 }

package/dist/fixtures/subscribe-tenancy/absent-appid-defaults.json

@@ -0,0 +1,18 @@
+{
+    "name": "absent-appid-defaults",
+    "description": "A subscribe that OMITS `appId` resolves the caller's identity-default app and acks. SPEC §12.2's subscribe-payload table makes `appId` optional: absent ⇒ the server resolves it from the connection's authenticated identity (token binding, else identity mapping, else the deployment default) — clients never invent the default. Under the kit's harness the identity-default is the conventional tenant 'conformance', so the provision-on-subscribe path must bind exactly that value to the fresh render row — a real string tenant, never an undefined one (the corrupt-row failure mode this fixture locks out: a silent ack whose provisioned row carries appId undefined, unreachable by any later legal subscribe). The runner-owned subscribe frame IS the probe (`subscribe.omitAppId` drops the runner's conventional appId stamp; the inputEnvelope is descriptive, not dispatched); graded as a session-state read-back of the bound `appId` through the host's readSessionField seam. The §12.2.3 APP_MISMATCH tenancy gate is the sibling `app-mismatch` fixture's claim and still applies to the RESOLVED value.",
+    "skipReason": null,
+    "setup": [],
+    "subscribe": {
+        "omitAppId": true
+    },
+    "inputEnvelope": {
+        "type": "handshake",
+        "sessionId": "ck-absent-appid-1"
+    },
+    "expectedBehavior": {
+        "kind": "session-state",
+        "field": "appId",
+        "expected": "conformance"
+    }
+}

package/dist/fixtures/subscribe-tenancy/app-mismatch.json

@@ -0,0 +1,20 @@
+{
+    "name": "app-mismatch",
+    "description": "The GguiSession exists but is bound to a DIFFERENT app than the subscriber claims: `create-session` binds appId 'conformance-other', while the kit's runner always subscribes with appId 'conformance'. SPEC §12.2's subscribe-payload table makes the tenancy check a MUST — appId 'MUST match the GguiSession's bound appId or subscribe fails APP_MISMATCH' — and §12.2.3 keeps the code distinct from SESSION_NOT_FOUND (the GguiSession exists; it is reachable only from a different app), so clients route 'fix your appId / API key' differently from 're-handshake'. The runner-owned subscribe frame IS the probe (the inputEnvelope is descriptive, not dispatched); expected: an `error` frame with `payload.code === 'APP_MISMATCH'`.",
+    "skipReason": null,
+    "setup": [
+        {
+            "type": "create-session",
+            "sessionId": "ck-app-mismatch-1",
+            "appId": "conformance-other"
+        }
+    ],
+    "inputEnvelope": {
+        "type": "handshake",
+        "sessionId": "ck-app-mismatch-1"
+    },
+    "expectedBehavior": {
+        "kind": "error-frame",
+        "code": "APP_MISMATCH"
+    }
+}

package/dist/fixtures/subscribe-tenancy/index.d.ts

@@ -0,0 +1,6 @@
+import type { TestCase } from '../../types.js';
+/** All fixtures asserting subscribe-time tenancy (SPEC §12.2 field
+ *  table — identity-default resolution on absent `appId` — and
+ *  §12.2.3 `APP_MISMATCH`). */
+export declare const subscribeTenancyFixtures: readonly TestCase[];
+//# sourceMappingURL=index.d.ts.map

package/dist/fixtures/subscribe-tenancy/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/fixtures/subscribe-tenancy/index.ts"],"names":[],"mappings":"AAwDA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAE/C;;+BAE+B;AAC/B,eAAO,MAAM,wBAAwB,EAAE,SAAS,QAAQ,EAGvD,CAAC"}