@jimhoyd/urlcode 0.4.0-alpha.1 → 0.4.0-alpha.3

package/ROADMAP.md

@@ -1,331 +1,61 @@
-# Public roadmap
-
-URLCode is a portable runtime for programmable URL behavior, not a URL
-shortener. Live links are one handler in the broader project contract. The
-[project direction](docs/PROJECT-DIRECTION.md) explains how application
-projects and provider adapters fit without redefining or restricting the free
-runtime.
-
-This is the public delivery sequence. Tests accompany every feature, not a
-separate late phase. The stable 0.1 self-hosted release covers much of M0/M1 plus initial
-process/container packaging and benchmarks. Provider adapters and the remaining
-production-readiness gates remain open.
-
-## 0.4.0-alpha.1 — current alpha
-
-`0.4.0-alpha.1` is the first alpha of the extension contract and the agent
-tooling on top of the `0.3.0` self-hosted release. It carries: the
-revision-pinned extension contract, capabilities and provider conformance,
-strict redirect interchange, bulk import, recipes and search, TypeScript
-guests, conditions, bounded proxy and signals, MCP read and authoring modes,
-the `context`, `explain`, `manifest` and `schema` queries, short forms,
-route-level auth, `init --with`, the agent benchmark harness, `llms-full`,
-and the generated `AGENTS.md` and skill. It is an alpha: provider
-deployments, soak and independent security review remain open. The
-extension packages declare `@jimhoyd/urlcode >=0.4.0-alpha.1 <0.5.0` and
-are published after core.
-
-## Extensions: accounts, administration and presentation — implemented, unreleased
-
-The runtime now carries a generic, revision-pinned extension contract
-(`@jimhoyd/urlcode/extensions`, [extensions](docs/EXTENSIONS.md)): a project
-declares versioned `extensions.<name>` blocks, exclusive `extension` mounts and
-`policies.extensions` requirements; the operator supplies the implementations
-in a host file loaded with `--host-file`, outside the project. Guest requests
-never see `Cookie`, `Authorization` or declared credential headers. Cloudflare
-refuses extensions until its artifact format can run them.
-
-The implementations live in their own repositories, each with an
-implementation-status file that is the authoritative feature list:
-[urlcode-auth](https://github.com/jimhoyd-com/urlcode-auth) (accounts, sessions,
-MFA, roles, account page, operator CLI), [urlcode-admin](https://github.com/jimhoyd-com/urlcode-admin)
-(users, sessions, roles, audit, approvals, cases, impersonation) and
-[urlcode-ui](https://github.com/jimhoyd-com/urlcode-ui) (escaped templates,
-partials, themes, translations). All three are Apache-2.0 and published to
-npm as `0.1.0-alpha.1` while first-release acceptance is reviewed; see
-[issue 58](https://github.com/jimhoyd-com/urlcode/issues/58) for what remains:
-browser and device WebAuthn coverage, accessibility assessment, soak, backup
-and recovery drills on a deployment, live provider senders and independent
-security review. [The framework](docs/FRAMEWORK.md) describes how the four
-packages compose, and [next steps](docs/NEXT-STEPS.md) is the phased plan to
-close the remaining gaps.
-
-## Capability foundation — implemented, unreleased
-
-`urlcode capabilities [--target self-hosted|cloudflare|aws|vercel] [--json]`
-and the public capability API centralize target support for handlers, bindings
-and effective policies. Runtime activation and Cloudflare builds use the shared
-preflight; unknown targets fail closed and unsupported requirements identify the
-route and capability before resources or artifacts are created. The existing
-compiled route IR is documented, not replaced. Configuration-dependent and
-delegated behavior remain explicit; all provider deployments remain unverified.
-See [capabilities](docs/CAPABILITIES.md) and the
-[next-phase review and implementation status](docs/NEXT-PHASE-PLAN.md).
-
-## Portability and URL behavior — implemented, unreleased
-
-Strict redirect interchange supports CSV/JSON/YAML, Netlify and Cloudflare
-`_redirects`, a bounded Netlify TOML subset and Vercel redirects. Conversion
-reports refuse unsupported semantics; provider differences require explicit
-acknowledgment and are never called lossless. A synthetic conformance fixture
-and bounded HTTPS runner distinguish local adapter tests from observed
-provider deployments. Actual Cloudflare/AWS/Vercel deployment evidence remains
-pending; this does not complete M4.
-
-Exact query/header/cookie/origin/method conditions and disjoint conditional
-redirect/response cases run in the self-hosted, AWS and Vercel runtimes.
-Cloudflare refuses these until its compiler can preserve their semantics.
-Self-hosted proxy and webhook signals use explicit revision-pinned operator
-origin grants, connection-pinned public DNS and bounded transport. Signals
-have no durable delivery or retry guarantee. Other targets refuse proxy and
-signals. See [conditions](docs/CONDITIONS.md), [egress](docs/EGRESS.md),
-[interchange](docs/INTERCHANGE.md) and
-[provider verification](docs/PROVIDER-VERIFICATION.md).
-
-## Developer ecosystem — implemented, unreleased
-
-Bundled Git-owned recipes, safe bulk imports into route includes, build-time
-TypeScript guest transpilation, read-only inspection APIs and optional stdio
-MCP tooling are available. The runtime still executes only JavaScript inside
-QuickJS/WASM; TypeScript authoring does not add host execution. Bulk benchmarks
-successfully cover 1,000, 10,000 and 100,000 routes without relaxing parser
-limits. See [recipes](docs/RECIPES.md), [bulk evidence](docs/BULK.md),
-[TypeScript authoring](docs/TYPESCRIPT-AUTHORING.md) and
-[SDK/MCP](docs/TOOLING.md). These features do not supply durable signals,
-protected downloads, a remote marketplace or provider deployment proof.
-
-## TypeScript source and shipped declarations — implemented, unreleased
-
-The runtime, scripts, tests and benchmarks are TypeScript under a strict
-configuration, checked by `npm run typecheck` inside `npm run verify`. The
-package ships `dist/`: Node's own type stripping of the source with the
-specifier extension rewritten, so it is the same JavaScript line for line,
-plus `.d.ts` declarations for every export (`urlcode`, `@jimhoyd/urlcode/plugins`,
-`@jimhoyd/urlcode/policies`, `@jimhoyd/urlcode/observability`, `@jimhoyd/urlcode/compliance`,
-`@jimhoyd/urlcode/prerender` and the three provider entries). `dist` is never
-committed; the build runs in the digest-pinned release container, its hashes
-are recorded in the manifest, and a CI job builds twice and diffs the trees.
-Measured cold start, throughput and memory of `dist/` equal the previous
-JavaScript (see [performance](docs/PERFORMANCE.md)). Contributors need Node
-22.18+ to run the source directly; installed packages still run on 22.13+.
-See [TypeScript](docs/TYPESCRIPT.md).
-
-## Host policies and plugins — implemented, unreleased
-
-A `policies` block in YAML, reusable `profiles` and an operator plugin API
-close the gaps the [extensions spike](docs/SPIKE-EXTENSIONS.md) ranked
-highest: no cross-cutting behavior, no per-client throttle, no bot policy, no
-security-header preset, no compression and no response cache. Five policies
-(`throttle`, `agents`, `security`, `compression`, `cache`) run in the host
-process after route match and before the route contract, all off by default,
-with a per-target table that refuses at activation what a target cannot
-enforce: the serverless adapters take `agents`, `security`, `cache` and
-route-partitioned `throttle`; the Cloudflare build compiles `agents` and
-`security` into the artifact and refuses the rest with the route named.
-`--trusted-proxies` names the hops allowed to set `X-Forwarded-For` for client
-identity. Plugins are host code passed to `startServer` and the adapters on
-the same hook seam the policies use; nothing in YAML names one. See
-[policies](docs/POLICIES.md) and [plugins](docs/PLUGINS.md).
-
-This checkpoint is on a branch and not in a published release. An
-interoperability review of the five policies together, the spike's `report`
-mode headers on every target and the audit's policy table remain open, and no
-deployment has exercised a policy on a provider.
-
-## Provider adapters — Vercel and AWS Lambda native handlers
-
-`@jimhoyd/urlcode/vercel` serves a project as a Vercel Node function, reusing the
-runtime's transport-agnostic handle() and a shared response writer, so a
-deployment returns byte-identical status, body and headers to the self-hosted
-server. Bindings arrive through a `URLCODE_POLICY` environment variable holding
-the same revision-pinned grant document the operator policy file carries.
-
-Native handlers only: isolated functions, middleware and stored live links are
-refused at activation, because every cold start would pay worker and WASM
-startup and a serverless filesystem cannot hold a durable link store. The
-`@jimhoyd/urlcode/aws` does the same for a Lambda Function URL or API Gateway HTTP API.
-Payload format 2.0 only: format 1.0 supplies an already-decoded path and query,
-and this runtime rejects ambiguous encoding deliberately, so rebuilding a target
-from decoded parts would misrepresent the request. Response policy, including
-content length, now lives in one place shared by every host rather than partly
-relying on Node's implicit behaviour.
-
-Neither adapter has been deployed; see the [Vercel](docs/VERCEL.md) and
-[AWS](docs/AWS.md) guides, which state what stays unverified as a result.
-
-## Provider targets — Cloudflare Workers
-
-Cloudflare Workers has no worker threads, no filesystem and no runtime code
-generation, so it gets a compiler rather than an adapter: `urlcode build
---target cloudflare` emits a Worker, the compiled routes and Ajv standalone
-validators, and `@jimhoyd/urlcode/cloudflare` serves them with the same matching, request
-policy and response policy as every other host. Declarative routes only —
-redirects and declared responses with parameters, defaults, validation, response
-headers, `enabled` and `expires`. Functions, middleware, stored links, assets and
-bindings are refused at build time with the route named, so an unsupported
-project fails the build instead of the deployment. Bindings are refused even as
-literals, because a build artifact must never carry a secret.
-
-Making this possible moved request-time matching into `src/match.ts` and header
-validation into `src/header-validation.ts`, both free of Node imports, so one
-implementation now serves the Node server, the serverless adapters and the
-Worker. `test/header-validation.test.ts` compares the header rules against
-`node:http` across the full character range, because disagreeing there is header
-injection, and `test/cloudflare.test.ts` asserts the Worker and the self-hosted
-server return the same status, body and headers for the same project.
-
-This has not been deployed to Cloudflare; see the
-[Cloudflare guide](docs/CLOUDFLARE.md) for the two request-level differences the
-platform imposes and what stays unverified.
-
-## Installation and publication — 0.1.0
-
-Added a tag-driven release workflow that reuses the audited candidate build path,
-publishes a GitHub release with the signed tarball, SBOM, manifest, `SHA256SUMS`
-and a rendered Homebrew formula, and optionally publishes to npm (with
-provenance) and GHCR behind repository variables. Added a checksum-verifying
-`install.sh`, a Homebrew formula template rendered only from measured bytes, and
-an [installation guide](docs/INSTALL.md) covering npm, Homebrew, the script, the
-container and provenance verification.
-
-0.1.0 was released from this pipeline: the GitHub release carries the signed
-tarball, SBOM, manifest, `SHA256SUMS` and Homebrew formula, and an install from
-the published release was verified end to end. npm and GHCR publication stay
-opt-in and remain unproven until enabled, so the Homebrew formula's registry URL
-does not resolve yet.
-
-Added tunnel and [monitoring](docs/MONITORING.md) recipes, and extended
-`urlcode benchmark` to measure a running deployment through its real path with
-warm-up and shed/transport separation; see [load testing](docs/LOAD-TESTING.md).
-M3's remaining gap is sustained soak and slow-peer behaviour, which that tool
-does not cover.
-
-## Hardening checkpoint — alpha.8
-
-Bound HTTP admission and inactive sockets, drain accepted link writes on shutdown,
-reject invalid store metadata, and correct management defaults/method responses.
-The [readiness register](docs/RELEASE-READINESS.md) distinguishes tested safeguards
-from deployment and stable-release gates. Feature breadth does not imply stability.
-
-## Live short links — alpha.8
-
-Implemented an optional native `link` handler, local SQLite persistence, CLI CRUD
-and a separate authenticated management API. Links become visible without YAML
-changes/reloads; versioned writes prevent silent lost updates. No guest storage
-or network access is added. Same-host only; distributed storage, general state,
-user accounts and provider adapters remain open. See [dynamic links](docs/DYNAMIC-LINKS.md).
-
-## Middleware — alpha.7
-
-Implemented route-local ordered `next()` middleware around every handler, early
-responses, request-local state and shared sandbox deadlines. Plain native routes
-retain their fast path. Native bodies stay opaque; middleware coverage requires
-explicit assertions. See [middleware](docs/MIDDLEWARE.md).
-
-## One starter — alpha.6
-
-`urlcode init <directory>` always creates the same function-plus-redirect project.
-There is no template selector. The public urlcode-template repository mirrors
-those examples with a pinned npm dependency. Richer asset examples remain under
-examples/assets. Historical starter branches are not maintained.
-
-## Route readiness and local project benchmarks — alpha.5
-
-Implemented route inventory, expected-count checks, active route/method coverage,
-generated native probes plus explicit fixtures, and bounded assertion-aware local
-benchmarks. [Readiness](docs/READINESS.md) documents the gate and remaining deployment,
-soak, remote-destination and business-coverage work. This does not complete M3/M4.
-
-## HTTP configuration and standalone starter — 0.1.0-alpha.4
-
-Implemented bounded request body/media-type/JSON checks, literal response headers
-and separate Set-Cookie values, and native text/JSON responses. See [HTTP](docs/HTTP.md)
-for precise scope; automatic CORS, multipart, streaming and other listed features
-remain open. The public [urlcode-template](https://github.com/jimhoyd-com/urlcode-template)
-provides two routes with a pinned runtime dependency and cross-platform CI.
-
-## Native assets — 0.1.0-alpha.3
-
-Implemented the page/static/download portion of M2: project-contained asset
-snapshots, automatic MIME types, attachment names, HEAD, cache validators and
-single byte ranges. Dedicated public directories, symlink/hardlink rejection and
-bounded memory are part of the contract. [Asset guide](docs/ASSETS.md).
-Bulk tools, recipes and best-effort signals were added in the unreleased next-phase work above; they were not part of alpha.3.
-
-## Security correction — 0.1.0-alpha.2
-
-All function code is untrusted. Node host execution has been replaced by
-QuickJS/WebAssembly isolation with fresh invocation state, no ambient host or
-network APIs, bounded resources, restricted module graphs and revision-pinned
-operator binding policy. This protection is part of the free product. See the
-[security model](docs/FUNCTION-SECURITY.md). Full Fetch/Node
-API compatibility and network integrations were not part of that alpha and
-remain outside the 0.1 contract.
-
-## Earlier implementation checkpoint — 0.1.0-alpha.1
-
-Implemented: versioned strict YAML/JSON Schema subset, explicit file composition,
-redirect/parameter semantics, JavaScript Request/Response functions with bounded
-workers, scoped binding context, init/add/validate/dev/serve/test/doctor, indexed
-snapshots, last-good reloads, graceful shutdown, health/readiness, safe request
-logs, two runnable starters, ESLint and unit/HTTP/package tests. Cross-platform
-CI and a non-root container build are included. See the [contract](docs/SPECIFICATION.md)
-and [operations guide](docs/OPERATIONS.md) for exact support and evidence limits.
-
-Still open in the early contract: host namespaces, stable identity beyond paths,
-fuller parameter vocabulary. Build-time TypeScript authoring and capability planning are now implemented in the unreleased work above.
-No claims of complete M0/M1 or stable production readiness. M2–M4 work continues
-in the order below; a few independently useful operational foundations shipped early.
-
-
-| Milestone | Scope | Completion evidence |
-|---|---|---|
-| M0 — contract/build loop | YAML schema, matching/input semantics, function API, composition, runtime/packaging prototype, CI | Fixture validates; invalid definitions fail; verification runs |
-| M1 — local alpha | CLI, aliases, redirects, parameters, custom functions, env/secrets, indexed routes and reload | Redirect plus function tested locally without accounts/DB; invalid reload preserves working version |
-| M2 — bulk/reusable behavior | CSV/YAML/JSON, safe bulk edits/checks, templates, best-effort async signals, simple pages/static/downloads | 10k-route example, local side-effect tests, safe file serving, benchmark datasets |
-| M3 — self-hosted beta | Process/container deployment, domain/TLS guide, packages/Homebrew, ngrok, monitoring and load tools | Install, test, deploy, observe and roll back a real project |
-| M4 — provider public release | Cloudflare/AWS/Vercel adapters, provider conversion, capability/limit checks and stable docs | Baseline redirect/parameter/function fixtures on each advertised initial target; additional capability gaps explicit |
-| M5 — advanced public features | Bounded proxies, protected/one-time downloads, durable signals/state, broader catalog and API/SDK/MCP | Feature-specific guarantees, tests and portable capability reports |
-
-The first provider-capable public release is M4; the 0.1 self-hosted release is
-useful within its documented scope. A marketplace and advanced stateful
-features are not prerequisites. No web UI/TUI or framework-hosting platform.
-Netlify starts as redirect interchange after the initial provider adapters.
-
-## Launch and stabilize the free version
-
-Stability means repeatable installs/upgrades, dependable routing/functions,
-working deployment and rollback, useful diagnostics, and serious recurring
-issues from actual users addressed. Feedback begins with usable alphas, but the
-free version is not stable until that evidence exists; do not invent a calendar
-deadline or adoption-count threshold.
-
-Keep the architectural direction: reusable runtime/compiler, provider adapters,
-separate configuration and secrets, versioned artifacts, Git-owned definitions
-and observable behavior. Avoid assumptions that would force users to rewrite
-projects later. No artificial restrictions in the free version; it is licensed
-under Apache-2.0.
-
-## Starter delivery
-
-The [starter plan](docs/STARTERS.md) makes both Git clone and CLI initialization
-release requirements: one function-plus-redirect starter in M1, bulk-growth examples in
-M2, and the business foundation with self-host tooling in M3. Provider recipes
-follow tested M4 adapters. All use the same runtime and portable project format.
-
-## Quality gates
-
-- Same fixtures pass on the local reference and each claimed runtime adapter.
-  A static exporter alone is not a complete function-capable adapter.
-- Pure redirects avoid Lambda/per-route user functions; generated shared routing
-  is allowed where native provider rules cannot preserve behavior.
-- CSV exports report unsupported nested content instead of silently losing it.
-- 1k/10k/100k datasets measure compile/reload, memory, latency and throughput.
-- Default tests run against local HTTP/fake services; ngrok is optional.
-- Load tests use bounded owned targets and do not follow third-party redirects.
-- Invalid reload preserves working config; secret values stay out of artifacts.
-- Installation claims match tested OS/architecture packages.
-
-Implementation runtime, exact schema/function API, first adapter order and package
-format are decided through early prototypes. Do not invent performance targets
-or advertise all providers before they pass tests.
+# Roadmap
+
+URLCode lets people and agents describe URL behavior in YAML and write application
+code only where the framework cannot express it. The free Apache-2.0 runtime
+stays useful on its own. [Project direction](docs/PROJECT-DIRECTION.md) owns the
+principles; [the specification](docs/SPECIFICATION.md) owns implemented behavior.
+
+## What works now
+
+The source at `db375bf` provides declarative routing, responses, assets, policies,
+conditions, proxy/signals, trusted Node functions and middleware, and opt-in
+`sandbox: true` isolation. Target support differs: use `urlcode capabilities`
+before promising a deployment. Stored short links have no supported package.
+
+Auth, admin, UI and middleware are separate optional packages. Auth/admin already
+render through the shared UI kit when configured. Core includes scaffolding,
+searchable recipes/examples, compact context, schema queries, a semantic manifest,
+and MCP inspection with separately enabled authoring. These are implemented,
+not future phases. See [the framework](docs/FRAMEWORK.md).
+
+## Next work
+
+Monorepo work is starting now. Move middleware in as a separate package before
+folding it into core; coordinate the guidance cleanup with that migration.
+
+1. **Make the existing product coherent.** Keep docs, examples, generated LLM
+   resources, installed skills and the standalone template consistent with their
+   runtime version. Resolve the [open decisions](docs/OPEN-DECISIONS.md).
+   [Issue 168](https://github.com/jimhoyd-com/urlcode/issues/168) tracks checking
+   schema-invalid documentation examples beyond the existing prose checks.
+   [Issue 174](https://github.com/jimhoyd-com/urlcode/issues/174) retains the
+   extension-schema retrieval proposal.
+2. **Measure the agent experience.** The benchmark harness and authoring evals
+   exist, but the committed baseline is a stub, not a real-model measurement.
+   [Issue 173](https://github.com/jimhoyd-com/urlcode/issues/173) tracks the
+   measurement. Run the existing tasks, retain the raw results and use observed friction to
+   choose improvements. See [the benchmark](benchmarks/agent/README.md) and
+   [the broader experiment proposal](docs/SPIKE-AI-FRAMEWORK-BENCHMARK.md).
+3. **Close release evidence gaps.** Browser/device coverage, accessibility,
+   independent security review, deployed recovery/soak tests and real provider
+   verification remain distinct from source implementation and local tests.
+   [Issue 58](https://github.com/jimhoyd-com/urlcode/issues/58) and
+   [release readiness](docs/RELEASE-READINESS.md) retain those gates. Live
+   Google/Apple/SES checks remain explicitly deferred.
+4. **After the monorepo move, consolidate middleware into core.** Move the
+   existing middleware package first, preserving behavior.
+   [issue 172](https://github.com/jimhoyd-com/urlcode/issues/172) tracks the later consolidation
+   and consumer migration; package retirement is not part of the initial move. Static targets continue rejecting
+   request-time middleware.
+5. **Choose expansion from evidence.** Collections, a business application suite,
+   and per-route Lambda compilation are proposals,
+   not available features. Decide scope before implementing them.
+
+## Records and ownership
+
+Track actionable defects and feature gaps in the owning repository's issues.
+This page explains sequence; package contracts explain behavior; dated evidence
+states what was actually tested. Completed and superseded plans live in the
+[archive](docs/archive/README.md), including the previous release chronology
+and detailed phase plan. Archiving an implementation plan does not close its
+remaining operational acceptance gates.

package/SECURITY.md

@@ -1,13 +1,28 @@
 # Security
 
-Application functions are **untrusted by default**. Alpha.2 replaces direct Node
-execution with QuickJS/WebAssembly isolation. Worker threads alone are not the
-security boundary. There is no unrestricted host-execution fallback.
-
-Guests have no Node, filesystem, shell, network or ambient process-environment
-access. Each invocation gets fresh state and bounded resources. Imports stay
-inside a snapshotted project module graph. Binding grants come from operator
-policy outside the project and are pinned to the configuration/code revision.
+Project `function`/`middleware` code is **trusted and unsandboxed by default**:
+it runs directly in the host process, exactly like any other project code,
+with full Node, filesystem and network access (docs/SPIKE-DEFAULT-TRUST-MODEL.md).
+A route opts into isolation explicitly with `sandbox: true`, which dispatches
+that route through the QuickJS/WebAssembly worker pool instead — unchanged
+from the isolation this project has always provided, still the boundary to
+reach for when a route's code specifically warrants it (input from a source
+the project doesn't fully trust, a contribution nobody has reviewed, logic
+handling an especially sensitive secret).
+
+A `sandbox: true` guest has no Node, filesystem, shell, network or ambient
+process-environment access. Each invocation gets fresh state and bounded
+resources. Imports stay inside a snapshotted project module graph. Binding
+grants — for a trusted route as much as a sandboxed one — come from operator
+policy outside the project and are pinned to the configuration/code revision;
+trusting a route's code by default does not grant it any `env`/`secrets` it
+was not explicitly declared and pinned to receive. This is a claim about what
+URLCode injects into `context.env`/`context.secrets` for a route, not an
+access-control boundary on trusted code itself: a trusted (non-`sandbox`)
+route runs with full Node access by design, so its own code can read
+`process.env`, the filesystem or the network independently of anything the
+binding grant declared or withheld. The grant only governs what URLCode hands
+that code through `context`; it is not a restriction the code is confined to.
 See the [security model and policy instructions](docs/FUNCTION-SECURITY.md).
 
 The host/runtime and sandbox engine still require patching, independent review

package/dist/BUILD-MANIFEST.json

@@ -3,88 +3,83 @@
   "files": {
     "dist/adapters.js": "a7153ec52f2ed7e0cdd8ed7d433504815f402ec53b2b1c3d38d0cf0e2fcf6509",
     "dist/agent-lists.js": "35ab484198897501d011cb6cc00b5a6787192e19df29c97646e8c118fcc19eef",
-    "dist/agents-guide.js": "9cecc60690fe91e1f09a5298273c1d918428f114b5abb11f40f37f341668309c",
+    "dist/agents-guide.js": "0b19909aee3f8a1039c34c43ff58116ec1bc3f1875e3dbc34b3b01655273201c",
     "dist/assets.js": "0833b093d2fe457ce68281110dc07d47914992753607741c13b339d92c76cf5c",
     "dist/authoring-files.js": "ad32814f9ae9c549c6247396f982aa700d13a293cc0a589609eccc68f8965550",
     "dist/authoring.js": "ec5240e8686c124f4601229b45f89ce112d9eeb9d35e3059fe55e93056c45209",
     "dist/aws.js": "7d8e3a97b4f6dbefbd68da058f05192469d1efcaed5458b284863ebe462e060e",
     "dist/build-cloudflare.js": "af4f49ad45287d7c4105bb84b1592b5b8e76c930f7159505338298f7c5fd5651",
+    "dist/build-static.js": "fe01ef4fcc66d83d8be7a787538b55974e84fd3d7c89e26f0a2f1a152762d565",
     "dist/bulk.js": "aac88d422bd9a7a341a421fb4e29ff5580b28d39250b7f1f5315ba20ae92da8a",
-    "dist/capabilities.js": "c1e28c7de676c3b43c154d6f767749a1b34df78a64c58b5c23ad95339f964608",
-    "dist/capability-query.js": "850525d542aeeaeb4f89397ac57c6f89daad3fe3fa02ecb0332ea9f75d140b32",
+    "dist/capabilities.js": "28dba05b3851b8b12b3c1b809af87b732f84d601c737afe9225abe429886e691",
+    "dist/capability-query.js": "ba148b27c6a60f8c895f13f26468b16c18ae0a5cddea26b602965c8efbba90ae",
     "dist/catalog.js": "ab1c01c9296cc277d2bd4fd682aeb053656a7d9f91c61974f4b78feea0211de8",
-    "dist/cli.js": "4cba007ed3666fdfdf9fc676de1e346ab8196e3907dc2541eeb3e59842d9891a",
+    "dist/cli.js": "ff3e583bd43044bdc06122e33c6137f400f677967ebff1ab49900b517682531c",
     "dist/client-address.js": "9d0d01466aab23124330605c5a0e0f981f87c897858acfad909f546a63df165b",
     "dist/cloudflare.js": "17b43b0a6b6a0ef8a893415c989e4ae3976d97cc966adbf897b785f9adc472e3",
-    "dist/compliance-rules/baseline.js": "0a0c03d932f30797c4837c78c6b64ca6bb88f2ca947eb7f6adf5fdcdd280616d",
-    "dist/compliance-rules/privacy.js": "0e4d12106cf777299a7d30451f53c7b996f202fe53d7e1047b69f5df2a74a53d",
-    "dist/compliance-rules/shared.js": "595a7ee3a5af8c52197c5c9cbf09f4289a234e52b7a198afdd498be9be8d28a1",
+    "dist/compliance-rules/baseline.js": "6296dea6bcb9f9bb80ed6ed5ab2f456e7f74e6de2be5d2d98ca8c983fb4df3ab",
+    "dist/compliance-rules/privacy.js": "4cfb1c07d7df698c362dfc8761cd3bba893769e92d7fb0a3901e1c2d25e801f1",
+    "dist/compliance-rules/shared.js": "86fd6db6a93375689acc64975cbc394ce9452dea21ae5941e743f99822515995",
     "dist/compliance-rules/strict.js": "73ee13c2f893acf20cc3d44bf054e58c1474dec52eafe0cf2ce7f4eb96a3bc53",
-    "dist/compliance.js": "e956dc89b0b729fed7031297b8d7554141110334e670edf5cedc3d052a8fb3e4",
+    "dist/compliance.js": "29a18da3cefea94802ac7d817d1ab4e3674abd5c3ac4ef893cb8b01c6a23fb61",
     "dist/conditions.js": "ff25e97da550a3bdd80af55522045669438aa31a77d2bc83ad602bcefdee0475",
     "dist/config-worker.js": "bc2170d60c35f8d5de227cbfc4c5067dc61d7cbc5b98aed88e68a11797072da5",
-    "dist/config.js": "8efc2cfc24e9a958770d73aa8464d18c81d7a9a1d2398398cd9cc2776e639127",
-    "dist/context.js": "a6b0278b4fd478175f43b1ef5ae640ce6e0782c906c6fd2c7d1aebaf5a31c918",
+    "dist/config.js": "0cd82b4c407848f9c66e804a6dd4bf9a8a8503264e51584456578073e0f01921",
+    "dist/context.js": "549a53e4738b9c20a1ec55614027f758026fb5860bf4ac962ce22d7029e48df0",
     "dist/ecosystem-cli.js": "1e71bacd53d6fa8c7857cfcce3c3012ce054771a434b78d1f39e892e32642edd",
     "dist/egress.js": "2ae29fe2cb4590fd2f715abe6817db47fed2f50dd31f37946ecf42eafbb0dd9e",
     "dist/errors.js": "a908e66496afebbdd632a8c159a6e14d23f8f38798a0b4342ca122f2511c6cde",
-    "dist/examples.js": "8de9917a82fb04e44a3182d57c6a95cc730feb8b22a37d54b9b3c4177aa83111",
-    "dist/explain-cli.js": "c5414e9627f428f0d8efa4e4f3f89951ea10a6b3fe1d7f633e48f71a792406d2",
-    "dist/explain.js": "5dd271b699c9b852fbaa4db271d9a370fe98fca43b1d0ac018de0c0b047bf7b8",
-    "dist/extensions.js": "7402ff86017fca83a0e08a50b402bc428056566d63511aa84d609e252dc456e8",
-    "dist/function-sources.js": "f6e8bdd9d4ef728b44c6e1f08c601b11fc4ad3e0c104dacf4fea0b71874ea4e7",
-    "dist/function-worker.js": "3f5bad4f1b5cb812924c2dcc73ece6f816cf6aac26cd471fd1030dcfbf009c3b",
-    "dist/functions.js": "6b1e5d4a3f8db17d4e5df261b98ed15f5f0c5e5507a6fc0f472e9f94ed2b6090",
-    "dist/guest-api.js": "bc2501496a6ef9fd20dddb606fbc6fd557d534dd075e7ad38406248b230013ed",
+    "dist/examples.js": "89ae2b764a688fe52acfb9b94d3d262d7742401ebd0ef10c9ebfc76edfa5631c",
+    "dist/explain-cli.js": "f0f8f3b5046430d03c6abb629b38651c9c734b03456040735ce9d7e582b2bcd5",
+    "dist/explain.js": "dff1ed9a1bd818906ea867f4fb6d4601397943f9bdc4fceccf1809a365f95168",
+    "dist/extensions.js": "0506ec6289fa0582399d8c6d27727ffeb629bd442264248c921c63cc5b46ff01",
+    "dist/function-sources.js": "16fad4abc81c7ee07b6cbcef2d23a9fc50e97a17cb4dde1db53469bbb555c96f",
+    "dist/function-worker.js": "35771790ada4e1b36d447d4967a5e6cf0b543f32944e4c904f5fbf8998e824a5",
+    "dist/functions.js": "0f09d1bd27eb655ceb5900a4a5e2b760d2028b02cb637a6a89a4eb5940828008",
+    "dist/guest-api.js": "49aec9ed72733ad119e63bcfcee18158dcc8ceb951e1823b8947f6407ff24afc",
     "dist/header-validation.js": "465181dbb08ff05f52defdd29fda025c0c64589bf319fa87fa6d3ab4b68216d5",
     "dist/http-policy.js": "4cb187642269078ddf3460a3f1813dc57878a616a6f8132ef8f8d3b4b91ebb56",
     "dist/http-response.js": "5fc3bb9eb932a3fd2fbc72c361416a5f1439b8bf45b2be37baca1c6446abf40c",
-    "dist/index.js": "53648d88b0db7d9168d2f212ea4a28b7fd3ead6238c99c0b8d7d41536274d6d4",
+    "dist/index.js": "7e9f6ec8a125e2dfd4230b2ecd17ac513c0153d778a57bbcee7a1a9cd9681f81",
     "dist/init-with.js": "8371f568867ebdc6ab8e9aa762234ae2aa015865f46aa901254528e20d69b791",
     "dist/interchange-cli.js": "35bd70ba8077af5c3e39404ff0e5d28707632090a59a90645141252449fd3f04",
     "dist/interchange.js": "26789420af33344d9a08c00fe6b2708aa71994224df527b3075295be2151611e",
-    "dist/link-api.js": "0d1f2fb5ef8cd6fda7b071d3e08c53eb4b1c01d4003167af2f400949b70dea4f",
-    "dist/link-cli.js": "c4e2121a3e66f33c640832a7cb362a6a1db8b6d91d55a4239ce38ba0ced67b22",
-    "dist/link-events.js": "502a6038a538fa43094a9ba9c7546f504b4a1832a1377f26ca8cb69c2326670e",
-    "dist/link-records.js": "ef67a58cd107db0c3ac1c0ffd7b32817553606cf69bb3002da4ca0138c272f69",
-    "dist/link-store-worker.js": "0080452bbada2154b923449cd14596579bde94ad5f8dab94ecc84aa0d59c089b",
-    "dist/link-store.js": "526cdbe1b917cc7a74fb6edbbf13717d823ace5b5d6a5f89bc91438056a10b37",
     "dist/logging.js": "8ec57fea26983aa071b05fe15d680d6550b03488101163ed9666da674118cf31",
-    "dist/management-policy.js": "bd5563da52c53ace71b01daed0d2a492baeb3f26f5ec5ee1b0981c2b88df9ffa",
-    "dist/manifest.js": "d4f58f936febbabf09ec1706baae7c1cb186dcd8a3d29b5725dad5b6eaf43a3f",
+    "dist/manifest.js": "aa450ff88d44b184ed1ad3331d1f81005a844a9f971e9e12dfa039952839bc75",
     "dist/match.js": "53ebcc2cda529a8d07fb83f8cb69a1446036ffc1641af3c4bd45a55851bded28",
-    "dist/mcp-authoring.js": "5030f52ef9c7ebc7b97305fcce687eb0a0d6164e34fda87f8278135a1e6f3d65",
-    "dist/mcp.js": "ac96c5a094d7cc88cf16d1d1e3c23f45773729fe28855f921581badb2b95eb89",
-    "dist/observability.js": "13a22b9e34cf8da3739856eeada8522fb6c43765386cae07c6aa0981447fcb83",
+    "dist/mcp-authoring.js": "4987b0ba08999309e07aea1b8bb31f4600cec22d79998e6982e56f765070587a",
+    "dist/mcp.js": "fa44f5f9e0bc4ca9790d1d1eb461147673c1539cf1704a4daae9bad30e4120eb",
+    "dist/observability.js": "f4b1ab496f051fe3ef2ed36b2b2e469c63a8940700e2df852e6ff2d9cccdd5ae",
     "dist/operator-host.js": "e3dac9d43a83beb775202b4ab9eeeba7ac63cebfc5dcc669be38d825be587bd0",
     "dist/plugins.js": "a61aa933cd9e1b41020b86fae78aa3a7f45f5313124aa11b50cb57898722385e",
     "dist/policies/agents.js": "c1dbc1e90339f472eeeb2372f7f4637f59a5d210797ea680ac8120a02aa20c10",
-    "dist/policies/cache.js": "ef16d7e592526c29f865b2693faa2c8afbea41c6526687563dffcb13a77fc1f7",
+    "dist/policies/cache.js": "03f79b91694bb78a98de4473384e5110e1ae1c3c83d46f929495d03af04d9da1",
     "dist/policies/compression.js": "800f3ae3b1a4c1fe58c3d9908364ea9d78f655ff50c7f7589f584378e7f194b0",
     "dist/policies/security.js": "2b3bfdf82140156fea4b162adc28ee43ccd85c402fb200680dbb8d8706417420",
     "dist/policies/throttle.js": "bbb0cb1c24cf70d0a1ac32fc0618efb6c44e5b5d42564842f9c585ff7e501603",
-    "dist/policies.js": "23fa019b7bf1cdedcc5f7772d2f157e4b381a554bce9e84594c2be4a0f8f76b8",
-    "dist/policy.js": "8285ed144ba42fd34e926e526cd4dcf60d5ab3668adf4f0b797f074ebd5243ce",
-    "dist/prerender.js": "0386ea2411e00b9563b5349133f1d723947b01f837fa92d4c61a699c9cfb5cdb",
-    "dist/project-tests.js": "225761d36bbe7e185c49c10c0334e579caf7d98647c9941faa4b0ea6406522fa",
+    "dist/policies.js": "3750a7032ec7326aa544f4808683ad9eb91d4f2c5afe79904420cd8a355710a9",
+    "dist/policy.js": "33c527008fafe4af18243ba668d069517c20659150f9f1d1a5a1d076e8724f89",
+    "dist/prerender.js": "6210999e848ab86c87f265943960ef63716896da7a40e248221a6a30425c56b8",
+    "dist/project-tests.js": "445eaa139d2f1a2534369cfdeef081ef518de03218a467e7c5c2059caf840270",
     "dist/provider-verification.js": "ffcf9f05e8cb5f71ea46a97e279e8a613fdfdf9435ab02bd57af11e2680a9107",
     "dist/proxy.js": "34107e59ac0dbbea090efa3cf5badf3226c5302ba25e8f8ff9b2b5596ed80e50",
-    "dist/readiness.js": "d419b09a83dc8e6790be7c91ba4e1a2a5cf9b141577c98bd24e99a3609553649",
+    "dist/readiness.js": "90b54bc0cf60dd155d05789a1aad767bd67483d5fa6064ae8b1143f8cf9e06b2",
     "dist/recipes.js": "11853f23e63c3c65c5bed03a278cde0349d28c9fa23266c9907a2df318bb5fc3",
-    "dist/route-diff.js": "eebac076a886ddfb2bf5b97ea09d81f888e7bb0063d482eddb8e5fef9acea107",
-    "dist/router.js": "4315585232561c1737e579a2cbd990596d337b37565dd449bcb1bbaa6abbfb13",
-    "dist/runtime.js": "f6f1bfa320a427423d66be845de3368552b1f4cca4a28136b913ac26fb9d6169",
-    "dist/scaffold.js": "9dd30112e070ec554bd7cae1ca0a8b03642632be57411ba76a72972f4ba49b3e",
+    "dist/route-diff.js": "8d71d50d332ffaaed588656bd32aa36763260d1ad87bb62d7ea1c8fb23383969",
+    "dist/router.js": "cf831025d5ed6778d1d6a0e541177799794e76766c82084ded81d3e87317ca1e",
+    "dist/runtime.js": "0470dcab0774d2da3336e9ce76a4853757bf96081e52bd741f6b44c1bdd4161f",
+    "dist/sandbox.js": "c88c5aa5dd95b4f55f1ba62da7969ad66dbd97c30f72e5b5f2817a2098ac1c65",
+    "dist/scaffold.js": "3ef243aceca7ddf2780aa2c8c04ae17edd07682d3a418fd5d65ba00f5c762f14",
     "dist/schema-query.js": "bfd1844acd8d54ac361115191fcfbaf828a67e223b9ec6e9c22f158761af149b",
-    "dist/server.js": "d8c78d1695b3c11328f3f983281fba78c2aca6a66cf755b39ecf4ec2ec4b6f29",
+    "dist/server.js": "d878bc8f0d6a05f8fd25997cace3150e2ff4d44ee9c8f4b5530e29601e164be1",
     "dist/signals.js": "b55e54efc8fb6703e08f2a1e808ec8e011bda67738db8ceadf1b248f695795be",
     "dist/site.js": "c40a06a6f9e2d6d3bea94727783c115fed4309bb0190787f58434eed64cbde84",
-    "dist/sqlite-version.js": "a3a08d99064bd0f35847e288027e00a516efdd61c675bfbbe7726e3aa900f0d1",
-    "dist/tooling.js": "eaf9aa49df17b5ab3bc538976b2849fac52b5ca779b6e814fd7ca592ecd757b7",
-    "dist/types.js": "8579202bf322e542969bbd9e5b98774963b12ac69bdf362eebfcb068de2d5421",
-    "dist/typescript-authoring.js": "156c617c2cbf992c299dbbbd5398500f0f30d1c90df8630509036da4ffd7cae9",
+    "dist/tooling.js": "7409db98422325cd4181d073d645ea57debca0e54cb151123474b85f4d4ed7dc",
+    "dist/trusted-functions.js": "befd256848be786f97e372c6af0e05ac08a0c93baed38bf2470ea49bc00dd3e4",
+    "dist/types.js": "2fe7664dbb5695ec72114197abde72de4031df9c3b211740eacefa68e9b21844",
+    "dist/typescript-authoring.js": "2e98498a15bdbb76f36fbee84afb7c42ca95bbf80a2e6dd4040147f3b1642a29",
     "dist/vercel.js": "a0da20c095d0c7fa8f579ed4dd5951e7a34191f8a72a57c5e782c9eab39f6f08",
-    "dist/verify-deployment.js": "cac5d10ea18ae5f699df0eb0a5229837297c7627b47e65140f053820cae2414d",
-    "dist/scripts/operational-drills.js": "b7e9448279c59ee9de62023055a9ff5c7a60bcceed4c33d023edc612f5575af9"
+    "dist/verify-deployment.js": "0c2e68f3cf258a364728c801411df5284343bc01b75a64fe275ff84e397e998b",
+    "dist/scripts/operational-drills.js": "c26c406d28013cc554b25a5b6bf8baf4e71d5e67e50d866fae546f538a192317"
   }
 }