@4xeoz/re-entry 0.2.0

package/README.md

@@ -0,0 +1,337 @@
+# Re-entry Local Connector
+
+Install it once on the Mac where Codex should open; after one browser approval, a macOS
+LaunchAgent keeps the outbound Connector running at login.
+
+> Current boundary: this is a verified macOS Connector preview with a publish-ready npm package.
+> It starts a fresh `codex exec` process with bounded context; it does not prove Browser/WebMCP
+> attachment or final Host effects.
+
+## One-time install
+
+Requirements: macOS, Node.js 24+, Codex installed and signed in, and an absolute project directory
+Codex may read and write.
+
+```sh
+npx @4xeoz/re-entry install --codex-cd /absolute/path/to/your/project
+```
+
+The published package uses the hosted Receiver by default. Use `--receiver` only when testing a
+different Receiver, such as the local preview:
+
+```sh
+npx @4xeoz/re-entry install \
+  --receiver http://127.0.0.1:43224 \
+  --codex-cd /absolute/path/to/your/project
+```
+
+`re-entry install` performs the whole user setup:
+
+```text
+check Node + find Codex + validate project directory
+  -> request a device authorization from Re-entry
+  -> show the verification URL and wait for the user to press Enter
+  -> open Re-entry in the default browser
+  -> sign in or create an account
+  -> approve this Mac once
+  -> save the device credential with mode 0600
+  -> install and start a per-user macOS LaunchAgent
+```
+
+The Connector opens no local port and accepts no inbound connection. It polls Re-entry over an
+outbound HTTPS connection in a deployed system; loopback HTTP is accepted only by the local
+preview.
+
+## Check it
+
+```sh
+re-entry status
+re-entry --help
+```
+
+The status view checks the local authorization, background job, Receiver reachability, Node, and
+Codex. Useful development commands are:
+
+```sh
+re-entry doctor --codex-cd /absolute/path/to/project
+re-entry connect --receiver http://127.0.0.1:43224
+re-entry claim-once --codex-cd /absolute/path/to/project
+re-entry start --codex-cd /absolute/path/to/project
+```
+
+`connect` repeats only account authorization. `install` is the normal product path because it also
+installs the background job. `claim-once` is the smallest manual delivery test. The legacy
+Host-code `pair` command remains only for compatibility tests.
+
+## Give this to a coding agent
+
+Copy this prompt into a coding-agent task:
+
+```text
+Install the Re-entry Local Connector on this Mac. First read the package README. Verify Node.js 24
+or newer and locate the installed Codex executable. Run `npx @4xeoz/re-entry install` with an absolute
+project directory. Let the human complete the Re-entry
+browser approval; never copy browser cookies, organization keys, Connector tokens, or private keys
+into chat, logs, source files, or git. Finish by running `re-entry status` and report the bounded
+results without claiming Browser/WebMCP or production deployment.
+```
+
+## Package map
+
+- `src/main.mjs` — `re-entry` CLI and long-running poll loop.
+- `src/pairing-client.mjs` — account-first browser device authorization.
+- `src/credentials.mjs` — atomic local credential storage.
+- `src/macos-service.mjs` — per-user LaunchAgent install and status.
+- `src/local-connector.mjs` — one claim and activation boundary.
+- `src/codex-exec-adapter.mjs` — fresh local Codex process adapter.
+- `src/terminal-ui.mjs` — dependency-free human CLI presentation.
+
+Verify the package with Node 24:
+
+```sh
+npm run verify
+```
+
+<details>
+<summary>Historical Host-code pairing notes</summary>
+
+The material below describes the older Host-issued pairing-code preview. It remains for protocol
+traceability but is not the current account-first install path.
+
+The Local Connector is one outbound-only Node.js process. It polls the Cloud Receiver for one
+short delivery lease, starts one fresh local Codex process, and then exits. It is not a web server,
+does not open a port on the user's Mac, and does not accept inbound connections from the Receiver.
+
+This is a local preview, not a background daemon or a production Agent integration.
+
+## What must be installed
+
+The current package is kept inside this repository, so install the repository first:
+
+1. macOS;
+2. Node.js 24 or newer;
+3. the ChatGPT/Codex application or a `codex` executable available on `PATH`;
+4. a Host project directory that the local Codex process can read and write; and
+5. a reachable Receiver origin. `http://127.0.0.1` is allowed only for the local preview; a
+   Receiver on another machine must use HTTPS.
+
+From a clean checkout:
+
+```sh
+git clone <repository-url>
+cd OpenAI-Web-MCP-Challenge/runtime/local-connector
+npm install
+npm run verify
+```
+
+The package bundles the reusable `@webmcp-challenge/reentry-core` modules it imports. It can be
+installed from npm without a checked-out repository or a local `file:` dependency at runtime.
+
+## Publish the package
+
+The package name is `@4xeoz/re-entry` and the core is included in the tarball. After signing in to
+the npm account that owns the `4xeoz` scope, publish from this directory:
+
+```sh
+npm login
+npm publish --access public
+```
+
+After publishing, users run `npx @4xeoz/re-entry install`. The executable inside the package is
+still named `re-entry`.
+
+## Check a Mac before pairing
+
+Run the read-only readiness check before connecting the machine:
+
+```sh
+npm run doctor -- \
+  --codex-cd "$HOME/Code/my-host-project"
+```
+
+`doctor` checks Node.js, finds Codex, runs `codex --version`, and checks that the Host directory
+exists and is readable and writable. In a terminal it shows each check; with `--json` or piped
+stdout it prints a bounded `connector_ready` JSON event when ready.
+
+Codex lookup order is:
+
+```text
+--codex-binary
+  -> CODEX_BINARY
+  -> codex on PATH
+  -> common macOS command directories
+  -> ChatGPT.app/Codex.app in /Applications or ~/Applications
+```
+
+If Codex is installed in a non-standard location, configure it without changing source:
+
+```sh
+npm run doctor -- \
+  --codex-binary "/path/to/codex" \
+  --codex-cd "$HOME/Code/my-host-project"
+```
+
+The same `--codex-binary` and `--codex-cd` values are used by `claim-once`.
+
+## Start with the guided CLI
+
+For a human using the terminal, the simplest entry point is:
+
+```sh
+npm start -- \
+  --receiver http://127.0.0.1:43218 \
+  --codex-cd "$HOME/Code/my-host-project"
+```
+
+On the first run, the Connector checks the Mac, asks for the one-time code from the Host
+backend, opens the approval page, waits for the user to approve it, stores the credential, and
+checks once for approved work. On later runs it reuses the saved credential and skips pairing:
+
+```sh
+npm start -- --codex-cd "$HOME/Code/my-host-project"
+```
+
+This guided command is still a one-shot preview: it exits after finding no work or after starting
+one Codex session. It does not yet install itself as a background service. The explicit `pair` and
+`claim-once` commands below remain available for scripts and for testing each block separately.
+
+When attached to a terminal, the CLI shows a readable status view with steps, checks, approval
+state, and next actions. When stdout is piped, or when `--json` is supplied, it emits bounded JSON
+events instead so another process can consume it:
+
+```sh
+npm start -- --json --codex-cd "$HOME/Code/my-host-project"
+```
+
+## Pair this Mac with a Host user
+
+Pairing connects one local Connector to one already-authenticated Host user. It is separate from
+the Host organization's API key and does not give the Connector permission to create Grants or
+send Host events.
+
+The flow is:
+
+```text
+Host backend -> Receiver: start pairing for its Host-user reference
+Receiver -> Host backend: one-time user code + verification URL
+Connector -> Receiver: claim the code
+Connector -> browser: open the verification URL
+user -> Receiver page: click Approve
+Connector -> Receiver: poll until approved
+Receiver -> Connector: one Connector credential
+Connector -> local disk: save the credential with mode 0600
+```
+
+The Host backend starts pairing with its organization credential. In the current local preview:
+
+```sh
+curl -s -X POST http://127.0.0.1:43218/v0.1/pairing-sessions \
+  -H 'Authorization: Bearer host-preview-api-key' \
+  -H 'Content-Type: application/json' \
+  --data '{"host_subject_ref":"host_user_001"}'
+```
+
+Run the Connector and enter the returned `user_code` when it asks for it. The code is not placed
+in shell history:
+
+```sh
+npm start -- pair \
+  --receiver http://127.0.0.1:43218 \
+  --credential-file "$HOME/.webmcp-connector/credentials.json"
+```
+
+For a non-interactive script, pass the code explicitly instead:
+
+```sh
+npm start -- pair \
+  --receiver http://127.0.0.1:43218 \
+  --code 'ABCD-EFGH-IJKL-MNOP' \
+  --credential-file "$HOME/.webmcp-connector/credentials.json"
+```
+
+In an interactive terminal, the Connector shows the verification URL and waits for you to press
+Enter before opening the approval page. If the browser does not open, use the displayed URL
+manually and click **Approve**. The command keeps polling until approval or expiry, then prints
+`connector_paired`. JSON and other non-interactive callers continue without the Enter prompt.
+
+The credential file contains the local bearer credential and is protected with filesystem mode
+0600. Do not commit it, copy it into a Host prompt, or put it in a repository. The Connector never
+prints the bearer value. The current preview permits one active pairing for a Host user; a second
+pairing returns `host_subject_already_paired` until the preview state is revoked or reset.
+
+## Claim one delivery and start Codex
+
+After pairing, run one manual poll:
+
+```sh
+npm start -- claim-once \
+  --credential-file "$HOME/.webmcp-connector/credentials.json" \
+  --codex-cd "$HOME/Code/my-host-project"
+```
+
+The command performs this sequence:
+
+```text
+read local credential
+  -> preflight Node, Codex, and Host directory
+  -> ask Receiver for one delivery lease
+  -> validate the lease
+  -> start `codex exec --cd <Host project> <fixed continuation prompt>`
+  -> print the typed activation result
+```
+
+The fixed prompt contains the canonical page, workflow, event, state version, and human decision
+boundary. It does not contain the Receiver bearer, lease token, or private process configuration.
+There is no existing-session lookup or thread mapping.
+
+The result meanings are:
+
+- `connector_idle`: no pending delivery was available;
+- `activation_dispatch_accepted`: the local Codex process exited successfully; and
+- `outcome_unknown` or another typed result: the process failed, timed out, or the activation was
+  rejected.
+
+`activation_dispatch_accepted` does not prove that Browser access, page-bound WebMCP execution,
+Host-effect verification, or acknowledgement occurred. Browser permission and the Agent-to-Browser
+connection remain separate runtime capabilities. A future production Connector may run this
+operation under a supervisor or scheduler; the current CLI is one-shot.
+
+## Troubleshooting
+
+| Code | Meaning | Next action |
+|---|---|---|
+| `connector_node_unsupported` | Node is older than 24 | Install/use Node 24 or newer |
+| `connector_codex_not_found` | No default Codex executable was found | Install Codex, add it to `PATH`, or use `--codex-binary` |
+| `connector_codex_binary_not_found` | The configured executable is missing or not executable | Correct the path or remove the override |
+| `connector_codex_unusable` | `codex --version` failed | Open/login/update Codex, then rerun `doctor` |
+| `connector_codex_cd_missing` | The Host directory does not exist | Correct `--codex-cd` |
+| `connector_codex_cd_unusable` | The Host directory is not readable and writable | Fix local permissions |
+| `connector_credentials_missing` | Pairing has not been completed for this credential file | Run `pair` |
+| `connector_pairing_code_missing` | Guided start needs a one-time code | Ask the Host backend for a code, then enter it or pass `--code` |
+| `pairing_code_invalid` | The entered code is not the expected 16-character Host code | Use a code like `ABCD-EFGH-IJKL-MNOP` from the Host backend |
+| `pairing_request_timeout` | Receiver did not answer in time | Check the Receiver origin and network |
+| `pairing_expired` | The one-time pairing window expired | Ask the Host backend for a new code |
+
+## Package boundary
+
+- `src/codex-discovery.mjs` — Codex lookup, version verification, Node check, and Host-directory check;
+- `src/pairing-client.mjs` — one-time pairing claim, browser open, and poll;
+- `src/credentials.mjs` — atomic local credential file with restrictive permissions;
+- `src/local-connector.mjs` — one claim and typed adapter dispatch;
+- `src/codex-exec-adapter.mjs` — the fresh-session Codex adapter inside the Connector process;
+- `src/terminal-ui.mjs` — the dependency-free human terminal presentation; and
+- `src/main.mjs` — the small CLI process, guided `start`, and `doctor` command.
+
+Run package checks with:
+
+```sh
+npm run check:syntax
+npm run test:codex
+npm test
+npm run verify
+```
+
+The reusable delivery protocol remains in `reentry-core/`; this package consumes it rather than
+forking Receiver or delivery semantics.
+
+</details>

package/node_modules/@webmcp-challenge/reentry-core/README.md

@@ -0,0 +1,112 @@
+# Re-entry Core
+
+**Status:** v0.1 protocol, Host SDK, Receiver C1, Receiver Grant control, Connector delivery C2,
+transport/process C3d, Agent Adapter contract C4b, private managed-context resolution C4c,
+source-repository conformance profile C6b, and app-independent quality and weight baseline locally
+verified  
+**Authority:** ADR-0006 through ADR-0014 and `Docs/Development/RECORE-001-foundation.md` through
+`Docs/Development/RECORE-006-private-managed-context-binding.md`
+
+This directory is the authoritative source for new application-neutral Re-entry Core behavior.
+MVP1 and MVP2 remain unchanged references.
+
+## Current surface
+
+- `src/protocol.mjs` — strict bounded Manifest, event envelope, public binding, private receipt,
+  canonical JSON, Ed25519 signing, and typed errors.
+- `src/host-sdk.mjs` — narrow Host-side Manifest and event issuance without Receiver or Agent
+  authority.
+- `src/receiver-core.mjs` — Receiver-owned consent challenge, private Grant, public binding,
+  authenticated same-subject inspection and atomic revocation, exact event replay, atomic
+  pending-delivery reservation, and a narrow delivery facade behind injected authority ports.
+- `src/receiver-delivery.mjs` — internal target-scoped claim, short lease, bounded-attempt,
+  stale-worker fencing, and Host-effect-backed acknowledgement state machine.
+- `src/receiver-support.mjs` — shared strict Receiver validation, immutable-value, and typed-error
+  helpers.
+- `src/sqlite-receiver-store.mjs` — optional Node SQLite reference store with explicit
+  transactions, additive schema migration, WAL and full synchronous durability for file-backed
+  state, and no fallback.
+- `src/sqlite-receiver-schema.mjs` — internal versioned schema and delivery projection.
+- `src/cloud-receiver-http.mjs` — strict bounded Host-event, delivery-claim, and effect-
+  acknowledgement HTTP mapping over an injected Receiver Core.
+- `src/local-connector-client.mjs` — outbound-only no-retry Connector client with secure-origin,
+  timeout, response-size, redirect, and exact-response validation.
+- `src/agent-adapter.mjs` — credential-free lease-to-activation derivation, one-call bounded
+  adapter dispatch, and explicit accepted, unsupported, rejected, or unknown outcomes.
+- `src/managed-context-adapter.mjs` — private Grant-to-context resolution through one configured
+  adapter authority and one selected driver, with no raw context locator in typed activation or
+  result surfaces.
+- `src/receiver-http-contract.mjs` — internal route, field, and transport-limit constants.
+- `conformance/` — source-repository-only domain-neutral Host, Receiver, Connector, deterministic
+  Agent, and redacted orchestration profile; excluded from runtime exports and package files.
+- `bench/` — bounded protocol, durable Receiver, Agent Adapter, and source-profile local regression
+  entrypoints; excluded from runtime exports and package files.
+- `test/` — positive, negative, tamper, boundary, privacy, rollback, restart, and independent-
+  process tests; fault wrappers remain test-only.
+- `protocol/test-vectors/` — frozen interoperability inputs and outputs.
+
+## Commands
+
+```bash
+npm run verify
+npm test
+npm run test:conformance
+npm run benchmark:protocol
+npm run benchmark:agent-adapter
+npm run benchmark:receiver
+npm run benchmark:profile
+node --test test/receiver-core.test.mjs test/sqlite-receiver-store.test.mjs
+node --test test/separate-process.test.mjs
+```
+
+From a source checkout, run the non-production conformance profile with:
+
+```bash
+node conformance/run.mjs
+```
+
+The package has zero runtime dependencies and targets Node 24 or newer.
+`npm run verify` is the source-checkout closure command: it checks JavaScript syntax, runs the full
+test suite, executes the direct conformance profile, and inspects the dry-run package surface.
+The repository `.node-version` selects the reproducible Node 24 closure runtime; runs on newer local
+runtimes are additional compatibility evidence and must name the executed version.
+`SqliteReceiverStore` is available only through the `./sqlite-receiver-store` subpath, so the
+root, protocol, Host SDK, and Receiver Core imports do not load `node:sqlite` implicitly.
+
+Local verification covers strict shapes, canonical encoding, Ed25519 signing and verification,
+trusted-origin anchoring, tamper and boundary rejection, frozen vectors, Host SDK isolation,
+trusted consent integration, private-output boundaries, atomic run reservation, exact replay,
+authenticated Grant inspection, revocation-before-event and event-before-revocation ordering,
+idempotent revocation replay, target and subject isolation, replayable lease claims, bounded
+reclamation, stale-worker fencing, pre-revocation effect convergence, post-revocation effect
+rejection, transaction rollback, token non-persistence, version-1 migration, and file
+close-and-reopen persistence. Focused transport tests also cover ordinary JSON request mapping,
+no-work responses, bounds, redacted failures, origin policy, redirects, timeouts, malformed or
+stale responses, and absence of automatic retry. The source-repository conformance profile runs
+Host, Receiver, and Connector children independently, exercises one deterministic Agent dispatch,
+rejects acknowledgement before a separate synthetic Host effect, emits one redacted result, and
+cleans its exact temporary files. The forced-restart test reuses those role implementations and
+adds test-only response-loss injection. Both remain local evidence only.
+Deterministic Agent Adapter tests cover credential omission, expiry and correlation rejection,
+all bounded outcomes and unavailable capabilities, one-call behavior, timeout, exception,
+malformed result, immutability, and the no-effect/no-acknowledgement boundary.
+Managed-context adapter tests cover private `grant_id` lookup, exact adapter scoping, active,
+missing, expired, lease-shorter, late-resolution, mismatched, malformed, accessor, exception,
+timeout, and raw-reference non-disclosure behavior. The deterministic authority and driver do not
+prove capture, persistence, or real context activation.
+
+The Receiver benchmark uses file-backed SQLite with WAL and full synchronous durability. The
+profile benchmark cold-spawns the unchanged source conformance runner. Both emit bounded JSON and,
+like the protocol and Agent Adapter measurements, are local regression baselines rather than
+throughput promises, production latency, cross-machine comparisons, or service SLAs.
+
+## Current non-claims
+
+This kernel does not implement a production consent, Grant-control, or pairing session; a consent
+or administration UI; a Grant-control HTTP route; a TLS listener or public Cloud Receiver service;
+a production Connector daemon; durable Connector credential or claim-token storage; a real Host-
+effect verifier; Agent activation; Browser acquisition; WebMCP runtime access; deployment; or a
+selected Host application. Test child processes are evidence scaffolding, not shipping services.
+The conformance profile uses synthetic authorities and is not a production service shell. The
+deterministic adapter is contract evidence, not a runtime fallback or a real Agent. Unsupported
+capability is not replaced by a hidden fallback.

package/node_modules/@webmcp-challenge/reentry-core/package.json

@@ -0,0 +1,38 @@
+{
+  "name": "@webmcp-challenge/reentry-core",
+  "version": "0.1.0",
+  "private": true,
+  "type": "module",
+  "description": "Lightweight domain-neutral contracts for governed WebMCP re-entry.",
+  "files": [
+    "src/",
+    "protocol/test-vectors/"
+  ],
+  "exports": {
+    ".": "./src/index.mjs",
+    "./protocol": "./src/protocol.mjs",
+    "./host-sdk": "./src/host-sdk.mjs",
+    "./receiver-core": "./src/receiver-core.mjs",
+    "./cloud-receiver-http": "./src/cloud-receiver-http.mjs",
+    "./local-connector-client": "./src/local-connector-client.mjs",
+    "./receiver-http-contract": "./src/receiver-http-contract.mjs",
+    "./agent-adapter": "./src/agent-adapter.mjs",
+    "./managed-context-adapter": "./src/managed-context-adapter.mjs",
+    "./sqlite-receiver-store": "./src/sqlite-receiver-store.mjs"
+  },
+  "scripts": {
+    "check:syntax": "node scripts/check-syntax.mjs",
+    "test": "node --test test/*.test.mjs",
+    "test:conformance": "node --test test/protocol.test.mjs",
+    "verify:conformance": "node conformance/run.mjs",
+    "verify:package": "node scripts/verify-package.mjs",
+    "verify": "npm run check:syntax && npm test && npm run verify:conformance && npm run verify:package",
+    "benchmark:protocol": "node bench/protocol.mjs",
+    "benchmark:agent-adapter": "node bench/agent-adapter.mjs",
+    "benchmark:receiver": "node bench/receiver-lifecycle.mjs",
+    "benchmark:profile": "node bench/profile-startup.mjs"
+  },
+  "engines": {
+    "node": ">=24"
+  }
+}

package/node_modules/@webmcp-challenge/reentry-core/protocol/test-vectors/v0.1.json

@@ -0,0 +1,47 @@
+{
+  "protocol_version": "0.1",
+  "issuer_origin": "https://host.example",
+  "key_id": "host_vector_001",
+  "public_key_pem": "-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEAexPFz3rVIm1COdpt2RVq3NBtTM9ycspPEAAVqC3VZlA=\n-----END PUBLIC KEY-----\n",
+  "verification_time": "2026-08-31T03:05:00.000Z",
+  "manifest": {
+    "type": "webmcp.reentry_manifest",
+    "protocol_version": "0.1",
+    "manifest_id": "manifest_vector_001",
+    "correlation_id": "correlation_vector_001",
+    "issuer_origin": "https://host.example",
+    "issued_at": "2026-08-31T03:00:00.000Z",
+    "offer_expires_at": "2026-08-31T03:10:00.000Z",
+    "workflow": {
+      "id": "workflow_vector_001",
+      "type": "domain-neutral-workflow",
+      "state_version": 7,
+      "canonical_url": "https://host.example/workflows/workflow_vector_001"
+    },
+    "display": {
+      "title": "Continue this workflow",
+      "reason": "The authoritative Host state changed while the Agent was away."
+    },
+    "grant_request": {
+      "event_type": "workflow.ready",
+      "grant_expires_at": "2026-08-31T04:00:00.000Z",
+      "max_runs": 1,
+      "human_boundary": "explicit_receiver_consent"
+    },
+    "signature": {
+      "algorithm": "Ed25519",
+      "key_id": "host_vector_001",
+      "value": "GJlwB_hB_o1X-Jk5u7jtAhooFQkQ5F4EWLOnrzPAdxpnjVfP1URSb642Pt2yuCyGjiIZ9ePjgC79kGGXttjrCQ"
+    }
+  },
+  "manifest_canonical_json": "{\"correlation_id\":\"correlation_vector_001\",\"display\":{\"reason\":\"The authoritative Host state changed while the Agent was away.\",\"title\":\"Continue this workflow\"},\"grant_request\":{\"event_type\":\"workflow.ready\",\"grant_expires_at\":\"2026-08-31T04:00:00.000Z\",\"human_boundary\":\"explicit_receiver_consent\",\"max_runs\":1},\"issued_at\":\"2026-08-31T03:00:00.000Z\",\"issuer_origin\":\"https://host.example\",\"manifest_id\":\"manifest_vector_001\",\"offer_expires_at\":\"2026-08-31T03:10:00.000Z\",\"protocol_version\":\"0.1\",\"signature\":{\"algorithm\":\"Ed25519\",\"key_id\":\"host_vector_001\",\"value\":\"GJlwB_hB_o1X-Jk5u7jtAhooFQkQ5F4EWLOnrzPAdxpnjVfP1URSb642Pt2yuCyGjiIZ9ePjgC79kGGXttjrCQ\"},\"type\":\"webmcp.reentry_manifest\",\"workflow\":{\"canonical_url\":\"https://host.example/workflows/workflow_vector_001\",\"id\":\"workflow_vector_001\",\"state_version\":7,\"type\":\"domain-neutral-workflow\"}}",
+  "event_envelope": {
+    "body": "{\"binding_id\":\"binding_vector_001\",\"canonical_url\":\"https://host.example/workflows/workflow_vector_001\",\"correlation_id\":\"correlation_vector_001\",\"event_id\":\"event_vector_001\",\"event_sequence\":1,\"event_type\":\"workflow.ready\",\"issuer_origin\":\"https://host.example\",\"occurred_at\":\"2026-08-31T03:04:00.000Z\",\"protocol_version\":\"0.1\",\"state_version\":8,\"type\":\"webmcp.continuation_event\",\"workflow_id\":\"workflow_vector_001\"}",
+    "headers": {
+      "WebMCP-Reentry-Key-Id": "host_vector_001",
+      "WebMCP-Reentry-Timestamp": "1788145440",
+      "WebMCP-Reentry-Signature": "3Nm3tu0kQJ63HRJy1bq0fMIz7zibO5z01A2wRdUawC7Vu9iY3RM6cUEWmIRfMARX7n6sA5KaXEtk7GadGjHgAA"
+    }
+  },
+  "event_canonical_json": "{\"binding_id\":\"binding_vector_001\",\"canonical_url\":\"https://host.example/workflows/workflow_vector_001\",\"correlation_id\":\"correlation_vector_001\",\"event_id\":\"event_vector_001\",\"event_sequence\":1,\"event_type\":\"workflow.ready\",\"issuer_origin\":\"https://host.example\",\"occurred_at\":\"2026-08-31T03:04:00.000Z\",\"protocol_version\":\"0.1\",\"state_version\":8,\"type\":\"webmcp.continuation_event\",\"workflow_id\":\"workflow_vector_001\"}"
+}