@ultimat3/cli 21.0.0 → 22.1.0

package/CLAUDE.md

@@ -1,1677 +1,111 @@
 # @ultimat3/cli — boundary
 
-Tier 5. May import tiers 0–4. Nothing imports this except `create-ultimate`.
+Tier 5. May import tiers 0–4. Declared sideways edges: `cli → admin` (`x dev` mounts the `/_x`
+dashboard), `cli → testing` (islands, the e2e step, `x shot`'s `launchChrome`). Nothing imports
+this except `create-ultimate`. The reasoning behind every rule below, verbatim and dated, is
+[`docs/history/cli.md`](../../docs/history/cli.md); where the two disagree this file wins.
 
-| Rule | Detail |
-|---|---|
-| Entry | `src/bin.ts` (`#!/usr/bin/env bun`) — argv, stdout, exit code only. Before `dispatch`, `local-cli.ts` decides whether THIS process is the app's own CLI: a global `x` inside an app re-executes `node_modules/@ultimat3/cli/src/bin.ts` when that is a different realpath, because a second module instance of `@ultimat3/entity` is an empty registry (a zero-entity manifest, green, 2026-09-05). Same realpath (a workspace symlink), no app, a compiled binary, or `ULTIMATE_KEEP_GLOBAL_CLI` set: no hand-over |
-| stdout | `write-line.ts`'s `writeLine` — synchronous fd 1, never `process.stdout.write`, which truncates at the 64KB pipe buffer when `process.exit` follows. Exported, because `create-ultimate`'s entry point needs the same one |
-| stderr | `write-line.ts`'s `writeErrorLine` — the same loop on fd 2, for a line that is not the command's answer. A `CommandResult` declaring `stream: 'stderr'` is routed there by `dispatch.ts`'s `sinkFor`, and `x mcp serve --transport stdio` is the one case: its fd 1 carries JSON-RPC frames, so the `✓ mcp stdio serving 13 tools` line rendered after the loop was a malformed frame. Neither renderer carries `stream`, exactly like `hold` |
-| Boot logs under `--json` | `dispatch.ts` calls core's `setLogStream('stderr')` when `args.json` is set, once, for all thirty commands. `x db migrate --json` printed the boot logger's `ultimate migrate applied` and then the command's own object, so `json.load` raised on the second document. A server's stdout stays its log stream; this is the CLI process only |
-| Test execution | `test-shards.ts`'s `testArgs` — ONE `bun test --parallel=N` per PASS (`test-passes.ts`; a selection mixing `live`/`e2e` files with the rest is two passes, the serial one at `--parallel=1`), never N processes this repo packs itself. It did pack them, largest-first greedy over file SIZE, and the packer was deleted for buying **nothing**: four interleaved runs each on the 1296-file unit corpus gave 58.2/60.0/65.0/66.5s hand-packed against 54.5/57.8/61.7/64.5s under `--parallel=8`, within noise, because both are work-bound — 436.7s of file time is a 54.6s floor on 8 workers and the slowest single file is 20.5s. A greedy pack of 1296 small items lands near-optimal by accident. `--timings` is refused on the same evidence (#342). `--parallel` implies `--isolate`, so the per-file module registry is unchanged, and the per-worker database is too: `@ultimat3/testing`'s `workerId` already read `BUN_TEST_WORKER_ID`, which Bun sets 1..N. `ULTIMATE_TEST_WORKER` is set only for a single-shard `x test --worker I` rerun, which is one process |
-| Numeric flags | `flag-number.ts` — one reader for `--port` / `--workers` / `--shard`. A bare `Number.parseInt` accepts `4abc` and answers `NaN`, which turned three checks into ones that cannot fail |
-| Shell quoting | `shell-quote.ts`'s `quoteArg` — every value the CLI pastes into a `fix:` or a reproduce line, `exec.ts`'s missing-program refusal and `test-shards.ts`'s reproduce command both. A name holding a space or a `;` interpolated bare is an instruction that runs something else |
-| Missing positionals | `MissingPositionalError`, never `BadFlagError` (names a flag that does not exist) and never `UnknownCommandError` (says a known command form is not one). Its `example` is a REAL invocation — `x g route <name>` in a shell is a redirect |
-| Bare subcommands | `CommandSpec.defaultSubcommand`, **declared**. The parser answered `subcommands[0]` until 1.2.0, so `x db` ran `gen` — the migration GENERATOR — because it sorted first, and `x mcp` started a server. A command with no defensible default declares none and `MissingSubcommandError` refuses the bare form; `parse.test.ts` pins the set at exactly `db` and `mcp`. Its fix is `x help <command>`. Both forms answer now: `--help` is read off the flag loop and `readSubcommand` is SKIPPED when it is set, so `x db --help`, `x mcp --help` and `x pr --help` print usage instead of exiting 1 with this same refusal — which is what they did on every command taking a subcommand until 2026-08 (`parse.test.ts` pins it across the shipped registry) |
-| Closed flag values | a flag whose values are a closed set is READ through a function that refuses the rest — `cmd-build.ts`'s `readTarget`, `cmd-deploy.ts`'s `readMethod`, `cmd-routes.ts`'s `readSurfaceFilter`, `cmd-mcp.ts`'s `isTransport`. `=== 'helm' ? 'helm' : 'compose'` made `x deploy --method helmm` a COMPOSE deploy reporting `method: "compose"`, and `--surface App` reported `0 routes` and exit 0 — a typo and an empty table rendering identically. The set is the framework's own where one exists (`SURFACES` from `@ultimat3/render`), never a list restated here |
-| Passthrough | `CommandSpec.passthrough`, **declared**. `ParsedArgs.passthrough` says "handed to the underlying tool verbatim" and had no reader anywhere, so `x test unit -- --coverage --bail` parsed both flags and dropped both — a run that measured nothing reporting what a coverage run reports. `x test` forwards them to `bun test` (before the file list) and prints them back in its reproduce line; every other command refuses a non-empty `--` tail with `X_CLI_BAD_FLAG` rather than dropping it. `help`/`version` short-circuit ahead of the command and are exempt |
-| App root | `CommandSpec.requiresApp`, **enforced by `dispatch.ts`** before `target.run` — the field's doc said so for 17 commands and nothing read it, so the promise was kept only by each command remembering to call `requireAppRoot` itself. Those 17 calls stay (they hand the command its root, and name subcommands the dispatcher cannot see), but the DECLARATION is what decides, ahead of any check a command makes about its own arguments; `--help` is exempt, because `target` is the help command by then |
-| Result helpers | `command.ts`'s `ok()` / `failed()` write `ok` **after** the `extra` spread: the function's name is the verdict and nothing a caller passes can overturn it. Spread last, `failed('verify', '1 of 20 steps failed', { ok: true })` answered `ok: true` and `exitCodeFor` exited **0** on it — a green CI over a red command (`command.test.ts`) |
-| I/O | only `dispatch.ts` renders or exits; commands return `CommandResult` |
-| Staying up | a command still listening when `run` resolves returns `hold` (`hold.ts`), or `bin.ts` exits out from under it |
-| `--json` | every command, no exceptions — same data as the human render |
-| Errors | codes + titles in `src/error-codes.ts`, classes in `src/errors.ts`, subclass `UltimateError`, never a bare `Error`. A class may sit beside its one thrower when `errors.ts` has no room under the 500-line ceiling — `db-seed.ts` and `metrics-endpoint.ts` do |
-| Subprocesses | only through `exec.ts`, so a test can inject a fake `Runner` |
-| Templates | `templates/*.ts` return strings; no fixture files on disk |
-| Strings | rendered output through `messages.ts`, missing key renders `⟦key⟧` — see below for what is *not* rendered output |
-| Facts | load the app (`app-load.ts`), then project it — never parse source for primitives |
-
-Every fact the CLI reports comes from a framework package: the manifest from
-`@ultimat3/manifest`, `openapi.json` from `@ultimat3/action`, the route table from
-`@ultimat3/render`, budget units from `@ultimat3/render`, the `/_x` panels from
-`@ultimat3/admin`, the MCP tool catalog from `@ultimat3/mcp`, eval coverage from
-`@ultimat3/ai`. A check that reimplements one of those here is the bug, not the fix.
-
-`app-evals.ts` is why the `eval` step can apply with no eval suite at all: a prompt no eval
-names is `X_EVAL_MISSING`, an eval whose baseline was never recorded is `X_EVAL_BASELINE_MISSING`,
-and a skipped step would read as a green gate over untested code. Its third rule runs *before* the
-suite rather than beside it — `ULTIMATE_EVAL_RECORD` makes every eval write its own numbers and
-pass, so a gate that inherited the flag would rewrite the committed baselines during the run, and
-a finding after the fact does not put them back.
-
-`verify-floor.ts` is the suite ratchet, and it is split across two owners on purpose. `runVerify`
-judges the **suites**: a step the committed `x.verify.json` names that reports nothing to check is
-recorded failed and not skipped, so the failure count, `data.failed` and every step table another
-gate parses all carry it. The `manifest` step judges the **file**: a floor that does not parse, or
-that names a step the gate does not run, enforces nothing — and a ratchet nobody notices is off is
-the false green it exists to close. Nothing writes the file; a gate that edits its own floor
-ratchets in both directions.
-
-**"Nothing to check" is two conditions and one code.** `applies` sees the first — no files — and
-cannot see the second, because `describe.skipIf` is decided inside the child process: measured with
-no `TEST_DATABASE_URL`, `live` is `4 pass, 114 skip` and the step reported green over a suite whose
-whole subject is the database. `test-counts.ts` reads bun's own summary back (`parseBunTest`, the
-same reader `x mcp`'s `test.run` uses — a second regex over one format is drift), each runner
-attaches `StepOutcome.tests`, and a floor step whose `ran` is zero is `X_VERIFY_SUITE_VANISHED`
-with `skippedSuiteFinding`'s cause. **Zero, not a ratio**: one real assertion is a suite that runs,
-and a threshold would be a number nobody can defend. An absent `tests` is a step that spawned no
-test process at all (`eval` answering with declarations alone), which is not the same claim.
-
-`x new` writes an `x.verify.json` (`templates/scaffold-repo.ts`), or the code above is unreachable
-in every generated app — the repo shape that grows suites fastest. It names the eleven steps the
-scaffold has proved apply, and deliberately not `e2e`: the scaffolded `page.e2e.test.ts` is an
-`e2eTest`, which is `test.skip` until the app registers a browser driver, so pinning it would fail
-the app's first gate on the scaffold's own placeholder.
-
-`tsconfig-references.ts` is `package-shape`'s fourth rule: **every published workspace is in the
-root `references`**. `bun run typecheck` is `tsc -b`, which builds referenced projects and nothing
-else, so a package no reference names is one the gate's own `typecheck` step passes over without
-reading a line of it — `X_PACKAGE_UNREFERENCED`, whose `fix:` is the exact `{ "path": … }` entry
-and the `tsc -b` that proves it took. Private packages are exempt (a generated app's are all
-private), and a root that declares **no** `references` array is not judged at all: project
-references are opt-in, and a scaffolded app builds through `extends` + `include`.
-
-`workspace-graph.ts` is `package-shape`'s fifth rule: **every cross-workspace import is declared
-in the importing workspace's own manifest**. Without it a scaffolded repo's dependency graph exists
-only inside `tsc` — imports resolve through the root `tsconfig.json` `paths`, so affected-package
-detection, `bun --filter` ordering and "what breaks if I change this" all read manifests and all
-answer too small a set (issue #239, found in a real app where a change reaching five packages
-reported one). `X_WORKSPACE_DEP_UNDECLARED` names the manifest and the exact line to add. Shipped
-source only: a test file's import is not judged, because `packages/*` here declares no
-`devDependencies` by design and the root's hoist is what resolves them. A manifest the scan cannot
-read is its own finding rather than a silent skip — a skipped workspace is a hiding place for the
-very edge the rule is looking for.
-
-`app-permissions.ts` is the `policy` step. Two references in the whole
-framework are bare strings nothing checks — `RoleDef.grants` and `RouteGuard.permission` — while
-`can()` calls `assertPermission` and throws `X_PERMISSION_UNKNOWN` on the first request that
-reaches the route. So `x new` shipped an app that granted `dashboard:read`, required it on
-`/dashboard` and declared it nowhere: HTTP 500 on two of its three routes, from the first `x dev`,
-under a green gate. It reads `roleDefinitions()` and `routeEntries()` after `loadApp` and reports
-each reference `isKnownPermission` refuses — **that predicate and no other**, because it is the one
-`assertPermission` uses, including its rule that an app which has declared NOTHING is not checked
-at all. A gate that disagreed with the process it gates would be worse than none. The cause and the
-`fix:` are `permissionUnknown`'s, so `@ultimat3/policy` owns both wordings; `X_PERMISSION_UNKNOWN`
-is in `CLI_BORROWED_ERROR_CODES`. Its own step rather than a rider on `budgets`, by that step's own
-test: reported there, an authz defect would hand the reader a byte budget (axiom 4). It costs no
-second app load.
-
-`dev-replica.ts` is where read-replica routing is WIRED, and it had to be wired in two places
-because it was opt-in twice. `@ultimat3/db`'s `defaultClient()` is the one composer of
-`replicatedClient(primary, replica)` from `DATABASE_REPLICA_URL`, and it runs only from
-`baseClient()` — "the client an app installed none for" — while every process the framework boots
-calls `setDbClient` in `dev-queue.ts`, so no booted process had ever read that variable. Routing
-also needs an open `withReplicaReads` scope, and nothing opened one. `startDb` now installs the
-replicated pair as the AMBIENT client while keeping the primary for everything this boot does
-itself (`applySchema`, the queue's `PgExecutor`, `ping`, `close` — DDL and a claim are writes), and
-`cmd-dev.ts` / `serve.ts` prepend one middleware frame that opens the scope per request. Both
-halves are `undefined`/empty with no replica configured, and an EMBEDDED binding never gets one:
-PGlite has no standby. Not `@ultimat3/http`'s pipeline, which would make the HTTP tier know what a
-database is; the boot is the only tier that may know about a request and a pool.
-
-`flag-number.ts`'s `portPairAfter` is the one suggestion for a caller that binds a PAIR, and
-`neighbouringPort` is for a caller that binds one port. `x dev` takes `PORT` **and** `PORT + 1`, so
-the neighbour of a taken web port is the sync port — both `x doctor`'s `X_PORT_IN_USE` and
-`dev-sync.ts`'s handed back the port the finding had just named as taken, each under a test that
-said it ended the failure. It answers downward at the top of the range for the reason
-`neighbouringPort` does, and one further: the suggestion's own neighbour has to exist, or
-`syncPortFor` refuses it with `X_PORT_INVALID`.
-
-`port-probe.ts` is the one `portFree`, because two commands ask it and must not disagree:
-`x doctor` reports it as a finding for BOTH ports `x dev` binds — the web port and the sync port,
-which it derives with `syncPortFor` (the boot's own rule: a `--port` at the top of the range has no
-sync port at all, so the probe reports `X_PORT_INVALID` instead of probing the port BELOW it, which
-is what `neighbouringPort` answered there) — each labelled with the role that wants it — and `startSync` asks it after a failed
-`listenSyncNode` so a taken neighbour is `X_PORT_IN_USE` rather than `X_CLI_UNEXPECTED` over
-`Bun.serve`'s own English rendered into a `cause:`. It is ASKED, never read off the caught value,
-which is what `scripts/catch-render.ts` refuses; anything else the listener failed on is re-thrown
-untouched. `x doctor` also probes `DATABASE_URL` with a real `select 1` through
-`@ultimat3/db`'s `checkDb` — a TCP connect answers "reachable" for a running server with wrong
-credentials, which is the case an operator most needs told about — and reports `X_DB_UNAVAILABLE`
-with that package's own two-branch fix. An EMBEDDED binding is not probed: that lock is `x dev`'s.
-
-`doctor-offline.ts` is `x doctor`'s offline-fallback check, and it is the shape of a diagnostic
-that could not be closed. The probe was the literal `apps/web/app/offline.tsx` — a filename
-`assertRouteFilename` REFUSES (`X_ROUTE_FILE_INVALID`: the directory is the URL, so a page is
-`page.tsx`) — while `x new` scaffolds `apps/web/site/offline/page.tsx` and the finding's own `fix:`
-writes `apps/web/app/offline/page.tsx`. Three different paths, so every app the framework has ever
-produced reported `X_PWA_NO_OFFLINE_FALLBACK` from its first `x doctor`, running the fix changed
-nothing, and the app that HAD the route was told it did not. It now reads the DECLARED
-`pwa.offline.fallback` through `loadPwaArtifacts` and matches it against `describeRoutes()` —
-**`site/` only**, `As of 2026-09`. It accepted `app/` too, on the argument that both surfaces answer
-the same URL; true, and not the question. `SURFACE_SPECS` allows `app/` exactly `stream | ssr`, only
-a `static` route is prerendered, and `serviceWorkerArtifacts` precaches a rendered DOCUMENT
-(`documents.get(fallback)`) — so an `app/` fallback has nothing to precache and the offline
-navigation reaches the network it exists to survive without. The check and its own `fix:` disagreed
-about one code. Not closed by this: a `site/` route declaring `render: 'ssr'` is not prerendered
-either, and `NavigableRoute` carries no render mode. An app whose modules will not import is not
-judged at all, which is
-`appEntities`' rule (`schema-drift.ts`) one registry over. The fix is `x g route <name>
---surface site` only where the fallback is one path segment the generator can really produce: a
-nested path slugifies to a DIFFERENT url, so there it is the config edit instead — a `fix:` that
-runs and leaves the finding where it was is the defect this file exists to end. **`site`, not
-`app`**: the document that answers a lost network has to render with no network, no session and no
-database, which `app/` (`ssr | stream`) cannot promise, and it is the line `@ultimat3/pwa`'s own
-`X_PWA_NO_OFFLINE_FALLBACK` hands out for the same code — two fixes for one code are two answers.
-
-`X_ENV_MISSING`'s fix is the file write, for the same reason. It was `x new --force`, which cannot
-run where the reader is standing: `x new` takes a `<name>` positional (`X_CLI_BAD_FLAG` without
-one) and with one it scaffolds a SECOND app beside the broken one. `cp .env.example
-.env.development` — the committed projection of `envSchema`, which is what `x env example` writes
-and `X_ENV_EXAMPLE_DRIFT` keeps honest.
-
-`i18n-index.ts` is the one writer of an app's `packages/i18n/src/index.ts`, shared by `x g` and
-`x i18n add|sync`. A catalog on disk and a SELECTABLE locale were two different sets: `x i18n add
-fr` wrote the file, exited 0, and left `x verify --only i18n` red with `X_CATALOG_UNREGISTERED`
-whose `fix:` named an edit that had already been made — an agent following it verbatim changes
-nothing and loops forever, on the command whose whole job is adding a locale. `unregisteredFix`
-(`i18n-registration.ts`) is the other half: one code over two causes, so where the index EXISTS and
-does not name the locale's own `catalogs/<tag>.json` import, the CLI substitutes a fix that
-performs the registration. The package's own "move the `defineCatalogs()` call" line still stands
-for the cause it was written for.
-
-`app-agents-md.ts` is why the `manifest` step declares no `applies` at all. The drift half needs
-a committed `x.manifest.json` to compare against, but `AGENTS.md` is required of every repo the
-gate runs in — so the step always has a question to answer, and gating both halves on the file
-that only the first one needs is how `X_AGENTS_MD_MISSING` stayed unreachable while its wiki row
-said it fails builds.
-
-## What goes in `messages.ts`, and what does not
-
-`messages.ts` holds the strings a command *renders* — `CommandResult.summary`, `lines`, anything
-the human renderer prints. Three things stay inline, deliberately, and a review asking to move
-them is answered by this table rather than by a second convention:
-
-| Not in the catalog | Why |
-|---|---|
-| `CommandSpec.summary` / `.usage` / `FlagSpec.summary` | the spec is the command's declaration, next to the `run` it describes; parsing and `x help` both derive from it. All command modules declare it inline — moving a subset creates two places to look for one command's help |
-| `Finding.cause` / `Finding.fix`, and `BadFlagError`'s `reason` | stable machine-readable diagnostics. A `fix:` is copied and run verbatim; a translated one is a broken command |
-| Fixed-width table headers (`renderJobTable`, `renderRouteTable`) | column keys, not prose — the widths are computed from them and `--json` carries the same names |
-
-## The introspection commands project registries, they never re-derive facts
-
-| Command | Files | Reads |
-|---|---|---|
-| `x actions` / `x queries` / `x entities` | `cmd-registries.ts` | the three declaration registries |
-| `x jobs` | `cmd-jobs.ts`, `jobs-{driver,report,drain,json,table}.ts` | `@ultimat3/jobs`' own introspection |
-| `x tasks` | `cmd-tasks.ts`, `tasks-facts.ts` | `registeredTasks()` + `@ultimat3/time`'s cron resolution |
-| `x policy` | `cmd-policy.ts`, `policy-facts.ts` | `@ultimat3/policy`'s `policyMatrix()` over the app's own `Policy` objects |
-| `x i18n` | `cmd-i18n.ts`, `i18n-audit.ts`, `i18n-registration.ts` | `@ultimat3/i18n`'s `extractFromFiles` + `auditCatalogs`, then the live catalog registry |
-| `x i18n check` and the `policy` step, before either registry | `duplicate-packages.ts` | `Bun.resolveSync` of `@ultimat3/i18n` / `@ultimat3/policy` / `@ultimat3/entity` from the app root, every workspace and the CLI's own directory, keyed by REALPATH. Two real directories is `X_PACKAGE_DUPLICATED`: a registry is per module instance, so the app registers into one copy and the CLI reads the other — `x i18n check` said "move `defineCatalogs()`" about a call that was already where it belongs (ai-maxxing, 2026-09-05), and the policy step was green over an undeclared grant. A workspace symlink to one checkout is one copy; two store entries at ONE version are two |
-
-Each pairs a `cmd-*.ts` of CLI wiring with a facts module that takes plain inputs and returns plain
-data, so the projection is testable without a `ParsedArgs` — the `cmd-jobs.ts` / `jobs-report.ts`
-split, repeated. Tables go through `table.ts`; a second padding helper is the drift it prevents.
-
-`x policy explain` exists because five packages already print it as the `fix:` on an authz denial
-(`policy`, `action`, `query`, `http`, `auth`), and `x i18n` because all three of `@ultimat3/i18n`'s
-own error fixes name it. A `fix:` line naming a command this build does not ship is the failure
-mode `cmd-planned.ts` closes for planned commands and these close for real ones.
-
-`x i18n check` scans source, which the "never parse source for primitives" rule below does not
-forbid: a `t()` call is not a primitive and no registry holds it. It uses `source-files.ts`, the
-same walk `errors` and `filesize` use, so the three cannot disagree on what the app's source is.
-
-**And then it asks the question the scan cannot answer.** A catalog complete on disk, its keys used
-everywhere in source, and an audit of one against the other were all green for an app that rendered
-`⟦key⟧` on every page — registration is a side effect of importing the module that calls
-`defineCatalogs()`, and nothing imported it (issue #249). `i18n-registration.ts` loads the app
-through `loadApp` — the same call `serveApp` makes at boot, so it is the boot's own answer and not a
-simulation of one — and compares the catalogs on disk against the live registry, per locale
-(`X_CATALOG_UNREGISTERED`). Two conditions, one code: a shipped catalog no module registered, and
-no catalog anywhere while source calls `t()` — the second is the vacuous green an app with an
-`app.config.ts` and no `packages/i18n/catalogs/` used to get. `loadApp`'s own findings ride along
-ONLY when something is unregistered, because "packages/i18n/src/index.ts: SyntaxError" is the
-evidence for the gap above it and noise on a pass.
-
-`catalogFindings(root)` is the one composition both callers report: `x i18n check` renders it as a
-table with a `registered` column, `x verify`'s **`i18n` step** returns it as findings. One
-implementation, so the command and the gate can never disagree about an app.
+Commands: `bun test packages/cli` (from the repo root — the test preload lives there),
+`bunx tsc --noEmit -p packages/cli/tsconfig.json`.
 
-**The generators emit `useT()` from the app's own catalog module, never `t` from `@ultimat3/i18n`.**
-The specifier is `resolveCatalogModule(root)` — `packages/i18n/package.json`'s `name`, read off
-disk, because a template is a pure string function and only a package name resolves as an import.
-An app with no such package keeps the framework import: emitting one that cannot resolve trades a
-wrong idiom for a file that does not compile. This is where the reported bug's idiom came from —
-every generated page imported `t` directly, so no page depended on the module that registers.
+## Rules
 
-**A catalog is authored nested and read flat.** `Catalog` (`{ 'nav.home': 'Home' }`) is the
-translator's form; the file on disk holds `{ nav: { home: 'Home' } }`, and `parseNestedCatalog`
-refuses a dot inside a key — so anything writing a catalog goes through `nestCatalog`
-(`serializeCatalog` for `x i18n add|sync`, `templates/catalog-json.ts` for every generator) or it
-emits a file `defineCatalogs` rejects at the app's first boot. `merge: 'json'` unions **deeply**
-(`json-merge.ts`) for the same reason: `x new` and `x g resource` both contribute under `app`, and
-a shallow spread keeps one of them.
-
-## Three commands that reach outside the process, and none of them is a gate step
-
-`x shot`, `x pr` and `x ci` exist because of the one line in the root `CLAUDE.md` that shapes this
-whole package: **the primary developer is an AI agent.** An agent cannot open a browser, cannot look
-at a running dev server and cannot read the GitHub web UI. It can read a file, and it can run a
-command that prints. These three turn each of those into a file and a print.
-
-They are also the only three commands that need something the process does not have — a browser, a
-network, a GitHub token — which is why **none of them is a step of `x verify`**, and why that is not
-an oversight to be corrected later. A gate that needs a browser goes red for reasons unrelated to the
-change, and CI does not install one.
-
-| | Reaches for | Never |
-|---|---|---|
-| `x shot <route>` | `x dev` on a scratch port, plus the app's own `puppeteer-core` through `@ultimat3/scraping` — launching Chrome here, or **attaching** to one over `--cdp-url` / `SCRAPE_CDP_URL`, which is what every stealth provider sells and what `remoteBrowser()` has called its primary path since it shipped | the static build — `--target static` prerenders `site/` only, so an `app/` route would photograph the landing page |
-| `x shot --island <name>` | the same server and the same browser, plus the app's own `*.island.states.ts` | a second command — photographing a route and photographing a component are one job with two subjects, and `--island` with a route positional is refused by name |
-| `x shot --all-islands` | every `*.island.states.ts` in the app, one boot, one browser per declared VIEWPORT across all of them | a second capture loop — one island and every island are `runIslandSweep` with one argument, because two loops are two answers to what a run produced |
-| `x pr review\|resolve\|reply` | `gh api graphql`, through the injected `Runner` | `gh pr view --comments`, which shows *issue* comments and not the line-anchored threads that carry the findings |
-| `x ci` | `gh run view --log-failed`, one call | a per-job log fetch — the run and all its jobs come back together |
-
-**`verdict.json` names its own blind spots, and that is the design.** `x shot` reports what it could
-not observe alongside what it did. A capture tool that silently omits what it cannot see is worse
-than one that says so, because the omission reads as a clean result.
-
-### `--island` photographs ONE component in a state nobody can click to
-
-A failed read, an empty list, over-quota, read-only: the states a reviewer most needs to see are the
-ones a running app will not produce on request. `--island` takes them, one address at a time.
-
-| File | Job |
+| Rule | Detail |
 |---|---|
-| `island-states-load.ts` | discover `*.island.states.ts`, prove each pure, import it, check the set |
-| `island-harness.ts` | the document that mounts ONE island over `data-x-entry` / `data-x-props` |
-| `island-harness-script.ts` | what runs before the chunk does: the sealed network, the pinned clock, the readiness watch |
-| `island-harness-route.ts` | `GET /_x/island`, mounted by `x dev` |
-| `island-shot.ts` | the RUN: which islands, in which order, which artifacts — and the missing-shot gate |
-| `island-capture.ts` | ONE picture: the assertions before the shutter, the crop rectangle, the one session |
-| `island-shot-index.ts` | `index.md` as a PURE function of (manifests, targets, verdicts) — no I/O in the rule |
-| `shot-browser.ts` | which browser a run gets — launch one here, or attach over `--cdp-url` / `SCRAPE_CDP_URL` — as three rules over plain inputs |
-| `island-verdict.ts` | the per-state verdict — a PNG cannot say the component threw or logged |
-| `cmd-shot-island.ts` | the flags, the refusals, and the one browser per declared viewport |
-
-The vocabulary is **`@ultimat3/testing`'s**, not this package's: `defineIslandStates`,
-`islandShotTargets`, `islandAddress` / `parseIslandAddress`, `findIslandStates`,
-`assertIslandStatesPure`. `cli → testing` is a declared sideways edge and `cli → scraping` is
-another, which is what makes `@ultimat3/cli` the only package that can hold both the mount half and
-the screenshot half.
-
-**The expected picture list exists before a browser does.** `loadIslandStates` → `findIslandStates`
-→ `islandShotTargets` is a pure expansion off files on disk, and the run ends by diffing it against
-what actually landed (`missingShots`, `X_SHOT_ISLAND_MISSING`). That diff is the point of the whole
-design: a loop that swallowed every failure would otherwise report a clean run with no pictures in
-it, and "produced nothing and exited 0" is the one outcome a reader cannot tell from success.
-
-**An unstubbed request FAILS the run.** The page's own seal replaces `fetch`, `WebSocket`,
-`EventSource` and `XMLHttpRequest` before the island's chunk is imported, answers the state's
-`routes` and publishes everything else on `window.__xShot.unstubbed`; the capture refuses on a
-non-empty list with `X_SHOT_ISLAND_UNSTUBBED_REQUEST`, naming each method and path. A component
-whose fetch quietly hangs paints its own loading branch, and the picture then shows a fixture gap
-dressed up as a real component state. `@ultimat3/testing`'s `sealNetwork()` is not reusable here:
-it patches THIS process's `globalThis.fetch` and the component runs in the page's realm.
-
-**Readiness is quiet, not idle.** Fonts ready, then N consecutive animation frames with an unchanged
-network-ACTIVITY counter — never "nothing in flight", which never comes for a state whose fixture is
-deliberately `pending`, and never a fixed sleep, which photographs whatever a slow machine painted.
-
-**Eight assertions before a shutter opens** (`photographFault`), each naming a fact the picture would
-have hidden rather than shown: no probe, not the harness, no host element, a mount that REJECTED, a
-mount that never finished, a page that never went quiet, a zero-sized box, a box with no children
-and no text. Then a byte floor as a backstop. Every one of them otherwise comes out as a plausible
-image of the wrong thing.
-
-**`--all-islands` is a spelling, never `--island` with no value.** The parser refuses a bare
-`--island` ("expects a value") and `--island=` is an empty NAME, so "every island" had no form a
-reader could type that could not be read as a mistyped one. A boolean cannot be confused with a
-name. Every contradictory pair is refused BY NAME and before a value is read — beside `--island`,
-beside a route positional, and beside `--state`, which belongs to ONE manifest's vocabulary
-(`empty` in two manifests is two unrelated states). An app declaring no states at all is refused
-too, rather than answered with an empty gallery: "produced nothing and exited 0" is the one outcome
-a reader cannot tell from success. Its `fix:` names `x g island`, and deliberately not a states
-generator — a `fix:` may only cite a command this build ships (`fix-command.ts`), and there is none.
-
-**A sweep never aborts on a failure.** Every state the app CAN photograph is captured, every
-per-island `verdict.json` and the index are written, and only then does the missing-picture gate
-turn the reasons into a non-zero exit. One island that will not mount must not cost a reader the
-other nineteen — which is the same rule the per-state loop already followed, one level up.
-
-**`.x/shot/island/index.md` is the file an agent opens**, and it is written for a SINGLE-island run
-too: the file that says what a picture IS cannot be a property of how many islands were asked for.
-`island-shot-index.ts` is a pure renderer over (manifests, targets, verdicts) — no disk, no browser
-— and the caller does the writing, which is the split every check in this repo uses. It carries the
-counts, the re-run commands, the verdict's own `blind` list (handed in, never reworded: two
-wordings drift), and per state the `id`, the `title`, the `note` — the *"you cannot reach this by
-clicking, because …"* line, which is the whole reason a reviewer knows what they are looking at.
-
-**A console WARNING and an overflowing box are recorded and gate NOTHING.** `stateShotOk` reads
-neither, on purpose: a signal that fails a run is a signal an author switches off. The warnings were
-already in `page.console()` and already in `--json`; what was missing is that nobody counted them.
-The overflow is new and is the readiness probe's own answer — `scrollWidth > clientWidth` on the
-crop target, measured in the same round trip, because a fact measured after the shutter is a fact
-about a different page.
-
-**The clip carries a margin, clamped to the document.** It was the readiness box EXACTLY, and a
-pixel-tight rectangle shaves off everything a component paints outside its border box — a
-`box-shadow`, an outline, a focus ring, a hairline border on a subpixel — so a reviewer reads a
-component with no elevation as flat. `ISLAND_CROP_MARGIN_PX` is the one constant; the clamp reads
-the document's own extent off the probe (`page`), never the viewport, and it may only ever make the
-frame BIGGER than the component's box — a clamp that could shrink it would crop the subject.
-
-**One session per picture, and that is not an optimisation to collapse.** `page.console()` and
-`page.pageErrors()` are bounded rings over the whole SESSION, so a shared one files state A's
-console errors under state B — and per-state attribution is the half of the artifact that gates.
-
-**The picture is the CROP TARGET, `As of 2026-08-26`** — the readiness probe's own box, which is
-the selector the manifest declared or the island's host element. Measured on `examples/dummy`
-before it: 720x560 for a component whose box the verdict reported, in the same run, as 688x104.
-`CaptureClip` had been on the port since #336 and `island-shot.ts` passed none, and this paragraph
-said the port "takes no clip rectangle" — so did the verdict's own `blind` list, which is a blind
-spot naming a capability the tool has, the same lie as one hiding a gap. The state's `viewport` is
-still what the page is LAID OUT in, so there is still one browser per declared viewport, memoised;
-it is no longer what the picture is.
-
-**The clip is translated, not copied.** `getBoundingClientRect()` answers VIEWPORT coordinates and
-a capture clip is in PAGE coordinates; they agree only at the origin, which is the one case a
-harness happens to be in and is a rule nothing enforces. So the probe returns `scroll` beside `box`
-and `clipFor` adds them — a component below the fold would otherwise crop a band it is not in, with
-a picture that looks like a picture and nothing anywhere to report it. `box` keeps meaning the DOM's
-own answer, because that is what the verdict publishes.
-
-**Both themes are photographed by emulating the PREFERENCE.** `page.colorScheme(target.theme)`
-before the navigation, so the first paint already has it. The harness's `data-theme` attribute stays
-— it is right for a component that READS a theme it does not own — but it is the OUTCOME of a theme
-decision, and a component that resolves `'system'` itself deletes it on mount: `x shot --island`
-reported four pictures and wrote two, byte-identical, same md5 (#338). Re-setting the attribute
-after readiness is not the repair; it photographs a state the component would never reach.
-
-**`loadApp` does not import a states file**, for the reason it does not import an island: it
-registers no primitive, and importing it would put `@ultimat3/testing` in the server module graph of
-every `x dev`, every `x build` and every gate step that loads the app (axiom 6).
-
-**`x shot` reuses a running `x dev` rather than booting a second one.** Embedded Postgres is
-single-writer, so a second boot is `X_DEV_ALREADY_RUNNING` and no picture is ever taken. A reused
-server's `stop()` deliberately does not clear the other process's lock.
-
-**`gh` is invoked through `ctx.runner`, never `Bun.spawn` directly** — that is what lets every test
-supply a reply table and assert the exact argv with no network and no `gh` installed. `GhOptions.fix`
-is a **required** field, so shelling out to GitHub without stating a remedy is a type error rather
-than a review comment. A GraphQL response is untrusted input and is parsed against a schema, never
-cast: a `null` where an id was expected would otherwise become a mutation against `undefined`.
-
-## The browser-backed e2e driver lives here, because the adapter has nowhere else to be
-
-`@ultimat3/testing` declares `PageLike` and has never had a driver for it; `@ultimat3/scraping` owns
-the only real browser in the tree and speaks `ScrapePage`. Both are tier 5, so neither may import
-the other, and `testing -> scraping` would be a NEW sideways edge. This package already holds
-declared edges to **both** (`SIDEWAYS_ALLOW`, `scripts/lib/tiers.ts`) and is the one package allowed
-to know about everything — so the join is here, and it is the same rule
-`docs/architecture/01-package-map.md` states for wiring a route table into `pwa`.
+| Entry | `src/bin.ts` — argv, stdout, exit code only. `local-cli.ts` re-executes the app's own `node_modules/@ultimat3/cli` when a global `x` is a different realpath: a second `@ultimat3/entity` instance is an empty registry |
+| Registry | `registry.ts`: every declaration static (`cmd-<name>-spec.ts`), every body `await import()`ed when that command runs. A command body is never imported to answer the parser or `x help` — `registry-lazy.test.ts`. A spec's constants live in the spec file or a leaf module, never in the body |
+| Startup cost | `sass` loads on the first stylesheet compile (`@ultimat3/render`'s `compileStylesheet`), Babel on the first island transform (`solid-loader.ts`); both pinned by `*-lazy.test.ts` in a child process |
+| Module names | `role-*` / `runtime-*` are booted by `serve.ts` in production; `dev-*` is `x dev`'s alone. Derived from the import graph by `module-naming.test.ts`, never listed |
+| stdout / stderr | `write-line.ts`'s `writeLine` / `writeErrorLine` — synchronous fd writes, never `process.stdout.write` (truncates at the pipe buffer before `process.exit`). A `CommandResult` with `stream: 'stderr'` goes to fd 2 (`x mcp serve --transport stdio`) |
+| `--json` | every command; `dispatch.ts` sets core's log stream to stderr under it. Same data as the human render |
+| I/O | only `dispatch.ts` renders or exits; commands return `CommandResult`. `ok()` / `failed()` write `ok` after the `extra` spread — the verdict cannot be overturned |
+| Staying up | a command still listening when `run` resolves returns `hold` (`hold.ts`); the release runs inside the drain's own deadline |
+| Test execution | `test-shards.ts`'s `testArgs` — one `bun test --parallel=N` per pass (`test-passes.ts`); `live`/`e2e` run serially (`SERIAL_TYPES`, `test-workers.ts`) |
+| Numeric flags | `flag-number.ts` — one reader for `--port` / `--workers` / `--shard` |
+| Shell quoting | `shell-quote.ts`'s `quoteArg` for every value pasted into a `fix:` or a reproduce line |
+| Missing input | `MissingPositionalError` (its `example` is a real invocation); a bare subcommand is refused unless the spec DECLARES `defaultSubcommand` (`MissingSubcommandError`); `--help` short-circuits both |
+| Closed flag values | read through a function that refuses the rest (`readTarget`, `readMethod`, `readSurfaceFilter`, `isTransport`), from the framework's own set where one exists |
+| Passthrough | declared per command (`CommandSpec.passthrough`); every other command refuses a `--` tail with `X_CLI_BAD_FLAG` |
+| App root | `CommandSpec.requiresApp`, enforced by `dispatch.ts` before `run` |
+| Declared flags | every flag a command declares is read in this package's source — `flag-reads.test.ts` (`X_CLI_FLAG_UNREAD`) |
+| Planned commands | `PLANNED_COMMANDS` / `PLANNED_SUBCOMMANDS` (`cmd-planned.ts`): in the registry, exit `X_NOT_IMPLEMENTED` with a fix naming a shipped command |
+| Errors | codes + titles in `error-codes.ts`, a runnable line per code in `mcp-errors.ts` (typed over `CliErrorCode`), classes in `errors.ts` or beside their one thrower when `errors.ts` is at its ceiling. Never a bare `Error` |
+| Subprocesses | only through `exec.ts`'s injectable `Runner`; `gh` through `ctx.runner` with a required `fix` |
+| Templates | `templates/*.ts` return strings, pre-formatted for Biome (`wrap.ts`'s `wrapList` / `wrapImport` / `sortSpecifiers`); no fixture files on disk |
+| Strings | rendered output through `messages.ts` (missing key renders `⟦key⟧`). NOT in the catalog: `CommandSpec` summaries and usage, `Finding.cause` / `fix`, fixed-width table headers |
+| Facts | load the app (`app-load.ts`), then project a framework package's registry — never parse source for primitives, never re-derive a fact another package owns |
+| Public API | `src/index.ts`, explicit re-exports only. Every name there is a semver promise; a name nothing outside this package reads is not exported (22.0.0 pruned 236) |
+
+## File map
+
+### Gate steps (`x verify`)
 
 | File | Job |
 |---|---|
-| `e2e-driver.ts` | `installE2eDriver({ page, baseUrl })` — the ONE call an app's test preload makes. Registers `page` over its declaration and installs the `e2eTest` seam; returns the undo |
-| `e2e-page.ts` | `PageLike` over four members of `ScrapePage`, declared structurally so a test stands one up in six lines |
-| `e2e-locator.ts` | `LocatorLike` — a handle that resolves nothing until asked, one round trip per question |
-| `e2e-selection.ts` | what a locator SELECTS, as data, and the one in-page expression that resolves it |
-| `e2e-evaluate.ts` | the closure→string crossing, which is the only lossy edge in the adapter |
-| `e2e-errors.ts` | one constructor per refusal |
-| `e2e-dom-fixture.ts` | a document small enough to hold in a test and real enough to RUN the expressions above |
-| `cdp-browser.ts` | the two doors: `openE2eBrowserIfAvailable()` (undefined when there is no browser) and `openE2eBrowser()` (refuses by name), and the close that undoes both halves |
-| `cdp-launch.ts` | which Chrome, and starting it — the candidate list, the flags, and the endpoint read off its stderr |
-| `cdp-connection.ts` | CDP over Bun's own `WebSocket`: request framing, reply correlation by `id`, one-shot event waiters, the per-call deadline |
-| `cdp-e2e-session.ts` | the BROWSER half, `E2eSession`: every target auto-attached at browser level and PAUSED until its Network domain is on (a SharedWorker opens its socket at start-up); `newTab()`, `addInitScript()`, `offline()` for every page and worker including later ones, `setCookie()`, and the log of every WebSocket (`sockets()`) and request (`requests()`) in any realm. A page's own workers attach under it UNPAUSED — paused there, the emitted service worker never took control (measured, `e2e/service-worker.e2e.test.ts`) |
-| `cdp-e2e-page.ts` | one TAB, `E2eTab`: `E2eBrowserPage`'s five methods plus `reload`, `waitFor`, `indexedDbNames`, `close`. `offline()` forwards to the session — the switch is browser-wide |
-| `e2e-app.ts` | `startE2eApp({ root, mode: 'dev' \| 'serve', seed })`: reset + seed + spawn on a THROWAWAY `ULTIMATE_STATE_DIR` (database, disk, dev lock) and a free web AND metrics port, `/readyz`-gated, `stop()` removes the directory. Never the developer's `.x/pgdata`; two apps and an `x dev` coexist. Measured: `examples/dummy` up in ~12 s |
-| `e2e-preload.ts` + `e2e-browser-handle.ts` | the `e2e` step's own preload: with `ULTIMATE_E2E_ROOT` set (`E2E_ROOT_ENV`, by `verify-e2e.ts`) it spawns that app on a throwaway database, opens ONE browser, `installE2eDriver`s its first tab, and publishes the whole `E2eBrowser` for `e2eBrowser()` and the app for `e2eApp()`; `e2eBaseUrl()` is a function answering the spawned app's origin, never an env var |
-| `verify-e2e.ts` | `withE2eApp`: in an APP on a machine with Chrome, the `e2e` step spawns the app and runs the suite with `--preload e2e-preload.ts`. No browser or not an app: the suite runs exactly as before. Until this, no app ever installed a driver, so every `e2eTest` skipped and every `page` fixture refused |
-| `cdp-errors.ts` | one constructor per way the browser half refuses |
-
-**Absent by default, and that is a requirement rather than a state.** Nothing here runs until
-`installE2eDriver` is called, so `hasE2eDriver()` still answers `false` and the gate's `e2e` step
-still refuses instead of passing over a browser it does not have. This paragraph also said "CI has
-no Chrome" until 2026-08-27, and that is false and was the reason issue #390's fourth requirement
-— a real browser check — was recorded as out of reach: GitHub-hosted `ubuntu-latest` ships one at
-`/usr/bin/google-chrome`, preinstalled, with no download step and no new dependency.
-
-**The browser is RAW CDP over Bun's own `WebSocket`, and carries no dependency.**
-`packages/scraping/src/cdp-port.ts` declares a ~25-method port because `ScrapePage` is a full
-scraping surface and its intended implementation is `puppeteer-core`. `E2eBrowserPage` is FIVE
-methods, and CDP's wire format is one JSON object with an `id` — so the whole thing an e2e driver
-needs is four small modules, which is why `x test e2e` needs nothing installed that `bun install`
-did not already put there. `e2e/cdp-browser.e2e.test.ts` drives a real Chrome against a real
-`Bun.serve` and asserts all five methods; `openE2eBrowserIfAvailable()` answering `undefined` is
-what makes it a SKIP on a laptop without one rather than a red step.
-
-**The load EVENT is the completion signal, never `Page.navigate`'s reply.** Measured on Chrome 150:
-a navigation that swaps the render process — `about:blank` → `http://localhost:<port>/`, the most
-ordinary one there is — loads the page, hits the server and answers a later `Runtime.evaluate` from
-the new document, and the navigate frame **never comes back at all**. A driver that awaited the
-reply waited out its full deadline on every first navigation. So `cdpConnect().once()` registers a
-`Page.loadEventFired` waiter BEFORE the send, and the reply is raced against it — still read, but
-only for `errorText`, which is the one place a refused navigation is named.
-
-**A CDP call is deadlined and a close settles every call in flight.** Without that, a suite whose
-browser died waits out one full deadline per call and reports a timeout, where the true fault is a
-dead browser. The four codes are four repairs, which is why they are not one:
-`X_CDP_BROWSER_MISSING` (install one), `X_CDP_LAUNCH_FAILED` (read the browser's own stderr, which
-the cause carries), `X_CDP_CALL_FAILED` (look at the page), `X_CDP_TIMEOUT` (raise the deadline).
-
-**`evaluate` is the edge that cannot be lossless.** `PageLike.evaluate` takes a closure and every
-browser port in this framework takes a string, so what crosses is `Function.prototype.toString()`
-and nothing else. A zero-parameter closure naming only page globals is supported; a native or bound
-function, a declared parameter and a method shorthand are refused STATICALLY, before a byte leaves;
-a binding the page does not have comes back named, from the page's own `ReferenceError`. Measured on
-Bun 1.3.14 and 1.4.0 alike — re-measured on both when the repo moved back to the 1.3 series, because a version-stamped claim that names one runtime is unread evidence on the other — and load-bearing: **Bun's transpiler folds `wanted === 3` to `!0` before `toString()` ever
-runs**, so a captured PRIMITIVE can vanish from the source and never fail at all, while a captured
-reference always survives as its name. No static rule in this process can see the difference — which
-is why the refusal is raised from the page's answer rather than from a scan of the source.
-
-**One of `E2eFixtures`' four members still refuses, and it is the one that is not a port gap.**
-`update()` needs a second build served under a new immutable build id, which is a fact about the
-SERVER, and no page port has ever been able to speak for one. `offline()`/`online()` FORWARD — to
-`E2eBrowserPage.offline`, which `cdp-e2e-page.ts` implements as
-`Network.emulateNetworkConditions` and `@ultimat3/scraping` implements through
-`CdpPageLike.setOfflineMode`. They refused until 2026-08-27 on a reason the tree contradicted on
-the day it was written. A fixture that silently no-opped would make the assertion after it read as
-proof — `offline()` followed by "the fallback rendered" is the app's ONLINE page passing an offline
-test — so an `E2eBrowserPage` that declares no `offline` still gets the refusal, now naming the
-method the double is missing rather than a capability the framework does not have.
-
-## The service worker is emitted here, because the emitter needs facts only a build has
-
-`@ultimat3/pwa` shipped `generateServiceWorker`, `buildPrecacheManifest`, `offlineFallbackSource`,
-`backgroundSyncSource` and `pushSource` since it existed, and every one had **zero callers** outside
-its own package. So `pwa.offline`, `pwa.backgroundSync`, `pwa.push` and every route's own `offline:`
-were declarations with no build behind them, and no Ultimate app worked offline however its config
-was written (#390). `sw-artifacts.ts` is the caller.
-
-**Why here and not beside the manifest.** `loadPwaArtifacts(root)` needs a root and a config file;
-the worker needs the ROUTE TABLE and the ISLAND BUNDLE as well — facts only a booted app and a
-finished build have. Splitting them keeps `loadPwaArtifacts` callable before either exists, which
-`x doctor` and the icon writer rely on. The route table is `describeRoutes()`, the one projection
-`x.manifest.json`, `/_x`, the sitemap and `sw.js` are all built from, so a route added to the app
-cannot be missing from the precache manifest.
-
-| Surface | What it does with the worker |
-|---|---|
-| `cmd-dev.ts` | mounts `/sw.js` and `/x-sw-register.js`; built ONCE at boot and deliberately not rebuilt on the watcher tick — a worker that changes under a page it already controls is the update path, and re-emitting one per keystroke exercises it on every save |
-| `serve.ts` | the same two routes in the container, from the same call |
-| `prerender.ts` | writes both as FILES into the export — a static host runs no route table, so a `<script src="/x-sw-register.js">` in every document is a 404 unless the bytes are in the artifact. In TWO halves, `As of 2026-09-06`: `serviceWorkerHead(pwa)` before the render loop, because every document has to name the script, and `serviceWorkerArtifacts` AFTER it, because a precache revision is the content hash of a document that does not exist yet |
-
-**A precache revision is the DOCUMENT's content hash, and until 2026-09-06 it was the build id.**
-`pwaRoutes` projected four of `PwaRoute`'s eight fields, so every route entry read
-`{"url":"/","revision":"<buildId>","bytes":0}`: two deploys of a byte-identical site re-fetched
-every precached page, which is the one thing `packages/pwa/src/precache.ts`' own header says must
-never happen, and `DEFAULT_PRECACHE_WARN_BYTES` was a 5 MB budget over a total that could not count
-one byte of HTML. The cause was ORDER — `prerender.ts` emitted the worker before the render loop —
-so the emission moved after it and `ServiceWorkerInput.documents` carries `renderStatic`'s own
-`hash` and byte count per rendered path. `x dev` and `serve.ts` pass none and keep the build id:
-neither has rendered a page at boot, and inventing a hash for bytes that do not exist is a revision
-that never changes when the page does. **The offline document is fed through its own pair**, because
-`buildPrecacheManifest` adds it ITSELF as `reason: 'fallback'` ahead of every route and `add()`
-keeps the first entry per url — so the route entry of the same url is shadowed and only
-`offlineFallbackRevision` / `offlineFallbackBytes` (`ServiceWorkerConfig`, `@ultimat3/pwa`) can
-decide it. That pair was declared and fed by nobody for one commit; `serviceWorkerArtifacts` reads
-the fallback path out of the same `documents` map, so the one page an offline navigation depends on
-is content-addressed like every other. A fallback this pass did not render — no route serves it,
-which `x doctor` reports as `X_PWA_NO_OFFLINE_FALLBACK` — is absent from the map and keeps the
-build id.
-
-**Registration is an EXTERNAL script, never inline**, and that is a CSP fact rather than a
-preference: `startWeb` computes a `script-src` sha256 per inline script, so an unhashed one is
-blocked in the container while passing report-only under `x dev` — which is how the hydration
-runtime shipped broken once already.
-
-**`sw.js` is served `no-store` with `Service-Worker-Allowed: /`.** A cached `sw.js` is a worker that
-cannot be replaced: the browser re-fetches it to decide whether an update exists, and an
-intermediary answering the old bytes pins every client to the deploy that shipped them. Without the
-header the browser refuses to let a worker served from `/` control `/` — the failure `assertScope`
-cannot see, because the scope a REGISTRATION asks for has to be allowed by the script's own response
-and not only by its path.
-
-**`api/` and `shared/` never cross.** An API response is a JSON document whose freshness is the
-app's business, and precaching one serves a stale answer to a client that had a network; `shared/`
-is not a URL at all. The filter is a `flatMap` rather than `filter().map()` because the predicate
-does not narrow `surface` for the map that follows it, and a cast would hide the day a fifth surface
-arrives.
-
-**`pwa.push` is read and still wires nothing, and it says so.** `generateServiceWorker` emits a push
-handler only when a VAPID key comes with the capability, there is no `pwa.vapid` config key, and it
-drops the handler in SILENCE otherwise. `pushWarning` is this module's own finding, reported through
-`x build --json`'s `serviceWorkerWarnings` — `jobs.driver`'s shape one package over, refused the same way.
-
-**The browser check is what let any of this ship.** #390's fourth requirement was *"a real browser
-check that the emitted worker installs, activates and serves the fallback offline. Until it exists,
-do not ship the worker"* — a bad `sw.js` is sticky in a way a manifest is not.
-`e2e/service-worker.e2e.test.ts` registers the emitted file in a real Chrome, waits for it to take
-control, takes the network away, and asserts that a runtime route with nothing cached renders the
-offline document.
-
-**And it found the driver bug first.** `E2eFixtures.offline()` did not take the SERVICE WORKER
-offline: a worker fetches on its own CDP target, the condition was only ever set on the page's, and
-a `networkFirst` route the cache had never seen still answered from the network. So an offline
-assertion made on a PWA tested nothing. `cdp-e2e-page.ts` now auto-attaches worker targets and
-carries the condition onto each, including one that attaches AFTER `offline(true)` — the ordinary
-case for a PWA.
-
-## The `errors` step enforces the error contract
+| `verify-checks.ts` / `verify-step.ts` / `verify-run.ts` | the step list, the outcome shape, the run order (`BESIDE_SERIAL_SUITES`) |
+| `verify-floor.ts` | `x.verify.json`: a floor step that ran zero tests is `X_VERIFY_SUITE_VANISHED` |
+| `load-findings.ts` | module-load failures are reported once, by `manifest`; other steps point there |
+| `boundary-findings.ts` / `app-boundaries.ts` / `boundary-cuts.ts` | surface + layer rules; a finding's `fix:` is the concrete cut |
+| `guards.ts` | an app's `guards/*.ts`, discovered, run on `boundaries`, held to the error contract |
+| `error-contract.ts` / `ts-scan.ts` / `fix-scan.ts` / `fix-imports.ts` / `fix-command.ts` / `fix-path.ts` | the `errors` step: every `fix:` names a runnable command, call or existing file |
+| `workspace-checks.ts` / `workspace-graph.ts` / `tsconfig-references.ts` | `package-shape`, `filesize` |
+| `app-permissions.ts` / `permission-grants.ts` | `policy`: every permission granted or required is declared, and every one required is granted by some role (`X_PERMISSION_UNGRANTED`) |
+| `job-registration.ts` | `manifest`: no job or task under a positional `anonymous-*` name (`X_JOB_UNREGISTERED`) |
+| `async-pages.ts` / `live-routes.ts` / `budgets.ts` | `budgets` riders: an async `Page` with no `load`, a live read no island imports, bytes per route |
+| `app-agents-md.ts` / `app-env.ts` / `app-openapi.ts` / `app-manifest.ts` | `manifest` and `contract-diff` |
+| `schema-drift.ts` / `drift.ts` / `db-destructive.ts` / `db-ungeneratable.ts` | `drift`: snapshot vs declarations, the source hash (core's `canonicalJson`), the header markers |
+| `i18n-registration.ts` / `i18n-audit.ts` | `i18n` |
+| `error-unthrown.ts` | host check: a registered code nothing throws must say so |
+
+### Generators (`x g`, `x new`)
 
 | File | Job |
 |---|---|
-| `ts-scan.ts` | the masking every scan shares, the `X_*` codes a file declares, and the ones it says it borrows |
-| `fix-scan.ts` | the strings a `fix:` can evaluate to: under a key, at a factory's argument, at a class constructor's |
-| `fix-imports.ts` | which of those factories a file can call that it did not declare — one relative specifier, one file read |
-| `error-contract.ts` | the rules, the two checks that turn them into findings, and `collectDeclaredCodes` |
-| `fix-command.ts` | resolving an `x <command>` a `fix:` cites against the registry |
-| `fix-path.ts` | resolving a PATH or a glob a `fix:` cites against the root the gate is running in |
-| `source-files.ts` | which files are shipped source — shared with `filesize`, never a second list |
-
-**A `fix:` may not cite a command this build does not ship.** Six shipped fix lines named
-`x db status`, `x logs tail`, `x trace`, `x metrics`, `x auth whoami` and `x ai prompts`, and every
-one passed — the text rule checks that a fix NAMES a command, never that the registry holds it.
-`fix-command.ts` resolves the citation, and a PLANNED command fails too: `x logs` parses, `x help`
-lists it, and running it hands the reader `X_NOT_IMPLEMENTED` instead of the fix.
-
-**A `fix:` may not cite a file this repo does not have, either.** That was the other half, and
-nothing resolved it: `X_UI_RUNTIME_MISSING` told its reader to paste a line no generator ever wrote,
-through every gate since it shipped (#274, #246). A file token is one of the four things that make a
-fix an instruction at all (`COMMAND_TOKENS`), so `fix-path.ts` is built from the SAME extension list
-— a token that satisfies the instruction rule is exactly the token this one has to resolve, and two
-lists would be a citation the second rule cannot see. `X_ERROR_FIX_PATH_MISSING` is its own code:
-`X_ERROR_FIX_INVALID` means the fix is not an instruction, this one means it is one and points at
-nothing, and the repairs differ.
-
-It is narrow so a finding never has to be argued with — three shapes are not judged at all, because
-each resolves against something other than the root the gate is running in: a scoped specifier
-(`@ultimat3/ui/global.scss`, which resolves through `node_modules`), a dot-relative path
-(`./global.scss`, which resolves against the reader's own file) and any path whose **parent
-directory** this root does not have (`src/errors.ts`, `apps/web/server.ts`,
-`packages/i18n/catalogs/en.json` — all three name a directory a generated app has and this repo does
-not). What is left is the citation a root really can answer: a directory that exists, named as
-holding a file it does not hold. A glob must match at least one file. Measured over all three roots
-the gate runs in — the framework, `examples/dummy`, `dummy/social-media-clone` — **117 path citations
-read, 0 findings**, so it enforces outright with no pin table.
-
-The rule is **conditional, and that is load-bearing**: *if* a fix cites `x <command>`, it must
-resolve. It does not require every fix to name one — `set OTEL_EXPORTER_OTLP_ENDPOINT=…` and
-`counter('orders_total', { maxSeries: 4000 })` are executable and correctly cite nothing, and a
-universal rule would push an author into citing a command that does not really fix it. A second
-word is judged as a subcommand only when the spec declares subcommands, or `x new my-app` reports
-`my-app` as one. The registry arrives through `await import('./registry')` — `registry → cmd-verify
-→ error-contract` closes a cycle back to the caller, and the precedent for the break is
-`cmd-build.ts`.
-
-**It reads a THIRD word, under the same condition.** `x db branch ls --json` resolved — `db` is a
-command, `branch` is one of its subcommands — and the word that decided what actually ran was never
-looked at, so a fix line that created a stray database passed every check the repo had. A third
-word is judged only where the subcommand declares a closed set (`CommandSpec.subcommandPositionals`,
-declared from the constant the command validates against), because `x jobs show <id>` and
-`x db gen "add publish_at"` take open positionals and a universal rule would report findings about
-working invocations. `positionalChoices` cannot express it: `fix-command.ts` reads that field only
-where a command declares no subcommands at all.
-
-**A command with no subcommands must still declare `positionalChoices`, or its second word is unjudged.** `x g migration` shipped in two `@ultimat3/admin` fix lines — a generator that has never existed, answered with `X_CLI_UNKNOWN_COMMAND` when run — because the `g` spec declared none and `fix-command.ts` returns `undefined` for an absent set. The third instance of this class (#131, then `x db branch <name>`). `cmd-generate.ts` now declares `positionalChoices: GENERATORS`, from the SAME constant `readKind` validates against, exactly as `cmd-test.ts` declares `TEST_TYPES` — `fix-command.test.ts` pins `x g migration` as a finding against the real catalog. A new command whose first positional is a closed set and does not declare it is a hole this rule cannot see.
-
-**And in that one slot, a `<placeholder>` is a finding too.** `x db branch <name>` is what two
-`@ultimat3/mcp` fix lines said; the citation reader does not read `<name>` as a word, so the slot
-was never examined and the line resolved clean while running it answers `X_CLI_UNKNOWN_COMMAND` —
-the same blind spot in a second disguise. A closed set means the slot is a verb, so there is
-nothing a reader could substitute that would make it run. `CITATION` therefore matches a
-placeholder in the third slot **only**: `x jobs show <id>` and `x db branch drop <name>` are correct
-fix lines and must stay invisible to this rule.
+| `cmd-generate.ts` / `generate-files.ts` / `generate-kinds.ts` / `generate-write.ts` | argv → pure file list → writes (conflict-checked, `merge: 'json'` / `'if-absent'`) |
+| `generate-feature.ts` | a `--feature` naming no slice is `X_FEATURE_UNKNOWN`; nothing invents an entity |
+| `generate-grants.ts` | a written `policy.ts` grants `:read` to `member`, `:write` to `admin` in `apps/web/shared/roles.ts` |
+| `api-registration.ts` | a written job or task is listed in `apps/web/api/index.ts` |
+| `app-artifacts.ts` | `x.manifest.json` + `openapi.json`, written together by `x g` and `x manifest` |
+| `templates/` | every emitted file; `scaffold-*.ts` for `x new`, one file per generator otherwise |
 
-`collectDeclaredCodes` is the only answer to "which codes exist, and where is each declared?" — one
-walk, one entry per code, the owning registry preferred over any throw site and over a registry
-that named the code in its `<PKG>_BORROWED_ERROR_CODES`. The docs check reads it and so does the
-framework's own `framework.manifest.json`, because a second scanner over a narrower file set is a
-manifest that claims completeness it does not have.
-
-**A `code:` is a literal, a module-scope const in the same file, or a finding** — `As of 2026-08-23`,
-and until then it was a literal or silence. `scanCodes` matched `code\s*[:=]\s*'X_…'`, so
-`const STALE = 'X_DOC_PACKAGE_GRAPH_STALE'` followed by `code: STALE` — the DRY thing to write, and
-what `scripts/package-map-graph.ts` really wrote — was a declaration to nobody: no manifest row, no
-row demanded on `wiki/Error-Codes.md`, no entry for `bun run gate-codes`, and `x errors explain`
-answering `X_ERROR_CODE_UNKNOWN` for a code the build throws. Silent, and in the **permissive**
-direction: the DRYer the author, the less the gate saw (#277).
-
-`scanCodeDeclarations` is that one pass, and it returns both halves. It resolves the identifier
-against the module-scope consts of the **same file** — anchored at column 0, which is what makes it
-module scope without a parser — and reports every name it cannot resolve as `X_ERROR_CODE_UNRESOLVED`
-rather than skipping it, which is the whole point: a scanner that reads only what it likes enforces
-only what it sees. `scanCodes` is its `.sites`, so the manifest, the docs check, `bun run gate-codes`
-and `x errors explain` (through `scanCodeFixSites`, which resolves the same way) cannot see different
-sets. Cross-file resolution was **refused** even though `fix-imports.ts` already does the harder
-version for `fix:`: it would make the scan async for every caller, and the finding is the better
-answer anyway — one file holds both the code and its only spelling.
-
-Three shapes are deliberately not judged, each measured over the framework and both tracked apps
-before the rule shipped. A name that resolves to something that is **not** a code is an answer, not
-a gap (`const STATUS_NOT_FOUND = 404` in `@ultimat3/realtime`'s NATS fake, the one live instance). A
-**table read** is not judged — `SEO_ERROR_CODES.metaMissing` is how `@ultimat3/seo` and
-`@ultimat3/ui` raise all 18 of their codes, and the registry those literals live in already declares
-them. A **lowercase** name is not judged: 164 sit at a `code:` position in this tree and every one is
-a type annotation (`readonly code: string`) or a re-raise (`code: opts.code`). Measured on all three
-roots: **0 findings**, so it enforces outright with no pin table.
-
-An empty `fix`, or a `fix` that says `check` / `make sure` / `try` / `see the docs` and names no
-command, call or file path, is `X_ERROR_FIX_INVALID`. A declared code the host's error reference
-does not name is `X_ERROR_CODE_UNDOCUMENTED` — `wiki/Error-Codes.md` here, nothing in a generated
-app, which is why that half arrives as a host check (`scripts/verify.ts`) rather than a hardcoded
-path in this package.
-
-`ts-scan.ts` masks comments and string contents before it looks for structure. The contract's own
-3-line rendering appears verbatim in doc blocks and interpolated messages, and a scanner that read
-those as declarations would report findings nobody can fix. What it cannot see is a `fix` with no
-literal — a parameter, or a table lookup with no fallback. Those are out of a static scan's reach,
-and the step says so rather than guessing.
-
-**A fix does not always arrive under a key**, and until `As of 2026-08` the scanner assumed it did.
-`@ultimat3/mcp`'s `readonly-sql.ts` hands every fix positionally to a local `rejected(cause, fix)`
-helper, so the file held no `fix:` at all and `scanFixes` returned `[]` for all of it — the
-citation resolver was never given a string to judge, and two stale `x db branch <name>` lines
-shipped through the hole. `scanFixes` now also reads the argument in the `fix: string` position of
-a **local** helper, under four rules, each with its own case in `fix-scan.test.ts`: the helper must
-BUILD an error (`code` key or `new …Error(` in its body), or `citedCommandProblem(fix, catalog)` —
-which takes a fix to *judge* it — would have its call sites read as declarations; the parameter
-list may hold no rest or destructured parameter, because neither has a reliable position; the call
-may not be a member access; and the argument must BE one literal, stricter than the key path,
-because `prefix + 'x doctor'` reads as one literal there and publishing half a fix is worse than
-publishing none. Measured over the whole tree: 16 files gained readable fixes, `readonly-sql.ts`
-went from 0 to 7, and **zero** new findings.
-
-**And a fix does not always arrive in the file that declares its builder**, which is where four
-bad `fix:` lines in `packages/ui/src/icons/build-icons.ts` shipped: `invalidIconDataError` is
-declared in `packages/ui/src/errors.ts`, and a per-package `errors.ts` full of factories is the
-house pattern, so the same-file rule left the most common shape of all unchecked. `fix-imports.ts`
-resolves it — the specifier is relative, the candidate paths are `<base>.ts{,x}` and
-`<base>/index.ts{,x}`, and the parameter position is the callee's. An alias is renamed to what the
-CALLER writes; a local declaration of the same name wins, because that is the function the call
-actually reaches. One module cache per run: `errors.ts` is imported by every file in its package.
-
-**An error CLASS is the same helper one keyword away**, and is now read too: the name is the
-class's, the parameter list its `constructor`'s, `new X(…)` is a call like any other. It was
-measured as dead code in the same-file rule — zero same-file call sites — and cross-file it is
-`@ultimat3/render`'s fourteen classes plus `@ultimat3/core`'s three image ones.
-
-Measured over the whole tree, `As of 2026-08`: **791 → 877** fix literals read, 37 files gained
-one, and **3 findings** the gate had never been able to see — `x verify --contract` and
-`x build --route` (two flags no command declares) and one `check …` line with no command token.
-
-What it still cannot see is a builder imported from another **package**: `candidatePaths` refuses a
-non-relative specifier, because resolving one means guessing which of 29 packages a bare name came
-from and a wrong guess reads an unrelated function's argument as a fix. Measured: 3 call sites in
-this repo, none of them a finding. It is **not** left silent — the step's `output` carries
-`checked {n} fix line(s), could not read {m}`, counted at `FixScan.unreadable`: an argument in a
-KNOWN fix position that is not one literal. Deliberately not "imports I could not open", which is
-1504 names here and 1310 of them are `join` and `UltimateError` — a number nobody can act on.
-
-`cli → admin` is a declared sideways edge (`scripts/lib/tiers.ts`): `x dev` **mounts** the
-dashboard, it never grows a second one. The CLI's only contribution is the facts no registry
-holds — a SQL runner, the caught outbox, the committed manifest, the process's own services, the
-spans it recorded — supplied as `defaultDevSources({ hooks })`.
-
-Wired means answerable: all eleven panels answer in a `x dev` process, and a hook the CLI does
-not supply is a panel that refuses with a wiring line, never one that renders empty. `timeline`
-is core's tracer (`x dev` is what calls `configureTelemetry`), `cache` is
-`recentInvalidations()`, `policy` is `@ultimat3/policy`'s own `policyMatrix()` over the app's
-roles — a verdict re-derived here would be the second authz the framework exists to prevent.
-`subscribers` is the one source left unwired: `@ultimat3/realtime` retains no matcher trace, and
-that trace is the live panel's question, so the panel degrades to its own note instead.
-
-`dev-traces.ts` reads a span's panel kind off its **name prefix** — a subsystem that starts emitting
-spans adds its prefix to `KIND_BY_PREFIX` or its work is filed under `action`. `db.` is there
-because `@ultimat3/db`'s two funnels open one span per statement (`db.select`, `db.begin`), and a
-statement is the one span that states its own identity — `STATEMENT_ATTRIBUTE`, **imported** from
-`@ultimat3/db` by both `dev-traces.ts` and its test rather than spelled as a literal, which the
-recorder prefers over the name, so the timeline's `repeatedSql` groups SQL texts and not span names. Those spans
-exist only where a `StatementObserver` is installed, so a trace with no DB children is a process
-with no statement diagnostic, not a broken recorder.
-
-`dev-n-plus-one.ts` is that observer, and `cmd-dev.ts` is the **only** place that installs it —
-`serve.ts` installs neither it nor the in-process trace RECORDER (`createTraceRecorder`, which is
-`/_x/timeline`'s source), the same line that file already draws for `/_x`. **It is not "no
-exporter"**, `As of 2026-08`: `serve.ts` calls `startOtlpExport(options.env)`, because a collector
-named in the chart has to receive spans from the container and not only from a laptop. What a
-production process does without is the *statement* diagnostic and the in-memory timeline — the
-ledger and the recorder go in together and come out together in `stop()`, because the timeline's
-SQL rows and the repeat counts are one feature with one toggle, and uninstalled the seam costs the
-one `undefined` branch it already pays (axiom 6).
-
-Three rules hold the ledger, each load-bearing. **Per request, keyed by the `Ctx` object** — a
-`WeakMap` whose entry dies with the request, so nothing sweeps and nothing accumulates across a dev
-session; a statement issued outside a request is not counted at all, because "five of one shape"
-only means something inside one unit of work. The price of keying on identity is that a
-`withChildContext` scope is its own tally. **A shape is `entity.op` when attributed**, the
-statement's own text with whitespace collapsed when it is not — `members.findById` fifty times is
-what an author can act on, and grouping fifty point lookups by their SQL would report bind values.
-That rule is **not written here**: `statementFingerprint`/`statementKind` are `@ultimat3/db`'s and
-the threshold is `@ultimat3/entity`'s `N_PLUS_ONE_THRESHOLD`, because `@ultimat3/testing`'s
-`statements` fixture is a second detector and a copy of either would let a loop that fails a test be
-a different loop from the one this ledger warns about. What stays here is what only a dev *server*
-knows: the request as the unit of work, the bound report list, one log line per request per code.
-**An expected statement is not counted** — `expectedQueryLoop` suppresses a verdict and this ledger
-is the verdict, so the span and the timeline still show the loop while the thing that warns is told
-the author already answered. A shape is promoted to a verdict exactly once, on the statement that
-crosses the threshold, and its count keeps rising: a loop of fifty is one report reading fifty. The
-report list is bounded and drops its oldest.
-
-`statement-loop.ts` is the **one** projection those verdicts reach four surfaces through, and the
-reason there is only one is that four renderings of one loop must be one sentence. It hands a
-verdict to `@ultimat3/entity`'s `nPlusOne()` — the `fix:` speaks that package's vocabulary and is
-derived from the relations the schema already declared — and each surface takes a field of what
-comes back: `cmd-dev.ts` appends `loopFinding` to the `findings` getter (text and `--json` render it
-for free), `dev-dashboard.ts` supplies `statementLoops` so `/_x/timeline` shows `nPlusOne` for the
-request on screen, `cmd-dev.ts` again passes `devNotices` down `startRoles` so the browser overlay
-renders the loop under the error, and the ledger itself emits `warnLoop` — one `logger.warn` per
-request per code, the ids riding along from core's `setLoggerContextFields`.
-
-Two rules about *when* a count is read. **A surface reads it live**: the finding, the panel row and
-the notice all say `ran 50 times` because they ask after the loop finished, while the log line says
-`ran 5 times` because it was written the moment the threshold was crossed — same verdict, two
-honest moments. **A verdict belongs to its request**: `repeatsFor(ctx)` reads the request's own
-tally rather than filtering the bounded global list, so the overlay still names a loop the bound
-already dropped. `serve.ts` supplies no `devNotices`, so the seam it boots through is a key that is
-absent, not a hook answering an empty list.
-
-`dev-n-plus-one.test.ts` and `statement-loop.test.ts` drive the ledger and the projection with
-hand-built `StatementEvent`s — fast, and enough to pin every rule above. `n-plus-one-detector.test.ts`
-proves the loop those events stand in for: real `posts`/`authors` entities, `postgresRepo` and
-`createPgliteClient` (an injected fake driver so no `@electric-sql/pglite` build is needed, but a
-real client — `createRecordingClient` implements `DbClient` on its own and never reaches the
-observer, so it cannot stand in here) — a naive per-row `findById` loop trips `X_N_PLUS_ONE_QUERY`
-with the exact `preload('author')` line, the `preload()` form of the same read stays quiet,
-`expectedQueryLoop` silences the naive form without stopping it from running, and a naive per-row
-`delete` loop trips `X_N_PLUS_ONE_WRITE`. Its describe block spells the pattern `n1`, matching
-`packages/entity/src/n-plus-one.test.ts`'s own fixture prefix, because `bun test -t 'n+1'` is a
-regex and `+` is a quantifier — `n1` is what actually selects these tests.
-
-## One migration engine, four environments
+### Boot (`x dev`, the container)
 
 | File | Job |
 |---|---|
-| `migrations.ts` | the app's `packages/db/migrations` read into `@ultimat3/db`'s `Migration` shape — the **one** reader |
-| `db-generate.ts` | `x db gen`: entities diffed against what the migrations declare, written as `.sql` + `.snapshot.json` + `.hash` |
-| `cmd-db.ts` | the subcommands, and nothing else — `gen` calls `db-generate.ts`, `migrate`/`reset` call `serve.ts`'s `runMigrations` |
-| `db-branch.ts` | what a branch IS: the closed verb set, the name it takes on disk and in `pg_database`, and list/create/drop per mode |
-| `cmd-db-branch.ts` | `x db branch`'s wiring alone — which verb, which refusal, and the one connection an external clone runs on |
-| `db-finding.ts` | one thrown value → one `Finding`, shared by `cmd-db.ts` and `cmd-db-branch.ts` |
-| `db-accept-created.ts` | `acceptCreatedTables`: the post-migrate report minus the tables the applied migrations' own SQL creates — the half `@ultimat3/db`'s `unexpectedTable` names |
-| `db-subscribes.ts` | `replicaIdentityTables`: the tables `x db gen` grants `REPLICA IDENTITY FULL`, read off each live query's declared `subscribes:` — and `X_QUERY_SUBSCRIBES_UNKNOWN` for a name no entity's table matches |
-| `drift.ts` | `checkSourceDrift`: the `.hash` sidecar the `drift` step compares, no database needed |
-| `schema-diff.ts` | what two GENERATED snapshots disagree about, as data — the pure half |
-| `schema-drift.ts` | `checkMigrationDrift`: entity declarations against the newest `.snapshot.json`, and the composition the `drift` step and `x doctor` both read |
-| `db-destructive.ts` | `checkDestructiveMigrations`: the same step's second half — every committed `up` that drops, truncates or retypes must carry `-- destructive: true` |
-| `db-ungeneratable.ts` | `checkUngeneratableMigrations`: the same step's fourth rail — every committed `up` holding SQL `x db gen` could not have written must say how many, as `-- ungeneratable: <n>` |
-| `db-backfill.ts` | `x db backfill --list`: the flag parsing, the ledger read and the table |
-| `db-seed.ts` | `x db seed`, everything except the argv: `SEED_GLOBS` (where a seed is declared), `discoverSeeds`, `parseSeedTierFlag`, `selectSeeds` (which seeds this invocation runs, and its two refusals — `X_DECLARATION_UNKNOWN` and `X_SEED_ENVIRONMENT`), `runSeeds` (one transaction **per seed**, never one around the run) and the two renderers. The `db-backfill.ts` split repeated: a driver plus plain strings in, plain rows out, so every rule is testable with no `ParsedArgs` and no boot. Which tiers an environment takes is `@ultimat3/entity`'s `seedTiersFor` — two copies of "may this seed run" would be two answers |
-
-`jobs-driver.ts` is the ONE place a CLI command gets hold of the app's queue — `withJobDriver`,
-which `x jobs` and `x db backfill` both call. It reuses an ambient `jobDriver()` when a process
-already installed one (inside `x dev` or `x mcp serve`, booting a second queue talks to the wrong
-database) and otherwise boots `startQueue` and releases it in a `finally`, or a CLI that exits
-holding the PGlite lock breaks the next command run against this app. A second copy of that boot
-would be two answers to "which queue is this command talking to".
-
-**`x db branch` takes a VERB, and a branch name can never be one.** `ls`, `create <name>`,
-`drop <name>` — a closed set, declared once in `BRANCH_SUBCOMMANDS` and read three ways: the
-command validates against it, `dbCommand.spec.subcommandPositionals` declares it so the `errors`
-step can resolve a citation against it, and the refusal for an unknown word lists it. The bare-name
-form it replaces is why: the argument *was* the name, so `x db branch ls --json` — the `fix:` on
-the planned `x branch`, on `X_DB_BRANCH_FAILED`, and (as `create`/`drop`) on `@ultimat3/db`'s own
-`X_BRANCH_EXISTS` and `X_SQL_UNSAFE` — cloned a database called `ls` and returned no listing. All
-four passed every check the repo had, because `fix-command.ts` resolved two words and the third was
-the one that decided what ran.
-
-**`drop` has no confirmation flag, and that is the design.** It may only drop what `ls` shows: an
-external branch is a database carrying the marker comment `createBranch` writes **and** this
-database's own `<source>_branch_` prefix, an embedded one is a `pgdata-<name>` directory, so the
-shared database this session is connected to is in neither set.
-The typo is impossible rather than the keystroke tedious — and `@ultimat3/db` already ships
-`x db branch drop <name>` as `X_BRANCH_EXISTS`'s `fix:` with no flag on it, so a flag here would
-break a shipped instruction.
-
-**The prefix half is not decoration, and it is no longer the only source guard.** The marker records
-the base `As of 2026-08-19` — `ultimate:branch:<base>:<iso>`, read back as `BranchInfo.base` — so
-`reapBranches` can skip another app's clones on its own. The prefix guard still stands and is what
-`ls`/`drop` read, because an **older** marker records no base at all: it is skipped by the reaper
-rather than dropped, which leaves `drop` needing an answer that does not depend on a field half the
-branches lack. One Postgres server hosting two Ultimate apps answers `listBranches()` with both
-apps' clones, and `branchNameOf` reduced `postly_branch_feat` and `analytics_branch_feat` to the
-same branch name — so `x db branch drop feat`, run against `postly`, was authorised by
-`analytics`'s row and then issued `drop database if exists "postly_branch_feat"` against a database
-carrying no marker at all: a `DROP DATABASE` the guard had never approved, and nothing recoverable
-about it. `branchNameIn(source, database)` is the source-scoped inverse of `branchDatabaseName` and
-the one `ls` and `drop` both read; `branchNameOf` survives for `mcp-db-target.ts` alone, which has
-a URL and no connection to ask `current_database()` with.
-
-**The membership check lives inside `dropExternalBranch`, not in the wiring above it.** One
-connection, one listing, one statement before the `DROP` — a listing taken by the caller and acted
-on afterwards is two connections and a window wide enough to hold a whole `create`. It is still not
-atomic and cannot be: `DROP DATABASE` runs in no transaction, so no single statement both verifies
-the marker and deletes. Closing the last gap means a lock around both halves inside
-`@ultimat3/db`'s `dropBranch` — which a `psql` at the next terminal would not hold either.
-
-**`ls` is the reason `create` no longer shells out to `psql`.** `listBranches()` finds branches by
-`createBranch`'s marker comment; the `psql` path wrote the `CREATE DATABASE` and no comment, so
-every branch the CLI made was invisible to the only lister the framework has. External branching
-now runs through `@ultimat3/db` on one `role: 'migrate'` client — `max: 1`, no statement timeout,
-both load-bearing: `CREATE DATABASE … TEMPLATE` is refused while any *other* session holds the
-template, and cloning a real database outlives a `web` profile's 10s.
-
-**`DatabaseTarget.production` is a fact this package supplies, and it was the literal `false`.**
-`mcp-db-target.ts` is the only place one is ever built, so `assertBranchDatabase`'s first refusal —
-"production is never migratable from MCP at all" — could not run for any database the CLI produced;
-a production database was refused only incidentally, because its name lacked `_branch_`, and one
-named `shop_branch_hotfix` read as a branch and was migratable. It is now core's one key, read the
-way `x doctor` reads it. An **unreadable** `ULTIMATE_ENV` counts as production: `tryResolveEnvironment`
-answers `undefined` for exactly one input — a value that is not an environment — and a guard that
-read a typo as "not production" would be defeated by the misconfiguration it exists to survive.
-`staging` stays false; `branch: null` is already what refuses it, and widening the flag would make
-the refusal say something untrue.
-
-`x db backfill` has four shapes and a **dry run is the default**: `--list` reports the ledger,
-`--pending` reports declared-minus-completed and exits non-zero when there is drift, `<name>` plans
-one sweep, and `--all` plans every pending one. `--write` is never implied — the inspection forms
-and the acting form are the same command, and the flag is the only thing that separates them.
-`--all --write` isolates per name and continues past a failure, exiting non-zero naming each, so one
-wedged cleanup cannot block every later one forever.
-
-Until 1.2.0 a bare `x db backfill <name>` threw `X_NOT_IMPLEMENTED`, and the ledger was the only
-half that existed: `x_backfills` recorded what had run, and **nothing recorded what was pending**, so
-a scaffolded backfill could be merged and deployed and silently never run. `--pending` is the alarm
-that closes it; `registeredBackfills()` is what makes a declaration visible before its first pass.
-
-`x db migrate` and `ROLE=migrate` are the same function call. That is the whole design: until
-1.2.0 the CLI shelled out to `bunx drizzle-kit` — a second engine, a second journal, declared in no
-`package.json` and fetched unpinned at run time — while the release phase used the framework's
-ledger, so "what has been applied" had two answers that only agreed by luck. `cmd-db.test.ts`
-holds the line from both ends: no shipped source spawns a second migrator, and this file still
-imports `runMigrations` from `./serve`.
-
-**The post-condition is one check too, and it is the database one.** `runMigrations` runs
-`@ultimat3/db`'s `checkDrift()` inside the queue's lifetime — the connection it opened for the
-migrator is the only one there is — and returns the report on `MigratedApp.drift`, so a developer
-and a release phase verify the same thing. `x db migrate` renders it through `driftFindings` and
-exits non-zero; `runRole` throws the first difference for `ROLE=migrate`, so the release phase
-exits non-zero too. Both entrypoints call the same `runMigrations` and both fail — the difference
-is only the channel each has. `ROLE=migrate` logged and exited 0 until it did not: a release phase
-whose only signal is the exit code reported success over a schema nobody can reconstruct, which is
-the failure the post-migrate check exists to catch.
-
-**`x db gen` emits `REPLICA IDENTITY FULL`, and the set is DECLARED rather than derived**,
-`As of 2026-08-26` (#357). `@ultimat3/realtime` refuses a live subscription to a table without it —
-logical replication carries no old row on an UPDATE, so no patch can be computed — and for two
-years nothing in the framework emitted one. It could not be derived, and that is the load-bearing
-fact: the relation name lives inside the query's `sql:` callback, which no generator can invoke
-without valid input (`describeSql` says so itself — "`null` when no sample input was supplied").
-So a live query DECLARES it (`subscribes:`, `@ultimat3/query`), the declaration is machine-checked
-against the resolved `shape.entity` on the first subscribe (`X_QUERY_SUBSCRIBES_DRIFT`), and
-`db-subscribes.ts` reads it off `describeQueries()` — the same source `frameworkSources` copies onto
-`QueryFact.subscribes`, one hop earlier, because building the manifest here would re-load the app
-and demand a `package.json` that `x db gen` has never needed.
-
-**The third `subscribes:` refusal is this package's, because no other tier can ask it.**
-`@ultimat3/db` keeps only the declared names an entity's table matches and DROPS the rest — it has
-no way to tell a typo from a table another migration owns — and `@ultimat3/query` holds no table
-catalog at all. So `subscribes: ['posts', 'user']` granted the identity to `posts`, dropped `user`
-in silence, and read as granted. `X_QUERY_SUBSCRIBES_UNKNOWN` refuses it BEFORE anything is
-written, naming the query and offering the tables the app does declare. It is checked after
-`loadApp`'s findings, never before: a module that would not import leaves the registry short, and
-every name whose entity lives in it would then look like a typo.
-
-**And it accepts a table the migrations it just applied demonstrably created**, `As of 2026-08-26`
-(issue #345). A snapshot records only what ENTITIES declare, so a table created by a HAND-WRITTEN
-migration reached no sidecar and was `unexpected-table` on every deploy forever — with a `fix:`
-that generated an empty migration, because `x db gen` diffs the entity registry against the newest
-snapshot and the table is on neither side. `@ultimat3/db` fixed the wording; `acceptCreatedTables`
-(`db-accept-created.ts`) is the half that file's `unexpectedTable` names, and it is composed around
-`checkDrift` inside `runMigrations`, so `x db migrate` and `ROLE=migrate` accept the same set.
-**Only `unexpected-table`, and only for a name a migration's SQL creates** — which is what keeps it
-an acceptance rather than the check switched off: a table absent from the snapshot produces exactly
-one difference (`diffSchema` reports it and never compares its columns), and a table nobody
-declared and no migration created is still reported, cause and `fix:` intact. The evidence is the
-applied list itself: `migrate()` runs first, so every file on disk has been applied by the time the
-question is asked. The verb phrase is read ANCHORED off the raw statement, which is the whole
-protection — a `create table` can only be at position 0 by being one, so `values ('create table
-ghost')` opens with `insert` and a comment-only chunk is not a statement at all. A `stripSqlNoise`
-pass was written first and deleted: it could not change one answer, and a defence that cannot fail
-is one nobody can test. Everything the anchor admits and the name grammar does not — a comment
-between the keywords, a `temp` table, a qualifier naming a schema `checkDrift` never introspected —
-contributes nothing, which reports drift that could have been accepted and never the reverse.
-
-**The `drift` step asks a third thing, off the same directory and with no database either: is every
-destructive statement declared?** `db-destructive.ts` reads each committed migration through
-`migrations.ts` — the reader `x db migrate` applies from, because a rail checking a list the
-migrator does not run enforces nothing — and refuses an `up` that drops a table, drops a column,
-truncates or retypes without a `-- destructive: true` line, as `X_MIGRATION_DESTRUCTIVE`. It decides
-none of that itself: `@ultimat3/db`'s `destructive.ts` owns the classifier `db-generate.ts` already
-wrote the marker from, so the generator and the gate cannot disagree about one file. One finding per
-file, never one per statement — the marker declares the whole migration. It rides on `drift` rather
-than becoming an eighteenth step because it is this step's own question over this step's own files;
-a new step is for a genuinely new question.
-
-**The `drift` step reads the SNAPSHOT, not only the hash, `As of 2026-08-25`.** `checkSourceDrift`
-compares a schema-source hash to a `.hash` sidecar and never reads what the migration RECORDED, so
-`dummy/social-media-clone` sat green while **nine declared CHECK constraints had never reached any
-database** — a comment body could be whitespace, a like count could go negative, an email needed no
-`@` — and a squash that dropped ten invariants and nine defaults would have been green too. The
-source had not moved, so nothing that hashes source could see it. `checkSnapshotDrift`
-(`schema-drift.ts`) diffs `snapshotOf(describeEntities())` against `declaredSchema(readMigrations())`
-— both sides are `snapshotOf`'s own spelling, which is what makes a check, a default and a column
-type comparable at all. Measured against that app rolled back to the state its gate was green in:
-**20 findings**, 9 checks and 11 defaults.
-
-**Two directions, two codes, because they are two repairs.** `X_DB_SCHEMA_UNMIGRATED` is a
-declaration the migrations do not carry — the database will never get it. `X_DB_SCHEMA_UNDECLARED`
-is a migration carrying what nothing declares any more, whose fix names BOTH branches, because the
-declaration may have been lost rather than removed and `x db gen` would emit the DROP. One "drift"
-verdict over both teaches a reader neither.
-
-**Absent is not empty, and reading it as "recorded none" would fail every existing app on its first
-run.** `TableDescription.checks` is absent — never `[]` — on a table declaring none, exactly like
-`IndexDescription.using` and `ColumnDescription.generated`. Both sides normalise to empty
-(`schema-diff.ts`), `using` reads through `indexMethodOf` and `order` through `?? 'asc'`, or an app
-whose sidecar predates any of the three reports a difference on every index it has.
-
-**The hash half stays, and runs second.** It catches what the snapshot comparison cannot see at all
-— a seed, a helper or a TS-only invariant moving under `packages/db/src` with no statement behind
-it, which is what `reconcileSchemaHash` exists to re-record. It is SUPPRESSED when the snapshot half
-found something: both then answer one condition and only one of them is an instruction, since
-`schema hashes to 3f2a, newest migration recorded 91bc` names no constraint, no column and no table.
-
-**An app whose modules will not import is not judged here.** `appEntities` answers `undefined`
-rather than a short registry, which would read as "every table was dropped" and hand out a DROP per
-table for one file's syntax error — the same stance `generateAppMigration` takes with its `blocked`
-outcome. The cost is that a schema check can be silently skipped under an already-red gate; the
-alternative is a false red whose fix destroys data.
-
-**The FOURTH thing the `drift` step asks is what neither hash nor snapshot can see: SQL no
-declaration carries at all.** `ALTER TABLE posts REPLICA IDENTITY FULL;` sits in
-`examples/dummy/packages/db/migrations/0001_init.sql`, no generator emits it, no snapshot records
-it, and a squash drops it in silence — and no declaration-based check can ever see it, because a
-regenerated sidecar equals the declaration by construction. `db-ungeneratable.ts` reports it,
-`As of 2026-08-25`. It classifies nothing itself: `@ultimat3/db`'s `ungeneratableStatements`
-matches each statement's leading verb phrase against `GENERATABLE_FORMS` — everything
-`generateMigration` emits, held honest in both directions by that package's own test — because
-every SQL classifier in the tree is db's (`sql-scan.ts`, `statement-split.ts`, `sql-noise.ts`,
-`destructive.ts`) and a second one here is the reimplementation this file's own rule forbids.
-Measured: **7 statements in `examples/dummy`** (five `CREATE TYPE … AS ENUM`, two
-`REPLICA IDENTITY FULL`), **0 in all four `dummy/social-media-clone` migrations** and 0 in
-`examples/dummy`'s own generated `0002_money_scale.sql` — real generator output reports nothing,
-which is the half a rail like this lives or dies on.
-
-**The declaration is a header line, and it carries a COUNT: `-- ungeneratable: 7`.** Not
-`@ultimat3/db`'s code but this package's (`X_MIGRATION_UNGENERATABLE`), because the only remedy
-available for every statement it reports is a line in the migration file, and where an app keeps
-its migrations is this package's fact — db classifies and deliberately declares no code. Three
-decisions behind that shape:
-
-| Decision | Why |
-|---|---|
-| in the migration file, not a pin table here | the gate runs in every generated app, and a table in `packages/cli/src` can hold no row for an app it has never seen. `-- destructive: true` in the same directory, read by the same reader, is the precedent |
-| a count, not a boolean | the first hand-written statement would otherwise buy the file an unlimited allowance, and statements a reader never sees again are this rail's whole subject. A ratchet in the `README_FENCE_BACKLOG` sense: `found > declared` reports, a declared count that is too high is a pin nobody lowered |
-| the **header** — before the first statement | `hasDestructiveMarker` had to become a lexical scan because a regex over the raw file matched its marker inside a block comment and inside a dollar-quoted body, and `noiseAt` is db's and unexported. A run anchored at index 0 needs no scanner to be exact: before the first statement there is no string, no quoted identifier and no dollar body for a marker to hide in |
-
-**The `fix:` names the marker first and `x db gen` second, and that order is the point.**
-Regenerating is exactly what *discards* these statements, so the command every other db code
-answers with is the one this one must not lead with — `X_MIGRATION_UNGENERATABLE`'s `CLI_FIXES` row
-is `x verify --only drift`, and the re-declare branch (an enum is a text column plus a check
-invariant) rides behind an em-dash because it is available for some of the statements and not all.
-**`REPLICA IDENTITY FULL` was the statement with no second branch, and stopped being one on
-2026-08-26** (#357): a live query declares the relations it is patched from (`subscribes:`),
-`db-subscribes.ts` reads them off the same registry the manifest is projected from, `x db gen`
-emits the ALTER and `@ultimat3/db` records it on the snapshot so it is emitted once. The re-declare
-branch covers it now: declare `subscribes:` and regenerate. A statement already committed is a
-different question and still counts — `GENERATABLE_FORMS` (`@ultimat3/db`) matches a leading verb
-phrase and does not carry this one, measured at 7 found / 7 declared on `examples/dummy`'s
-`0001_init.sql`, `As of 2026-08-26` — so the marker branch remains the only remedy for SQL on disk.
-
-**`x db gen` reports what it could not write, and exits 0.** `GeneratedMigration.unrendered` reached
-the committed `.sql` as a `-- UNRENDERED` comment and nothing else read it; `db-generate.ts` now
-carries it on every branch (a REQUIRED field, so forgetting to project it is a type error) and
-`cmd-db.ts` prints the count plus each entry's own remedy and carries the list under
-`data.unrendered`. Not a non-zero exit: `x db gen` is the `fix:` on `X_DB_DRIFT` and four other
-shipped errors, and a fix that always exits 1 is not an instruction — the `x i18n add fr` failure,
-repeated. The red belongs at the gate, and the `drift` step reads the SAME list to decide that
-`x db gen` is not the fix it should be handing out.
-
-The *source* half is a different question with a different answer: `checkSourceDrift` hashes the
-entity source against what `x db gen` recorded, answers the same before and after a migration, and
-opens nothing — which is what lets the gate run it in a CI with no database. It stays on `x verify`
-and `x doctor` and is deliberately **not** repeated on `x db migrate`; two reporters of one
-condition is the duplication this package's own rule forbids. Both were called `checkDrift` until
-1.2.0, and the one that was wired everywhere was the one that cannot see a column added by hand.
-
-Generation opens no database. It diffs `describeEntities()` against `declaredSchema(readMigrations(root))`
-— the snapshot the newest migration wrote down — so `x db gen` answers the same in CI, on a laptop
-with nothing running, and against a database three migrations behind. An app whose modules will not
-load generates **nothing**: a short registry is indistinguishable from deleted entities, and the
-diff would be a DROP nobody asked for.
-
-**An empty diff re-records the `.hash` sidecar, and that is what makes `X_DB_DRIFT` followable.**
-The hash `checkSourceDrift` compares covers every non-test file under `packages/db/src` — a seed, a
-helper, a decorator — not only the ones that imply DDL, and narrowing that glob would trade a loud
-error for a silent gap in the one check that catches "entities changed and no migration was
-generated". So detection stays broad and the REMEDY carries the weight: `x db gen "describe the
-change"` — the exact `fix:` the error hands out — records the current hash against the newest
-migration when the diff is empty, instead of writing nothing and leaving the gate red forever with
-hand-editing a generated file as the only way out. `GeneratedFiles.outcome` is the four things a run
-can be — `generated`, `hash-recorded`, `unchanged`, `blocked` — and `runGen` projects it onto
-`--json` on **every** branch: reporting `hash-recorded` as `generated` would name a migration nobody
-can apply, and reporting it as `unchanged` would hide a file this command wrote. That second one
-shipped: the no-migration branch hardcoded `data: { migration: null, files: [] }`, so the run that
-wrote the sidecar reported writing nothing to the machine reading the output.
-
-Nothing is masked, and the branch proves it rather than promising it: `loadApp` reported no findings
-(the registry is whole, never short), `declaredSchema` returned a real snapshot (`X_MIGRATION_SNAPSHOT_MISSING`
-otherwise), and the emptiness is `generateMigration`'s own verdict — the same call the written path
-takes. A migration with no migration id to record against writes nothing, which is the
-`x new --no-example` case: an entity against zero migrations is `create table` for all of it and
-never an empty diff. `reconcileSchemaHash` also declines to write when an OLDER migration already
-recorded the hash, because `checkSourceDrift` already answers clean there and restamping the newest
-sidecar would claim it produced a schema it did not — one predicate, `isRecorded`, read by both.
-
-One migration is one file, split by a lone `-- down` line. `<id>.down.sql` is a pre-1.2.0
-hand-written layout and `readMigrations` skips it — read as a migration it sorts next to its own
-`up` and drops every table the pair exists to reverse.
-
-## `x dev` boots the app; it does not simulate one
-
-| File | Job |
-|---|---|
-| `api-routes.ts` | the app's API over HTTP: every registered action AND every registered query |
-| `dev-services.ts` | resolve which service each binding points at — embedded or external |
-| `dev-queue.ts` | the db + queue pair alone, and the one place that takes every ambient accessor back |
-| `dev-runtime.ts` | start the rest on top of it and install the remaining accessors (storage, mail, transport) |
-| `dev-cache.ts` | which cache tiers this process reads through, and the cross-instance invalidation hop |
-| `dev-purge.ts` | the hourly retention sweep: which framework tables this boot owns, the `purge()` job over them and the `task` that fires it |
-| `dev-notify-retention.ts` | `notify.inboxReadRetentionMs` / `inboxUnreadRetentionMs` off the app's own `app.config.ts` — the sibling of `loadSignInPath` and `loadCacheTiers`, because `startServices` holds no `AppConfig` |
-| `dev-sync.ts` | the `sync` role: its live-query registry, who is dialling it, and the socket it owns |
+| `serve.ts` / `serve-boot.ts` / `serve-entry.ts` / `serve-env.ts` | the production entry: roles from `ROLE`, bindings from env, `ROLE=migrate` = `x db migrate` |
+| `cmd-dev.ts` / `dev-route-table.ts` | `x dev`: every role in one process, `/_x`, the watcher |
+| `runtime-bindings.ts` | which service each binding points at (embedded or external); events follow `realtime.transport` / `urlEnv` |
+| `runtime-queue.ts` / `runtime-services.ts` | the db + queue pair; everything else and every ambient accessor |
+| `runtime-jobs.ts` / `runtime-realtime.ts` / `runtime-notify-retention.ts` / `runtime-cache.ts` / `runtime-purge.ts` / `runtime-replica.ts` | `app.config.ts` sections the boot obeys, and what each wires |
+| `role-start.ts` / `role-start-types.ts` / `role-realtime.ts` | `--role` selection and start/stop for `web`, `sync`, `worker`, `scheduler`; `realtime.enabled: false` drops `sync` and `replicator` |
+| `role-sync.ts` / `role-replicator.ts` / `runtime-live-feed.ts` | the sync node, the change feed |
+| `runtime-render.ts` / `runtime-assets.ts` / `runtime-storage.ts` / `runtime-hooks.ts` / `api-routes.ts` | the HTTP surface: pages, `/icons` + `/media`, `/_storage`, authz, the app's API |
 | `runtime-overrides.ts` | the one field a host hands the framework a driver through |
-| `sync-authenticator.ts` | the app's HTTP authenticator, seen as the sync node's |
-| `otlp-export.ts` | the exporters `OTEL_EXPORTER_OTLP_ENDPOINT` switches on, and their drain hooks |
-| `dev-render.ts` | one HTTP route per registered `route`, through render's own mode function |
-| `style-csp.ts` | the `style-src` sha256 of every inline `<style>` the web role **still** serves — the app's own surface CSS is a file under `/styles/` (`style-bundle.ts`) admitted by `'self'`, so a production boot extends the directive with nothing |
-| `script-csp.ts` | the `script-src` sha256 of every inline `<script>` it serves — the hydration runtime, from `@ultimat3/render`'s own `HYDRATE_RUNTIME_BODIES` |
-| `dev-assets.ts` | the image pipeline's only HTTP surface: `/icons/*` and `/media/*` |
-| `favicon.ts` | `/favicon.ico`: the app's own file, and the bytes the framework answers with when there is none |
-| `dev-hooks.ts` | the pipeline's `authorize` seam, decided from the app's own `Policy` objects |
-| `dev-replica.ts` | which boot gets a standby, and the one middleware frame that opens the read scope |
-| `dev-replicator.ts` | the `replicator` role: the feed selected, locked and pumped — and `replicatedRelations()`, the entity TABLES it filters on |
-| `dev-roles.ts` | `--role` selection plus start/stop for `web`, `sync`, `worker`, `scheduler` |
-| `dev-dashboard.ts` | the `DevSources` hooks only this process can answer, and the two CLI panels |
-| `dev-traces.ts` | core's spans → the `/_x` timeline's request traces |
-| `dev-n-plus-one.ts` | statement shapes counted per request, and the ones that repeat past the threshold |
-| `statement-loop.ts` | one verdict → the finding, the panel fact, the overlay notice and the log line |
-| `dev-policy.ts` | which actors to ask about, and which capability each policy gates |
-| `cmd-dev.ts` | boot order, mounting `/_x`, installing the span exporter, the file watcher |
-| `dev-watch.ts` | which paths under the app root `x dev` may not watch: the app's own `.gitignore` (`gitignore.ts`) plus a floor of five directory names an ignore file cannot be relied on to carry — `.git`, `.x`, `node_modules`, `.personal`, `.claude` — every one of them dotted or an install, matched as a path SEGMENT at any depth |
-| `dev-watch-tree.ts` | the watch SET: one `watch(dir, { recursive: false })` per ADMITTED directory, a new directory picked up on `rename`, a removed one giving its descriptor back, and the 30ms trailing debounce |
-| `dev-reload.ts` | one rebuild at a time — a tick arriving mid-build coalesces into ONE trailing rebuild, for the newest file |
-| `gitignore.ts` | what git ignores, as data: parse, the ancestor chain up to the repository, and last-match-wins |
-| `path-segments.ts` | `hasPathSegment` — a directory of that exact name, never a substring of one |
-| `style-bundle.ts` / `style-routes.ts` | a surface's CSS as one content-hashed file under `/styles/`, served `immutable` — `island-bundle.ts` / `island-routes.ts`' shape one asset over. It was an inline `<style>` until 2026-09-06: 156,738 bytes, identical on every page, inside a `private, no-store` document. The URL is the hash alone, no surface in the name: a surface is not a property of the bytes, and an app whose only CSS is its global layer would otherwise write three identical files into its static export and three entries into a precache manifest that has a budget |
-| `mcp-host.ts` | the `DevCapabilities` half of `@ultimat3/mcp`'s `DevHost` — db, tests, logs, verify |
-| `mcp-db-target.ts` | which database the host is pointed at: whether it is a branch, and whether it is production |
-| `mcp-errors.ts` | `errors.explain`: one runnable command per code, typed over `CliErrorCode` |
-| `error-catalog.ts` | imports every `@ultimat3/*` package so `x errors` answers for codes no command loads |
-| `mcp-test-output.ts` | reading `bun test`'s own summary back into a `TestRun` |
-| `cmd-mcp.ts` | `x mcp serve`: the two transports, and the local developer's caller |
-
-**The watch set is a REGISTRATION decision, not a filter, `As of 2026-09-06`.** `watch(root, {
-recursive: true })` takes one inotify descriptor per directory in the tree — measured on `x dev`
-against `examples/dummy`: **110 descriptors, 39 of them (35%) under `.x/` and `node_modules/`**, and
-on a monorepo root **1901, of which 1490 (78%) were `.git/` and `node_modules/`**, where one
-`git status` delivered 5 `.git/index` events into the JS callback. `isIgnoredPath` answered
-correctly every time and answered too late: the kernel queue entry, the callback and the slot out of
-`max_user_watches` (8192 on many distributions) were already spent. Bun 1.4.0's `fs.watch` has no
-ignore option, so `dev-watch-tree.ts` walks the root itself and registers one non-recursive watcher
-per admitted directory, pruning at descent.
+| `script-csp.ts` / `style-csp.ts` / `style-bundle.ts` / `page-sync.ts` / `worker-bundle.ts` | CSP hashes, the CSS file, the page's sync target and worker |
+| `island-bundle.ts` / `island-store.ts` / `island-realtime.ts` / `solid-loader.ts` | islands: one `Bun.build` each, source-addressed; `x build --target docker` writes a verified store the container loads |
+| `dev-*.ts` | `x dev` only: dashboard sources, traces, the N+1 ledger, the watcher, the reload, the lock, the port |
 
-**And the ignore set is the app's own `.gitignore`.** Seven hand-listed directory names were wrong
-in both directions. Nothing read the ignore file, so `touch tsconfig.tsbuildinfo` — the file every
-`bun run typecheck` rewrites, named by `x new`'s own scaffolded `.gitignore` — logged
-`reloaded tsconfig.tsbuildinfo in 113ms`, a full `appManifest()` plus `buildIslands()`; on the
-framework root 54 git-ignored directories were unfiltered. And `dist` and `coverage` were matched at
-ANY depth, so an app's own `/dist` or `/coverage` ROUTE never reloaded — silently, which the file's
-own header calls worse than a spurious rebuild. `gitignore.ts` reads it with git's own anchoring
-(unanchored at any depth, a leading `/` or an inner slash where it is written, `!` re-including,
-a trailing `/` directory-only) and walks ANCESTOR ignore files up to the directory holding `.git` —
-`examples/dummy` carries none of its own and every rule about it lives in the repository root's. The
-file is re-read, and the whole watch set re-walked, on any write naming `.gitignore`; nothing ever
-spawns `git check-ignore`. `x new`'s scaffold writes `/dist/` and `/coverage/` **root-anchored** for
-this reason, plus `packages/*/dist/`. It is `fix-path.ts`'s parser, lifted: two readers of one file
-are two answers to what an app committed.
-
-**A watcher event carries no filename when the WATCHED directory itself moves.** Bun's recursive
-watcher delivers `undefined` — not `null` — on `mv myapp myapp2`, a re-clone or a volume remount,
-and `isIgnoredPath(undefined)` threw a `TypeError` inside an fs callback, outside any `try`, with no
-`uncaughtException` handler: `x dev` died with a stack trace. The listener is total over
-`string | Buffer | null | undefined` and logs `dev.watch.unnamed_event` once.
-
-**The reload has an in-flight guard, and it is the state that needed it.** A 45ms drip — a slow
-`git checkout`, a formatter walking files, `x db gen` — measured **40 reloads for 40 files**, each
-launching `Promise.all([appManifest, buildIslands])` while the previous still ran and assigning
-`state.manifest` / `state.islands` in COMPLETION order, so a slower earlier tick could land on top
-of a newer one. `coalesceReloads` (`dev-reload.ts`) keeps the LAST tick that arrived during a
-rebuild and starts exactly one more.
-
-`api-routes.ts` is the app's own API surface, composed **once** and mounted by both `cmd-dev.ts`
-and `serve.ts`: `listActions().map(toRoute)` from `@ultimat3/action` plus
-`listQueries().map(toQueryRoute)` from `@ultimat3/query`. Two lists is how `query.client()`
-shipped deriving `/_x/query/<kebab>` against a route neither file mounted — a typed read that
-compiled everywhere and 404'd everywhere — and a surface that answers in `x dev` and not in the
-container is the same failure one release later. It reads the registries at call time, never at
-import: importing the app IS the registration, and it happens after this module loads.
-
-`startWeb` warns when the route table declares `auth: 'required'` and the app configured no
-authenticator: `hooks.authenticate` is the only place an actor can come from, so such a process
-boots clean, reports healthy, and refuses every valid session. A warning and not a throw, because
-`x new` scaffolds guarded routes before it scaffolds an authenticator.
-
-The roles live in `@ultimat3/core` (`ROLES`, `isRole`), never in a second list here. A dev-only
-driver, a dev-only authorizer or a dev-only queue is the bug this design exists to prevent — the
-only thing dev changes is which driver is behind an interface.
-
-### `HOST` is the interface, read the way `PORT` is
-
-`serve.ts`'s `hostnameFromEnv` — `HOST`, trimmed, empty is `0.0.0.0` — and `ServeOptions.hostname`
-overrides it as `port` overrides `PORT`; `containerBinding(env, hostname)` is the one `WebBinding`
-`serveApp` hands `startRoles`, so `web`, `sync` and the metrics endpoint bind the same interface.
-Before 2026-09-07 `CONTAINER_BINDING` was the only production binding and an app whose auth mode
-admits one implicit actor without a login — which must refuse a public interface — could not run in
-a container at all. A loopback bind in a container is unreachable through `-p`; the wiki row says
-where it IS reachable. Not `HOSTNAME`: Docker sets that to the container id.
-
-### `RuntimeOverrides` is the only way to hand the framework a driver
-
-`ServeOptions` was `{ root, env, role?, port?, metricsPort? }`, so the ONLY way an app could
-install a driver was an ambient setter at module scope — and `loadApp` imports the app's modules
-*after* `startServices` has captured its own. The slot moved and the capture did not: every
-`handle.enqueue()` went to the app's queue while the worker claimed from Postgres, and `/_x` read
-the ambient one, so the dashboard agreed with the enqueue side and disagreed with reality.
-
-Every field REPLACES the env-selected default rather than sitting beside it — `overrides?.x ?? <the
-env switch>`, one expression, one answer (axiom 1). A field nothing consumes is not there: the
-entity `Driver` in particular, because `@ultimat3/entity` exposes no installer for one
-(`database(entities, { driver })` is the app's own call), and a slot the boot cannot honour is the
-class of defect this seam exists to end.
-
-**The split is refused, not reconciled.** `assertOneJobDriver` runs first in `startRoles` and
-throws `X_RUNTIME_DRIVER_SPLIT` when `jobDriver()` is not the object this process serves. Reading
-through the accessor instead would make the split invisible rather than impossible — and the app
-would still have installed a driver the boot never saw, with no outbox store bound to it and no
-relay draining it.
-
-### What the boot now calls that nothing called before
-
-| Mechanism | Where | Was |
-|---|---|---|
-| the transactional outbox | `dev-queue.ts` installs the store + facade, `worker` runs the relay | staged rows nothing published |
-| the durable scheduler | `pgSchedulerState` + `createPgLeaseLeader` in `startRoles` | a watermark forgotten on restart, and every replica its own leader |
-| the Postgres event bus | `dev-queue.ts` | `step.waitForEvent` forgot every correlation on restart |
-| the shared idempotency store | `dev-queue.ts` | a retry on another replica charged the card twice |
-| the shared auth limiter | `configureAuthLimiters` in `startServices` | account lockouts counted per POD, so N replicas granted `maxAttempts × N` guesses |
-| the retention sweep | `dev-purge.ts`, declared in `startServices` | three `purgeExpired()` with no caller — every row `x_idempotency`, `x_rate_limit` and `x_auth_*` ever took was kept |
-| the cache tiers | `dev-cache.ts` | only the CDN tier was registered; memo, LRU and Redis had zero callers |
-| WebSocket authentication | `dev-sync.ts` | `actorId: null` on every socket — realtime was single-tenant by wiring |
-| OTLP export | `otlp-export.ts` | the chart set the variable and no code read it |
-
-`createPgLeaseLeader`, never `createPgLeader`: the latter's `pg_try_advisory_lock` is
-session-scoped and the grant dies when the connection returns to the pool, so every node reads
-itself as leader and a rolling update double-fires every task.
-
-The relay runs on `worker` and only `worker` — the role that exists wherever jobs run at all.
-Duplicating it is safe — the claim is a **lease** taken in the statement that locks the row
-(`@ultimat3/jobs`' `outbox-pg.ts`, fenced on `claimed_by`), so two relays never hold one batch —
-but pointless. The idempotency key is not the reason and never was: its conflict target is a
-partial index over live states, so it collapses a repeat only while the first job is still live.
-
-`SQL_IDEMPOTENCY_TABLE` is applied beside `SQL_JOBS_TABLE`, and the store is installed by the boot
-rather than by the app, even though `@ultimat3/action` documents
-`postgresIdempotencyStore({ executor: Bun.sql })`: **`Bun.sql` has no `.query(text, values)`** — it
-is a tagged template whose positional form is `unsafe` — so that line does not satisfy `PgExecutor`,
-and a second executor would open a second pool against a URL this boot already resolved. The app
-owes only the declaration, `configureIdempotency({ scope: 'shared' })`, which `x new` names in
-`apps/web/server.ts`.
-
-The per-TENANT subscription cap is deliberately unset, and **both halves of it are**:
-`assertCapacity` returns early unless `maxPerTenant` AND `tenantOf` are given, so passing one arms
-nothing — and no default is defensible when one tenant is a person and the next is five thousand
-seats. The per-socket 128 stands because a socket is one browser tab.
-
-**The change feed is filtered by TABLE, never by entity name**, `As of 2026-08-26`.
-`replicatedRelations()` (`dev-replicator.ts`) is the one projection, and both of its readers are
-catalog readers: `PgReplicationStream` keeps a change only when `#entities.has(relation.name)` and a
-pgoutput Relation message names the table, while `warnPartialIdentity` matches the same list against
-`pg_class.relname`. An entity NAME is the framework's own registry key — a cache tag, a policy and
-`x entities describe` are all keyed by it — and `entity('user', { table: 'users' })` makes the two
-different strings. It passed `.name`, so a renamed table matched on neither side: **every change
-skipped** and a replica-identity warning that could never fire, with no error anywhere. Invisible to
-every fixture in the tree, because `table` defaults to the name verbatim and all six entities in
-`examples/dummy` have `name === table` — `dev-replicator.test.ts` uses `billingAccount` on
-`billing_accounts` for exactly that reason, and proves the value through the real call chain:
-`assertIdentifier` refuses `billingAccount` before any connection and accepts `billing_accounts`.
-
-`trustProxy` is read from `TRUSTED_PROXY_HOPS` in `startWeb`, the way `PORT` and `ROLE` are read: it
-is a fact about the deployment, not an app config choice, and one image runs behind an ingress in
-one cluster and behind nothing on a laptop. Without it `ctx.ip` is the ingress's socket address on
-every request, so the limiter keys the whole fleet's anonymous traffic into one bucket.
-
-### The document carries the page's client scope — on private documents only
-
-`dev-render.ts` puts `@ultimat3/render`'s `clientScopeTag(clientScopeOf(ctx.actor))` (`@ultimat3/auth`) in the head of a
-gated `ssr` page and every `stream` — the documents whose own headers say `private`
-(`documentCarriesScope`). A shareable document carries none, because a CDN would hand one visitor's
-scope to the next. `dev-render-scope.test.ts` drives `static`, `isr`, `ssr` (gated and not) and `stream` over the real pipeline. There is
-no island bootstrap: the page client is created lazily by the first transport call or realtime hook
-(plan 101, decided 2026-09-22; `island-bundle.ts`'s header records what an eager one cost).
-
-### The page's sync target is the framework's, and so is the worker that hosts the socket
-
-`page-sync.ts` is ONE call `cmd-dev.ts` and `serve.ts` both make (plan 101 slice 11, `As of
-2026-09-22`), so the two boots cannot serve different targets:
+### Build and data
 
 | File | Job |
 |---|---|
-| `sync-url.ts` | `syncUrlFrom(env)`: `SYNC_URL` verbatim (must be `ws:`/`wss:`, else `X_CONFIG_INVALID` at boot), otherwise the same-origin `SYNC_PATH` — `/_x/sync`, which `x dev`, a combined-role container and the chart's ingress all serve. Never a derived neighbouring port: behind an ingress that is a URL nothing publishes. No app owns a `sync-url.ts` any more |
-| `worker-bundle.ts` | `@ultimat3/realtime/sync-worker`, resolved from the APP root, built as ONE classic-script (`iife`) browser bundle, source-addressed with `island-bundle.ts`'s `graphHash`, served `immutable` at `/_x/sync-worker/<hash>.js`. `undefined` when the app cannot resolve it — no realtime means no socket to share, and the tab-side host falls back in-page. Built at boot only: it is framework code, and a new URL per deploy is what keeps an old tab on the worker it started with. The SAME builder makes `@ultimat3/realtime/boot` at `/_x/page-boot/<hash>.js`: the disk restore and the outbox, once per page instead of in every island (a `useRecord` island 34.8 → 19.4 kB, `examples/dummy`'s `likes-badge` 48.6 → 32.9 kB) |
-| `dev-route-table.ts` | `x dev`'s route table in mount order, and the theme, error-page styles and MCP path it resolved on the way — split from `cmd-dev.ts` at its 500-line ceiling. It is where `pageSync` is called on the dev side |
-| `page-sync.ts` → `persisted` | `@ultimat3/entity`'s `persistedRecordTypes`, read per render, passed as `DocumentOptions.persisted` by both boots: render's `clientPersistTags` puts `ultimate-persist` beside the scope tag and ONLY there — persistence is per principal, so a shareable document names none |
-| `dev-render.ts` | `DocumentOptions.sync` → render's `clientSyncTags`: `ultimate-sync`, `ultimate-build`, `ultimate-sync-worker` on EVERY document (principal-free, unlike the scope tag). The page boot's `<script defer>` (render's `clientBootTags`) is rendered after the body, only when the document carries the SCOPE tag (restoring and replaying are per principal) AND an island this render emitted reaches `@ultimat3/realtime` (`island-realtime.ts` records the answer every island build computes; a page whose islands never touch a record — `examples/dummy`'s settings — pays nothing). `dev-render-scope.test.ts`. Both framework scripts resolve realtime from the root, then from `apps/*` — a workspace app's realtime is `apps/web`'s dependency, and resolving from the root alone silently built no worker and no boot for `examples/dummy`. The static export carries none — it has no sync node |
-
-### Realtime is installed FOR the author, only where it is used
-
-`island-realtime.ts` (plan 101 slice 14, `As of 2026-09-22`): an island whose own import graph
-reaches `@ultimat3/realtime` — walked with `live-routes.ts`'s `firstInGraph`, relative specifiers
-only, the transpiler reading re-exports and erasing `import type` — is built from a virtual entry
-that calls `installRealtime({ signal: createSignal })` with that bundle's solid-js before the
-island's module body runs. Every other island is built from its own file, byte for byte. +103 B on
-a Solid island reading `useConnection`, +0 elsewhere. A PACKAGE importing realtime for an island is
-the walk's blind spot, and a hook there throws `X_REALTIME_UNINSTALLED` by name.
-
-### `x verify` runs the static steps beside the serial suites
-
-`verify-run.ts`'s `BESIDE_SERIAL_SUITES` — `lint`, `boundaries`, `filesize`, `package-shape`,
-`errors` — start when `live` does and are joined before the first step after `eval` (DX ledger #14).
-They read the tree and write nothing a later step reads; `typecheck` stays first and alone, `unit`
-alone. The table, `--json` and every step name keep the declared order; `data.durationMs` is WALL
-time now, not the sum of step times. Measured locally on the framework root, 12 cores, one run
-each, `As of 2026-09-22`: **395 s → 270 s** wall. `verify-run-overlap.test.ts` pins both halves.
+| `cmd-build.ts` / `image-prepare.ts` | `x build`: static gate first; docker stamps `BUILD_ID` and writes the island store |
+| `prerender.ts` / `measure-scope.ts` / `static-report.ts` | the static export; routes rendered only to weigh run inside a request as core's `measurementActor()`, with the app's API answered in process (`withInProcessFetch`) |
+| `sw-artifacts.ts` / `pwa-artifacts.ts` / `favicon.ts` | the service worker, the web manifest, `/favicon.ico` |
+| `cmd-db.ts` / `migrations.ts` / `db-generate.ts` / `db-branch.ts` / `db-seed.ts` / `db-backfill.ts` / `db-subscribes.ts` / `db-accept-created.ts` | one migration engine for `x db` and `ROLE=migrate` |
 
-### A browser-only read in a module no island imports is `X_LIVE_ROUTE_NO_ISLAND`
-
-`live-routes.ts`, `As of 2026-09-22`: the rule walks each route's SERVER graph (the page's relative
-imports — an island is a `src` string, never an import) and reports every module there that reads
-`useQuery`, `useConnection`, `useMutation`, `useMutationQueue`, `useRecord`, `useChannel` **or
-`hasPageSocket`**, unless some island's own graph imports that module too. Once per module, however
-many routes reach it. `hasPageSocket()` was an EXEMPTION until this date, on the argument that a
-module asking had written its fallback; on the server it answers false every time, so a guarded
-module no browser runs renders nothing forever — `examples/dummy`'s update banner, in a layout no
-island imported, never showed "A new version is ready.". The fix line starts "move it into an
-island".
-
-### A registered code nothing throws must say so
-
-`error-unthrown.ts`'s `checkErrorCodesThrown(root, page)` (DX ledger #9, `X_ERROR_CODE_UNTHROWN`):
-a code a package registry names, used nowhere else in shipped `packages/*/src` — not at a `code:`,
-not as a fallback literal, not through a table member something reads — is reported unless its
-reference row says `thrown by nothing` / `not thrown` or sits under `## Reserved codes`. The fix is
-the row, never the registration: a shipped code is stable forever. A host check, like the other
-reference-page rules — in a generated app every framework code would read as unthrown. Its limit:
-an exported class holding `code: 'X_…'` counts as a thrower whether or not anything constructs it,
-which is why `X_RPC_FAILED`'s `RpcFailedError` is not reported.
-
-### `island-bundle.ts` is the bundler half of `hydrate`
-
-`@ultimat3/render` shipped `island()`, the collector, `emitIslandAttributes`, `hydrateRuntime`,
-`RouteEntry.islands` and `routeJsBytes` — and **nothing constructed or populated any of them**.
-`hydrate` was a documented capability with no implementation, to the point that `render-static.ts`
-told authors to "move the request-dependent part into an island", naming a mechanism the framework
-could not express. This package is the half that can see a file on disk, so it is the half that was
-missing.
-
-| File | Job |
-|---|---|
-| `island-bundle.ts` | discover `*.island.tsx`, build each as its own entry point, hash it, resolve a page's specifier to its URL |
-| `island-solid-dedupe.ts` | the plugin installed FIRST: every `solid-js` specifier in an island's graph resolves to the APP's copy. `Bun.build` resolves from a module's real path, so a package reached through a symlink (`file:` overrides, `bun link`) brought its own `solid-js` — the scaffold's theme toggle shipped two runtimes under CI's own links, 62,463 B against 50,042 B with one (issue #490), and two runtimes are two reactive graphs |
-| `island-routes.ts` | serve those chunks, at `ISLAND_BASE_PATH`, immutable |
-| `dev-render.ts` | one collector **per render**, and `hydrateRuntime` after the body |
-| `prerender.ts` | build first, write the chunks into the export, then measure |
-| `budgets.ts` | `measureDocumentJs` weighs `data-x-entry` as well as `<script src>` |
-
-**A stats row is keyed by the route's DECLARED path, and holds its heaviest page**
-(`As of 2026-08-23`). `checkBudgets` looks a route up by `route.url` off the manifest, which is the
-pattern (`/blog/:slug`), and `prerenderSite` pushed `artifact.path` — the filled one
-(`/blog/hello`). So no dynamic static route had ever been weighed: each was `X_BUDGET_UNMEASURED`
-and `X_BUDGET_EXCEEDED` could not fire for the whole class. The heaviest page and not the first,
-because a budget is a ceiling and the page that breaks it is the one the route answers for; the
-report's `emitted` list still names every filled path.
-
-**Both halves of the CSP are computed at boot, `As of 2026-08-23`.** `style-csp.ts` was alone, and
-the hydration runtime is emitted INLINE in every document carrying an island — so with
-`script-src 'self' 'wasm-unsafe-eval'` no island booted in any container. `x dev` sends the policy
-report-only (`dev: true`), which is exactly why nobody saw it: the page hydrated on a laptop and
-never in the image. `startWeb` extends both directives; the property is pinned end to end by
-`dev-roles-script-csp.test.ts`, which parses a served document, hashes every executable inline
-script in it and asserts the response's own `script-src` names each one — with `dev: false`, the
-only mode in which the policy can block anything.
-
-**One `Bun.build` per island, never one call with N entry points**, and `splitting: false`. The
-island's `src` is a string, so no import edge reaches it and the page's graph stays the page's
-(axiom 6) — a shared chunk would put that number back behind a graph walk, and the budget compares
-against bytes. Two islands that both import the same helper each carry a copy; that is the honest
-number for what booting either one costs.
-
-**The chunk URL is SOURCE-addressed, not byte-addressed, `As of 2026-09-06`.** `graphHash` hashes
-the build's inputs — the source map's `sourcesContent`, sorted, plus the entry's app-relative path,
-the framework version and `Bun.version` — with render's own `contentHash`, the function that already
-stamps an ETag and a precache revision. Hashing the OUTPUT is what it did, and `Bun.build` is not
-byte-deterministic under `minify`: measured on 1.4.0, one entry point, no source file touched, a
-131,589-byte island alternated between two outputs of identical length differing only in minified
-identifier names, roughly one build in ten. The URL then flapped — ten names in ten minutes in
-ai-maxxing — so the service worker precached a chunk that 404ed and the `immutable` cache never hit.
-The cost of the alternative was measured and refused: `minify: { identifiers: false }` IS
-deterministic and is +47% raw, +20% gzipped, on every island of every app. `sourcemap: 'external'`
-pays for the input list (277ms against 276ms) and its `//# debugId=` line is stripped, so the
-shipped bytes are unchanged. Two processes can therefore serve two byte strings at one URL — the
-same program under different local names — and a per-file cache keeps ONE process serving one.
-Delete `graphHash` the day `Bun.build` is deterministic.
-
-**`x dev`, the container and the static export all mount the same table.** `serve.ts` builds the
-islands at boot for the same reason it mounts `apiRoutes()`: a seam that works in dev and not in the
-image is the same failure one release later. `x dev` rebuilds them on the watcher tick — an island
-is the single module this process never imports, so there is no Bun module cache to invalidate —
-and the SAME tick re-imports the route module beside them when its source changed
-(`app-load.ts`'s `reloadRoute`: `<path>?x-reload=<hash>` is the one cache key Bun honours,
-`registerRoute` replaces the entry for the same file, and `dev-render.ts` reads the entry back from
-the table on every request rather than closing over the one it was built from). Until 2026-09-07
-the island was the only reload that took effect, so a save served a new island under an old page —
-the old props, the placeholder the new island renders when they are missing. A route module and
-nothing else: an action, a query or an entity is held by every module that imported it, and no
-re-import can rebind those. `@ultimat3/render`'s loader admits the query
-(`/\.tsx(?:\?[^/]*)?$/`) and strips it before reading the file — anchored on `.tsx$`, the
-re-import fell through to Bun's own JSX loader and every reloaded page died on `__xh`.
-
-**The dev fixture is its own repository** (`.git/HEAD` in `DEV_FIXTURE_FILES`). The framework's root
-`.gitignore` lists `packages/cli/.dev-fixture/`, `devIgnore` honours every ancestor up to a `.git`,
-and so the watcher admitted the fixture root and nothing under it: every run booted the reload path
-and none exercised it. The marker is what lets `cmd-dev.test.ts` save a page and await the tick.
-
-**`app-load.ts` skips `*.island.tsx` deliberately.** It registers no primitive, and importing it
-would put the one module guaranteed to be outside the server's graph inside this process's, where a
-top-level `document` reference takes the whole scan down.
-
-**The budget is charged from the emitted document, and it names the island.** An island's chunk is
-reached by `import()` from inside the hydration runtime, so it is never a `<script src>` — weighing
-script tags alone charged a page for the runtime and never for the code that runtime boots.
-`measureDocumentJs` reads `data-x-entry` as what it is, dedupes it (two instances of one island are
-one module), and `prerenderSite` maps the heaviest URL back through the bundle so
-`X_BUDGET_EXCEEDED` names `apps/web/site/pricing/calculator.island.tsx` and not a hash.
-
-`X_ISLAND_INVALID` is **borrowed** from `@ultimat3/render`, not twinned: "this src cannot become a
-client entry" is what that code already means, and the bundler is simply the half that can see
-whether the file exists. A failed compile is `X_BUILD_FAILED` — an island is a bundle entry point
-like any other, and `Bun.build` *rejects* rather than answering `success: false`, so the catch is
-the real path.
-
-### `dev-assets.ts` is where the image pipeline meets HTTP
-
-Three packages declare what an image is and none of them serves one: `@ultimat3/seo` says what a
-variant URL means (`parseImageQuery`) and produces the bytes (`builtinImageDriver`),
-`@ultimat3/storage` says what a variant is called and where it is cached (`variantKey`), and
-`@ultimat3/pwa` says which icons a web manifest promises (`planIcons`, `BuiltinImagePipeline`).
-Pixels are `@ultimat3/core`'s pipeline, only ever. This file picks two base paths — `ICON_BASE_PATH`
-and `MEDIA_BASE_PATH` — and decides nothing else; a resize, a format table or a second cache key
-here is the drift the split exists to prevent.
-
-**`/media` and `/_storage` are one authz decision, not two.** Both serve objects off the app's only
-disk, so `/media/*key` declares what `dev-storage.ts` declares — `auth: 'required'` +
-`STORAGE_READ_PERMISSION` + `enforcedBy: 'handler'` — and calls the same two functions, in the same
-order: `authorizeStorageRead` then `assertReadableKey`. It shipped `auth: 'public'` with no policy
-and no tenant check while its twin required both, which made every tenant's uploads one URL away in
-production (`serve.ts` mounts it), and `?w=` made it an unauthenticated `put` besides. The tenant
-test lives in ONE function both routes call, and `storage-surfaces.test.ts` pins the pair against
-each other — every case names the verdict absolutely as well as comparing the two, because equality
-alone is satisfied by both surfaces failing open together. Cacheability follows the key, not the
-route: a tenant-scoped key takes `AUTHORIZED_OBJECT_CACHE` (`private, max-age=0`, varying on
-`authorization`/`cookie`), and only a key no tenant owns keeps `immutable`. A genuinely public image
-belongs under `apps/web/site/`, which is a static asset and never touches that disk.
-
-**A variant is CACHED only at a width the framework can mint.** The cache key is built entirely
-from caller-supplied query values, so `?w=1`, `?w=2`, … each wrote a new object to the app's only
-disk, on a route every signed-in tenant may reach for their own keys. `@ultimat3/seo`'s
-`MAX_IMAGE_WIDTH` (8192) bounds that and does not close it. `isMintableWidth` is the bound:
-`DEFAULT_WIDTHS` **plus the source's own intrinsic width**, which is exactly the set `usableWidths`
-puts in a `srcset` — the constant alone would refuse the widest entry of any image whose intrinsic
-width is not one of the eight. Anything outside it is still served; only the `put` is refused, so
-no caller gains a new 4xx. `?q=` is deliberately still unbounded here — the closed set for quality
-is `@ultimat3/seo`'s to declare, not this file's.
-
-**`/favicon.ico` is a mechanism, not a scaffolded file.** Every browser requests it unprompted, the
-scaffold wrote none and neither served surface mounted a route, so a permanent 404 sat in the console
-of every app the framework produces — noise that trains the reader to ignore console errors, which is
-the opposite of what `--json` and an executable `fix:` are for (#272). Two rungs and one path: the
-app's own `apps/web/site/favicon.ico` wins, and `favicon.ts` answers a 32x32 PNG encoded through
-`@ultimat3/core`'s own pipeline when there is none — the same encoder `x new`'s icon goes through, so
-there is no second image format in the tree and no base64 blob nobody can verify. It is deliberately
-NOT derived from `ICON_SOURCE`: resizing the install icon needs `@ultimat3/pwa`'s pipeline and would
-make the answer depend on a file that may be absent, which is a third rung under a mechanism that has
-exactly two. The file is read per REQUEST, so dropping one into a running `x dev` takes effect
-without a restart. It mounts through `assetRoutes`, which is the one route set `serve.ts` and
-`cmd-dev.ts` both compose — a favicon added to one of them alone is a 404 that comes back in
-production only — and `prerenderSite` writes the same bytes into the static export, because an
-artifact served with no process behind it has to carry every byte the browser will ask for.
-
-`ICON_SOURCE` lives here, not in `cmd-doctor.ts`, because this is the module that reads it: the
-diagnostic checks what `x dev` serves, so one constant cannot pass the check and serve nothing.
-It is a **PNG** — core decodes PNG and JPEG only, and the SVG this used to name could never
-become an icon.
-
-The routes mount whether or not the source icon exists, and a missing one is refused with
-`X_PWA_ICON_MISSING` and its fix — a route that silently disappears is a 404 whose meaning an agent
-has to guess. Deliberately **not** also a boot finding: `x doctor` already reports this condition,
-with this code, and two reporters of one condition is the duplication this package's own rule
-forbids. `x dev` owns the runtime half; the diagnostic owns the other.
-
-### `hold.ts` is why a long-running command outlives its own result
-
-`dispatch` renders a `CommandResult` and `bin.ts` exits on the code — so a command whose server is
-still listening when `run` resolves is a command the exit code takes down, between the line that
-announced the url and the first request to it. `x dev` and `x mcp serve --transport http` both did.
-
-The one answer is `CommandResult.hold`: report first, then `dispatch` awaits the hold before the
-exit code. `holdUntilShutdown` installs core's signal handlers (`installSignalHandlers` — until
-this it had no callers anywhere, which is why `cmd-mcp.ts`'s `onShutdown` registration was never
-reached), waits on the **drain's first phase** rather than on a signal list of its own, and
-releases what core's lifecycle never learned about — the embedded Postgres, the worker, the
-watcher — *after* the drain, so an in-flight request still has the database it opened against.
-Ctrl-C is therefore the same three phases production runs, not a kill that leaves `.x/pgdata`
-locked by a process that no longer exists.
-
-**The release runs INSIDE the drain's own deadline, `As of 2026-08-23`, and it is the same
-deadline.** `drain()` ABANDONS a hook that overruns `ShutdownReason.deadlineAt` — the process is
-meant to exit without it — and `release` re-enters the very same teardown one call later:
-`app.stop()` → `startRoles().stop()` → `worker.stop()`, memoised in the package that owns it, so
-awaiting it is awaiting the promise the drain just walked away from. Unbounded, that hung past
-`terminationGracePeriodSeconds` and the kubelet SIGKILLed a process that had already drained
-cleanly. The budget is the hook's own `reason.deadlineAt`, not a stopwatch of ours, so there is one
-number and not two; an overrun is logged as `X_SHUTDOWN_TIMEOUT` and a REJECTION still rejects,
-because `dispatch` awaits the hold inside its own `try`.
-
-**`options.exit` has exactly one caller: `runRole` in `serve.ts`.** `bin.ts` ends in
-`process.exit(code)`, so `x dev` and `x mcp` need nothing; `apps/web/server.ts` — which is what a
-container runs — has no such line, and one non-unref'd interval anywhere in the app then holds an
-event loop with nothing left to do. A function rather than a boolean because `process.exit` inside
-a library is untestable, and the caller is the one that knows.
-
-Commands: `bun test`, `bunx tsc --noEmit -p tsconfig.json`.
-
-## A declared flag with no reader is a promise `x help` makes and nothing keeps
-
-`x deploy --critical` said *"security deploy: forces clients to reload"* and forced nothing: the
-value is written into the plan JSON (`cmd-deploy.ts`) and **no package reads that field**. The
-parser accepts every declared flag, so this is neither a parse error nor a type error — the flag
-worked perfectly and meant nothing, to the operator most likely to be shipping a security patch.
-
-`flag-reads.ts` is the rule that can see the class of defect: **every flag a command declares is
-read by something in the CLI's own source**, as `X_CLI_FLAG_UNREAD`. The four global flags are
-excluded — `--json`, `--help`, `--cwd` and `--verbose` are the parser's, read once for every
-command, and a per-command rule would report all thirty declarations of `--json`. The read test is
-deliberately generous: a bare `'name'` literal anywhere outside a `name:`/`short:` spec field
-counts, so a flag echoed only into `--json`, or read through a shared constant, is read. A gate
-that guessed at intent would report findings about working commands.
-
-It is enforced by `flag-reads.test.ts`, in the `unit` step — the same shape `cmd-planned.test.ts`
-and `error-catalog.test.ts` use for a rule about the CLI's own declarations, and the reason its
-`fix:` is a `bun test` line rather than an `x` command: the rule can only ever fire in this repo.
-Promoting it to `x verify`'s `boundaries` host check is one line in `scripts/verify.ts`.
-
-**It does not catch `--critical`, and that is the honest limit.** The flag IS read —
-`flagBool(ctx.args, 'critical')` — and what had no consumer was the plan FIELD, one level below any
-rule over names. Two stronger rules were measured and rejected: "the read must not be a property
-initializer" reports six flags, five of which work (`x db --allow-destructive`, `x jobs --queue`);
-"the summary must match the behaviour" is undecidable. So the flag's summary now says what it does,
-and forcing a reload is **not a thing this framework does**, `As of 2026-08`. `updateSignal`
-had no runtime caller for four majors and 9.0.0 deleted it rather than wiring it: `pwa` is tier 4
-and the two runtimes holding both build ids — `http` (2) and `sync` (3) — are below it, so no
-legal import could ever have reached the function. A deploy command has no channel to a running
-client regardless; the plan is `docker compose up` or `helm upgrade`. What ships is notification:
-`useConnection().updateAvailable` from `@ultimat3/realtime`.
-
-## Planned commands are commands
-
-Every command in `wiki/CLI-Reference.md`'s planned table is in the registry, built from
-`PLANNED_COMMANDS` in `cmd-planned.ts`, and exits `X_NOT_IMPLEMENTED` with a `fix:` naming the
-closest **shipped** command. `X_CLI_UNKNOWN_COMMAND` would say "you typed something that does not
-exist", which is false and sends an agent hunting a typo. `cmd-planned.test.ts` enforces both
-halves: every row is reachable through the parser, and no `fix` points at another planned command.
-
-`PLANNED_SUBCOMMANDS` is the same promise one level down, and `x db studio` is its only entry.
-A subcommand stays in its command's `subcommands` list — the parser reaches it, `x help db` lists
-it — and the owning `run` does `throw plannedSubcommand('db', 'studio')`. Dropping it from the list
-instead would answer `X_CLI_UNKNOWN_SUBCOMMAND`, which is the same lie the table above closes.
-
-## `guards/` is how an app makes its own convention a build error
-
-Axiom 3 says a convention that is not a build error does not exist, and until 1.2.0 the framework
-gave an app no way to create one: `VERIFY_STEP_NAMES` is a closed literal list with no extension
-point. A file in `guards/` closes it.
+### Introspection and tools
 
 | File | Job |
 |---|---|
-| `guards.ts` | what a guard IS, how the directory is read, and what a guard is held to |
-| `templates/guard.ts` | `x g guard <name>` — the emitted rule, its pure half and its test |
-| `cmd-verify.ts` | one line in the `boundaries` step: `guardFindings(ctx.root)` |
-
-**It rides on `boundaries`, and it is not an eighteenth step.** The `HostCheck` contract already
-says the shape — *a host adds findings to a step; it can never add, remove, reorder or skip one* —
-so "green" keeps meaning exactly what it meant, whatever an app writes. `boundaries` is the step
-whose host slot already carries "rules this repo makes about itself that the framework cannot
-know" (the monorepo's tier table arrives through it), and it runs third, before any suite, so a
-convention failure comes back in seconds. `guardFindings` is *typed* as a `HostCheck` and is
-composed by the step rather than registered as one: the slot is `Partial<Record<VerifyStepName,
-HostCheck>>`, one function per step, so an app registering there would evict the framework's own
-tier check — and `verifyCommand.run` passes no `hostChecks` at all, which is why an app-supplied
-check could not have reached the gate through that field in the first place.
-
-**Discovered, never registered.** `guards/*.ts`, minus `*.test.ts`, sorted. Nothing imports a
-guard, nothing lists one, and there is no `defineGuard` to call — a guard that has to announce
-itself is a guard an app can forget to announce, which is the coupling axiom 8's extension model
-rejects. A `*.test.ts` beside a guard is its test: importing it would run a suite inside the gate.
-
-**A guard returns `Finding[]`, so it inherits everything.** `--json`, the step table, the summary
-counts and the exit code are all projections of what it returns (axiom 2); a guard that printed or
-chose an exit code would be a second gate. It never throws for a normal result — a throw is
-`X_GUARD_FAILED`, reported as a finding rather than taking the run down.
-
-**And what it returns is held to the error contract.** `findingProblem` demands an
-`X_SCREAMING_SNAKE` code, a non-empty cause, and a `fix:` that passes `fixProblem` — the *same*
-rule `x verify`'s `errors` step applies to every shipped `fix:` in this repo. It runs on the
-returned value, which is the half a static scan cannot reach: a `fix` assembled at run time has no
-literal to read. Three codes, one per way a guard can fail to be one — `X_GUARD_INVALID` (no
-usable export), `X_GUARD_FAILED` (it threw), `X_GUARD_FINDING_INVALID` (what it returned is not a
-finding). Anything else about a guard is the app's business: no size ceiling, no budget, no rule
-about what it may check.
-
-**The validator may never be the thing that crashes.** `findingProblem` names an offending value
-through `shown()` and not `JSON.stringify` — which refuses a BigInt — and every candidate is read
-inside a `try`, because reading one can throw on its own (a getter that raises, a proxy that
-refuses). A guard returning `[1n]` is `X_GUARD_FINDING_INVALID`, per candidate, so one unreadable
-entry costs its own line and not the real findings beside it. The mechanism whose job is producing
-structured failures handing back a stack trace is the one outcome it exists to prevent.
-
-**`x new` ships NINE guards, `As of 2026-09-08`** — the four below plus five interface rules
-(`semantic-interactive`, `focus-visible`, `image-dimensions`, `animated-layout-property`,
-`island-without-states`), each statically decidable and each carrying a legitimate-lookalike test
-that must NOT be reported. **Two of the original four were broken the whole time and nobody could
-see it**, because no guard had ever run against a real app: `raw-colour` reported all 87 uses of
-`rgb(var(--color-…))` — which IS the token form `_colors.scss` emits, so its own cause line ("a
-value no theme can restate") was false of every one — and `untranslated-string`'s JSX mask
-`/\{[^{}]*\}/g` does not nest, so `{t('k', { org: x })}` lost its inner brace group first and the
-remnant read as prose, flagging every `t()` call with an interpolation object or a template-literal
-key. Both are fixed and both now report zero against `examples/dummy`, which is the first tracked
-app to carry a `guards/` directory at all. Read the count, never this sentence:
-`bun -e "import {scaffoldGuardFiles} from './packages/cli/src/templates/scaffold-guards'; console.log(scaffoldGuardFiles().length)"`.
-
-The scaffolded `AGENTS.md` states nine
-non-negotiables, and five of them used to be prose — each proven green on `x verify`: a hardcoded
-JSX string beside a `t()` call, `color: #ff0000` in a stylesheet whose own scaffolded header called
-it "a lint failure", `toLocaleDateString('en-US')` with no `timeZone`, `t.number` money, and a bare
-`throw new Error` in a repo. Four of the five are now guards the scaffold writes —
-`guard-raw-colour`, `guard-unzoned-date`, `guard-bare-error`, `guard-untranslated-string` — so the
-rule is a build error the day the app is created rather than a sentence an agent may skip. The
-fifth, money-as-float, has **no static signature**; the scaffolded `AGENTS.md` row now points at the
-`MoneyInput` type error that already fires, because shipping a guard that cannot work is worse than
-naming the mechanism that does. Their codes are app codes derived from the guard name, so none of
-them appears in `wiki/Error-Codes.md` or the manifest.
-
-`x g guard <name>` writes `guards/<name>.ts` and its test, and nothing else — no index, no
-registry row, no manifest entry. The emitted rule is the class of failure a guard exists for: a
-migration that adds a `NOT NULL` column with no `DEFAULT` applies cleanly to an empty local
-database and fails on the first production table that already holds rows. The `drift` step reads
-those same files and asks a different question, and a test suite runs against a database the
-statement has never met — which is exactly when an app needs a rule of its own. Its code is
-DERIVED from the guard's name (`guardCode`), never written as a literal: an `X_*` literal in
-framework source is a framework code and `error-catalog.test.ts` requires it to be registered.
-
-That rule is held to a real bar, because it is the worked example every app starts from and a
-demonstration that is wrong on realistic input teaches the wrong shape. Block comments are
-stripped before line comments and both before statements are split, so a commented-out
-`ALTER TABLE` is a note and not a finding that blocks `x verify` over nothing; and `DEFAULT NULL`
-counts as **no** default, because it is one in syntax and none in effect — every existing row still
-takes NULL and still violates `NOT NULL`. Both cases are in the emitted test, which is what proves
-an app's copy still works, and both run through the real seam in `guards.test.ts`.
-
-It is in `FIXTURE_GENERATORS` like the other two, and it is the only generated file that imports
-`@ultimat3/cli` for its types — so the scaffold gate compiling it is what proves a scaffolded app
-can write one at all. The root `tsconfig.json` `x new` scaffolds has no `include`, so `guards/` is
-typechecked there by default; an app whose tsconfig names an explicit `include` list has to add
-`guards/**/*` to it, or its guards compile nowhere.
-
-## Two generators that scaffold something other than a primitive
-
-`x g island <name> [--at <dir>]` writes a **client entry point**, not a component: the filename is
-how the bundler discovers it and `mount` is how the hydration runtime calls it, so the filename,
-the `mount` export and that `mount` RENDERS are what `templates/island.test.ts` pins — it builds
-the emitted entry with `buildIslands` and drives it with `mountIsland`, so a template that
-typechecks and does not mount is a failing test. It runs the mutation too, rather than describing
-it: the same island with `{count()}` replaced by `{0}` must fail the assertion the live one passes.
-`--at` takes the directory directly rather than deriving one, because the caller that cannot guess
-is `X_ISLAND_INVALID` — its cause already holds the exact path a page's `src` resolved to, so its
-`fix:` hands that path straight back.
-
-`x g admin:page <name> --permission <perm> [--at <dir>]` writes an ordinary TSX component and **no
-`defineRoute` call**, deliberately. `@ultimat3/admin`'s `pages:` is the one thing that puts a page in the route
-table and `guardedPage()` is the one thing that decides it; a generator that emitted a route
-declaration would hand back the unguarded second way in that seam exists to close. The emitted test
-asserts the absence. `--permission` defaults to `<name>:read` rather than to nothing, because an
-empty permission list is `X_ADMIN_PAGE_UNGUARDED` at declaration time. `--at` is the same flag
-`x g island` takes and for the same reason — an app's admin is wherever its `defineAdmin` is, which
-no generator can derive, and the hardcoded `apps/admin/src/pages` sent every other layout (the
-demo's is `apps/admin/app/admin`) to `git mv` after every run.
-
-Both are in `FIXTURE_GENERATORS`, so both are compiled by the scaffold gate.
+| `cmd-registries.ts` / `cmd-jobs.ts` / `cmd-tasks.ts` / `cmd-policy.ts` / `cmd-i18n.ts` | project a framework registry; each pairs CLI wiring with a facts module |
+| `cmd-mcp.ts` / `mcp-host.ts` / `mcp-errors.ts` / `mcp-db-target.ts` | `x mcp serve`: 18 tools, two transports |
+| `cmd-shot*.ts` / `cdp-shot-*.ts` / `browser-launcher*.ts` / `island-*` | `x shot` over raw CDP; `verdict.json` names its own blind spots. Not a gate step |
+| `cmd-pr.ts` / `cmd-ci.ts` | GitHub through `gh`, parsed against a schema. Not gate steps |
+| `error-catalog.ts` | imports every `@ultimat3/*` package so `x errors` answers for any code |
 
-Implementing one means deleting its row and adding a real `cmd-<name>.ts` — the summary's
-`(planned)` suffix disappears with it, and `x help` follows automatically.
+## Adding a command
 
-Adding a command: write `cmd-<name>.ts` exporting a `CliCommand`, register it in `registry.ts`,
-add its message keys to `messages.ts`. Help and parsing derive from the spec automatically. A
-command's `run` must be `async`: a synchronous throw escapes every caller that awaits the promise
-the signature promises, `dispatch`'s own error path included.
+Write `cmd-<name>-spec.ts` (the declaration) and `cmd-<name>.ts` (a `CliCommand` whose `spec` is
+that declaration), add one `lazy(<name>Spec, …)` row to `registry.ts`, add its message keys to
+`messages.ts`. Help and parsing derive from the spec. `run` must be `async`.