@volter/twin-tunnel 0.1.36 → 1.0.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,123 +1,13 @@
 # @volter/twin-tunnel
 
-> **Legacy connector helpers:** this package still has callable helpers using the retired v1
-> `syncPull` API. Those paths require migration before use on the current kernel;
-> older helper descriptions below do not establish current compatibility. Check the
-> [generated index](../../../generated/INDEX.md) for protocol standing and use the
-> [shared model](../../../docs/concepts/the-model.md) for current state semantics.
-
-A local twin of two tunnel surfaces used by Volter worlds:
-
-- Cloudflare Quick Tunnel allocation (`POST /tunnel`) using the first-party `cloudflared`
-  quick-service field envelope. Generated field values are independent twin-local facts; the twin
-  does not assert undocumented relationships among `id`, `name`, `hostname`, or `account_tag`.
-- The owned `@volter/tunnel` WebSocket control protocol and HTTP relay path.
-
-The boundary is deliberate. The control plane is twinned; payload transport is real loopback
-HTTP. `world-tunnel quick --url ...` prints the machine-readable
-`VOLTER_SHARE_URL=http://127.0.0.1:...` handshake and genuinely forwards through that loopback
-ingress. It does not claim Cloudflare edge QUIC, public DNS, TLS, reachability, or an SLA. Those
-remain real deployment concerns. `quick --url` accepts a credential-free loopback HTTP(S) origin
-only; path/query/fragment and backslash-normalized inputs are rejected rather than silently
-discarded while forwarding.
-
-```bash
-# Local share rehearsal used by world cookbooks
-world-tunnel quick --url http://127.0.0.1:3000
-
-# Standalone quick API + Volter relay
-world-tunnel serve --port 8787 --root .volter/world/tunnel
-world-tunnel conformance
-# Cloudflare control URL: http://127.0.0.1:8787/tunnel
-# @volter/tunnel host:   http://127.0.0.1:8787
-```
-
-An unmodified `@volter/tunnel` client registers against the `serve` URL and forwards requests to
-its configured local port. Its normal default (`authRequired: true`) is preserved: anonymous
-requests receive 401, and the server's `mintToken(tunnelId)` helper creates a fake-local,
-tunnel-bound HS256 token for Bearer/query/cookie rehearsal. Matching the owned relay default, a
-valid signed token without `tid` is shared SSO while a present `tid` must match; start `serve` with
-`--require-tid` to select the owned `REQUIRE_TID=true` policy. Basic-auth values remain only in the
-live socket session; the append-only kernel stores a SHA-256 digest and configured bit, never the
-plaintext. As upstream does, Basic auth is configured only when both user and password are
-non-empty; an SDK-emitted empty value leaves that gate disabled. The twin accepts any non-empty
-fake relay credential and rejects a missing one.
-
-**Browser WebSockets relay for real.** A `ws://<relay>/__twin/tunnels/<id>/<path>` upgrade passes
-the same Basic/JWT gates the HTTP path does, then bridges: the relay sends `ws-upgrade` with a
-fresh `connId`, the tunnelled path and the browser’s own handshake headers; the client answers
-`ws-ready` (or `ws-error`, which closes the browser socket with 1011 and the client’s own reason);
-`ws-message` carries base64 payloads with the `binary` flag in both directions; `ws-close` bridges
-either way with the vendor’s own code clamping. Frames a browser sends before `ws-ready` are
-QUEUED and delivered in order rather than dropped, a control socket may only drive the `connId`s
-it owns, and a control socket closing takes its bridges with it. `request-abort` is now sent from
-ONE place for every way a request can end badly — timeout, visitor hang-up, malformed frame, owner
-disconnect — so the client always stops producing for a request the relay has forgotten.
-
-Still explicit capability todos: reliable end-to-end incremental delivery and its
-backpressure/cancellation (see "the streaming trade" below), account/reservation management,
-usage metering, inspector/replay, and Cloudflare managed tunnels.
-
-There is no UI mirror. Both products' relevant surface is a CLI/control protocol; their hosted
-dashboards are incidental account and operations tooling, not an agent navigation target.
-
-## Coverage
-
-The capability manifest in `src/tunnel-capabilities.ts` is the honest denominator for both the
-Cloudflare Quick Tunnel allocation surface and the owned Volter relay. Run
-`bun scripts/twin-capabilities.ts tunnel` for the current counts. Every capability is classified
-as done or planned; nothing disappears behind a broad feature label.
-
-### Done (proven, verifiable)
-
-- Cloudflare Quick Tunnel allocation envelope, unique ephemeral allocations, persistence,
-  read-only refusal, and bounded reserved-route/loopback-origin handling.
-- Real loopback forwarding through both the quick adapter and the owned relay, including method,
-  path, body, status, the owned cache/privacy response-header rules, CORS preflight,
-  malformed-frame containment, and single durable/live ownership under overlapping claims.
-- Relay registration, replacement, disconnect, authentication, JWT bootstrap/cookie behavior,
-  session-only Basic-auth plaintext, persistence ordering, and live status.
-- An authoritative 15-discriminator census imported from `@volter/tunnel-core`, with one explicit
-  capability row per frame; implemented frames have transport proofs and unimplemented frames
-  remain planned. Fourteen of the fifteen now carry transport proofs — everything but `quota` —
-  driven over a genuine loopback WebSocket against a real local server, with the pretend client
-  a harness shaped after the owned client's `handleWsUpgrade` — it dials with the offered
-  subprotocols, strips the hop-by-hop handshake headers, and reports a real local failure as
-  `ws-error`; it does not reproduce the client's `x-forwarded-*` re-stamping, its 15s dial
-  timeout or `safeClose`'s teardown, none of which any assertion depends on.
-- Visitor-disconnect abort: a browser hang-up before `response-start` sends `request-abort`, and
-  the request is genuinely FORGOTTEN — a late response frame naming it is refused.
-- Read-only connector pull, mapping, idempotence, refusal-state survival, conformance, and the
-  fail-closed persistent live-call budget.
-
-### The streaming trade, measured
-
-The relay BUFFERS a streamed response to `response-end` before answering the visitor, and that is
-a measured choice rather than an unfinished one. On this runtime a response body that has begun
-cannot be failed THROUGH `Bun.serve`'s response surface: erroring the `ReadableStream` behind a
-`Response` ends the chunked body cleanly,
-so a visitor reads a truncated payload as a successful 200 and cannot tell it from a complete one
-— and a `content-length` that would have made the truncation detectable is dropped the moment the
-body is a stream. `node:http` on the SAME runtime CAN signal it (`src/tunnel-stream-boundary.test.ts`
-measures that too) — so this is a trade with a named alternative, not an impossibility: re-hosting
-the HTTP plane would mean giving up `server.upgrade`, which the entire WebSocket bridge is built
-on. The first two measurements go RED the day `Bun.serve` gains the ability; that is the signal to build
-`tunnel.volter.http.streaming`, `…stream_backpressure` and `…stream_cancel_abort` and revisit the
-trade. Committing the head today would buy latency and sell the ability to fail a response
-honestly — which is what keeps the malformed-sequence 502 reachable at all.
-`stream_backpressure` has a second, independent blocker: the owned protocol's fifteen
-discriminators contain no pause frame, so a relay cannot ask a client to slow down.
-
-### Planned (todo — covered by default, not yet built)
-
-- Reliable incremental streaming, backpressure and cancellation (blocked as above).
-- Reconnect/backoff, quota frames, forwarded/response-header rules, rate limiting, and
-  constant-time shared-secret comparison.
-- Managed tunnel/account/reservation/usage/signup/inspector surfaces and confirmed public push.
-- Cloudflare Quick Tunnel concurrency and SSE limitations, plus Cloudflare managed tunnels.
-
-### No UI mirror
-
-The modeled products expose a CLI, HTTP API, and WebSocket control protocol. Their hosted account
-dashboards are operations tooling rather than an agent workflow, so this package deliberately has
-no React mirror and no UI capabilities. Coverage is API + connector.
+The tunnel relay twin (Protocol 3): Volter's volter-tunnel relay as Volter Harness's remote access uses it
+([journeys/demand.json](./journeys/demand.json)). A client opens the control socket (`/ws?id=<tunnelId>`) and
+registers with its account's token; it is told its tunnel's URL (`https://<tunnelId>.voltertest.xyz`). A request to
+that host (or `?__tunnel=<id>` on the relay's direct host) is sent down the socket as a `request` frame and answered with
+what the client sends back: a whole `response`, or `response-start`, `response-chunk`s and `response-end` (the kernel's
+request answered by a session). No client holding the tunnel is 502 "Tunnel not connected"; no answer in 30 s is 504; a
+body over 750000 bytes is 413. A second registration of a live id needs `replace` (the first is closed 4001); another
+account's id and a bad token are refused. Browser WebSocket bridging, quotas and the inspector are not served.
+
+The World's door: `POST /_twin/accounts` ({ slug }: an account and its token). The credential door answers TUNNEL_SECRET
+and the relay URL (TUNNEL_SERVER_URL, SUPERCODE_TUNNEL_SERVER_URL).

package/dist/generated/pack-facts.json

@@ -0,0 +1,54 @@
+{
+  "//": "GENERATED by scripts/pack-facts.ts — current pack descriptors and explicit world-runtime server backings; no prior-artifact entries are retained.",
+  "packs": {
+    "tunnel": {
+      "adoption": {
+        "sdks": [
+          "@volter/tunnel"
+        ],
+        "envStems": [
+          "TUNNEL",
+          "VOLTERTUNNEL"
+        ]
+      },
+      "hosts": [
+        {
+          "host": "voltertest.xyz"
+        },
+        {
+          "suffix": ".voltertest.xyz"
+        },
+        {
+          "host": "www.voltertest.xyz",
+          "exclude": true
+        },
+        {
+          "host": "twins.voltertest.xyz",
+          "exclude": true
+        }
+      ],
+      "archetype": "proxy",
+      "protocol": {
+        "declared": "3",
+        "major": 3,
+        "standing": "current"
+      },
+      "transport": "rest",
+      "resources": [],
+      "endpointEnvNone": "the relay URL is the credential door's (TUNNEL_SERVER_URL, SUPERCODE_TUNNEL_SERVER_URL), the World claiming voltertest.xyz",
+      "credentialDoor": {
+        "path": "/_twin/accounts",
+        "body": {
+          "slug": "world"
+        },
+        "fill": {
+          "TUNNEL_SECRET": "token",
+          "TUNNEL_SERVER_URL": "server",
+          "SUPERCODE_TUNNEL_SERVER_URL": "server"
+        }
+      },
+      "serveExport": "createTunnelTwinServer"
+    }
+  },
+  "undeclared": []
+}

package/dist/spec/SOURCE.md

@@ -0,0 +1,14 @@
+# volter-tunnel relay spec — provenance
+
+- **Why this document:** the relay publishes no OpenAPI document. Its contract is volter-ai/volter-tunnel at
+  `c14b6e3` (2026-09-28): `packages/core/src/protocol.ts` (the control channel's frames, "the single source of truth
+  for the messages exchanged over the control WebSocket between a client and the relay") and the Cloudflare relay,
+  `server-cf/src/worker.ts` (routing: the control channel at `/ws?id=<tunnelId>`; a tunnel at `<tunnelId>.<domain>`,
+  or `?__tunnel=<id>` on a direct host such as localhost; `/api/status` at the apex) and `server-cf/src/tunnel-do.ts`
+  (registration: `registered` with `url: https://<tunnelId>.<domain>`, a rejected credential `{type:"error"}` then
+  close 4003, a replaced client closed 4001 "Replaced by new client"; a public request: 502 "Tunnel not connected",
+  504 "Tunnel timeout" after 30 s, 413 over 750000 bytes of body; the reply frames `response`, `response-start`,
+  `response-chunk`, `response-end`). The domain is `voltertest.xyz` (`server-cf/wrangler.jsonc`, `TUNNEL_DOMAIN`).
+- **Corrections:** none.
+- **Read by:** the twin orchestrator, 2026-09-30.
+- **Vendored bytes (sha256):** `openapi.json` `b4fcdc3d599026bef687c946cea3c8837c63ff982e5d899df1425e585832aebd`.

package/dist/spec/openapi.json

@@ -0,0 +1,18 @@
+{
+ "openapi": "3.0.2",
+ "info": {
+  "title": "volter-tunnel relay",
+  "version": "2",
+  "description": "The volter-tunnel relay's HTTP surface at its apex: its status. A client's control channel (a WebSocket at /ws?id=<tunnelId>) and the public requests it answers (every path of <tunnelId>.<domain>) are the relay's protocol, recorded in spec/SOURCE.md. Written from volter-ai/volter-tunnel (spec/SOURCE.md)."
+ },
+ "servers": [{ "url": "https://voltertest.xyz" }],
+ "paths": {
+  "/api/status": {
+   "get": {
+    "operationId": "getStatus",
+    "summary": "The relay's status.",
+    "responses": { "200": { "description": "The relay is up.", "content": { "application/json": { "schema": { "type": "object", "properties": { "ok": { "type": "boolean" }, "relay": { "type": "string", "example": "cloudflare-do" } } } } } } }
+   }
+  }
+ }
+}

package/dist/src/cli.js

@@ -1,59 +1,21 @@
 #!/usr/bin/env node
-import { keepProcessAlive } from '@volter/world-core/lifecycle';
+// world-tunnel: serve the tunnel twin.
 import { hasFlag, optionValue } from '@volter/world-core/args';
-import { createTunnelTwinServer, parseTunnelLoopbackOrigin } from "./tunnel-server.js";
-const [command, ...args] = process.argv.slice(2);
-const rawPort = optionValue(args, '--port');
-const port = rawPort === undefined ? undefined : Number(rawPort);
-if (port !== undefined && (!Number.isInteger(port) || port < 0 || port > 65535)) {
-    process.stderr.write(`world-tunnel: --port must be an integer 0-65535 (got ${JSON.stringify(rawPort)})\n`);
-    process.exit(2);
-}
-const root = optionValue(args, '--root') || undefined;
-if (command === 'serve') {
-    const server = createTunnelTwinServer({
-        ...(port ? { port } : {}),
-        ...(root ? { root } : {}),
-        readOnly: hasFlag(args, '--read-only'),
-        requireTid: hasFlag(args, '--require-tid'),
-    });
-    process.stdout.write(`tunnel twin listening on ${server.url}\n`);
-    process.stdout.write(`Volter SDK host=${server.url}; Cloudflare quick service=${server.url}\n`);
-    await keepProcessAlive();
-}
-else if (command === 'quick' || command === 'tunnel') {
-    const origin = optionValue(args, '--url');
-    if (!origin) {
-        process.stderr.write('world-tunnel quick requires --url http://127.0.0.1:<port>\n');
-        process.exit(2);
-    }
-    try {
-        parseTunnelLoopbackOrigin(origin);
-    }
-    catch (error) {
-        process.stderr.write(`world-tunnel quick: ${error instanceof Error ? error.message : String(error)}\n`);
-        process.exit(2);
-    }
-    const server = createTunnelTwinServer({ ...(port ? { port } : {}), ...(root ? { root } : {}) });
-    const allocation = await fetch(`${server.url}/tunnel`, { method: 'POST', headers: { 'content-type': 'application/json' }, body: '{}' });
-    const body = await allocation.json();
-    if (!allocation.ok || !body.success || !body.result)
-        throw new Error('quick-tunnel allocation failed');
-    server.registerQuickOrigin(body.result.id, origin);
-    // The world runtime discovers the first URL in stdout. This is deliberately a loopback URL:
-    // the twin proves the control plane and genuine HTTP forwarding, not Cloudflare edge/DNS/TLS.
-    process.stdout.write(`VOLTER_SHARE_URL=${server.url}\n`);
+import { keepProcessAlive } from '@volter/world-core/lifecycle';
+import { createTunnelTwinServer } from "./server.js";
+const [cmd, ...rest] = process.argv.slice(2);
+const port = Number(optionValue(rest, '--port', '0')) || undefined;
+const root = optionValue(rest, '--root') || undefined;
+const readOnly = hasFlag(rest, '--read-only');
+// the World's managed Postgres, which the runtime binds a pack declaring managedDatabase to
+const database = optionValue(rest, '--database') || undefined;
+// the World's scenario file, for a model vendor's turns
+const scenarioPath = optionValue(rest, '--scenario') || undefined;
+if (cmd === 'serve' || cmd === undefined) {
+    const s = await createTunnelTwinServer({ readOnly, ...(root ? { root } : {}), ...(port ? { port } : {}), ...(database ? { database } : {}), ...(scenarioPath ? { scenarioPath } : {}) });
+    process.stdout.write(`tunnel twin${readOnly ? ' [read-only]' : ''} at http://127.0.0.1:${s.port}\n`);
     await keepProcessAlive();
 }
-else if (command === 'conformance') {
-    // Dev-only and lazy: the runtime entrypoint does not pull conformance into normal serve/share.
-    const { checkTunnelConformance } = await import("./tunnel-conformance.js");
-    const report = await checkTunnelConformance({ ...(root ? { root } : {}) });
-    process.stdout.write(`${JSON.stringify(report, null, 2)}\n`);
-    if (!report.ok)
-        process.exitCode = 1;
-}
 else {
-    process.stdout.write('Usage: world-tunnel serve|conformance [--port N] [--root DIR] [--read-only] [--require-tid]\n');
-    process.stdout.write('       world-tunnel quick --url http://127.0.0.1:<port> [--port N] [--root DIR]\n');
+    process.stdout.write('Usage: world-tunnel serve [--port N] [--root DIR] [--read-only] [--database URL] [--scenario FILE]\n');
 }

package/dist/src/fetch.d.ts

@@ -0,0 +1,2 @@
+import { type DerivedFetch, type PackFetchOptions } from '@volter/world-core';
+export declare function createTunnelFetch(options?: PackFetchOptions): DerivedFetch;

package/dist/src/fetch.js

@@ -0,0 +1,19 @@
+// GENERATED by scripts/create-pack.ts (--init, --index): a fixed file. The kernel serves the discovery door, the clock,
+// the World's doors, the vendor's screens and the API from the pack's parts (architecture, "The pack contract").
+import { createPackFetch } from '@volter/world-core';
+import surface from './generated/surface.gen.json' with { type: 'json' };
+import { manifest } from "./manifest.js";
+import { around } from "./semantics/around.js";
+import * as sockets from "./semantics/sockets.js";
+import * as doors from "./semantics/doors.js";
+import { tunnelSemantics } from "./semantics/index.js";
+export function createTunnelFetch(options = {}) {
+    return createPackFetch({
+        manifest,
+        surface: surface,
+        handlers: tunnelSemantics,
+        doors,
+        around,
+        sockets,
+    }, options);
+}

package/dist/src/generated/surface.gen.json

@@ -0,0 +1 @@
+{"generatedBy":"scripts/derive-pack.ts","spec":"openapi.json","format":"openapi","version":"2","resources":[],"operations":[{"id":"getStatus","method":"get","path":"/api/status","pathParams":[],"query":[],"body":[],"bodyEncoding":"none","successStatus":200,"class":"computed"}]}

package/dist/src/generated/ui.gen.json

@@ -0,0 +1 @@
+{"generatedBy":"scripts/derive-pack.ts","resources":{"_account":{"actions":[],"states":{},"embeds":{}},"_tunnel":{"actions":[],"states":{},"embeds":{}}}}

package/dist/src/index.d.ts

@@ -1,7 +1,5 @@
-export { createTunnelTwinFetch, createTunnelTwinHandler, createTunnelTwinServer } from './tunnel-server.js';
-export { handleTunnelRelayMessage, handleTunnelTwinRequest } from './tunnel-twin.js';
-export { liveTunnelExecute, mapTunnelRelay, pullTunnelRelay, syncTunnelFromReal } from './tunnel-connector.js';
-export { TunnelBudget, TunnelBudgetError, TUNNEL_RATE_BUDGET, TUNNEL_BUDGET_CEILING, TUNNEL_BUDGET_WINDOW_MS, TUNNEL_CALL_WEIGHTS, } from './tunnel-budget.js';
-export type { RelayControlMessage, RelaySession, TunnelRequest, TunnelResponse } from './tunnel-twin.js';
-import type { TwinPack } from '@volter/world-core';
-export declare const pack: TwinPack;
+import { manifest } from './manifest.js';
+export { createTunnelFetch } from './fetch.js';
+export { createTunnelTwinServer } from './server.js';
+export { manifest };
+export declare const pack: import("@volter/world-core").PackDescriptor;

package/dist/src/index.js

@@ -1,42 +1,8 @@
-export { createTunnelTwinFetch, createTunnelTwinHandler, createTunnelTwinServer } from "./tunnel-server.js";
-export { handleTunnelRelayMessage, handleTunnelTwinRequest } from "./tunnel-twin.js";
-export { liveTunnelExecute, mapTunnelRelay, pullTunnelRelay, syncTunnelFromReal } from "./tunnel-connector.js";
-export { TunnelBudget, TunnelBudgetError, TUNNEL_RATE_BUDGET, TUNNEL_BUDGET_CEILING, TUNNEL_BUDGET_WINDOW_MS, TUNNEL_CALL_WEIGHTS, } from "./tunnel-budget.js";
-import { TUNNEL_RATE_BUDGET as RATE_BUDGET } from "./tunnel-budget.js";
-export const pack = {
-    vendor: 'tunnel',
-    // The SAME object tunnel-budget.ts declares at module load — one source of truth, so
-    // registering the pack and importing the connector can never arm two different ceilings.
-    rateBudget: RATE_BUDGET,
-    // The CONTROL plane is HTTP/REST (POST /tunnel, GET /api/status). The relay's control link is a
-    // WebSocket and its data path is real loopback HTTP — neither is a raw line protocol, so this is
-    // not the `raw-tcp` class; the split is described in the README and spec-sources.json.
-    transport: 'rest',
-    archetype: 'proxy',
-    bin: 'world-tunnel',
-    // The subject types the twin stores: `quick_tunnel`/`relay_tunnel` written by tunnel-twin.ts,
-    // and `relay` folded by the connector's status pull (mapTunnelRelay).
-    resources: ['quick_tunnel', 'relay_tunnel', 'relay'],
-    specSource: 'No single first-party machine-readable spec spans this combined pack. The Cloudflare Quick Tunnel ' +
-        'half is pinned to first-party cloudflared commit 733bfb939963e150dcf5c4faddb1603f744fbc98 (POST ' +
-        '/tunnel and its {success,result,errors} envelope) plus Cloudflare\'s own Quick Tunnels docs; the ' +
-        'owned Volter relay half is pinned to volter-ai/volter-tunnel commit ' +
-        'a5abc6287384429d32cde200d8ecd042814e6619 (@volter/tunnel 2.0.5, @volter/tunnel-core\'s 15 control ' +
-        'frames). See spec-sources.json.',
-    description: 'Cloudflare Quick Tunnel control-plane and owned Volter relay twin — POST /tunnel allocation and the ' +
-        '@volter/tunnel WebSocket control protocol, with a genuine loopback HTTP data path (no Cloudflare ' +
-        'edge, DNS, TLS or SLA claimed).',
-    // INTERCEPTION RULING — hostsNone, the pack's own home for it: no injector entry by design:
-    // native cloudflared is an external binary, while @volter/tunnel opens a configurable
-    // WebSocket control channel and the CLI reads TUNNEL_SERVER_URL. Worlds wire that app-read
-    // endpoint directly; claiming api.trycloudflare.com in the Node injector would not redirect
-    // cloudflared and would falsely imply the Cloudflare edge data plane was twinned.
-    hostsNone: "no injector entry by design: native cloudflared is an external binary, while @volter/tunnel opens a configurable WebSocket control channel and the CLI reads TUNNEL_SERVER_URL. Worlds wire that app-read endpoint directly; claiming api.trycloudflare.com in the Node injector would not redirect cloudflared and would falsely imply the Cloudflare edge data plane was twinned",
-    // Adoption, moved off the central maps unchanged (descriptor-first back-migration, adding-a-twin.md §3,
-    // 2026-08-31).
-    adoption: {
-        // Internal Volter tunnel; the client is `@volter/tunnel` and there is no Python distribution.
-        pypi: [],
-        sdks: ['@volter/tunnel'], envStems: ['TUNNEL', 'VOLTERTUNNEL'],
-    },
-};
+// @volter/twin-tunnel — the tunnel twin (Protocol 3). A fixed file: the descriptor is the manifest's.
+import { packOf, registerPack } from '@volter/world-core';
+import { manifest } from "./manifest.js";
+export { createTunnelFetch } from "./fetch.js";
+export { createTunnelTwinServer } from "./server.js";
+export { manifest };
+// The descriptor: twin-world's architecture, "The descriptor"; declared in manifest.ts.
+export const pack = registerPack(packOf(manifest));

package/dist/src/manifest.d.ts

@@ -0,0 +1,2 @@
+import type { DerivedManifest } from '@volter/world-core';
+export declare const manifest: DerivedManifest;