Skip to content

Error Codes cli

github-actions[bot] edited this page Nov 16, 2026 · 2 revisions

Error codes: @ultimat3/cli

Part of Error codes: every code @ultimat3/cli registers. x errors explain <CODE> --json prints the same row.

Code Means Typical cause Fix
X_ADMIN_RESOURCE_UNWIRED an admin override x g wrote is not in the app's defineAdmin() call x g resource --admin writes the override and lists it under resources: in apps/admin/app/admin/admin.ts; that file is missing or holds no defineAdmin({ … }) call the generator can add to x g resource widget --admin --dry-run --json — lists the files; the finding names the two lines to add to apps/admin/app/admin/admin.ts
X_ADMIN_UNSCANNED a defineAdmin() declaration sits outside the app scan, so the admin is never mounted the admin lives under apps//src/, which no boot imports — the app scan reads apps/*/{site,app,api,shared}/** only git mv apps/admin/src/index.ts apps/admin/app/admin/admin.ts — then repoint its relative imports and x verify --only manifest --json
X_ADVISORY_FLOOR_UNMET a resolved dependency is below its advisory floor bun.lock resolves a package below the first release past its published advisories bun update source-map-js immutable
X_APP_EMPTY an app with an app.config.ts registered no primitive the loader imported nothing — an app whose absolute path contained .test. read every module as a test — so manifest, x db gen, policy and i18n all checked nothing x doctor --json
X_APP_IMPORT_UNRESOLVED an app module imports what does not resolve A module under the app globs imports a package nobody installed, or a relative path with no file behind it. One finding per specifier, however many modules reach it bun add <pkg> — a relative import: edit it in the file the finding names
X_APP_MIGRATIONS_UNAPPLIED a serving role booted over a database missing migrations this build ships this build ships migrations the database has not applied, so serving would fail on the first statement naming a column they add: the migrate step must run first x db migrate --json
X_APP_MODULE_LOAD_FAILED an app module failed to load, so the role refused to serve a partial app a module under apps/* threw on import or on registration in the container boot; serving without it would drop its routes, actions, policies or jobs x manifest --json — names each module that does not load and why; fix it, then restart the role
X_APP_NAME_EMPTY the app name has no letters or digits a name that slugifies to nothing (!!!) names no directory, so x new scaffolded into the current one — and --force then committed the files already there x new my-app --json — a name with letters or digits; it becomes the directory
X_APP_PACKAGE_INVALID the app's package.json has no usable name/version — the manifest never fabricates app@0.0.0, because its version is the compatibility gate a malformed or hand-trimmed package.json bun pm pkg set name=<app> version=0.1.0
X_APP_ROOT_NESTED a second app.config.ts inside the app An app.config.ts under apps/ or packages/ makes that workspace a second app root — its own registry, its own migrations, its own image. One repository is one app: every apps/* workspace boots in the one image, ROLE picks the process, and packages/db/migrations is the one migration owner x verify --only drift --json — after deleting the nested app.config.ts and moving what it configured into the root app.config.ts
X_APP_URL_PORT_MISMATCH APP_URL names a loopback port x dev does not serve APP_URL is a localhost origin whose port is not the one x dev binds (--port, then PORT, then 3000), so OAuth redirects, absolute links and the sync origin point at a server that is not this one export APP_URL=http://localhost:3000
X_ASSET_RETAIN_FAILED Build assets were not retained publishing this build to the retained-asset disk failed x doctor --json
X_ASSET_RETAIN_UNDECLARED A served build keeps no earlier build's assets a web role booted outside development and test with no assets.retain in app.config.ts: across a rolling deploy, or after one, a page can name a stylesheet or island chunk the answering replica 404s edit app.config.ts: add assets: { retain: { disk: 'assets', builds: 3 } }, naming a disk your defineStorage({ disks }) declares that every web pod reads
X_ASSET_VARIANT_UNDECLARED an /assets image variant responsiveImage() never mints ?w=, ?f= or ?q= on a hashed /assets URL names a width, format or quality outside the declared set for that source (usableWidths over DEFAULT_WIDTHS, DEFAULT_FORMATS, no quality), or the file is not a raster the pipeline decodes responsiveImage({ src: asset('assets/hero.png'), width, height, alt }) — no widths/formats override for a site asset; an upload under /media answers any width
X_BACKFILL_SLICE_ENTITY the slice holds no entity a generated backfill can sweep x g backfill --feature writes a sweep over the slice's own scaffolded table (db., its title column); the slice exists and its entity.ts declares other tables, so the generated files would not compile x g job <name> --feature <slice> — then wrap its body in backfill({ source: db., … }) from @ultimat3/jobs
X_BOUNDARY_ADAPTER_IMPORT an app module imports an adapter installer a site/app/api/shared module imports @ultimat3//adapter at runtime export const runtime = { jobs: yourDriver } satisfies RuntimeOverrides; # in apps/web/runtime.ts — name the port your import installed
X_BOUNDARY_APP_TO_API app/ imported api/ at runtime a value import instead of import type use import type, and call the typed client
X_BOUNDARY_LOADER_IMPORT an app module imports a registration loader a site/app/api/shared module imports @ultimat3/action/loader or @ultimat3/query/loader — registerAction(s)/registerQuery(ies) are the boot's, and calling one is a second registration path beside defineApi export const api = defineApi({ actions: [yourActions], queries: [yourQueries] }); — in apps/web/api/index.ts — list the module there, then delete the loader import
X_BOUNDARY_PACKAGE_TO_APP packages/ imported apps/ at runtime A file under packages/ imports a module of an app: a shared package that depends on one app is no longer shared, and the import graph has a cycle no tier names x verify --only boundaries --json — after moving the shared code into the package, or importing in the opposite direction
X_BOUNDARY_ROUTE_TO_DB a route touched the database SQL in a page file x g query <route-name> --feature <slice> when the import resolves into a slice, x g resource <name> when none; then call it from the route
X_BOUNDARY_SERVICE_TO_HTTP a service imported HTTP request awareness inside business logic take the values as arguments so a job can reuse the service
X_BOUNDARY_SHARED_LEAF shared/ imported a surface shared/ is a leaf invert the dependency
X_BOUNDARY_SITE_TO_APP site/ imported app/ the classic transitive import the chain is printed in cause; break it at the named hop
X_BOUNDARY_SURFACE_IMPORT a surface imports one SURFACE_SPECS does not allow an import between surfaces the table does not list move the imported code into shared/ and import it from there — then x verify --only boundaries --json
X_BROWSER_SERVER_BARREL browser-reachable code imports a package's server barrel where the package publishes a browser entry an island's import closure reaches, for example, @ultimat3/entity, whose barrel retains ~1 MB of SQL rendering and @ultimat3/db, while @ultimat3/entity/record is the entry published for a browser (@ultimat3/query → @ultimat3/query/client). The browser entries are derived from each installed manifest's exports (a record, browser or client subpath, packages/cli/src/server-barrels.ts), never listed. Reported by x verify's boundaries step in every app, As of 2026-10 x verify --only boundaries --json — each finding opens with its edit: the import swapped to the browser entry it names (@ultimat3/query/client for @ultimat3/query), or the cut where the island first reaches the barrel
X_BROWSER_TRANSPORT_BYPASS browser-reachable code opens its own connection instead of using the one seam a fetch( call, new WebSocket(, new XMLHttpRequest( or new EventSource( — or the global fetch handed on as a value (rpc({ fetch }), fetch: fetch, const f = window.fetch, make(globalThis.fetch); a property named fetch, a local binding and a type position are not) — in an island or a module one reaches (its import closure, followed name by name through barrels, into the app's own packages/*). Such a request skips the page's record store, the idempotency header and the principal fence. Reported by x verify's boundaries step in every app (As of 2026-10; built in, not a guards/ file, so an app cannot delete it) — there no file may hold one: the three seams are the framework's, inside node_modules, and the walk stops at that boundary. In this repository bun run browser-transport runs the same rule with the seams as files: packages/core/src/client-dispatch.ts for fetch, packages/realtime/src/browser-socket.ts for sockets, packages/storage/src/upload-client.ts for XHR, nothing for EventSource; the service worker's files are exempt. Blind spots, stated: a browser module that is no island, names no seam and is imported by neither; a request made inside an installed package; a computed member (globalThis['fetch']); a bare fetch( in a file that binds a local fetch. A route.ts, a job and a test are server code and never reported x verify --only boundaries --json after replacing the call the finding names: an action → await browserClient.<action>(input) (rpc<Api['actions']> in apps/web/shared/browser-client.ts); a read → useQuery(<QUERY_REF>, input); a socket or SSE → useQuery / useChannel; a file → uploadFile({ file, grant }) from @ultimat3/storage; anything else → clientTransport({ method, url }) from @ultimat3/core/page; a fetch passed as a value → delete it (rpc() and queryClient() send through clientTransport when given none) and move the module that took it onto one of the above
X_BUDGET_PARAMS_UNDECLARED a dynamic route with a budget declares no prerender() paths to weigh it by The budgets step: the build renders an app/ route only to weigh it, and a route with params needs one real path to render prerender: () => [{ <param>: '<a real value>' }] — on the route's defineRoute, then x build --target static
X_BUDGET_UNMEASURED a route declares a budget the build never measured the route is absent from .x/build-stats.json, or the file was written by an earlier measurement rule than this gate's (its measuredBy is not BUILD_STATS_RULES), so its numbers are not this gate's to read. .x/ survives framework upgrades. x verify's budgets step builds when the stats are missing or stale, so inside the gate this means a static build ran and wrote no stats (apps/web/prerender.ts must call prerenderSite()) x build --target static --json && x verify --json
X_BUILD_ENTRY_MISSING the build target's entry file is not in the app an app scaffolded before x new wrote apps/web/server.ts and apps/web/prerender.ts, or one whose docker/Dockerfile was deleted — refused before the builder is spawned, because bun build's own "module not found" names no owner the fix names the file; x new <name> --dry-run --json lists every entry a build needs
X_BUILD_FAILED x build failed a static check or the bundler. For a browser entry the framework builds, the cause names which: an island file, the sync worker or the page boot read cause; the failing step is named. For a framework script: bun build --target browser --format iife <entry>
X_BUILD_OUT_UNSAFE the static export directory is not one a build may empty every static build empties its export directory first, and this one is the app root, an ancestor of it, or an existing non-empty directory that carries no .x-export marker a previous build wrote (the default .x/static is exempt) — --out apps, --out .x (the dev database), a home directory. Nothing is removed x build --target static --out .x/static --json
X_BUN_VERSION Bun is older than the framework floor the runtime is below the floor — x doctor checks the CONSUMER floor (packages/cli/src/app-root.ts), scripts/setup.ts checks the CONTRIBUTOR floor, which tracks CI's pinned series and is higher bun upgrade
X_CATALOG_SLOT_MISMATCH two locales define one key with different interpolation slots a translation added or dropped a slot: the two values interpolate different sets of names, so one locale renders a placeholder the other never had. The sets are compared by name, and their order does not matter x i18n check --json — the finding names the locale, the key and the slots that differ
X_CATALOG_UNTRANSLATED a locale still carries the reference locale's value a value copied from the reference catalog and never translated. A value of 24 characters or less is legitimate — Postly, Free and Blog read the same in every language — and is not reported x i18n check --json — the finding names the locale and the key still carrying the reference value
X_CHART_MISSING x g chart-alerts found no Helm chart to write into the app has no docker/helm/Chart.yaml with a name: it deploys with Compose or outside Kubernetes, or its chart lives elsewhere — and a rule loader outside Kubernetes takes the plain rule groups instead x g chart-alerts --print --json
X_CI_RUN_NOT_FOUND no workflow run for this branch x ci on a branch that has never been pushed, whose runs have aged out, or whose --workflow/--event filter matched nothing (the cause names the filter given) x ci --branch main --json
X_CLIENT_EDITED a generated client file was changed by hand a file x client wrote no longer hashes to the value in its own header, so the next regeneration would silently discard the edit x verify --only drift --json — regenerate with the command the finding names, and keep custom code in a file of your own that wraps the client
X_CLIENT_SPEC_INVALID x client was handed a document that is not OpenAPI 3.0 or 3.1 the file or URL given to --from is not JSON, or is JSON without an openapi field of 3.0.x or 3.1.x x help client --json — then point --from at the OpenAPI 3.0 or 3.1 document itself
X_CLIENT_SPEC_UNSUPPORTED x client met an OpenAPI construct its compiler refuses the source document uses a construct the compiler does not read (the cause names its JSON pointer): not, if/then/else, patternProperties, a non-JSON body, a cookie parameter x help client --json — then rerun with --only naming the tags around the pointer the cause names, or pin a corrected source.json
X_CLIENT_STALE a generated client is older than the document it was compiled from the source document (a vendor's source.json, or the app's openapi.json) changed and the client was not regenerated, so it still calls the old contract x verify --only drift --json — each finding names the line that regenerates its client
X_CLI_BAD_FLAG flag or positional rejected unknown flag, a bad value (--port abc, --workers 4.9 — refused, never coerced), a required positional left out, or a mandatory-subcommand command called bare. A missing positional says so and names it, rather than inventing a flag that does not exist. A well-formed argv whose answer is still no is not this code — a dev-tier seed refused against production is X_SEED_ENVIRONMENT, because a flag code says "you typed it wrong" and sends the reader to x help, which is the wrong instruction there x help <command>. Use that form and not --help on db and mcp — they declare no default subcommand, and the subcommand is resolved before the flag loop, so x db --help raises this same error again. Its fix: said exactly that until 2026-08
X_CLI_FLAG_UNREAD a command declares a flag no code reads the CLI's own declarations held to each other: a FlagSpec the parser accepts and no file under packages/cli/src reads is a promise x help makes with nothing behind it. x deploy --critical said "forces clients to reload" and reached no reader outside the plan JSON. The four global flags are excluded — the parser owns them — and any bare 'name' literal outside a name:/short: spec field counts as a read, so a flag echoed into --json still counts bun test packages/cli/src/flag-reads.test.ts — the finding names the flag and the file to read it in
X_CLI_UNEXPECTED the CLI itself failed a bug, or a broken environment x doctor --json and attach it to an issue
X_CLI_UNKNOWN_COMMAND not a command a typo x help — the suggestion is in fix
X_COVERAGE_BELOW_FLOOR the unit suite covers less of the app than x.verify.json states Line or function coverage of the app's own source — every .ts/.tsx under apps/ and packages/, a file no unit test loads counted at 0% — is under the coverage floor in x.verify.json. A test was deleted, or source landed without one. The finding names the measured and required numbers and the ten files that lose the most lines x verify --only unit --json — names the ten files losing the most lines; cover the worst with a test beside it
X_COVERAGE_FLOOR_STALE the app now covers more than the floor in x.verify.json states A floor under 95 is more than 1.5 points below what the unit suite measures. The floor only rises: left alone it would let the next regression fall back to a number the app left behind x verify --only unit --json — the finding carries the measured numbers; raise "coverage" in x.verify.json to them
X_COVERAGE_FLOOR_UNSTATED x.verify.json states no coverage floor, or one under 95 with no reason x.verify.json has no coverage: { lines, funcs }, so the gate has no floor to hold the unit suite to — an app is never held to a default it did not write. Also raised for a stated floor under 95 on either number that carries no why x verify --only unit --json — the finding carries the measured numbers and the exact "coverage" line to add to x.verify.json
X_DB_BRANCH_FAILED x db branch refused, or failed for a reason no framework error claimed two shapes under one code. A deliberate refusal: delete aimed at a name x db branch list does not show, whose cause names the exact database or data directory it would have touched, so the refusal is checkable rather than assertable. Or an unclaimed failure of any of the three verbs — the clone connection refused, the data directory unwritable. X_BRANCH_EXISTS (the name is taken) and X_SQL_UNSAFE (the name is not [a-z0-9_-]+) reach you as themselves for the refusal, x db branch list --json — the name is not in the set, and only what that lists can be deleted. Otherwise read cause, then x doctor --json
X_DB_GEN_FAILED / X_DB_MIGRATE_FAILED the x db step failed for a reason no framework error claimed a write the filesystem refused, the database unreachable. A failure the engine itself names — X_MIGRATION_CONFLICT, X_MIGRATION_IRREVERSIBLE, X_DB_UNAVAILABLE — reaches you as that code, with its own fix, never wrapped in these read cause — it carries the underlying error verbatim — then x doctor --json
X_DB_HANDLE_UNREGISTERED an entity x g wrote is not in the app's typed database handle The generated repo.ts reads db., and packages/db/src/client.ts has no entity set the generator can add to, or packages/db/src/index.ts does not export the handle
x g entity widget --dry-run --json — lists the files; the finding names the two lines to add to packages/db/src/client.ts
X_DB_INDEX_UNDECLARED Schema dump holds an index nothing declares an index in packages/db/schema/05_indexes is in neither the newest migration snapshot nor any entity declaration; every write maintains it x verify --only drift --json # each X_DB_INDEX_UNDECLARED warning names the index: its DROP INDEX CONCURRENTLY IF EXISTS "<name>"; goes in a new hand-written migration (-- transaction: false), or declare it in the entity's indexes: [...] and x db gen "<change>"
X_DB_ROW_SECURITY_OFF Raw sql reaches tenant tables while database.rowSecurity is off database.rowSecurity is off and a raw sql statement in the app's source names a tenant table; the repository's tenant scope does not reach a raw statement, so one missing tenant predicate reads every tenant's rows database: { rowSecurity: true } — in defineConfig, app.config.ts; then: x db gen "row security" --json && x db migrate --json && x doctor --json
X_DB_SCHEMA_UNDECLARED a migration records schema no entity declares the other direction, and a different repair: the database carries a constraint, column or index the entities no longer ask for. Reported separately from X_DB_SCHEMA_UNMIGRATED because "your database is missing this" and "your last generation lost something" are not one finding delete the stale declaration, or bun run x -- db gen "drop what the entities no longer declare" if the removal is intended
X_DB_SCHEMA_UNMIGRATED an entity declaration no migration recorded the half X_DB_DRIFT cannot see: that check compares a schema-source hash and never reads the SQL, so a committed migration smaller than its declaration passes. Measured on dummy/social-media-clone, whose drift was 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 @. Compares snapshotOf(describeEntities()) against the newest .snapshot.json, so it needs no database connection. Also names a table a channel with params or a live query's subscribes: needs REPLICA IDENTITY FULL on when no migration recorded it (As of 2026-10-02): that need is a realtime declaration, so no entity hash moves when the channel is added bun run x -- db gen "describe the change" — the generated migration is additive, one add constraint per finding
X_DB_STUDIO_FAILED reserved, not thrown — studio left x db As of 2026-11-15 (Known gaps). It shelled out to bunx drizzle-kit studio, a second schema engine for one subcommand — x dev, then the db panel at /_x
X_DECLARATION_UNKNOWN no declaration with this name is registered a typo, or a module that never imported. x db seed <name> answers with it too — a seed is a declaration, and the cause lists every seed the app does declare x actions list --json (or queries / entities); x db seed --dry-run --json for a seed, which lists them and writes nothing
X_DEPLOY_BUILD_MISMATCH production never served this build no /readyz sample carried the build before --timeout passed x deploy verify --url https://app.example.com --build "$BUILD_ID" --json — the id CI stamped; meta.byBuild names what answered
X_DEPLOY_BUILD_UNSTAMPED the deployment answers with no build header /readyz answered 2xx with no x-ultimate-build, so no sample can name a build x build --target docker --json — stamps BUILD_ID into the image; or set BUILD_ID in the image's environment
X_DEPLOY_ENV_MISSING x deploy --method compose found no complete .env.production the app has no .env.production, or it leaves a ${VAR:?} the compose file requires unset or empty, so every compose step would refuse x env init --production --json
X_DEPLOY_FAILED a deploy step failed the compose/helm command exited non-zero run the printed command directly for full output
X_DEPLOY_QUEUE_UNSERVED a registered queue has no serving worker of this build no worker row that is not draining and runs this build claims the queue x jobs list --json # then WORKER_QUEUES=<queue> on a worker Deployment, or --idle-ok <queue> on the deploy verify subcommand for a scale-to-zero pool
X_DEPLOY_UNSTABLE the build answered but did not hold the build answered, but the --window of consecutive good samples never closed before --timeout x deploy verify --url https://app.example.com --json — samples.byStatus and samples.byBuild name what interrupted it
X_DEV_ALREADY_RUNNING another x dev already owns this checkout a live x dev holds .x/ — embedded Postgres is a single-writer data directory, so a second one cannot open it x stop --json — or use the one already running
X_DEV_DATA_UNOPENABLE x dev set aside an embedded data directory that would not open the embedded PGlite directory under .x/ failed to open — a crash mid-write, a PGlite upgrade or a copied directory — so x dev renamed it to .unopenable- and booted an empty database; the old rows are in the moved directory x db migrate --json — the fresh database has no tables yet; then x db seed --json if the app declares a seed. The moved directory (meta.aside) is kept: delete it once its rows are not needed
X_DEV_HOST_REFUSED a /_x request named a host that is not this machine the request reached x dev with a Host header that is not localhost, a *.localhost name or a loopback address, which is how a DNS-rebinding page reads the dev dashboard and its database cross-origin curl -sS -H 'accept: application/json' http://localhost:3000/_x
X_DEV_LOCK_UNREADABLE the dev lock file cannot be read or removed .x/dev.lock parses as no lock and unlink refused it — a directory left at that path, or a file this user may not delete. Its own code because the alternative was X_DEV_ALREADY_RUNNING naming the READER's own pid as the holder, whose fix: was kill <self> rm .x/dev.lock, then re-run x dev
X_DEV_LOG_ABSENT the dev log does not exist yet logs.tail or x logs tail found no /dev.log; x dev writes it x dev --json # the dev server writes the dev log as it boots; then: x logs tail --json
X_DEV_PEER_REFUSED a /_x request came from a non-loopback peer x dev is bound beyond loopback (--host) and a request for the dev dashboard came from another machine x doctor --json # /_x answers a loopback peer only: open it on the machine the dev server runs on, or forward the port with ssh -L
X_DEV_RESTART_REQUIRED a save reached a module that defines a primitive; only a new process serves it a slice service, a view under defineAdmin, or an action/query/entity/job file itself was saved, and the module that defines the primitive still holds the old code x stop --json && x dev — the supervised x dev restarts itself; an embedded startDev() passes onRestart
X_DEV_ROOT_GONE the app root x dev serves was deleted or moved the directory x dev was started in was removed or renamed while it ran (a test fixture torn down, a re-clone, mv of the checkout) x dev # from the app root, once it exists again (restored, re-cloned or moved back)
X_DEV_STATE_UNWRITABLE x dev cannot claim its state directory the state directory could not be created, written, or hard-linked into, so x dev cannot take its lock — a read-only checkout, a .x/ this user may not write, or a filesystem without hard links ls -ld .x — make it writable by this user, on a filesystem that supports hard links, then re-run x dev
X_DEV_STOP_DENIED x stop may not signal the x dev the lock names the pid in .x/dev.lock belongs to another user, so SIGTERM is refused with EPERM ps -o user= -p <pid>, then run x stop --json as that user
X_DEV_STOP_TIMEOUT x stop sent SIGTERM and x dev did not exit in time the x dev the checkout lock names is still running when the wait ends: a drain past its deadline, or a process that ignores SIGTERM x stop --timeout 2m --json; still running: kill -9 the pid its cause names, then x dev --json (a hard kill leaves the lock, which the next boot clears)
X_ENTITY_RETAIN_UNSWEPT an entity declares retain and no purge() sweeps it retain is a promise only a purge job keeps; with none registered, expired rows are never deleted add export const retention = purge({ entities: 'declared' }) to a jobs module named in jobs: [...] in apps/web/api/index.ts, then x verify
X_ENTITY_VIEW_DRIFT a view entity's columns disagree with the view its migration created entity({ view }) declares columns the view's query does not output, or the query outputs columns no entity column names — measured on the scratch replay of the migrations, so every read of a missing column would fail with 42703 at runtime x verify --only drift --json # the cause names the view entity and both column lists: make columns name exactly the view's output, or change view.sql and x db gen
X_ENV_FILE_EXISTS x env init --production found .env.production already written the file holds the secrets this deploy already runs with, and minting new ones would lock the running database and sessions out NODE_ENV=production x env check --json
X_ENV_NAME_RESERVED An app variable is named on a name the framework reads envSchema in app.config.ts declares, or secrets.enc.json seals, a name FRAMEWORK_ENV lists as a switch or an internal name of an @ultimat3/* package, so the app's value also switches that package's behaviour edit app.config.ts: add an APP_ prefix to the envSchema name the finding cites (or delete it where the value is meant for the framework); then: x env example --json && x doctor --json
X_ERROR_CODE_UNDOCUMENTED a shipped error code has no row in the error reference a package declared an X_* code and the same pull request never added its row x errors explain <code> --json — its title and fix, for the row to add to the owner's wiki/Error-Codes-<owner>.md
X_ERROR_CODE_UNKNOWN no package registered this error code a typo, or a code from a package this process could not import x errors list --json — the nearest real code is in fix, and data.unavailable names any package that would not load
X_ERROR_CODE_UNREGISTERED the error reference documents a code no package registers a row written for a code that was renamed, never built, or emitted as a Finding without a registerErrorCodes() call registerErrorCodes({ <code>: { title: '<what it means>' } }) — in the owning package's src/errors.ts; or move its row under Reserved codes
X_ERROR_CODE_UNRESOLVED an error code is written as a name this repository cannot resolve the errors step read a code: whose value is an identifier, and no module-scope const in that same file gives it a value — an import, a local, an enum member. Every reader of the code set is then blind to whatever code it holds: no row in framework.manifest.json, no row demanded on this page, no entry for bun run gate-codes, no x errors explain answer. Silent and permissive, so the DRYer the author the less the gate saw (#277). A const NAME = 'X_…' in the SAME file is resolved and is not a finding; a table read (SEO_ERROR_CODES.metaMissing) is not judged, because the registry it reads from declares those literals itself edit <file>:<line> — …: the fix names the offending line — write the X_* code as a string literal there, or declare it as a module-scope const in that same file
X_ERROR_CODE_UNTHROWN a registered error code is constructed by nothing and UNTHROWN_CODES in packages/cli/src/unthrown-codes.ts does not list it a code is registered and this page presents it as live, but no shipped source constructs it, so a reader matching on it waits for an error that cannot arrive. The waiver is a list, UNTHROWN_CODES in packages/cli/src/unthrown-codes.ts, or the code's place under Reserved codes — a row's wording waives nothing. Add the code to UNTHROWN_CODES and write "registered, thrown by nothing since " into its row, naming the code that replaced it — or throw it again where it belongs. Never delete the registration: a shipped code never changes meaning x errors explain X_ERROR_CODE_UNTHROWN --json
X_ERROR_CODE_UNTHROWN_STALE a code UNTHROWN_CODES lists as thrown by nothing is thrown again — delete it from UNTHROWN_CODES in packages/cli/src/unthrown-codes.ts UNTHROWN_CODES in packages/cli/src/unthrown-codes.ts waives the unthrown check for a code, and shipped source constructs the code again, so the listing would excuse a code that is live x errors explain X_ERROR_CODE_UNTHROWN_STALE --json
X_ERROR_FIX_INVALID an error's fix line is not a runnable instruction the errors step read a fix: that is empty, or one that advises (check, make sure, try, see the docs) with no command, call or file path in it. Also one that opens with the failing command and defers the edit to a trailing # after … / # once …, or that only says to re-run (As of 2026-11: ratcheted per file in packages/cli/src/fix-sequence.ts, a file past its count reports every such line). And one whose runnable half runs x g … --force: a generator's file can be shared by a slice, and a pasted fix shows no diff before it overwrites — no allowance edit <file>:<line> — …: the fix names the offending line — rewrite that fix: as a runnable command, a call, or an edit naming a file
X_ERROR_FIX_PATH_MISSING an error's fix line cites a file this repository does not have the errors step read a fix: naming a path or a glob and resolved it against the root the gate is running in. Only x <command> citations were checked until 2026-08, so a fix telling its reader to open a file that was moved, renamed or never written passed every gate — the live instance was X_UI_RUNTIME_MISSING, whose fix named a line no generator emitted. Narrow on purpose: a scoped specifier (@ultimat3/ui/global.scss), a dot-relative path (./global.scss) and any path whose parent directory this repo does not have (src/errors.ts, apps/web/server.ts — those name a directory the reader's app has) are not judged at all; since 19.1.1 neither is a path under a directory the root .gitignore never commits (.personal/fleet.yml) — private by design, present on a developer's disk and absent on CI edit <file>:<line> — …: the fix names the offending line — correct the path to one this repo holds, or create the file it names
X_ERROR_REPORTER_DSN_UNCLAIMED SENTRY_DSN is set, and the app installed a reporter marked neither as its Sentry transport nor as a local sink the app installs an ErrorReporter of its own (a wrapper around sentryErrorReporter, a hand-written sink) without sentryTransport() or localErrorSink(), and the container also sets SENTRY_DSN; it might already be a transport, so the boot adds none and the DSN is unused edit the file that calls configureErrorReporting: wrap your Sentry wrapper in sentryTransport(wrapper), or a reporter that keeps reports on the box in localErrorSink(sink)
X_EXERCISE_FILE_UNEDITABLE x g could not add an entry to apps/web/exercise.ts the app keeps apps/web/exercise.ts in a shape the generator cannot edit safely: no single export const exercise = defineExercise({ … }) with an object literal edit apps/web/exercise.ts — paste the entry the finding names into export const exercise = defineExercise({ … })
X_EXERCISE_UNPROVEN_ABOVE_FLOOR The exercise pass left more primitives unproven than x.verify.json allows exercise.unprovenMax in x.verify.json is below the share of reached primitives whose tenant, crash or scale proof could not ask — usually a sized seed that failed or an override that no longer fits x exercise --json — each unproven record in .x/exercise.json names the proof and its reason: fix the seed or the override it names; the floor only falls
X_EXPLAIN_PRODUCTION_DATABASE x explain refused to run on a production database DATABASE_URL names an external Postgres and ULTIMATE_ENV (else NODE_ENV) resolves production, or ULTIMATE_ENV is set to something that is not an environment: x explain sends the query for real with its policy skipped, so it runs on the dev database or a staging copy only env -u DATABASE_URL x explain <query> --json — the thrown fix names the query; it plans on the embedded dev database. For a copy of production data, point DATABASE_URL at a staging restore with ULTIMATE_ENV=staging. No override flag: production is never planned on
X_FEATURE_REQUIRED x g query or x g backfill named no slice to read A read and a sweep read an existing table, and nothing but x g resource or x g entity creates one: with no --feature and no slice of that name, the generator would have written an entity and a migration nobody asked for x help g --json # then the query generator with --feature <slice>, or the resource generator for a new table
X_FEATURE_UNKNOWN x g --feature names a slice that does not exist A generator writing into a slice refuses one with no directory rather than inventing an entity table for it. The cause lists the slices the closest slice within edit distance 2: x g action foo --feature post. None near: x g resource <feature>
X_FILE_TOO_LONG a source file is over 500 lines one file doing several jobs split it; the fix names the file
X_FIX_TARGET_UNKNOWN the named file is not one of the app's source files a path outside apps/*/{site,app,api,shared}, or a typo x fix boundary <nearest real path> — fix carries it
X_FRAMEWORK_PIN_RANGE An @ultimat3/* dependency is pinned as a range a package.json of the app writes an @ultimat3/* version through an operator (^31.0.0, ~31.4); the framework releases in lockstep, so the next install can move one package without the rest x doctor --json # each X_FRAMEWORK_PIN_RANGE names a package.json line and the exact version: write it there, then: bun install
X_FRAMEWORK_SCHEMA_FAILED a framework table could not be created at boot a statement in FRAMEWORK_SCHEMA did not apply — the two real ones are a role that cannot apply DDL (42501: no create on schema public, or not the owner of an existing framework table — a production runtime role, which is why only the migrate step applies it), and a relation of that name already present with an incompatible shape. Raised in place of the driver's own rejection, which names neither the framework table being created nor the package that wants it, and a boot failure is read by an operator with no source tree open: cause names both and meta.tables lists every relation that entry creates. The list is reached on every boot path through startQueue: ROLE=migrate, x db migrate, x dev and x mcp serve apply it; a serving role on an external database only verifies the stamp the migrate step left; every other CLI command (x db backfill, x jobs, x auth) applies it only when this build's stamp is absent, because Postgres refuses even create index if not exists to a role that does not own the table — so "installed in dev and not in production" is not a state this framework can be in, and a runtime role with DML only runs no DDL provided this build's stamp is present — on a database the migrate step has not stamped, or stamped by another build, that command attempts the DDL and fails here, which is the signal to run the migrate step first. What it closed: x_users, x_sessions, x_accounts, x_verifications and x_api_keys were exported as DDL for an app to paste into a migration nobody wrote, and applied by NOTHING. They are not entity() declarations, so x db gen never saw them either, and the reference app recorded the symptom — nobody could hold a session — without anyone reaching the cause x db migrate with DATABASE_URL naming the role that owns schema public, as ROLE=migrate runs
X_FRAMEWORK_SCHEMA_UNAPPLIED a serving role booted over a database whose framework schema this build never applied since 24.0.0 only ROLE=migrate (x db migrate, x dev, and the other CLI commands) applies the framework tables, under the migration advisory lock with a bounded lock_timeout; a serving role on an external DATABASE_URL only verifies that the build it runs has been applied, by the stamp migrate leaves on x_jobs. The stamp lacks this build: the release ran the web, sync, worker, scheduler or replicator role before its migrate step, or skipped it x db migrate
X_FRAMEWORK_TABLE_ORPHANED a framework table no release reads any more is still in the database a table an earlier release created is still present after the upgrade that stopped using it; nothing reads or writes it, and the boot never drops a table a replica on the previous release may still be using x doctor --json
X_GENERATE_CONFLICT a generator would overwrite a file the name is taken x g … --force, or choose another name
X_GENERATE_JSON_INVALID a generator's own merge: 'json' output does not parse as a JSON object a bug in the template that produced it — never a file already on disk, which X_GENERATE_CONFLICT covers fix the template that emits it, then bun test packages/cli/src/cmd-generate.test.ts
X_GH_COMMAND_FAILED a gh invocation exited non-zero the invocation and its exit code are in the cause. gh exits non-zero whenever a GraphQL response carries errors, so a partial answer never reaches the parser the finding carries the exact gh invocation that failed — run it yourself to see why
X_GH_NOT_AUTHENTICATED gh holds no credentials for this host a fresh machine, an expired token, or a GitHub Enterprise host gh was never logged into. Detected from gh's own refusal text, so it is never confused with a network failure gh auth login
X_GH_RESPONSE_INVALID gh's output is not the shape the command reads GitHub changed a field, or a query was edited without its schema. The response is parsed, never cast: a null where an id was expected would otherwise become a resolve call against undefined the finding names the field that did not parse; x pr review --json
X_GH_UNAVAILABLE the GitHub CLI is not runnable from here gh is not installed or not on PATH. x pr and x ci shell out to it rather than embedding an HTTP client — no new dependency, and the user's existing auth gh auth login — install first from https://cli.github.com
X_GRAPH_NODE_UNKNOWN x graph or x impact was asked about a node the app graph does not hold the name or path matches no route, primitive, entity, file or test of the loaded app (the cause lists the nearest three) x graph --json — every node id is in data.nodes
X_GUARD_BASELINE_STALE a guard baseline is above what the tree reports guards/.ts reports fewer findings than x.verify.json's guardBaseline still allows: a baseline only falls x verify --only boundaries --json
X_GUARD_BUILT_IN x g guard named a shipped guard the guard already runs from the installed framework; a second copy would shadow it x verify --only boundaries --json — set its severity in guards/shipped.json, or generate an app guard under another name
X_GUARD_FAILED an app guard threw instead of returning findings a guard is a function returning Finding[]; a throw means it could not answer at all, which is different from finding nothing. The cause carries the throw verbatim x verify --json — the cause carries the throw the guard raised
X_GUARD_FINDING_INVALID an app guard's finding breaks the error contract a finding whose code is not X_-prefixed SCREAMING_SNAKE, an empty cause, or a fix that says "check" or "make sure" and names no command. Held to the identical rule x verify's errors step applies to shipped source — and checked on the returned value, which is the half a static scan cannot reach, since a fix built at run time has no literal x verify --json — then give the finding an X_ code, a cause, and a fix naming a command
X_GUARD_INVALID a file in guards/ exports no usable guard the module has no guard export, or one missing summary/check. Discovery is the directory — nothing registers a guard, so a file that looks like one and is not must say so loudly rather than being skipped x verify --json — then export a guard from the file the finding names
X_GUARD_OVER_BASELINE a guard reports more findings than its x.verify.json baseline allows guards/.ts reports more findings than x.verify.json's guardBaseline allows for it; the baseline never rises x verify --only boundaries --json
X_GUARD_VENDORED a guards/ copy of a shipped guard the copy runs in place of the guard the installed framework ships, and never receives its fixes x upgrade --json
X_IMAGE_NOT_PREBUILT a container role built at boot what the image build should have: island chunks or stylesheets an image whose Dockerfile predates the prebuilt step, or one built from a context that carried a store for another Bun or framework version edit docker/Dockerfile: add RUN bun node_modules/@ultimat3/cli/src/bin.ts build --target prebuilt after COPY . . in the runtime stage, then rebuild the image
X_IMAGE_SOURCE_UNREADABLE a responsiveImage src is not a file the static export holds responsiveImage({ src }) on a static page named a site path the export does not contain, so no variant of it can be written x build --target static --json — lists the export; put the file under apps/web/site/assets/ and pass asset('assets/') as src, or give an absolute https:// URL
X_ISLAND_DISPOSER_MISSING an island's mount returns no disposer an .island.tsx mount() is typed void or returns nothing, so the client router cannot dispose it on navigation and its listeners, hotkeys and live reads stay registered x verify --only boundaries --json — names the file; end its mount() with return mountOver(el, (root) => render(() => <Island {...props} />, root)) (mountOver from @ultimat3/render/client), the disposer the client router calls on navigation
X_ISLAND_MODULE_DUPLICATED An island chunk bundles one module more than once the island build shipped one framework module twice — one file under two path spellings, or a second @ultimat3/* copy — so its bytes and its module state are duplicated in the chunk gh issue create --repo developerz-ai/ultimate --title "X_ISLAND_MODULE_DUPLICATED" — paste this error's --json as the body: the framework bundled one of its own modules twice
X_JOB_OUTLASTS_DRAIN a job's declared timeout outlasts the worker's budget the job's timeout exceeds drain.workerRetireMs (or, retire off, drain.workerDeadlineMs / drain.deadlineMs), so a deploy cuts a run still inside its own limit drain: { workerRetireMs: 7200000 }, // at least the job's timeout, in app.config.ts, then x verify --only manifest --json
X_JOB_UNKNOWN the queue holds no job with this id a stale id, or a job already reaped x jobs list --json
X_JOB_UNREGISTERED a job reached the manifest under its positional anonymous name The manifest step: a job module no defineApi jobs list names keeps the anonymous-job-N name job() gave it import * as <module> from '<its file>'; — in apps/web/api/index.ts, and added to jobs: [...] there; then x manifest
X_LAYOUT_SIBLING_MODULE a primitive module beside its directory actions.ts and actions/ (or live, queries, jobs, tasks) in one slice — ./actions resolves to the file, and the directory form is the one layout x verify --only boundaries --json — then move each declaration in X.ts to X/.ts, one primitive per file
X_LINT_FAILED Biome failed any, a default export, a bare Error, a raw hex colour. One finding per lint-rule diagnostic (at, line and rule); every format and import-order miss together in ONE finding (As of 31.22) per finding. The format and import-order misses: bunx @biomejs/biome check --write <file…>, every file in one command. A lint rule: bunx @biomejs/biome check <file>, then edit the line its comment names
X_LIVE_ROUTE_NO_ISLAND a route reads live rows and boots nothing that could receive them a browser-only read (useQuery, useConnection, useMutation, useMutationQueue, useRecord, useChannel, or hasPageSocket) sits in a module of the route's server graph that no island imports, or on a route declaring hydrate: 'never'. It only ever runs on the server, where it answers its server state (nothing, or loading) forever, at 200. hasPageSocket() is no exemption since 21.0.0: it answers false on the server every time, which is how the reference app's update banner never showed. Reported by the budgets step x g island <route-dir> --at <route-dir> — moves it into an island: import the module from that island's mount(), and declare it with island({ src }) in the route file, with a hydrate other than 'never'
X_MANIFEST_MISSING the app ships no x.manifest.json at all nothing ever ran x manifest: after x new, bun run setup and every generator, the file did not exist while the gate's manifest step reported green — because the drift check has nothing to compare when the file is absent. Its own code because the repair differs from both neighbours: X_MANIFEST_DRIFT means the committed file disagrees with the code, X_MANIFEST_STALE means openapi.json does, this one means there is nothing there. Raised only at an app root — this repo emits framework.manifest.json and has no x.manifest.json to be missing x manifest
X_MANIFEST_STALE openapi.json is stale the committed spec does not match the actions the code registers x manifest, then commit
X_MIGRATION_UNGENERATABLE this migration holds SQL no declaration carries and does not say so the third rail of the drift step, and the one a squash discards. x db gen can only write what an entity declares, so a hand-written CREATE TYPE … AS ENUM, CREATE EXTENSION, GRANT, ALTER TABLE … REPLICA IDENTITY FULL or a data backfill is lost the moment anyone regenerates — and no declaration-based check can see it, because a regenerated sidecar equals the declaration by construction. examples/dummy's 0001_init.sql holds 7: five enum types and both replica identities. A count, not a boolean, so the first hand-written statement does not buy that file an unlimited allowance edit packages/db/migrations/<id>.sql:1 — add the header line "-- ungeneratable: <n>" — the file the finding names, so a squash carries these statements by hand — or re-declare what an entity can express (an enum is a text column plus a check invariant) and run x db gen "<name>". Add the marker before the migration is applied: it is SQL the checksum covers, so marking an applied file answers X_MIGRATION_CONFLICT
X_NATIVE_FORM_UNANSWERED a page form posts to an action that declares no native answer a page.tsx names an action whose declaration has no native: { success }, so a browser submitting it with scripting off is answered as a fetch would be. A warning in the manifest step on main (the step stays green); a refusal is planned for next native: { success: (output) => '/where-it-lands' } in the action's declaration, then x verify --only manifest
X_NEW_SHAPE_CONFLICT x new --shape with --no-example a shape is its own example, so --no-example asks for two different apps at once bunx @ultimat3/cli new myapp --shape blog
X_NEW_SHAPE_GENERATE_FAILED a shape generator failed in the new app x new --shape ran an x g generator in the app it had just written, and the generator refused or failed bunx x g sign-in --password --json — in the app x new wrote, reproduces it; then bun test packages/cli/src/templates/shapes
X_NEW_SHAPE_UNKNOWN x new --shape names no registered shape the value of --shape is not one of the shapes x new ships bunx @ultimat3/cli help new
X_NOT_IN_APP command must run inside an Ultimate app no app.config.ts at or above the cwd x new myapp && cd myapp
X_PACKAGE_DUPLICATED two copies of one registry-holding framework package (@ultimat3/i18n, @ultimat3/policy, @ultimat3/entity) are installed in one app a workspace pinning an older range than the root (packages/i18n on ^19.0.0, the root on ^19.1.0), or two resolutions of one version. Each copy is its own module instance with its own registry, so the app registers into one and the CLI reads the other: x i18n check reported X_CATALOG_UNREGISTERED over a defineCatalogs() call that was exactly where its fix said to put it, and the policy step is green over an undeclared grant because isKnownPermission checks nothing while its own copy holds no declaration. Judged by realpath — a workspace symlink to one checkout is one copy the finding names both copies and the package.json to pin: set every @ultimat3/* to one exact version there, then bun install; two copies of ONE version are collapsed by bun install --force. x i18n check --json and x verify --only policy --json re-check
X_PACKAGE_SHAPE a workspace package is missing a contract file a package added by hand bun run scripts/new-package.ts <pkg> --only <file>
X_PACKAGE_TEST_ONLY_SHIPPED a test-only module ships in the tarball a src/ module imported only by tests is not named *-fixture.ts, so the package files list publishes it — test scaffolding (fakes, probes, bun:test imports) in every install bun run x -- verify --only package-shape --json # then rename each listed module to <name>-fixture.ts and update its importers
X_PACKAGE_UNREFERENCED a published workspace is not in the root tsconfig build graph bun run typecheck is tsc -b, which builds referenced projects and nothing else — so a package no root references entry names compiles nowhere and the gate's typecheck step reports green over it. scripts/new-package.ts never added the entry and nothing asked for it. Private packages are exempt, and a root that declares no references at all is a repo that builds another way { "path": "./packages/<pkg>" } — in "references" of tsconfig.json, then bunx tsc -b --pretty false
X_PARTITIONS_UNMAINTAINED a partitioned entity with no partitions() job An entity declares partitionBy and no partitions() job from @ultimat3/jobs is registered: no partition is ever created ahead, so the first insert past the last migrated partition fails in production, and retention never drops one x verify --only manifest --json — after exporting partitions() from @ultimat3/jobs in a module listed under jobs in apps/web/api/index.ts, and its .schedule under tasks
X_PERMISSION_BORROWED an app rule requires a permission only an imported package declared an action, query or route the app declares requires a permission that only a package it imports declared — @ultimat3/admin's defineAdmin() declares :read|write|delete for every mounted entity — so the app's own definePermissions() never names it and the rule holds only in a process that ran defineAdmin() first: a worker role, a script or a test that never mounts the admin throws X_PERMISSION_UNKNOWN at the rule's can() x verify --only policy --json
X_PERMISSION_UNGRANTED an action, query or route requires a permission no role grants The policy step: a single-permission rule no role in the app role map holds, so no actor can ever pass it grants: [..., '<permission>'] — one role's, in the module that calls defineRoles() (apps/web/shared/roles.ts in a scaffold); then x verify --only policy
X_PORT_INVALID PORT is not a TCP port number a platform-injected PORT that is empty, non-numeric or out of range — never defaulted past, because a web role that quietly bound 3000 fails the platform's health probe with nothing in the log that names the cause docker run -e PORT=3000 <image>
X_PORT_IN_USE the dev port is taken an unrelated process holds it — usually another project's dev server; the pid and command are named when the OS will say x dev --port 3001, or kill the named pid if it is yours. The scrape port on a deployed role: set METRICS_PORT=<free port> in this role's environment, one per role on a host; the refusal stays, a scrape target must not move on its own
X_PREBUILT_REGISTRY_STALE the image's prebuilt module registry does not list the app's modules, so the role scanned instead a module added, moved or deleted after x build --target prebuilt ran — the registry is written inside the image build, after COPY . . edit docker/Dockerfile: move RUN bun node_modules/@ultimat3/cli/src/bin.ts build --target prebuilt after the last COPY in the runtime stage, then rebuild the image
X_PROFILE_ROUTE_FAILED the profiled route answered an error x profile rendered the route and it answered a status of 400 or more, so the profile measures an error path x routes --json
X_PR_NOT_FOUND no pull request for this checkout x pr with no --pr, on a branch GitHub has no PR for x pr review --pr <n> --json, or open one first: gh pr create
X_QUERY_SLICE_ENTITY x g query into a slice whose entity is not the one it scaffolds The slice's entity.ts declares a table under another name than the slice's, and the generated read imports the slice's own row type and repo: written anyway, it does not compile x queries list --json — then declare the read by hand over the entity the slice declares
X_QUERY_SUBSCRIBES_UNKNOWN a live query subscribes to a table no entity declares subscribes: on a live: true query names a relation this app has no entity for — a typo, or a table that was renamed. Raised by x db gen and the drift step, the one tier holding both the manifest and the entity registry: @ultimat3/query has no table catalog and cannot see it. Since #518 x db gen grants no REPLICA IDENTITY FULL for subscribes: (a keyed table is correct on DEFAULT); the list is validated, never granted subscribes: ['<table>'] — on the query the cause names, a table the app declares; or drop the name, then x db gen "fix subscribes" --json
X_RELEASE_VERSION_SKEW a workspace is not at the lockstep version a package bumped on its own, or a release that stopped half-way bun run scripts/release.ts --bump patch --dry-run --json to see the realignment, then run it without --dry-run and review the package.json diff
X_REPRO_BUNDLE_INVALID the file is not a repro bundle this version can open the file is missing, carries another format tag, or names no reproducer under repro/ x repro --json — lists the failing jobs and error groups; then run it again with one id and --bundle, and attach the file it writes
X_REPRO_CAPTURE_OFF x repro was given a request id while failure capture is off failureCapture is disabled in app.config.ts, so no request bundle was ever stored x jobs list --json # a job id replays with capture off; for requests set failureCapture: { enabled: true } in app.config.ts
X_REPRO_NOT_REPRODUCED a written repro test did not fail the way the original did the generated test ran and did not end in the captured code: a masked field, a row the code read by hand, or a different build changed the outcome x repro --list --json # re-read the bundle (x repro ID --json), then set its listed masked fields and unread rows by hand in the written test
X_REPRO_UNKNOWN x repro was given an id nothing holds no job, captured request, trace or fingerprint matches the id x repro was given x repro --list --json
X_ROLE_LOAD_INCOMPLETE a worker or scheduler did not register a job or task the manifest names a worker or scheduler imports apps/web/api/index.ts and every module that reaches no component or stylesheet; a job or task registered only by a module that also imports a .tsx or a stylesheet is not loaded, while x.manifest.json names it. At boot it is logged and answered by importing the whole app; the manifest step reports the same gap before a deploy import * as <module> from '<the file that declares it>'; — in apps/web/api/index.ts, with in jobs: [...] or tasks: [...]; then x manifest
X_ROLE_UNKNOWN ROLE names something that is not a role a typo in a compose file, a Helm value or a docker run — one image runs every role, so the typo would otherwise start a process that serves nothing and reports healthy docker run -e ROLE=web <image> — one of web, sync, worker, scheduler, replicator, migrate
X_ROUTE_ASYNC_PAGE a route exports an async Page Its data read bypasses load, so it gets neither load caching nor its meta export const load = (ctx) => … — in the file the cause names: move each await in Page into it, and read it with the page's data prop
X_ROWS_SLICE_ENTITY the slice's entity is not the scaffolded table x g export-rows or import-rows moves the slice's own scaffolded table, and its entity.ts declares a different one x help g --json # then generate a job with the name and feature the finding names, and declare exportRows/importRows in it over the table that entity.ts declares
X_RUNTIME_DRIVER_SPLIT the ambient driver is not the one this process serves an app module installing a driver itself at import time (before 31.0.0, setJobDriver()). startServices builds the drivers and captures them, and loadApp runs after it — so the ambient slot moves and the captured object does not: the worker claims from what was captured while every handle.enqueue() publishes to what is ambient. Jobs are accepted, acknowledged, visible in /_x and never run. Refused at boot, because the alternative is a deployment that only ever looks healthy export const runtime = { <driver>: yourDriver } satisfies RuntimeOverrides; in apps/web/runtime.ts — and delete the module's own install call
X_SCAFFOLD_PATH_ESCAPE a generated path resolves outside the scaffold sandbox a .. segment or an absolute path in a template's GeneratedFile.path make the path relative to the app root with no .., then bun test packages/cli/src/scaffold-typecheck.contract.test.ts
X_SEAL_RESEAL_PENDING sealed columns still hold values under a retired master key x doctor: the app declares .sealed() columns and ULTIMATE_SECRETS_RETIRED_KEYS still declares a retired key — a rotation whose re-seal has not finished. Until it has, a lookup column matches through in (…) over every key and its .unique() is only as strong as one key: one value can be stored once per key re-seal with a backfill() that rewrites each row (update(id, { <column>: row.<column> }) seals under the current key), then x secrets rotate --drop <keyId>
X_SECRETS_EDITOR_MISSING no $EDITOR to open the decrypted secrets in neither VISUAL nor EDITOR is set. No editor is guessed — opening a decrypted file in a surprise program is the last place a default belongs EDITOR=nano x secrets edit, or write one value without an editor: printf %s "$TOKEN" | x secrets set STRIPE_KEY
X_SECRETS_EDIT_FAILED the editor exited non-zero, so nothing was resealed a crash or a deliberate abort. The buffer is discarded and the committed file is untouched x secrets edit
X_SEED_ENVIRONMENT the seed's tier is not one this environment runs x db seed <name> naming a dev-tier seed while ULTIMATE_ENV resolves production, which runs reference only. dev fixtures reaching production is the one irreversible thing x db seed can do, so it is refused rather than confirmed — and the check runs twice, in selectSeeds and again in cmd-db.ts before the driver is booted, because the layer that opens a connection to production must not be the only layer that decided it was allowed to. Its own code and not X_CLI_BAD_FLAG: the argv was well formed, and the one remedy is naming the tier rather than re-reading x help x db seed <name> --tier <tier> --json — the cause names the tier and the environment. For a container whose command line is fixed, ULTIMATE_SEED_TIER=<tier> says the same thing, and the cause names it too
X_SEED_FAILED a seed threw an uncoded error a seed run threw an error that carries no X_ code, so it names no fix of its own bun --eval 'await (await import("./packages/db/seeds/dev.ts")).dev.run()'
X_SEO_CARD_BROWSER_MISSING a static build with social cards found no browser to photograph them a site/ route declares og.capture, x build --target static photographs each card in Chrome, and no CHROME_PATH or PUPPETEER_EXECUTABLE_PATH is set and no browser is installed at a probed path export CHROME_PATH=/usr/bin/google-chrome — any Chrome, Chromium or Edge binary; or drop og.capture from the route. The gate build passes --no-capture and needs none
X_SEO_CARD_ROUTE_UNKNOWN og.capture names a path no site/ route answers a route's meta declares og: { capture: '/og/…' } and no page.tsx under apps/web/site/ matches that path, so the build has no page to photograph x routes --json — list the site/ routes; add apps/web/site//page.tsx at 1200 x 630 with robots: { index: false }, or correct the og.capture path
X_SHIPPED_GUARD_MISSING A guard x new ships is not in this app's guards/ A guard x new ships is absent from this app's guards/ directory, so x verify does not hold the app to that rule. A warning beside x doctor's verdict on main, never in it. x doctor --json # each X_SHIPPED_GUARD_MISSING warning's fix is the command that writes its guard, then x verify --only boundaries --json
X_SHOT_BROWSER_MISSING x shot has no browser to launch none was named — --browser, PUPPETEER_EXECUTABLE_PATH, CHROME_PATH — and none of the four probed paths (/usr/bin/google-chrome and its siblings) is on disk. Raised before the dev server boots. As of 22.0.0 x shot drives Chrome over raw CDP, with no browser library in the app: it no longer means puppeteer-core is missing export CHROME_PATH=/usr/bin/google-chrome — or attach to a browser somebody else runs: x shot / --cdp-url wss://cdp.example.com/session/abc
X_SHOT_ELEMENT_MISSING no element matched the selector before the deadline a ui.interact step or a waitFor whose selector matched nothing for the whole budget — the markup changed, or the selector was never right. Its twin below is the other question: it matched and could not be acted on { "route": "<the route>", "selectors": ["main", "button"] } — ui.inspect's input: copy a selector it reports with count >= 1
X_SHOT_ELEMENT_UNREADY the element matched and never became ready to act on the first match stayed hidden, zero-sized, disabled, covered at its centre by another element, or still moving between two polls. The cause names which { "route": "<the route>", "selectors": ["<selector>"], "a11y": true } — ui.inspect's input: see what covers or disables it, then act on that element first
X_SHOT_HOST_REFUSED x shot was asked to open a host outside the run's allow list a goto to a host no allowHosts rule matches, refused before Page.navigate is sent. A request the PAGE makes to such a host is not this code — it is paused in the browser (Fetch.requestPaused), failed, and recorded in verdict.json as refused: "host" x shot /route --allow-hosts cdn.example.com — the app's own host is always allowed
X_SHOT_ISLAND_MISSING a declared picture is not on disk when the run ends the expected list is computed from the manifest BEFORE a browser exists, so the run diffs what it owed against what landed and refuses independently of the browser's own exit code each absent picture carries its own refusal above; re-run x shot --island <name> --json and read the first one
X_SHOT_ISLAND_STATES_EMPTY a *.island.states.ts exports no defineIslandStates result the file was found, imported and read, and it declares no picture — so the run photographs nothing and exits 0, which is the one outcome a reader cannot tell from success export const states = defineIslandStates({ island: '<path>', states: [] }) — in the file the cause names, with at least one state
X_SHOT_ISLAND_UNPHOTOGRAPHABLE the island never reached a state worth photographing one of eight assertions failed before the shutter: no probe, not the harness document, no host element, a mount that rejected or never finished, a page that never went quiet, a zero-sized box, a box with no children or text, or bytes under the floor. Asserting BEFORE capturing is what separates this from a screenshot script — a component whose fetch hangs paints its own loading branch and photographs as a real state the cause names which assertion failed; re-run with a longer settle window: x shot --island <name> --settle 8000 --json
X_SHOT_ISLAND_UNSTUBBED_REQUEST the component requested something no state stub answers the picture would show a fixture gap dressed up as a component state. Every address is sealed: an unmatched request is refused by name rather than allowed to hang routes: [{ match: 'GET /api/x', respond: { kind: 'json', body: {} } }] — on that state, in the states file
X_SHOT_KEY_INVALID a key chord the browser cannot press an empty chord, a trailing +, a modifier other than Meta/Control/Alt/Shift (Ctrl is refused), one held twice, or a key that is neither one character nor a named key. Parsed before any key goes down, so no modifier is left held { press: 'Meta+K' } — modifiers then one key, in the browser's names; or Control+Enter, Shift+Tab, Escape
X_SITEMAP_EXTRA_INVALID a seo.sitemap.extra path names no public page the path matches no registered route, a route that declares a policy, an api/ route, or a site/ page the sitemap already lists x routes --json # then list in seo.sitemap.extra only a path a registered app/ route without a policy answers
X_SLICE_POLICY_INCOMPLETE a generator needs an export the slice policy.ts does not declare x g action or x g mutator was pointed with --feature at a slice whose hand-written policy.ts does not export the names the generated file imports (can<Feature>Write, and for an action <feature>Tag). Refused before anything is written, because the generated file would not compile. A barrel or a nested destructuring the scan cannot read is never refused add the export lines the thrown fix: spells out for the slice — export const can<Feature>Write = can('<feature>:write'); and, for an action, export const <feature>Tag = tag('<feature>'); — to the slice's policy.ts, then run the generator again
X_SOCKET_HAND_ROLLED an app upgrades a websocket itself an app source file calls server.upgrade( or passes Bun.serve a websocket handler set, so the token check before the handshake, the per-actor cap, the heartbeat, the frame limit and the drain are the app's to remember, and the boot never serves the socket on the web listener x verify --only boundaries --json — names the file and line; delete the upgrade and declare the socket with deviceSocket({ path, resolveToken, onFrame }) from @ultimat3/realtime/server
X_STORAGE_SECRET_DEV upload grants would be signed with the shipped development key STORAGE_SIGNING_SECRET is unset or holds the constant published in @ultimat3/storage, in a non-local environment — anyone can then mint a PUT grant offline with a maxBytes and contentType of their choosing, and the signed constraints outrank the app's uploadPolicy. Reported by x doctor; the local disk driver also refuses to construct export STORAGE_SIGNING_SECRET="$(openssl rand -hex 32)"
X_STORAGE_UNWRITABLE the storage disk this process needs cannot be written to a hardened container (readOnlyRootFilesystem: true) with no writable volume at the embedded disk's root, or S3_ENDPOINT set with S3_BUCKET empty mount a writable volume at the path in the message, or set S3_ENDPOINT + S3_BUCKET to use object storage. x doctor --json shows which binding this process resolved
X_STREAM_ALREADY_FLUSHED a response header was written after the stream flushed setCookie(), deleteCookie() or setRedirect() ran inside a <Hole> on a render: 'stream' page, after the status and headers left with the first flush. The hole shows its error markup and the monitor hears it load: async () => { setCookie(name, value); return data; } in defineRoute, never under a <Hole>
X_SUPERSEDED_WORKAROUND a workaround the framework has since retired is still in the app a comment or doc note names a workaround for a feature that has since shipped x doctor --json — each finding names the file, the release that retired the workaround and its replacement
X_TEST_BUDGET_INVALID a test memory budget or worker cap env var does not parse ULTIMATE_TEST_MEMORY_BUDGET is not a size like 3g/512m, or ULTIMATE_TEST_MAX_WORKERS is not a positive integer ULTIMATE_TEST_MEMORY_BUDGET=3g x verify # or unset it; ULTIMATE_TEST_MAX_WORKERS takes a positive integer
X_TEST_FAILED a test type failed a red test the fix is the exact bun test … invocation the step ran
X_TEST_NO_FILES the test selection matched no files a type or --filter that matches nothing, or x test run outside the app drop the filter (x test), or point it at the right root: x test --cwd <repo root>. A green run over zero files is the most expensive false pass
X_TEST_SERVICES_UNAVAILABLE the live step's test database is not reachable and could not be started no test database answers at docker/test-services.env's TEST_DATABASE_URL with this app's credentials (nothing listens, or another app's database holds the port), and docker compose could not start one docker compose -f docker/docker-compose.test.yml up -d --wait
X_TEST_SHARD_FAILED a test shard exited non-zero registered, thrown by nothing since x test --worker was deleted. It was that flag's failure; one CI job's share of the suite is x verify --only unit --shard i/n, and a red test there or in x test is X_TEST_FAILED delete any branch matching this code, because it never runs. Match X_TEST_FAILED, whose fix is the rerun
X_TRUSTED_PROXY_HOPS_INVALID TRUSTED_PROXY_HOPS is not a whole number of proxies the boot accepts TRUSTED_PROXY_HOPS must be a whole number from 1 to @ultimat3/http's MAX_PROXY_HOPS (64): the count of proxies that append to x-forwarded-for in front of this process. A malformed count is refused rather than defaulted, because reading the header at the wrong index trusts a value the client typed. It was reported as X_PORT_INVALID ('is not a TCP port number') until 24.0.0 TRUSTED_PROXY_HOPS=1 ROLE=web bun apps/web/server.ts
X_TYPECHECK_FAILED tsc failed a type error anywhere in the workspace bunx tsc -b --pretty false
X_TYPESCRIPT_VERSION The app declares a TypeScript older than the one x new scaffolds a package.json's typescript range admits a compiler below the scaffold's TYPESCRIPT_VERSION (packages/cli/src/templates/scaffold-repo.ts); the framework's own source and .d.ts are checked by that compiler, so typecheck and build go red on files the app never wrote — x doctor and x upgrade name each lagging manifest x doctor --json — each X_TYPESCRIPT_VERSION finding names its manifest and the bun add that moves it
X_UI_DIFF_FILE_MISSING ui.diff was handed a capture that is not on disk a path from an earlier session, a .x/shot/ that was cleaned, or a typo in the slug x shot / --json, then diff the image path it answers — ui.shot's own answer lists the file it wrote
X_UI_DIFF_PATH_OUTSIDE ui.diff was handed a path that does not resolve inside .x/shot/ an absolute path, a .. segment, a sibling directory sharing the prefix's characters, or a symlink under .x/shot/ pointing out of it. The gate is what lets a file-reading tool sit under dev:read: it reads the captures the ui.* tools wrote and nothing else, so a read token cannot reach .env through a tool that says "diff" x shot / --json, then pass the image path it answers, relative to the app root
X_UI_DIFF_SIZE_MISMATCH ui.diff was handed two captures of different sizes two viewports, or fullPage on one and not the other — a page that grew is a taller picture. cause and meta name both sizes; nothing is compared photograph both at one viewport with one fullPage setting — ui.shot with the same viewport/width+height — then diff those two
X_UI_INTERACT_LEFT_APP a ui.interact step navigated off the dev server origin after a step, page.url()'s origin is not the dev server's — an external link clicked, an OAuth redirect followed. A same-origin navigation is allowed and reported navigated: true with the new URL; another origin is a page the picture cannot be of, and the step list stops there. meta.step and meta.url name the step and where it went x routes --json, then resend ui.interact with steps that stay on one of its paths
X_UI_INTERACT_SECRET_FIELD ui.interact refused to type into a password field a type step whose selector's first match is <input type="password">, checked BEFORE any keystroke: a filled password lands in the PNG in pixels, in the verdict's console and in the agent's transcript, and the scraping package already refuses a screenshot of a page a secret was typed into x shot --all-islands --json, or x shot --island <name> --json: a declared state renders the filled form without the secret ever being typed
X_UI_INTERACT_STEPS_INVALID a ui.interact step list is over its bounds or malformed more than 12 steps, a wait over 5000 ms or negative, a type.text over 500 chars, an empty selector or text, a step with zero or two keys, or a key that is no verb. Refused WHOLE and never trimmed: a step dropped changes what the picture is of, and an agent judging that picture would judge the wrong scene. The MCP schema (anyOf over five one-key shapes) catches the shapes first; the count and the lengths are the handler's, because the validator enforces no maxItems x help shot --json, then resend ui.interact with at most 12 one-key steps, type.text under 500 chars and wait under 5000 ms
X_UI_INTERACT_STEP_FAILED a ui.interact step raised a scraping error the driver refused the step — X_SHOT_ELEMENT_MISSING for a selector that never matched, X_SHOT_ELEMENT_UNREADY for one that never became actionable, X_SHOT_KEY_INVALID for a chord it cannot spell. Wrapped rather than passed through so the cause names WHICH step (step 3 (click "#nope"): X_SHOT_ELEMENT_MISSING — …) and meta.step / meta.code carry it structurally; the driver's own error is sourceError x routes --json, then run ui.inspect on the route first and copy a selector it reports with count >= 1
X_UI_SHOT_ROUTE_UNBUDGETED a ui.* tool (ui.shot, ui.inspect, ui.interact) refused a route that declares no budget.js a picture of a route nobody has finished declaring is a picture of a draft — the gate refuses the same route as X_BUDGET_UNMEASURED, and an agent judging the picture would judge the wrong thing budget: { js: '<n>kb' } — in the route file, then x build --target static --json && x verify --only budgets --json
X_UI_SHOT_ROUTE_UNKNOWN a ui.* tool (ui.shot, ui.inspect, ui.interact) was asked for a path no route in this app answers a typo, a route that has not been declared yet, or a full URL where a path was expected x routes --json, then call the ui.* tool with one of its path values
X_UPGRADE_CODEMODS_PENDING files an older x upgrade left for codemods an x upgrade driven by a CLI older than the codemod engine installed this release but applied none of its codemods, so scaffold files are still in their older form x upgrade --json
X_UPGRADE_DIRTY_TREE x upgrade refused a tree with uncommitted changes git status reports changes, or the directory is not a git repository: a hop must be one reviewable commit, and git is the only state between runs git status --short — then commit or stash, and re-run: x upgrade --json
X_UPGRADE_GATE_UNREADABLE the installed x verify answered with no JSON report the CLI this hop installed exited without one document on stdout: it crashed at import, or is not at node_modules/@ultimat3/cli. The hop is not done bun node_modules/@ultimat3/cli/src/bin.ts verify --json
X_UPGRADE_HOP_TOO_WIDE x upgrade --to is outside the one hop a run may make the version skips a major, or sits below what the app already pins: each hop gets its own gate so a red one names its own major x upgrade --to <next major's newest> --json
X_UPGRADE_INSTALL_FAILED bun install failed after x upgrade wrote the pins bun install exited non-zero: a package that no longer exists at the target version, a peer conflict, or the network. The pins and Bun floor are written and uncommitted git restore . — undoes the pins, since the tree was clean; then fix what the cause names and re-run: x upgrade --json
X_UPGRADE_LOCKED another x upgrade holds this app a second x upgrade started while one held .x/upgrade.lock, or the lock could not be claimed because .x/ is not writable ps -p <pid>
X_UPGRADE_MIXED_PINS x upgrade found two @ultimat3/* versions across the workspaces the framework moves in lockstep, so a hop from a mixed set has no one starting version x upgrade --to <the lowest pins' next major> --json — one hop per run until the set is level
X_UPGRADE_PIN_UNREADABLE x upgrade found an @ultimat3/* dependency that names no version a workspace:, file:, link:, catalog: or tag spec, or no @ultimat3/* dependency at all: there is nothing to hop from x upgrade --json — after editing the package.json the cause names, so every @ultimat3/* carries a version
X_UPGRADE_REGISTRY_UNREACHABLE x upgrade could not read the published versions from npm bun pm view failed: no network, a proxy, or a registry that refuses the request. Nothing was written bun pm view @ultimat3/cli version — once this answers, re-run: x upgrade --json
X_UPGRADE_VERSION_UNPUBLISHED x upgrade --to names a version npm does not have the version is not in the list npm publishes for @ultimat3/cli. Nothing was written bun pm view @ultimat3/cli versions --json — then: x upgrade --to --json
X_VERIFY_E2E_BROWSER_MISSING a floored e2e step found no browser to drive x.verify.json requires the e2e step and no Chrome or Chromium was found, so every browser-backed e2e test skipped curl -fsSLo /tmp/google-chrome.deb https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb && sudo apt-get install -y /tmp/google-chrome.deb
X_VERIFY_FAILED one or more verify steps failed the gate is red x verify --json — every step's findings arrive in one run
X_VERIFY_MERGE_INCOMPLETE x verify merge was handed parts that do not add up to the whole gate a gate step is missing, a shard of a split step is missing or duplicated, or two shards counted different corpora x verify merge parts/*.json --json # after every CI job uploaded its part
X_VERIFY_MERGE_INPUT a part handed to x verify merge is not an x verify --json document the file is missing, empty, not JSON, or not the output of x verify --json x verify --only --json > part.json # one document per part
X_VERIFY_SHARD_INVALID x verify --shard was given a spec or a step list it cannot split the spec is not i/n with 1<=i<=n, --only is missing, or --only names a step that is not unit, contract or job x verify --only unit --shard 1/4 --json
X_VERIFY_SKIPS_OVER_CEILING a step skipped more tests than its skipCeiling allows the suite skipped more tests than x.verify.json skipCeiling states for the step, so most of it did not run x test unit --json — then set what the skipped tests need, or raise skipCeiling in x.verify.json with the reason in the diff
X_VERIFY_STEP_TIMEOUT a gate step ran past its deadline and was stopped A step of x verify did not finish within its deadline (5 minutes for a check, 8 for a test suite, or the step's own stepTimeoutMs entry in x.verify.json). The step is failed by name and every process it started is killed, so a hung step cannot consume a CI job's whole timeout and leave no trace. When a bun test was in flight, the finding names the file(s) still running — the ones bun test reports its killed workers were holding (at, meta.inFlight[].stuck) and the killed processes (meta.killed), and its fix: is bun test <file>. A batched step that had finished runs (meta.finished) and whose in-flight runs were no older than twice the slowest finished one (meta.inFlight[].runningMs) was not hung: the finding says it outgrew its deadline at this width, and its fix: reruns it wider (--only <step> --workers <n>) or raises its stepTimeoutMs entry x verify --only unit --json — reproduce the step alone; a step that legitimately needs longer states it under "stepTimeoutMs" in x.verify.json
X_VERIFY_STEP_UNFLOORED A gate step applies to this app but x.verify.json does not floor it the step has suite files or committed input here, and x.verify.json "steps" does not hold it, so a deleted suite reads as skipped and the gate stays green x doctor --json — its X_VERIFY_STEP_UNFLOORED fix names the steps: run that x verify --only, then add each step that passed, not skipped, to "steps" in x.verify.json
X_VERIFY_STRICT_UNRUN x.verify.json is strict and a step ran no check with no written why x.verify.json sets strict: true and a step ran no check (it did not apply, or its suite skipped every test) with no skip entry giving the reason x verify --json # data.skipReasons names each step that ran no check: give it a suite, or write "skip": { "<step>": "<why>" } in x.verify.json
X_VERIFY_SUITE_VANISHED a step the committed floor requires had nothing left to check x.verify.json names a step this repo already ran and the step found nothing — either its suite was deleted (the step reports as skipped) or every test in the files it did find skipped itself, which applies cannot see and only bun test's own summary reports. Both are a green gate over an unrun suite restore the suite or set what it skips without (TEST_DATABASE_URL for live), or delete that name from x.verify.json in the commit that says why — then x verify --json
X_WORKER_QUEUE_UNKNOWN WORKER_QUEUES names a queue no job and no jobs.queues entry declares a typo, or a pattern (banks-*) the app meant to expand before the worker read it — the worker would claim a queue nothing is ever enqueued on and leave the real ones waiting x jobs list --json # set WORKER_QUEUES to queues it lists, or add the queue to jobs.queues in app.config.ts
X_WORKSPACE_DEP_UNDECLARED a workspace imports another workspace its own package.json does not declare an import added long after the scaffold, or a generator that emitted the import and not the edge. The graph then exists only inside tsc — affected-package detection, bun --filter ordering and blast radius all read manifests, and a missing edge makes each of them silently answer too small a set. 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 { "dependencies": { "@demo/web": "0.0.0" } } — the finding carries the manifest path and the exact entry; merge it into that package.json
X_WORKSPACE_EXTERNAL_DEP_UNDECLARED a workspace imports a registry package that neither it nor the app root declares a workspace imports a package only a sibling workspace declares; it resolves through the hoisted node_modules until a clean or filtered install stops hoisting it bun add <package> --cwd <workspace> — the package-shape finding names both
X_WORKSPACE_NAME_TAKEN x g app or x g package was given a name the other workspace kind already holds apps/ and packages/ are both named @/, so a second workspace under one name is two packages bun install cannot tell apart x g app admin-app --dry-run --json

Notes

Encrypted secrets

One committed file, secrets.enc.json, sealed with AES-256-GCM under a 32-byte master key read from ULTIMATE_SECRETS_KEY first and the gitignored .secrets.key second. Values are decrypted into the process environment by installSecrets() and read back through the app's own envSchema — a secret is an env var, so it has one declaration, one mask and one reader. See CLI reference for x secrets.

The envelope carries a key id: a domain-separated, truncated SHA-256 of the master key, safe to commit. It is what makes "you used the wrong key" and "this file was edited after it was sealed" two different codes instead of one unexplained decryption failure.

Clone this wiki locally