@jterrazz/test 16.1.0 → 17.0.0

package/docs/decisions/001-v9-conventions-on-three-channels.md

@@ -1,50 +0,0 @@
-# ADR-001: v9 — conventions enforced on three channels
-
-**Status:** Accepted
-**Date:** 2026-07-17
-
-Retroactive record, written 2026-09-04 from the v9 design lock (2026-07-17)
-and the `@jterrazz/test@9.0.0` ship (2026-07-18, after a multi-agent review
-campaign). Moved into this repository 2026-09-06, from the OS wiki where it
-was ADR-003 — this package alone can falsify it, and the normative spec was
-always here.
-
-## Context
-
-Testing conventions lived in prose and review habits; every consumer repo
-drifted its own way, and partial assertions ("status is 200") hid silent
-failures.
-
-## Decision
-
-v9 is specification-first: three constructors (`specification.api/jobs/cli`),
-one `{{token}}` grammar across every fixture kind, and golden files (`.http`
-_requests/responses, full-output text snapshots) as the default assertion — a
-partial probe must earn its place as a deliberate scalpel.
-
-Crucially, every convention is enforced on one of THREE channels, or
-documents why it cannot be:
-
-1. **Static** — oxlint rules living IN this package, so a rule versions with
-   the API it describes, wired by `@jterrazz/typescript` through composable
-   presets (`compose(node, testing)`).
-2. **Meta-tests** — executed truths: every token matcher tested both ways,
-   update-mode fixtures re-verified on the next run.
-3. **Runtime** — strict errors: an outbound request with no matching intercept
-   fails the spec.
-
-Any newly discovered defect class must, in the same change, produce a rule on
-one of the channels — the package's "rule K".
-
-## Consequences
-
-- Product specs live under `specs/<facet>/<domain>/`; unit tests are siblings
-  of their module. A consumer's own conventions derive from this package,
-  except where its doctrine states a more specific shape — the first such case
-  is jterrazz-os's `docs/decisions/006-cli-specs-mirror-the-command-tree.md`.
-- Migrations proved the value immediately: strict intercepts caught a real
-  production-class bug in a consumer (an undrained handler), and dead test
-  layers were deleted by the dead-fixture checker.
-- The docs are code: each rule's normative text lives in its implementation's
-  metadata and the catalog is generated — hand-synced convention documents are
-  banned by construction.

package/docs/decisions/002-the-statique-channel-holds-only-what-upstream-does-not.md

@@ -1,49 +0,0 @@
-# ADR-002: the statique channel holds only what upstream does not
-
-**Status:** Accepted
-**Date:** 2026-09-15
-
-## Context
-
-The statique channel grew by writing a rule for every mechanizable convention,
-without asking whether oxlint already carried one. Four hygiene rules ended up
-restating rules of oxlint's own `vitest` plugin — J1 (`.only`/`.skip`), J3 (an
-assertion per test), J4 (unique literal titles), J5 (a lowercase title).
-
-That cost nothing while the plugin was off. `@jterrazz/typescript` v10 turns it
-on over the test globs in every profile, so a consumer composing
-`compose(node, testing)` gets both layers: one violation reported twice, two
-ids to suppress, and two normative sentences that have to be kept in step by
-hand — the drift this package's docs-as-code inversion exists to prevent.
-
-## Decision
-
-A convention an upstream oxlint rule already enforces belongs to that rule. The
-statique channel holds only the residue: what no loaded plugin carries.
-
-Equivalence is proved before a rule is deleted, on this package's own fixtures
-and on both the installed oxlint and the version the preset pins — every
-invalid sample of the rule's test must fire the upstream rule, and every valid
-sample must stay silent. A rule that catches something upstream misses is kept
-and narrowed to that residue.
-
-The four were proved equivalent and deleted (`vitest/no-focused-tests` +
-`vitest/no-disabled-tests`, `vitest/expect-expect`, `vitest/no-identical-title`,
-`vitest/prefer-lowercase-title`). J2, the arbitrary-sleep ban, has no upstream
-counterpart and stays.
-
-## Consequences
-
-- Breaking for consumers: `jterrazz/j1-no-only-skip`,
-  `jterrazz/j3-no-expectless-test`, `jterrazz/j4-unique-test-names` and
-  `jterrazz/j5-lowercase-title` no longer exist, and a config still naming one
-  fails oxlint's unknown-rule check.
-- The hygiene floor now reaches this package only through the base preset. A
-  repository that adopts the conventions without `@jterrazz/typescript` wires
-  `plugins: ['vitest']` itself — the catalogue chapter says which rules.
-- One behaviour is configuration, not code: `prefer-lowercase-title` flags an
-  all-caps first word (`VALID_CATEGORIES`, `HTTP`, `DI`) that J5 exempted, and
-  `allowedPrefixes` restores the exemption.
-- The rule of growth changes with it. A new mechanizable defect class (K1) is
-  now searched for upstream first, and a rule is written here only where the
-  search comes back empty.

package/docs/decisions/003-a-rendered-component-is-a-facet-on-vitest-browser-mode.md

@@ -1,84 +0,0 @@
-# ADR-003: A rendered component is a facet, on Vitest Browser Mode
-
-**Status:** Accepted
-**Date:** 2026-09-19
-
-## Context
-
-The estate tested its UI in two dialects at once. A page spec said
-`click(link('Articles'))` against a real Chromium and goldened what the page
-MEANT; beside it, in the same repository, a component test said
-`render / screen / fireEvent / waitFor` against `happy-dom` with a scripted
-`fetch`, and goldened nothing. Same product, same reader, two vocabularies —
-and the second proves the least of the two, because the thing it renders never
-met a browser.
-
-The corpus had sanctioned that split. `docs/18-conventions.md` and the agent
-skill both said a component test "needs vitest alone", on the ground that the
-framework is for a SURFACE and a component has none. The reading was wrong in
-one word: a component has no surface it is SERVED through, but it needs
-everything the framework owns — a real browser, a Vite pipeline, a network
-double, a golden engine, an element vocabulary. Rule I2's own message had been
-saying so all along: "a test needing more than its module is a specification".
-
-What forced a decision now is that the estate has a UI to migrate (a console's
-42 tests, a browser extension's DOM renderer, a web app's string renderer) and
-every one of them would otherwise be written a third time.
-
-## Decision
-
-A rendered component is a FACET of `@jterrazz/test`, running in Vitest Browser
-Mode on the `playwright` peer the website facet already drives.
-
-It is the facet with **no constructor**. A component starts nothing — no
-server, no database, no binary, no simulator — so there is no handle to
-destructure and no `*.specification.ts` to hold it. The chain is exported
-directly (`component.intercept(…).wrap(…).render(<X />, scenario)`), and what
-every render of a project shares belongs to the PROJECT: `component()` in
-`vitest.config.ts`.
-
-Its test file sits **beside its subject**, as a module test does, and the
-suffix states the kind: `<file>.test.ts` is a module, `<file>.test.tsx` is a
-component. `unit()` excludes `.test.tsx`; `component()` collects exactly those.
-
-The package keeps **one specifier**. A page cannot load the node entry, so
-`exports["."]` gains a `browser` condition resolving to a second build of the
-same surface, in which every node-only name is a stub that throws where it was
-called. The split is the runtime's, never the facets'.
-
-Weighed and rejected:
-
-- **A Node-side gallery** — Playwright driven from the test process, one
-  browser context per render. Measured at ~15 s against 0.6–1.1 s per file for
-  Browser Mode, and it needs an undeclared `vite` to build what it serves.
-- **Playwright Component Testing** — a second runner beside vitest, with its
-  own config, its own reporters and its own assertion library. The estate has
-  one runner on purpose.
-- **`happy-dom` + Testing Library** — the status quo. Two vocabularies, and the
-  cheaper one is the one that proves least.
-- **A second specifier, `@jterrazz/test/browser`** — considered and dropped: it
-  makes every test file remember which entry it may import, and needs a rule to
-  enforce the memory. One specifier and a condition costs nothing at the call
-  site.
-
-## Consequences
-
-- `happy-dom`, `jsdom` and `@testing-library/*` leave the estate's test
-  vocabulary. Rules E5, E5b, F6 and G4 refuse them and name the move; E6
-  refuses a hand-rolled `browser:` project, because the provider pin, the
-  service worker, the JSX transform and the cold-cache pre-bundling are four
-  ways for a run to pass here and fail on the next machine.
-- A component spec and a page spec now read alike: same descriptors, same
-  verbs, same W3 ambiguity refusal, same ARIA-tree golden in the same dialect.
-  The vocabulary gains what a rendered surface needs and a page lacked —
-  `gone`, `focused`, and five role descriptors.
-- A consumer takes on optional peers it did not have (`@vitest/browser-playwright`,
-  `vitest-browser-react`, `vite`, `react`), and one hard constraint with them:
-  the provider peers vitest on an EXACT version, so the two move in one change.
-- CI pays for a second Chromium project. `sequence.groupOrder` keeps it from
-  sharing a slot with the website project on a two-vCPU runner.
-- React Native stays out: Browser Mode does not run it. `.astro` pages stay
-  website specs; only islands are components.
-- The package's own suite grows a component tree that is NOT under `_fixtures/`
-  — ground is what a spec stands on from a distance, and here the spec stands
-  next to it.

package/docs/decisions/004-a-module-against-real-services-or-a-golden-is-the-integration-facet.md

@@ -1,81 +0,0 @@
-# ADR-004: A module against real services, or against a golden, is the integration facet
-
-**Status:** Accepted
-**Date:** 2026-09-19
-
-## Context
-
-The fork the corpus drew had two rungs: a module alone, tested beside its code
-with no runner, and the assembled product behind an entry — HTTP, a binary, a
-served page, a screen — specified through `specification.*`. A whole kind of
-test fell between them, and every repository invented its own answer for it.
-
-A module that needs a real database is one. signews-api kept a
-global-setup file that built a sqlite template by hand and a project named
-"integrations" running plain vitest, because no constructor covered "this
-repository function, against the real schema". package-broadcast and
-package-analytics did the same with a root tests folder and `vi.mock`.
-
-A module whose oracle is a GOLDEN is the other. package-attestation's byte
-contracts and package-intelligence's fifty-three input/output pairs are
-golden-file tests, and both reached for `toMatchSnapshot` — a second golden
-mechanism, with no token grammar, no `{ frozen }`, and no `TEST_UPDATE=1`,
-living beside the one the package owns. Rule D20 could ban the matcher only
-once the tests it serves had somewhere to go.
-
-Neither case needed a new idea. Both needed a constructor.
-
-Three shapes were weighed and refused:
-
-- **Widen `jobs`.** `trigger(name)` takes no input and a job is
-  `() => Promise<void>`, so the Given would have to leave the test and live in
-  the specification file. A spec whose input is elsewhere is not a spec.
-- **Plain vitest under a folder named for it.** The shape every repository had
-  already reached, and the shape the evidence indicts: the services are
-  hand-started, nothing resets between tests, and the goldens are somebody's.
-- **`sqlite()` outside a runner.** A second lifecycle path for services — two
-  answers to "when does this start and who stops it", which is the defect the
-  orchestrator exists to prevent.
-
-## Decision
-
-`specification.integration({ services?, root? })` is the eighth kind of test
-and the sixth constructor. Its subject is a MODULE; its terminal action is
-`.call((services) => …)`, which hands the started record to the subject so it
-is built with real connection strings; its result is `CallResult`.
-
-`CallResult` has two readings and never both: `value` is what the call
-returned — a `TextAccessor` for a string, a `JsonAccessor` for anything else —
-and `error` is what it threw, as text, empty when it returned. Both are the
-package's ordinary accessors, so `toMatch`, the `{{token}}` grammar,
-`{ frozen }` and `TEST_UPDATE=1` reach them with no new mechanism.
-
-The setups are the ones every facet already has: `.seed()`, `.intercept()`,
-`.clock()`. Without `services` the constructor starts nothing: that is the
-golden-only half, and it is the whole of what a fifty-three-row table needs —
-one `.call()` inside `test.each`.
-
-## Consequences
-
-- **A refusal is a reading.** No `try`/`catch` in a spec, and no "it should
-  throw" test that passes because nothing threw. A chain says "and it did not
-  refuse" with `await expect(result.error).toBeEmpty()`.
-- **D20 gains its destination.** `toMatchSnapshot` can be banned because every
-  test it served now has a facet, a folder and a golden engine.
-- **One more folder name is spoken for, and no unowned one is added.**
-  `specs/integration/` is a facet folder: singular, like `website/`, and
-  holding a `*.specification.ts` at its root. The package renamed its own
-  plural folder in the same change. What lived there — probes of the container
-  adapters themselves — became integration specs under
-  `specs/integration/<seam>/`: an adapter met against a real service IS a
-  module against a real service. Folder = constructor holds for the package
-  too, so no probe earns a folder under `specs/` that no constructor owns, and
-  what a probe cannot reach through the public entry is a module test beside
-  its module (rule F3).
-- **An env-gated sub-suite stops being a project.** With `{ include, exclude }`
-  on the helper, package-attestation's five projects become `unit()` plus one
-  `integration()`.
-- **A door closed.** A module test may not carry a golden (D20) and an
-  integration spec may not assert only on doubles: the ladder's rungs are now
-  distinguishable by where the test lives, which is what makes both
-  mechanizable.

package/docs/decisions/005-the-doubles-ladder-is-closed.md

@@ -1,86 +0,0 @@
-# ADR-005: The doubles ladder is closed, and a ban an upstream rule can carry is an option, not a rule
-
-**Status:** Accepted
-**Date:** 2026-09-19
-
-## Context
-
-Two questions had no written answer, and the estate's tests answered them
-differently in every repository.
-
-**What may stand in for the real thing?** The measured failure mode is not
-subtle: a survey of the workbench found seven files replacing `fetch` with
-`vi.stubGlobal`, thirteen importing `vitest-mock-extended` directly, sixteen
-calling `vi.mock` on a module, two declaring `msw` themselves, five using
-`toMatchSnapshot`. Every one of them is a substitute chosen because nothing
-said which substitute to reach for first. Agents make this worse rather than
-better — the published measurements put a third of agent-written test commits
-at "adds a mock", and nearly all of those at "mocks everything".
-
-**Who owns a ban?** ADR-002 settled that a convention oxlint's own `vitest`
-plugin already enforces belongs to that plugin, and four hygiene rules left the
-`jterrazz/*` channel on that ground. It did not settle the case where the
-upstream rule exists but is inert without OPTIONS —
-`vitest/no-restricted-matchers` bans nothing until it is told which matchers,
-`vitest/no-restricted-vi-methods` until it is told which methods. Those options
-are a convention, and they had nowhere to live.
-
-Two shapes were weighed and refused. Writing a `jterrazz/*` rule for each ban
-duplicates an upstream rule that already does the work, which is exactly what
-ADR-002 forbids. Asking `compose()` to MERGE options across fragments is a
-toolchain change with no other caller, and it would make two owners of one
-rule's configuration.
-
-## Decision
-
-**The ladder is closed and ordered.** An agent takes the first rung that fits:
-
-1. **The real thing**, in-process — a pure module, a Hono app handed to
-   `server`, a component mounted in a real Chromium.
-2. **A declared service** — `sqlite()`, `postgres()`, `redis()`, `process()`:
-   real, isolated per worker, reset per chain.
-3. **A contract** — `.intercept()` on a chain, `intercept()` in module scope;
-   msw's server, msw's worker, or the `node:http` stub, all over one queue;
-   strict from the first contract.
-4. **A typed port double** — `mockOf<Port>()`, or `vi.fn<Fn>()` for a
-   function-shaped dependency.
-
-Nothing else is a rung. `vi.mock`, `vi.stubGlobal`, a raw `msw` import, `nock`,
-`sinon`, `jest` and `mockdate` are not lower rungs; they are off the ladder,
-and each has a named destination.
-
-**A ban an upstream vitest rule can carry as an OPTION is set from the
-`testing` fragment**, and the rulebook marks that rule `covered` so one owner
-states it. A ban a CORE rule would carry — `no-restricted-imports`,
-`no-restricted-globals` — stays a `jterrazz/*` rule, because an oxlint override
-REPLACES a rule's options rather than merging them, and three toolchain owners
-already set those two.
-
-This extends ADR-002: the option mechanism is this record's, the principle it
-serves is that one.
-
-## Consequences
-
-- **The ladder is citable.** "Use a contract, not a stubbed `fetch`" is a rung
-  number, not an opinion, and each ban's message names the rung above it.
-- **`mockOf` earns its place on rung four.** It pins
-  `vitest-mock-extended`'s range on the consumer's behalf, which is why the
-  consumer is forbidden to declare it. Its `{ deep: false }` form exists so
-  rung four does not push a test back down to a hand-written object.
-- **A mandatory type argument is not expressible.** `mockOf<T extends object>()`
-  has no default, but TypeScript falls back to the CONSTRAINT where no
-  inference site says otherwise, so `mockOf()` compiles and answers for
-  `object`. The refusal lands where the double is used — it is assignable to
-  no port — rather than where it was made. Stated rather than worked around: a
-  cast or a never-typed overload would buy the earlier error with a worse
-  signature.
-- **Three bans move upstream.** `no-restricted-matchers` (the snapshot
-  matchers), `no-restricted-vi-methods` (`stubGlobal`, the timer methods) and
-  `max-nested-describe` are configured, not reimplemented. They turn on in the
-  toolchain release that follows the package's next major.
-- **`vi.mock` keeps one door.** A native module a consumer cannot inject is
-  allow-listed per specifier, with a reason, and the allow-list is the
-  repository's — not a silent exception.
-- **A cost accepted.** Two channels now state bans: the fragment's options and
-  the `jterrazz/*` rules. The catalogue carries both, with `upstream` as a
-  channel value, so a reader still finds one list.

package/docs/decisions/006-the-catalogue-reaches-a-file-by-its-role.md

@@ -1,245 +0,0 @@
-# ADR-006: The catalogue reaches a file by its role, states its reach, and is born on a count
-
-**Status:** Accepted
-**Date:** 2026-09-20
-
-## Context
-
-The catalogue of 15.x held sixty-odd rows and could not answer three questions
-a reader asks of any one of them: which files does this reach, what do I do
-about it, and what proves it is true.
-
-**Reach was a path segment.** Five rules gated on `parts.includes('specs')` or
-`includes('src')` — I2, I4, J2, d12w, d15w — and each of them drew the line in
-a slightly different place. The consequences were not theoretical: a sleep in a
-module test beside `src/` was invisible to J2, while the same sleep two folders
-away failed a build; a repository's consistency suite was an "orphan module
-test" to I2 because it sat under a folder called `specs`. The gate was also
-unreadable: nothing in a row said which files it judged, so the only way to
-find out was to read the implementation.
-
-**A row could not say what to do.** A ban with no destination is an argument
-rather than a rule, and forty-odd messages ended on `see docs/19-linting.md`
-with no fragment — a route to a chapter, not to a row. Nothing failed when a
-heading moved, so the routes rotted silently.
-
-**Nothing said which pass a finding came from.** The manifest's `channel` field
-was a union a row could name loosely, and three of the seven values (`type`,
-`meta`, `upstream`) had no rows at all: the conventions they stood for were
-held by tests nobody could find from the catalogue, or by nothing.
-
-**And a row could be born out of nothing.** The A-family's `allowedPrefixes`
-story is the warning: a rule shipped at `error` on a shape no consumer had ever
-been run against, and every consumer paid for it.
-
-## Decision
-
-### One gate, by role
-
-**One gate, by ROLE.** `roleOf(file)` returns `{ role, inSpecs, legacyDir }`,
-and the role is read from the SUFFIX: `.specification.ts(x)`, `.spec.yaml`,
-`.spec.ts`, `.test.tsx`, `.test.ts`, `vitest.config.*`, a ground ancestor, a
-`contracts/` ancestor. A statique rule reads those three fields and, where it
-must know where the file sits, the ONE package-bounded anchor every pass shares
-(`specsAnchor` in `src/lint/ast.ts`) — never a bare path segment. The rules
-that need it say so: C1, C4, C8, C13, F2, F3, I1, I4. Walking a TREE is the
-checker's — C1's depth, C12, C18, C20, C21w.
-
-### A row says what it reaches, and what to do
-
-**Every row states its REACH and its FIX**, both required by the type, and the
-fix is one imperative line the message carries too.
-
-### Seven channels, each answering for its rows
-
-**Seven channels, one per row** — `statique`, `upstream`, `checker`, `runtime`,
-`type`, `meta`, `process` — and each channel answers for its rows the way that
-channel can: a rule file and a fixture pair, an assertion on the resolved
-option, a bundled pass, a `// RUNTIME <ID>` marker above the spec that drives
-the refusal, an `@ts-expect-error` in `src/type-channel.test-d.ts`, a named
-meta-test. One meta-test holds that contract for all seven.
-
-**English, and anchored.** Every sentence the catalogue publishes is English
-(K5 holds the line with a deny-list of the tokens the manifest actually
-carried), and every message the PLUGIN ships ends with a generated
-`(<ID> — <chapter>#<rule>)` tail whose anchor is asserted to exist (K3). A
-checker finding carries its id and its chapter; several of its passes report
-under a family code (`d4`, `d4b`, `d10w`) rather than a row name, so the tail
-routes to the chapter and the id says which row.
-
-### A row is born on a count
-
-**A row is born on a COUNT.** A rule is written when its defect class has been
-seen once and its criterion is decidable. A class nobody has seen is a backlog
-line with its criterion written, coded on its first occurrence. The R8 dry run
-— the whole catalogue run over every clone of the workbench, read-only — is
-what settles which of the two a row is, and it is re-run whenever a criterion
-changes. The counts below are the run of 2026-09-20, re-run after the fix pass
-that bounded six false classes: 27 clones plus the estate's own `apps`,
-`packages` and `specs`, with each package's own violation FIXTURES excluded —
-they violate on purpose, and counting them would let a rule justify itself.
-`jterrazz-web-astro-react` and `signews-web-astro` are not repositories: they
-are clones of `jterrazz-web` and `signews-web` checked out on a merged
-experiment branch, counted here as the folders the run walked.
-
-| rule                          | total | where                                                                                                                                                                                                                                                                                                                                 |
-| ----------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `b4-given-then`               | 2569  | jterrazz-design 902, signews-mobile 532, archive 419, hoverfly-lsp 246, extensions 216, package-attestation 144, spwn 104, package-typescript 4, package-test 2                                                                                                                                                                       |
-| `b11-marker-one-line`         | 240   | package-test 160, signews-api 40, hoverfly-lsp 13, jterrazz-web-astro-react 5, jterrazz-web 5, archive 4, package-typescript 4, spwn 4, jterrazz-studio 3, jterrazz-os 2                                                                                                                                                              |
-| `i2-sibling-test-naming`      | 224   | archive 169, signews-mobile 35, hoverfly-lsp 15, package-typescript 2, jterrazz-design 1, package-test 1, spwn 1                                                                                                                                                                                                                      |
-| `c12-spec-file-name`          | 180   | spwn 40, package-test 37, jterrazz-web 22, jterrazz-web-astro-react 21, signews-api 15, package-typescript 9, signews-mobile 8, jterrazz-os 6, package-attestation 6, package-intelligence 3, signews-web 3, jterrazz-design 2, jterrazz-studio 2, spwn-web 2, cap01 1, package-analytics 1, package-broadcast 1, signews-web-astro 1 |
-| `j6w-given-in-the-test`       | 165   | archive 54, package-test 41, signews-api 19, package-typescript 17, hoverfly-lsp 14, jterrazz-os 6, spwn 6, package-telemetry 4, signews-mobile 2, package-analytics 1, package-intelligence 1                                                                                                                                        |
-| `d16w-ambient-value`          | 57    | signews-api 36, package-test 10, archive 6, hoverfly-lsp 2, jterrazz-os 2, signews-mobile 1                                                                                                                                                                                                                                           |
-| `e9w-env-assignment-in-test`  | 49    | package-test 47, jterrazz-os 2                                                                                                                                                                                                                                                                                                        |
-| `d18w-existence-only-oracle`  | 37    | package-test 14, hoverfly-lsp 10, archive 4, package-intelligence 2, signews-mobile 2, jterrazz-os 1, jterrazz-web-astro-react 1, jterrazz-web 1, package-typescript 1, signews-api 1                                                                                                                                                 |
-| `c1-domain-structure`         | 33    | jterrazz-os 26, package-typescript 7                                                                                                                                                                                                                                                                                                  |
-| `c18-module-test-under-facet` | 31    | package-typescript 27, jterrazz-web 2, spwn 2                                                                                                                                                                                                                                                                                         |
-| `i4-no-module-doubles`        | 23    | signews-mobile 13, archive 5, package-intelligence 2, jterrazz-web 1, package-typescript 1, signews-api 1                                                                                                                                                                                                                             |
-| `d19w-probe-cluster`          | 22    | package-typescript 7, spwn 6, jterrazz-os 3, jterrazz-web 3, archive 2, jterrazz-web-astro-react 1                                                                                                                                                                                                                                    |
-| `f2-no-test-imports-in-prod`  | 21    | package-test 13, jterrazz-design 3, archive 2, package-manifest 2, hoverfly-lsp 1                                                                                                                                                                                                                                                     |
-| `e3-config-present`           | 17    | archive 16, extensions 1                                                                                                                                                                                                                                                                                                              |
-| `d12w-response-body-probe`    | 14    | signews-api 9, archive 5                                                                                                                                                                                                                                                                                                              |
-| `d15w-status-only-probe`      | 14    | package-test 4, archive 3, jterrazz-os 3, jterrazz-web-astro-react 2, jterrazz-web 1, signews-api 1                                                                                                                                                                                                                                   |
-| `d5w-spec-pinned-value`       | 10    | jterrazz-os 9, package-test 1                                                                                                                                                                                                                                                                                                         |
-| `d8w-text-bypass`             | 9     | jterrazz-web-astro-react 3, jterrazz-web 3, archive 2, spwn 1                                                                                                                                                                                                                                                                         |
-| `c9-dead-fixtures`            | 8     | package-test 7, spwn 1                                                                                                                                                                                                                                                                                                                |
-| `d17w-double-only-oracle`     | 8     | signews-api 4, signews-mobile 4                                                                                                                                                                                                                                                                                                       |
-| `j2-no-sleep`                 | 8     | package-test 3, archive 2, jterrazz-os 1, signews-mobile 1, spwn 1                                                                                                                                                                                                                                                                    |
-| `w5w-scenario-settles`        | 8     | package-test 4, cap01 1, jterrazz-web-astro-react 1, jterrazz-web 1, signews-mobile 1                                                                                                                                                                                                                                                 |
-| `a1-specification-file`       | 7     | package-test 7                                                                                                                                                                                                                                                                                                                        |
-| `e2-preset-config`            | 6     | package-test 3, spwn 2, archive 1                                                                                                                                                                                                                                                                                                     |
-| `c21w-ground-owned-by-one`    | 5     | spwn 2, jterrazz-web-astro-react 1, package-attestation 1, signews-api 1                                                                                                                                                                                                                                                              |
-| `d5-spec-volatile-literal`    | 3     | package-test 3                                                                                                                                                                                                                                                                                                                        |
-| `e7w-include-prefix-exists`   | 3     | spwn 2, package-test 1                                                                                                                                                                                                                                                                                                                |
-| `f5-fixtures-only-from-tests` | 3     | jterrazz-design 3                                                                                                                                                                                                                                                                                                                     |
-| `f8-no-seam-dependency`       | 3     | archive 1, jterrazz-design 1, spwn 1                                                                                                                                                                                                                                                                                                  |
-| `b10-when-between-markers`    | 2     | archive 1, spwn 1                                                                                                                                                                                                                                                                                                                     |
-| `e4w-project-binding`         | 1     | package-test 1                                                                                                                                                                                                                                                                                                                        |
-| `f6-no-foreign-test-runtime`  | 1     | signews-web 1                                                                                                                                                                                                                                                                                                                         |
-
-Four rows were at zero with no new surface to be the boundary of, and the gate
-moved them to the backlog with their criteria written: **B12** (a marker inside
-a declarator chain), **C19** (backend ground under a screen facet — the
-component facet that was its reason stopped being a folder when component tests
-became colocated), **D21w** (a volatile literal in a golden: 108 findings, every
-one a publication date the PRODUCT pins rather than a value a run minted; once
-the criterion excludes midnight UTC, which a clock read never is, it falls to
-zero) and **D22w**. Three rows ship at zero as the boundary of a surface born
-with them: **W2** (the escape hatch nobody uses yet), **E8** (the literate door
-the `cli()` helper now defaults) and **C20** (folder = constructor, which the
-`integration` facet of 15.3 is the first new folder to answer to).
-
-Two rows ship at zero for a reason the re-run wrote itself. **D16** is the
-error half of a class d16w counts 57 times: the one occurrence the first run
-found was a test that PINS its clock and then reads it, which is what the rule
-tells an author to do — so the exemption that made it disappear is the rule
-working. **J9** has no occurrence because the toolchain's suppression gate
-reads `oxlint-disable*` and nothing else: the checker's own directive has never
-been held by anything, and the 16 of them on the workbench were written under
-no obligation to say why.
-
-Six false classes the re-run bounded, each of which had made a row look larger
-than it is: C18 read a spec importing `../x.specification` (no extension) as
-reaching no runner — 13 of its 44; C12 and C18 both claimed the same file, and
-`--fix` performed the wrong one; C21w counted a golden named through a template
-as no reader at all; W5w read a `db.select()` as a visitor's action and every
-component test as a screen scenario — 13 of its 26 were the estate's console;
-D18w called a precise negative (`not.toHaveBeenCalled()`) an existence check;
-D19w called three reads of one `value` a cluster.
-
-The chapters are renumbered ONCE, in the same release, so a link repointed by
-this change is repointed for good. The map it lands on runs the fork's own
-order: the spine, then the kinds of test from the one with no runner to the one
-that drives a simulator, then the shared references every kind links into, then
-the enforcement. Two chapters are BORN by it — 05, the majority kind that had no
-page, and 13, the element vocabulary two facet chapters were each holding half
-of — and every kind chapter is rewritten on one seven-section skeleton.
-
-| Old | New | Chapter                                   |
-| --- | --- | ----------------------------------------- |
-| 01  | 01  | Architecture                              |
-| 02  | 02  | Developing                                |
-| 03  | 03  | Testing                                   |
-| 04  | 04  | Operating                                 |
-| —   | 05  | Module tests (new)                        |
-| 17  | 06  | Integration specs                         |
-| 16  | 07  | Component specs                           |
-| 14  | 08  | Website specs                             |
-| 15  | 09  | Mobile specs                              |
-| 05  | 10  | API specs                                 |
-| 06  | 11  | Jobs specs                                |
-| 07  | 12  | CLI specs                                 |
-| —   | 13  | Elements (new)                            |
-| 08  | 14  | Assertions                                |
-| 09  | 15  | Tokens (+ update mode end to end)         |
-| 10  | 16  | Contracts (+ `intercept()`)               |
-| 11  | 17  | Services                                  |
-| 12  | 18  | Conventions                               |
-| 13  | 19  | Linting (carries the generated catalogue) |
-
-A rule message anchored at `docs/13-linting.md#<name>` now reads
-`docs/19-linting.md#<name>`; K3 holds that every one of them resolves, so a
-renumbering that missed a message fails the suite rather than a reader.
-
-## What the proof holds, and what it does not
-
-The release proof of this wave reads: the package's own tree green under
-`typescript check`, the `unit` project inside the budget
-[03 — Testing](../03-testing.md) states, the
-catalogue's own meta-tests holding freshness, completeness, reach and channel,
-and the R8 counts above re-derivable from the branch head. All of it holds.
-
-**Suppressions are the one stated exception**, and it has two halves, both
-counted. The proof as written asked for zero directives added to this package's
-own tree: `src/` and `specs/` carry 66 `oxlint-disable` outside fixtures and
-goldens where `main` carried 51, so the wave adds 15. They are three shapes,
-and none of them is debt: a test whose SUBJECT is the primitive the rule bans —
-the clock seam, `waitUntil`, the adapter deadlines, the marker rule's own
-one-line fixture; a negative spec whose violation IS the behaviour under test;
-and one skipped spec, the repro of the seam defect chapter 16 names, which
-leaves the day the seam answers. A rule cannot exempt the test that proves it
-without exempting the class it guards, so the directive carries the reason
-instead.
-
-The second half is the RATCHET, and it is debt rather than exemption: the wave
-absorbs 107 findings of this package's own rules into `oxlint.baseline.json` —
-`e9w` 39, `j6w` 37, `d18w` 14, `d16w` 10, `w5w` 4, `d15w` 3, beside the single
-`i1` line `main` already carried. A ratchet key names a convention, never a
-pass, so those are 107 lines a reader can spend one convention at a time, and
-the baseline may only fall.
-
-Both numbers are written here so the next release holds itself to them: 66
-directives and 107 absorbed findings, and a rise in either asks for the same
-reading.
-
-**Not done in this cut**, deliberately, each with the reason:
-
-- **The website and mobile duplicates**, and **the eight hand-written skill
-  references**, were both deferred from the catalogue cut to the renumbering
-  that follows it in the same release: the vocabulary had no page to move to
-  until chapter 13 existed, and the references had no generated card to be
-  replaced by. Both landed with it — 13 owns the vocabulary, and
-  `references/<kind>.md` is generated from the facet matrix.
-- **`response.body.cancel()`.** A seam defect, not a catalogue one: chapter 16
-  states it and M3's row names the one suppression it sanctions, with the repro
-  skipped beside the other intercept specs.
-- **W4 stays a runtime row** rather than a type one, for the reason written in
-  `src/type-channel.test-d.ts`.
-- **The three statuses.** ADR-006, 007 and 008 are `Proposed`; only the owner
-  writes `Accepted`, in the commit that cuts the version.
-
-## Consequences
-
-- A reader deciding whether a rule applies to the file in front of them reads
-  the row, never the implementation; a rule that wants a different reach must
-  change `roleOf`, where every rule sees it at once.
-- The three channels that were empty carry rows, and a row of any channel that
-  loses its proof fails a meta-test rather than going quietly stale.
-- The gate costs rules: four written, tested and fixtured rows went to the
-  backlog on the strength of the dry run. That is the price of the criterion,
-  and the criterion is the reason a consumer can trust a new `error`.
-- A count is evidence of a CLASS, not a migration estimate: `b4-given-then` at
-  2575 is narration debt that is already baselined everywhere, and no row's
-  tier is decided by how expensive it would be to fix.
-- Every consumer's first 16.0 run is a baseline update. The counts above are
-  what that update will hold.