@geonosis/oxlint-plugin-biological-architecture 2.9.0 → 2.11.0

package/RULES.md

@@ -2,8 +2,8 @@
 
 Read from the two source trees on 2026-08-29:
 
-- `dielime/packages/eslint-plugin-biological-architecture` — **36 rules**
-- `during.day/packages/eslint-plugin-biological-architecture` — **52 rules** (51 when the union was
+- a Medusa storefront's `packages/eslint-plugin-biological-architecture` — **36 rules**
+- a Workers + D1 app's `packages/eslint-plugin-biological-architecture` — **52 rules** (51 when the union was
   cut; `step-opens-its-own-cell` landed there hours later and was folded in afterwards)
 
 One plugin name, two rule sets, no shared code. **33 rules had the same filename in both trees; only
@@ -15,8 +15,8 @@ plus twenty-eight the kit wrote for itself: `layer-walls`, `emit-declares-attemp
 `cell-no-cross-feature-organelles`, the `backend-medusa` ten, `no-unregistered-plugin-dir` +
 `router-schema-parity`, the `themekit` two, `no-mock-db-in-integration`, `todo-names-its-plan`,
 `boundary-time-is-primitive`, `durable-body-reads-through-steps`, `subpath-over-barrel` and the six
-of the W67 batch — **80**. The two retired ids still resolve for one release, as no-ops that say
-they are retired, so a config naming them parses; they go at the next major.
+of the W67 batch — **80**. The two retired ids still resolve until the next major, as no-ops that
+say they are retired, so a config naming them parses.
 Every one of the twenty-eight is marked **written here** in the inventory, and the table below is
 held against that column rather than kept by hand.
 
@@ -24,8 +24,8 @@ held against that column rather than kept by hand.
 |---|---|
 | in both trees, byte-identical | 3 |
 | in both trees, **diverged** | 30 |
-| dielime only | 3 |
-| during.day only | 16 |
+| A Medusa storefront only | 3 |
+| A Workers + D1 app only | 16 |
 | **union** | **52** |
 | written here | 28 |
 | **total** | **80** |
@@ -34,12 +34,12 @@ held against that column rather than kept by hand.
 
 Two shapes of divergence, and one resolution rule each.
 
-**dielime broadened the path patterns.** Every dielime rule scoped its file test as
+**A Medusa storefront broadened the path patterns.** Every Medusa storefront rule scoped its file test as
 `(?:features/[^/]+/)?<tier>/`, so it fires on a FLAT kit (`packages/ui/src/tissues/…`) as well as a
-feature-sliced app. during.day's kept `features/<name>/<tier>/`. **The broader pattern wins** — a
+feature-sliced app. A Workers + D1 app's kept `features/<name>/<tier>/`. **The broader pattern wins** — a
 rule that reaches more files is the stricter rule.
 
-**during.day broadened the node coverage.** Its August 2026 sweep added
+**A Workers + D1 app broadened the node coverage.** Its August 2026 sweep added
 `ExportAllDeclaration` / `ExportNamedDeclaration` handlers to every import-direction rule (a
 re-export names a module exactly as an import does), and turned `tissue-no-hooks` from an import
 check into a hook-CALL check — the hole three review rounds missed was a tissue reaching a store
@@ -50,19 +50,19 @@ Where a divergence was a false-positive fix rather than a reach change (own-sibl
 `Kind`-vocabulary props), it was kept: both repos' fixtures depend on those, and a rule that fires on
 an accepted convention is a rule people learn to ignore.
 
-**Both repos' test suites are ported and green** — during.day's 300-odd hand-built-AST tests, its
-`real-source-tests` cases through the real binary, and dielime's 45-case oxlint fixture lock.
+**Both repos' test suites are ported and green** — a Workers + D1 app's 300-odd hand-built-AST tests, its
+`real-source-tests` cases through the real binary, and a Medusa storefront's 45-case oxlint fixture lock.
 
 ## Named decisions
 
-### `cell-must-be-stateful` (dielime) vs `cell-handles-are-scoped` (during.day) — **both kept, one renamed**
+### `cell-must-be-stateful` (a Medusa storefront) vs `cell-handles-are-scoped` (a Workers + D1 app) — **both kept, one renamed**
 
 These share only the word "cell", and they mean different things by it.
 
-- dielime's `cell-must-be-stateful` is the **biological tier**: a file in `cells/` whose whole family
+- A Medusa storefront's `cell-must-be-stateful` is the **biological tier**: a file in `cells/` whose whole family
   is props-in / JSX-out is a compound in the wrong folder. It is the inverse of
   `compound-must-be-stateless`. → kept as-is, `frontend`.
-- during.day's `cell-handles-are-scoped` is a **Cloudflare D1 database cell**: a worker that opens a
+- A Workers + D1 app's `cell-handles-are-scoped` is a **Cloudflare D1 database cell**: a worker that opens a
   cell handle must wrap every invocation in `withCells` or it leaks a pool per call. Nothing to do
   with a tier. → kept, **renamed `worker-handles-are-scoped`**, `backend-d1`.
 
@@ -75,7 +75,7 @@ vocabulary at every diagnostic, so the backend one gave up the word.
 compiled in — a rule exactly one repo could enable, and the thing pinning that repo's last
 generic-utility package in place, because moving the door would have silenced the rule guarding it.
 The door is now the `door` option and the directories are `exempt`, both regex sources over the
-normalised filename, and the rule refuses the run when `door` is missing. The LIBRARY it polices was
+normalised filename, and the rule reports the missing `door` once a run. The LIBRARY it polices was
 compiled in for one release longer — `dayjs`, so a repo on date-fns kept the raw-`Date` half and
 lost the half that catches a second configured formatter, which is the defect that half exists for.
 It is the `libraries` list now, defaulting to `['dayjs']`, and every diagnostic names the library
@@ -98,14 +98,45 @@ work. What changed is that they are counted: each of those rules declares `meta.
 pattern exempts in THIS tree beside the number the enumeration names — so a grant nobody decided
 stops being a grant nobody can see.
 
+### An enabled rule that cannot fire **reports that, once a run** (2.11.0 — amends the 0.2.0 refusal)
+
+The requirement below stands unchanged: a rule enabled without the option it cannot run without is
+a config error, and it has to be visible. What changed on 2026-09-18 is HOW. From 0.2.0 the rule
+threw from `create()`, which read as "the run is refused". Measured, it was destructive and
+unreadable at once: oxlint reports a throwing plugin rule against the file it was being constructed
+for and drops every other finding in that file — one file carrying a real `todo-names-its-plan`
+finding, linted beside a bare `no-brand-names`, reported nothing but the throw — and under
+`--format=unix`, the format every counter and the parity tool read, the throw rendered as
+`:0:0:  [Warning]`: no path, no rule id, no sentence.
+
+So the rule now reports the refusal as a **finding**, on the first file a run constructs it for,
+and is inert for the files after it (#202: one finding, one problem in the summary, however many
+files the run has — measured over 300 files and 8 threads). The finding has a place and a rule id,
+the ratchet counts it, the parity tool attributes it, its neighbours stay where they were, and the
+run still exits non-zero. The wording is the same header as before —
+
+```
+biological-architecture/<rule> requires option `<option>`. It is enabled but its `<option>` option
+is nothing, so it judges no file — this finding stands in for every file it did not read, once a
+run. Configure `<option>`, or turn the rule off: an enabled rule that judges nothing would
+otherwise read exactly like a rule that found nothing. It accepts { … }.
+```
+
+— so the doctor and `optionsNeededBy` read the rule and the option out of the same fixed position
+(#199), and both hear a refusal a plugin throws (older builds) as well as one it reports. Nothing
+exported from the plugin throws for a missing option any more; `requireOption` inside a rule module
+raises the requirement, and the registry (`src/index.ts`) turns it into the finding. Everywhere
+the prose below says "refuses the run", read "reports the missing option once a run and judges
+nothing".
+
 ### An enabled rule that cannot fire **refuses the run** (0.2.0)
 
 This replaces the "does nothing until configured" posture below, and it is the one breaking change
-in 0.2.0 that a consumer will feel.
+in 0.2.0 that a consumer will feel. (The mechanism was amended in 2.11.0 — see above.)
 
 Making every repo-specific list an option (law 6) has an obvious implementation and a wrong one:
 return an empty visitor when the option is missing. The result is a rule that is enabled, graded
-`"error"`, and **indistinguishable from compliance**. dielime ran `no-raw-html-atoms` at `"error"`
+`"error"`, and **indistinguishable from compliance**. A Medusa storefront ran `no-raw-html-atoms` at `"error"`
 for months with no element→atom map. 136 raw elements in the tree. Zero findings. A green gate. It
 was found by hand, not by a gate, because there was no gate — only a rule with nothing to compare
 against, which is the silent-fallback class one level up from a counter reading zero under a format
@@ -117,7 +148,7 @@ So the posture splits in two:
 - a rule that **is** enabled without the options it needs is a **config error**, and `create()`
   throws, naming the rule and the missing option. oxlint refuses and exits non-zero.
 
-**Nineteen** rules take this, and the list is not kept by hand: `src/rules/option-gated.ts` names
+The rules that take this are not listed by hand: `src/rules/option-gated.ts` names
 each with the option its refusal must say and a bag that makes it run clean, and
 `src/option-gated.test.ts` asks every rule the plugin exports whether it refuses a bare `create()`
 and fails when one of them is not on the list — or is on it and no longer refuses. It found seven
@@ -143,7 +174,7 @@ non-zero, and the summary counts a problem no line accounts for — which is exa
 never re-enter kit source (the ones the fork had compiled into its regex) — proved reaching by
 adding one to a source file and watching it fire.
 
-### `no-brand-names` (dielime only) — brand list is now an **option**
+### `no-brand-names` (a Medusa storefront only) — brand list is now an **option**
 
 The rule shipped with a two-brand regex and a matching CDN-host allowance compiled into it. It could
 only ever serve the repo that wrote it. Now:
@@ -155,7 +186,7 @@ only ever serve the repo that wrote it. Now:
 ]
 ```
 
-Enabled with no `brands`, it refuses the run — see the decision above.
+Enabled with no `brands`, it reports that once a run and judges nothing — see the decision above.
 
 ### `step-opens-its-own-cell` — one law, two spellings, every fact an **option**
 
@@ -197,7 +228,7 @@ finding there is a saga importing the engine's `step` around that wrapper — re
 ]
 ```
 
-Enabled with no `within`, it refuses the run. Type-only imports never fire: they bring no handle, so
+Enabled with no `within`, it reports that once a run. Type-only imports never fire: they bring no handle, so
 they can share none. The diagnostic quotes the option values rather than any repo's paths, and the
 preset is its own — the invariant is true of a DURABLE run that hibernates between steps and false
 of an inline saga sharing the request's connection, so `backend-workflows` would have been a repo
@@ -270,7 +301,7 @@ run, like every other option a rule cannot fire without.
 
 Preset `backend-medusa`, which is twelve rules now.
 
-**One correction to the brief that asked for it**: dielime does not guard 50 emit sites this way
+**One correction to the brief that asked for it**: a Medusa storefront does not guard 50 emit sites this way
 today. It has **four** `emitEventStep` calls (`create-sample-order`, `ingest-shipment-milestone`,
 `convert-sample-to-order` ×2), and **all four would fire** — three carry
 `options: { priority: EventPriority.CRITICAL }` with no attempts, one carries no options at all.
@@ -290,12 +321,12 @@ registry is read as SOURCE — a rule that had to import it would need the repo'
 up inside a linter, and every string in it is a name the registry knows whether it is spelled as an
 id or as an import path.
 
-dielime is the fixture that matters just as much: measured, **zero** of its provider directories are
+A Medusa storefront is the fixture that matters just as much: measured, **zero** of its provider directories are
 unregistered. A rule that fired on the clean tree would be off within a day. And its third seam has
 no directories at all — `email-gmail.ts` and `whatsapp-360dialog.ts` sit flat beside their registry —
 so it is out of scope because nothing matches `<root>/<dir>/<manifest>`, not by a special case.
 
-*`registry` takes a list, because a registry can be split.* dielime's `medusa-config.ts` imports
+*`registry` takes a list, because a registry can be split.* A Medusa storefront's `medusa-config.ts` imports
 `medusa-config.fulfillment.ts`, and the carrier directories are registered in the half that is
 imported. Reading only the file the option named made two REGISTERED directories a standing FAIL
 there — a false positive on a working tree, which is how a rule gets turned off. The halves are
@@ -313,16 +344,16 @@ its fixture exists to catch. The hand-built nodes could not find this: a hand-bu
 prose in it. Comments are stripped first now, and the direction is the point — a name that appears
 only in a comment is usually the note explaining why the directory was abandoned.
 
-**`router-schema-parity`.** during.day holds the mirror by hand at 21 of 22 routers and 21 of 23
+**`router-schema-parity`.** A Workers + D1 app holds the mirror by hand at 21 of 22 routers and 21 of 23
 contracts; Midday holds its own at 33 of 37. A router with no schema is a wire contract written
 wherever the handler happens to say it; a schema with no router is a contract nothing serves.
 
 Two facts were measured before the rule was written, and both changed its shape:
 
-1. during.day's two halves are in **different packages** — `apps/api/src/trpc/routers` against
+1. A Workers + D1 app's two halves are in **different packages** — `apps/api/src/trpc/routers` against
    `packages/api-contract/src` — so the options are repo-root-relative. A package-relative option
    could not name them both.
-2. during.day's three apparent gaps are ONE deliberate arrangement: `routers/documents-mounted.ts`
+2. A Workers + D1 app's three apparent gaps are ONE deliberate arrangement: `routers/documents-mounted.ts`
    mounts the invoice and purchase-order entities and imports both contracts. A strict filename
    mirror reports all three and is wrong all three times, on the very tree the rule was built from.
    So `mounts` (`{ "documents-mounted": ["invoice", "purchase-order"] }`) is config, and the corpus
@@ -334,20 +365,20 @@ Neither of these came from review. Both came from running the rule read-only ove
 then running a CONTROL that should have made the same files fire.
 
 **`no-unregistered-plugin-dir.manifests` is required, with no default.** The rule first shipped a
-default entry-file list — `index.ts`, `index.tsx`, `config.ts`. Over dielime's two provider roots it
+default entry-file list — `index.ts`, `index.tsx`, `config.ts`. Over a Medusa storefront's two provider roots it
 reported zero findings, and every directory there IS registered, so the run read as a pass. It was
-not one: dielime's plugin directories contain `service.ts` and no index at all, so the rule matched
+not one: a Medusa storefront's plugin directories contain `service.ts` and no index at all, so the rule matched
 no file and answered a question it had never asked. The control — the same files, with a registry
 naming none of them — also reported zero, which is what exposed it. With `manifests: ["service.ts"]`
 the control fires on all three directories and the real config on none.
 
 **`emit-declares-attempts.budgetHelpers`, empty by default.** The claim this rule carried was that it
-covers dielime's emit sites, so that repo's 132-line source walker could be deleted. Measured: all
+covers a Medusa storefront's emit sites, so that repo's 132-line source walker could be deleted. Measured: all
 **54** `emitEventStep` sites spell the bag `options: retryableEvent(…)` — zero object literals, zero
 missing bags — and a call is precisely the shape the rule declines to judge. It reported zero, and
 that zero proved only that no bag was absent. Named as a budget helper, a call to `retryableEvent`
 passes and a call to anything else is reported as a budget nobody can check; the control naming a
-helper dielime does not use reports all 54. Empty by default, so no existing consumer moves.
+helper a Medusa storefront does not use reports all 54. Empty by default, so no existing consumer moves.
 
 Both are the same failure as a counter that reads zero under a format it cannot parse, and both were
 invisible to the rules' own fixtures — a fixture is written to match the rule, which is exactly what
@@ -359,8 +390,8 @@ The only rule in the plugin whose landmine is in **neither** source repo. Measur
 
 | tree | `mockDb` | `vi.mock('…db…')` | `vi.mock(` in integration suites |
 |---|---:|---:|---:|
-| dielime | 0 | 0 | **0** of 106 integration files |
-| during.day | 0 | 0 | 0 (`vi.mock` appears nowhere in the tree) |
+| A Medusa storefront | 0 | 0 | **0** of 106 integration files |
+| A Workers + D1 app | 0 | 0 | 0 (`vi.mock` appears nowhere in the tree) |
 | Midday | 32 references in 4 files | — | the gate |
 
 Midday's shape: `apps/api/src/__tests__/setup.ts:80` exports `mockDb = createMockDb()`;
@@ -391,22 +422,22 @@ Three matching decisions, each with a case in the node layer:
 
 Every rule below exists because the framework **infers** something instead of making you say it.
 None of them throws at runtime; all of them are found in production, far from the cause. Six were
-scans in dielime's `packages/verify-arch` first and are now also per-file rules; two come from
+scans in a Medusa storefront's `packages/verify-arch` first and are now also per-file rules; two come from
 Medusa's own source; one from an estimate a route already labels by hand. Three more — the per-file
 halves of R4.3, R3.8 and R5.1 — landed after adoption showed what a text scan misses.
 
 | rule | the silence | source |
 |---|---|---|
-| `mutating-step-declares-retry` | `maxRetries` defaults to **0** (`orchestration/transaction/types.ts:48`), so a transient failure reverts real state a retry would have absorbed | dielime scan R5.2 |
-| `step-declares-compensation-or-none` | `stepConfig.noCompensation = !compensateFn` (`create-step.ts:184`) — a deliberate non-compensation and a forgotten one are the same source | analysis §1.1, "highest-value lint gap"; dielime scan R5.6 |
-| `named-when-block` | an unnamed `when()` derives a `when-then-{ulid}` step name (`composer/when.ts:120-126`), so a resumed run cannot find its checkpoint | dielime scan R5.5 |
-| `subscriber-declares-id` | the loader infers a subscriber id from a function or file name; two that infer alike dedupe each other | dielime scan R5.4 |
-| `no-loader-side-effect-in-index-file` | `ResourceLoader.discoverResources` filters files named `index` (`resource-loader.js:51`) | dielime scan #15442 |
-| `service-name-not-reserved` | a module key matching the `Modules` enum silently REPLACES the built-in (`medusa-app.ts:175-198`); `registerModule` guards only aliases and mains | analysis §1.3 — dielime's `catalog_search` scar |
-| `no-index-count-as-exact` | the index engine's count is an EXPLAIN plan-row estimate and reads as an exact total | analysis §3a; dielime's b2b route labels it by hand |
-| `unique-query-step-name` | the step-handler map is a plain assignment and the orchestrator appends a duplicate action with no dedupe, so two un-named query steps in one body last-win: one read never happens | dielime scan R4.3 |
-| `plugin-route-namespaced` | the routes-loader assigns last-write-wins, so a plugin route with no namespace segment is claimable by any other package with no error | dielime scan R3.8 |
-| `route-no-inline-mutation` | a route that writes directly succeeds, returns 200, and skips the compensation and retry class that live behind the workflow door | dielime scan R5.1 |
+| `mutating-step-declares-retry` | `maxRetries` defaults to **0** (`orchestration/transaction/types.ts:48`), so a transient failure reverts real state a retry would have absorbed | a Medusa storefront's scan R5.2 |
+| `step-declares-compensation-or-none` | `stepConfig.noCompensation = !compensateFn` (`create-step.ts:184`) — a deliberate non-compensation and a forgotten one are the same source | analysis §1.1, "highest-value lint gap"; a Medusa storefront's scan R5.6 |
+| `named-when-block` | an unnamed `when()` derives a `when-then-{ulid}` step name (`composer/when.ts:120-126`), so a resumed run cannot find its checkpoint | a Medusa storefront's scan R5.5 |
+| `subscriber-declares-id` | the loader infers a subscriber id from a function or file name; two that infer alike dedupe each other | a Medusa storefront's scan R5.4 |
+| `no-loader-side-effect-in-index-file` | `ResourceLoader.discoverResources` filters files named `index` (`resource-loader.js:51`) | a Medusa storefront's scan #15442 |
+| `service-name-not-reserved` | a module key matching the `Modules` enum silently REPLACES the built-in (`medusa-app.ts:175-198`); `registerModule` guards only aliases and mains | analysis §1.3 — a Medusa storefront's `catalog_search` scar |
+| `no-index-count-as-exact` | the index engine's count is an EXPLAIN plan-row estimate and reads as an exact total | analysis §3a; a Medusa storefront's b2b route labels it by hand |
+| `unique-query-step-name` | the step-handler map is a plain assignment and the orchestrator appends a duplicate action with no dedupe, so two un-named query steps in one body last-win: one read never happens | a Medusa storefront's scan R4.3 |
+| `plugin-route-namespaced` | the routes-loader assigns last-write-wins, so a plugin route with no namespace segment is claimable by any other package with no error | a Medusa storefront's scan R3.8 |
+| `route-no-inline-mutation` | a route that writes directly succeeds, returns 200, and skips the compensation and retry class that live behind the workflow door | a Medusa storefront's scan R5.1 |
 
 Four postures they share, all of them the one `emit-declares-attempts` set:
 
@@ -435,7 +466,7 @@ parameter and its doc comment, and nothing else). So a `workflows/index.ts` **is
 2.19 and a `subscribers/index.ts` is not. A rule firing on a file the framework reads is a false
 positive, and false positives are how a rule gets ignored — so the default is what was measured, and
 a repo below 2.19 adds `workflows/` back. The `medusa` scanner pack in `@geonosis/verify-arch`
-defaults the same way, and `examples/dielime.verify-arch.json` adds the third kind, which is what
+defaults the same way, and `examples/medusa-storefront.verify-arch.json` adds the third kind, which is what
 keeps that repo's numbers identical to today's.
 
 **The class an AST rule wins over a text scan.** These three are the per-file halves of scans a
@@ -463,48 +494,48 @@ claiming one route, a `serviceName` that must be unique across every module. The
 decision rule, not a ranking: whole-graph facts are scans, per-file facts are rules, and the six
 that are both are defence in depth on purpose.
 
-**`step-declares-compensation-or-none` judges every step, not only mutating ones.** dielime's R5.6
+**`step-declares-compensation-or-none` judges every step, not only mutating ones.** A Medusa storefront's R5.6
 scan restricts itself to steps whose text contains a write; the rule does not, because
 `noCompensation = !compensateFn` is true of every step and a read-only step declares
 `noCompensation: true` once and is done. The two are therefore not redundant: the scan is the
 repo-wide backstop, the rule is the finer instrument. `noCompensation: false` is the inferred state
 written out and is still reported.
 
-### `store-route-scopes-tenant-data` (dielime only) — Medusa-specific
+### `store-route-scopes-tenant-data` (a Medusa storefront only) — Medusa-specific
 
 `/api/store/**/route.ts` is a Medusa convention. It is in `backend-medusa`, and also in
 `tenant-scoping` because that is what it enforces.
 
-### `no-logic-in-component-files` — dielime's narrowed version
+### `no-logic-in-component-files` — a Medusa storefront's narrowed version
 
-during.day's version also reported type re-exports and custom hooks in component files. Both are
+A Workers + D1 app's version also reported type re-exports and custom hooks in component files. Both are
 covered by dedicated rules in the union (`no-type-definitions-in-components`,
-`no-hook-in-component-disguise`), and during.day's own suite does not test this rule. dielime's
+`no-hook-in-component-disguise`), and a Workers + D1 app's own suite does not test this rule. A Medusa storefront's
 narrower "one public component per file" version is the one under test, and the one kept.
 
-### `tissue-must-compose` — dielime's, minus its backstop
+### `tissue-must-compose` — a Medusa storefront's, minus its backstop
 
-dielime added a "renders ANY PascalCase tag" backstop. during.day has a test proving that backstop
+A Medusa storefront added a "renders ANY PascalCase tag" backstop. A Workers + D1 app has a test proving that backstop
 lets a tissue satisfy the gate by rendering a component it imported as a **type** — precisely the
-lint-theater the rule exists for. The backstop is dropped; dielime's broader `COMPOSITION_PATTERNS`
+lint-theater the rule exists for. The backstop is dropped; a Medusa storefront's broader `COMPOSITION_PATTERNS`
 (feature barrels, `.parts`/`.sections` siblings, react-email primitives) already recognise real
-arrangements, and dielime's fixtures stay green without it.
+arrangements, and a Medusa storefront's fixtures stay green without it.
 
 ### `cell-must-not-compose-cell` — the union's two halves collided on the barrel
 
-The kit's version is dielime's scope (`(?:^|/)cells/`, so the rule reaches a `packages/ui` tree with
-no `features/<name>/` segment) plus during.day's visitors (`ExportAllDeclaration` and
+The kit's version is a Medusa storefront's scope (`(?:^|/)cells/`, so the rule reaches a `packages/ui` tree with
+no `features/<name>/` segment) plus a Workers + D1 app's visitors (`ExportAllDeclaration` and
 `ExportNamedDeclaration`, so a cell cannot launder an import through `export … from`). Each half is
 right. Together, unguarded, they reported every `cells/index.ts` barrel — because a barrel is
-nothing but `export … from` lines naming sibling cells. dielime's first adoption produced 32 such
+nothing but `export … from` lines naming sibling cells. A Medusa storefront's first adoption produced 32 such
 errors, and every one of them was a file obeying `cells-folder-index-is-barrel`, which is also an
 error and demands exactly that shape.
 
 Neither fork could see it:
 
-- **dielime** had the broad scope but visited `ImportDeclaration` only, so the re-exports in its
+- **A Medusa storefront** had the broad scope but visited `ImportDeclaration` only, so the re-exports in its
   barrels were invisible to the rule;
-- **during.day** visited all three, but scoped to `features/[^/]+/cells/`, and it has no
+- **A Workers + D1 app** visited all three, but scoped to `features/[^/]+/cells/`, and it has no
   `cells/index.ts` or `cells/dynamic.ts*` anywhere in `apps/` or `packages/` — nothing to collide
   with.
 
@@ -519,7 +550,7 @@ holds `cells/`.
 ### `no-raw-html-atoms` — the tier it was always documented for (0.3.0)
 
 Its own description said levels 2-6 and it fired at every level, `atoms/` included, where a raw
-`<button>` is not a violation but the whole point of the file. dielime armed it by switching the rule
+`<button>` is not a violation but the whole point of the file. A Medusa storefront armed it by switching the rule
 off over `**/atoms/**` in its own config: a repo carrying the kit's defect as configuration.
 
 It is now silent inside the atom tier — `(?:^|/)(?:features/[^/]+/)?atoms/`, the merged pattern from
@@ -547,17 +578,17 @@ rule the option refusal exists to stop, one option along.
 
 | Rule | Option | Unconfigured |
 |---|---|---|
-| `organelle-dependency` | `sharedFeatures` | `['shared']` — during.day's `charts`/`document` are config, not law |
+| `organelle-dependency` | `sharedFeatures` | `['shared']` — a Workers + D1 app's `charts`/`document` are config, not law |
 | `mutating-step-declares-retry` | `retryKey` | `maxRetries` — Medusa's key. `@geonosis/workflows` spells the same budget `retry: { limit, backoff }` (`create-step.ts`), and with the key compiled in a correctly budgeted step on that engine was a finding for ever |
 | `mutating-step-declares-retry` | `retryLimitKey` | `limit` — the key that holds the NUMBER when the budget is an object. #191: reading only the bare form let `retry: { limit: 0 }` pass, which is the same silence as `maxRetries: 0` |
 | `worker-handles-are-scoped` | `within` + `wrapper` | **refuses the run** — `withCells` and `/apps/api/src/` were compiled in, so the rule served one repo's layout and one repo's vocabulary and a scope opener called anything else read as unscoped for ever |
-| `subpath-over-barrel` | `packages` (`{ name, subpaths: { <subpath>: string[] } }[]`) | **refuses the run** — which of a repo's own packages expose subpaths, and which names live under each, is a map only that package's owner has |
+| `subpath-over-barrel` | `packages` (`{ name, subpaths?: { <subpath>: string[] } }[]`) | optional — the map is the package's own `package.json` `exports`, read for the repo's own packages (linked into `node_modules`, or private) with the names behind each door read off its entry file. `{ name, subpaths }` replaces the map for one package; `{ name }` alone reads a third-party package too |
 | `durable-body-reads-through-steps` | `ports` | **refuses the run** — what a body reaches the outside world through is the repo's vocabulary; `durableKey` / `durableValue` (default `durable: true`) say how a workflow declares itself durable |
-| `unique-query-step-name` | `queryStepCalls` | **refuses the run** — the two names it shipped with are Medusa framework calls with no counterpart, so on the org engine the rule had zero reach while reading as enforced (026-W2, measured through the binary). There is no second spelling to inherit: `@geonosis/workflows` has no query-step primitive, and a repeated step name there is DEFINED rather than lost — `reserve`, `reserve#2` in call order (`engine.ts:124`) |
+| `unique-query-step-name` | `queryStepCalls` | **refuses the run** — the two names it shipped with are Medusa framework calls with no counterpart, so on `@geonosis/workflows` the rule had zero reach while reading as enforced (026-W2, measured through the binary). There is no second spelling to inherit: `@geonosis/workflows` has no query-step primitive, and a repeated step name there is DEFINED rather than lost — `reserve`, `reserve#2` in call order (the engine's `reserveName`) |
 | `no-raw-html-atoms` | (positional) element→atom map | **refuses the run** |
 | `no-raw-html-atoms` | `scope` (second positional, `{ scope: ["cells", …] }`) | every file except the atom tier |
 
-Package specifiers in diagnostics (`@dielime/ui`, `@during/utils/time`) were made generic, and
+Package specifiers in diagnostics (`@shop/ui`, `@app/utils/time`) were made generic, and
 `CLAUDE.md §…` citations were removed: they pointed at a law file this package does not ship, and
 the remedy now lives in each rule's `fixShape`.
 
@@ -577,7 +608,7 @@ fix to how a path is read had to be found rule by rule.
 | `lib/imports.ts` | `sourceOf` (import · `export … from` · `export * from` · `import()` · `require()`), `isTypeOnly`, `resolveRelative` |
 | `lib/visitors.ts` | `onImportSource` — one visitor set over all five shapes — and `mergeVisitors` |
 | `lib/direction-rule.ts` | `directionRule()`: a direction rule as a declaration (scope, forbidden, messages) |
-| `lib/options.ts` | `requireOption` — an enabled rule that cannot fire refuses the run |
+| `lib/options.ts` | `requireOption` — an enabled rule that cannot fire says so; `reportingOncePerRun` — the registry reports it as one finding a run |
 | `lib/cells-barrel.ts` | the barrel list two rules must agree on |
 | `lib/literal-call.ts` | the string a `saga('x', …)`-shaped call names |
 
@@ -588,7 +619,7 @@ declaration and holds no mechanism at all.
 `onImportSource` visits a type-only import only when the rule counts one. Four do:
 `no-orm-outside-db` and `dialect-through-the-seam` say why in their docs (a type borrowed from the
 ORM is a line a replacement would still have to rewrite), and `atom-no-deps` and
-`molecule-atoms-only` inherited it from dielime — an atom that borrows a domain's type is an atom
+`molecule-atoms-only` inherited it from a Medusa storefront — an atom that borrows a domain's type is an atom
 that knows a domain. The other six direction rules skip them, as they always did.
 
 ### Direction rules resolve relative imports (0.4.0)
@@ -597,7 +628,7 @@ that knows a domain. The other six direction rules skip them, as they always did
 importing file before judging it. The other eight direction rules read the string as written, so
 `../../billing/organelles/totals` — which names no feature and no tier until it is resolved — was
 invisible to them. Whether a relative climb across a feature boundary was a finding depended on
-which rule happened to look at it. during.day's A2b probe found this; it was one resolver in two
+which rule happened to look at it. A Workers + D1 app's A2b probe found this; it was one resolver in two
 rules and no resolver in eight.
 
 **Now:** the classification every direction rule judges by goes through `resolveRelative` once, in
@@ -624,9 +655,9 @@ argued — `proofs/018-T3-relative-imports/`:
 | tree | A | B | lost | gained |
 |---|---:|---:|---:|---:|
 | the kit's corpus | 99 | 101 | 0 | 2 — `no-cross-feature-stores` and `organelle-dependency`, on the two fixtures written RED for this |
-| dielime, its own config, `apps packages` | 135 | 135 | 0 | 0 |
+| A Medusa storefront, its own config, `apps packages` | 135 | 135 | 0 | 0 |
 
-dielime's zero is not luck: that tree has seven relative cross-feature imports of a store or an
+A Medusa storefront's zero is not luck: that tree has seven relative cross-feature imports of a store or an
 organelle, five of them into `shared/organelles/*` (which `organelle-dependency`'s `sharedFeatures`
 option permits) and two of them in **cells** reaching another feature's organelle — which no rule
 here polices, because `organelle-dependency` is scoped to `organelles/` and `no-cross-feature-stores`
@@ -641,7 +672,7 @@ and says nothing about who imports it. `no-cross-feature-stores` is scoped to ce
 but only judges `features/<x>/stores/`. So a **cell** importing another feature's **organelle** — a
 hook holding that feature's state, pulled across the boundary — passed both.
 
-It is not hypothetical. dielime, on its own config, with the rule enabled through a temporary config
+It is not hypothetical. A Medusa storefront, on its own config, with the rule enabled through a temporary config
 and nothing else changed:
 
 | site | import |
@@ -672,42 +703,42 @@ theme whether or not it is organised biologically. `backend-d1` exists because `
 them would be a repo fact wearing a preset's name. `backend-workflows-cf` exists for the same reason:
 `step-opens-its-own-cell` is true of a durable run on Cloudflare Workflows and false of an inline
 one. It was called `backend-sagaflow-cf` until 1.5.0, after the engine it was written for; the old
-name resolves to the same rules for ONE release and says so once, then goes. `package-subpaths` exists because `subpath-over-barrel` is inert until a repo writes out which
-of ITS packages expose subpaths and which names live under each — a map only that package's owner
-has, and one a kit that guessed at it would keep stale on somebody else's behalf.
+name resolves to the same rules for ONE release and says so once, then goes. `package-subpaths` exists because `subpath-over-barrel` reads the repo's own packages off disk —
+their `exports` and the entry file behind each door — which is a fact about that repo's layout, not
+every repo's.
 
-| Rule | Preset(s) | Requires | Core | In dielime | In during.day | Same code |
+| Rule | Preset(s) | Requires | Core | In a Medusa storefront | In a Workers + D1 app | Same code |
 |---|---|---|---|---|---|---|
 | `atom-no-deps` | frontend | — | `directionRule` | yes | yes | diverged |
 | `boundary-time-is-primitive` | backend-workflows | `types` | `nodes` + `paths` + `options` | — | — | **written here** (D-050, #145) |
-| `cell-must-be-stateful` | frontend | — | `paths` | yes | — | dielime only |
+| `cell-must-be-stateful` | frontend | — | `paths` | yes | — | a Medusa storefront only |
 | `cell-must-not-compose-cell` | frontend | — | `directionRule` + `cells-barrel` | yes | yes | diverged |
 | `cell-no-cross-feature-organelles` | frontend | — | `directionRule` | — | — | **written here** |
 | `cell-no-tissues` | frontend | — | `directionRule` | yes | yes | diverged |
 | `cells-folder-index-is-barrel` | frontend | — | `paths` + `cells-barrel` | yes | yes | diverged |
 | `compound-must-be-stateless` | frontend | — | `paths` | yes | yes | diverged |
 | `compound-no-stores` | frontend | — | `directionRule` | yes | yes | diverged |
-| `constants-in-constants-file` | backend-workflows | — | `paths` | — | yes | during only |
-| `dialect-through-the-seam` | backend-workflows | — | `onImportSource` + `mergeVisitors` + `paths` | — | yes | during only |
+| `constants-in-constants-file` | backend-workflows | — | `paths` | — | yes | a Workers + D1 app only |
+| `dialect-through-the-seam` | backend-workflows | `seam` | `onImportSource` + `mergeVisitors` + `paths` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
 | `durable-body-reads-through-steps` | backend-workflows | `ports` | `nodes` + `objects` + `steps` + `options` | — | — | **written here** (#167, design-026 §8) |
 | `effect-hook-naming` | frontend | — | `paths` | yes | yes | diverged |
 | `emit-declares-attempts` | backend-medusa | — | `options` | — | — | **written here** |
 | `font-roles-only` | themekit | `roles` | `paths` + `options` + `styling` | — | — | **written here** (U2) |
 | `layer-walls` | tooling | `layers` | `onImportSource` + `imports` + `paths` + `options` | — | — | **written here** |
 | `list-take-without-order` | backend-medusa | — | `nodes` + `options` | — | — | **written here** (#21) |
-| `max-comment-density` | comment-ceiling | — | `paths` | — | yes | during only |
+| `max-comment-density` | comment-ceiling | — | `paths` | — | yes | a Workers + D1 app only |
 | `molecule-atoms-only` | frontend | — | `directionRule` | yes | yes | diverged |
 | `molecule-must-compose` | frontend | — | — | yes | yes | diverged |
-| `mutating-step-declares-retry` | backend-medusa + backend-workflows | — | `nodes` + `objects` + `steps` + `options` | — | — | **written here** (dielime scan R5.2) |
-| `named-when-block` | backend-medusa | — | `nodes` + `options` | — | — | **written here** (dielime scan R5.5) |
+| `mutating-step-declares-retry` | backend-medusa + backend-workflows | — | `nodes` + `objects` + `steps` + `options` | — | — | **written here** (a Medusa storefront's scan R5.2) |
+| `named-when-block` | backend-medusa | — | `nodes` + `options` | — | — | **written here** (a Medusa storefront's scan R5.5) |
 | `next-route-segment-is-thin-delegate` | frontend | — | `paths` | yes | yes | diverged |
 | `no-unregistered-plugin-dir` | integrations | `roots` | `options` + `paths` | — | — | **written here** (Midday's 8 dead dirs; flat seam #36) |
 | `no-mock-db-in-integration` | testbed | `integrationDirs` | `options` + `paths` | — | — | **written here** (Midday's 35 mocked router suites) |
-| `router-schema-parity` | backend-trpc | `routers` | `options` + `paths` | — | — | **written here** (during.day's mirror) |
-| `no-brand-names` | frontend | `brands` | `paths` + `options` | yes | — | dielime only |
+| `router-schema-parity` | backend-trpc | `routers` | `options` + `paths` | — | — | **written here** (a Workers + D1 app's mirror) |
+| `no-brand-names` | frontend | `brands` | `paths` + `options` | yes | — | a Medusa storefront only |
 | `no-card-shaped-div` | frontend | — | — | yes | yes | diverged |
 | `no-cross-feature-stores` | frontend | — | `directionRule` | yes | yes | diverged |
-| `no-d1-transaction` | backend-d1 | — | `paths` | — | yes | during only |
+| `no-d1-transaction` | backend-d1 | — | `paths` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
 | `no-date-string-compare` | backend-workflows | — | `nodes` + `options` | — | — | **written here** (#20) |
 | `no-duplicate-jsx-patterns` | frontend | — | `paths` | yes | yes | diverged |
 | `no-generic-utility-package` | tooling | — | `paths` + `options` | — | — | **written here** (#171) |
@@ -716,47 +747,47 @@ has, and one a kit that guessed at it would keep stale on somebody else's behalf
 | `no-inert-hidden-jsx` | frontend | — | `paths` | yes | yes | diverged |
 | `no-inline-data-in-jsx` | frontend | — | `paths` | yes | yes | diverged |
 | `no-invalid-feature-folders` | frontend | — | `paths` | yes | yes | diverged |
-| `no-loader-side-effect-in-index-file` | backend-medusa | — | `nodes` + `paths` + `options` | — | — | **written here** (dielime scan #15442) |
+| `no-loader-side-effect-in-index-file` | backend-medusa | — | `nodes` + `paths` + `options` | — | — | **written here** (a Medusa storefront's scan #15442) |
 | `no-logic-in-component-files` | frontend | — | `paths` | yes | yes | diverged |
-| `plugin-route-namespaced` | backend-medusa | `packages` | `paths` + `options` | — | — | **written here** (dielime scan R3.8) |
-| `no-orm-outside-db` | backend-workflows | — | `directionRule` | — | yes | during only |
+| `plugin-route-namespaced` | backend-medusa | `packages` | `paths` + `options` | — | — | **written here** (a Medusa storefront's scan R3.8) |
+| `no-orm-outside-db` | backend-workflows | — | `directionRule` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
 | `no-raw-html-atoms` | frontend | `element→atom map` | `tiers` + `options` | yes | yes | diverged |
-| `no-raw-sql-outside-allowed` | backend-workflows | — | `paths` | — | yes | during only |
+| `no-raw-sql-outside-allowed` | backend-workflows | — | `paths` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
 | `no-react-namespace` | frontend | — | — | yes | yes | **identical** |
 | `no-renamed-html-props` | frontend | — | — | yes | yes | **identical** |
 | `no-render-prop-reader` | frontend | — | `paths` | yes | yes | diverged |
-| `no-swallowed-catch` | failure-paths | — | `nodes` + `paths` + `options` | — | — | **written here** (#3) |
-| `no-runtime-dead-affordance` | frontend | — | `options` | — | — | **written here** (#5) |
+| `no-swallowed-catch` | failure-paths | `paths` | `nodes` + `paths` + `options` | — | — | **written here** (#3) |
+| `no-runtime-dead-affordance` | frontend | `element→atom map` | `options` | — | — | **written here** (#5) |
 | `no-trivial-wrapper-component` | frontend | — | `paths` | yes | yes | diverged |
 | `no-ts-in-bio-folders` | frontend | — | `paths` | yes | yes | diverged |
 | `no-type-definitions-in-components` | frontend | — | `paths` | yes | yes | diverged |
-| `no-void-port` | backend-workflows | — | — | — | yes | during only |
+| `no-void-port` | backend-workflows | — | — | — | yes | a Workers + D1 app only |
 | `organelle-dependency` | frontend | — | `directionRule` | yes | yes | diverged |
 | `organelle-single-source` | frontend | — | `onImportSource` + `mergeVisitors` + `paths` | yes | yes | diverged |
-| `queries-require-org-scope` | tenant-scoping | — | `paths` | — | yes | during only |
-| `queue-loop-is-the-library` | backend-workflows | — | — | — | yes | during only |
-| `route-no-inline-mutation` | backend-medusa | — | `nodes` + `paths` + `comments` + `options` | — | — | **written here** (dielime scan R5.1) |
+| `queries-require-org-scope` | tenant-scoping | `queries` | `paths` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
+| `queue-loop-is-the-library` | backend-workflows | — | — | — | yes | a Workers + D1 app only |
+| `route-no-inline-mutation` | backend-medusa | — | `nodes` + `paths` + `comments` + `options` | — | — | **written here** (a Medusa storefront's scan R5.1) |
 | `service-name-not-reserved` | backend-medusa | — | `nodes` + `objects` + `options` | — | — | **written here** (Medusa source) |
-| `ssot-no-inline-facts` | backend-workflows | — | `paths` | — | yes | during only |
-| `ssot-no-process-env` | backend-workflows | — | `paths` | — | yes | during only |
+| `ssot-no-inline-facts` | backend-workflows | — | `paths` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
+| `ssot-no-process-env` | backend-workflows | — | `paths` | — | yes | a Workers + D1 app only |
 | `step-declares-compensation-or-none` | backend-medusa + backend-workflows | — | `nodes` + `objects` + `steps` + `options` | — | — | **written here** (Medusa source) |
-| `step-opens-its-own-cell` | backend-workflows-cf | `within` | `nodes` + `objects` + `paths` + `options` | — | yes | during only, re-targeted |
-| `store-route-scopes-tenant-data` | backend-medusa + tenant-scoping | — | `nodes` + `imports` + `paths` + `options` | yes | — | dielime only, de-hardcoded |
-| `subpath-over-barrel` | package-subpaths | `packages` | `nodes` + `options` | — | — | **written here** (#180, during.day asked) |
-| `subscriber-declares-id` | backend-medusa | — | `objects` + `paths` + `options` | — | — | **written here** (dielime scan R5.4) |
-| `tables-declare-their-plane` | backend-workflows + tenant-scoping | — | `paths` + `literal-call` | — | yes | during only |
-| `tenant-tables-carry-org-id` | tenant-scoping | — | `paths` + `literal-call` | — | yes | during only |
+| `step-opens-its-own-cell` | backend-workflows-cf | `within` | `nodes` + `objects` + `paths` + `options` | — | yes | a Workers + D1 app only, re-targeted |
+| `store-route-scopes-tenant-data` | backend-medusa + tenant-scoping | — | `nodes` + `imports` + `paths` + `options` | yes | — | a Medusa storefront only, de-hardcoded |
+| `subpath-over-barrel` | package-subpaths | — | `nodes` + `options` | — | — | **written here** (#180, a Workers + D1 app asked) |
+| `subscriber-declares-id` | backend-medusa | — | `objects` + `paths` + `options` | — | — | **written here** (a Medusa storefront's scan R5.4) |
+| `tables-declare-their-plane` | backend-workflows + tenant-scoping | `schema` | `paths` + `literal-call` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
+| `tenant-tables-carry-org-id` | tenant-scoping | `tenant` | `paths` + `literal-call` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
 | `test-no-clock-polling-for-promise-flips` | testbed | — | `nodes` + `paths` + `options` | — | — | **written here** (#4) |
 | `tokens-only-colors` | themekit | `tokenPrefix` | `paths` + `options` + `styling` + `colors` | — | — | **written here** (U2) |
-| `time-through-the-door` | backend-workflows | `door` | `paths` + `options` | — | yes | during only, de-hardcoded |
+| `time-through-the-door` | backend-workflows | `door` | `paths` + `options` | — | yes | a Workers + D1 app only, de-hardcoded |
 | `tissue-must-compose` | frontend | — | `paths` | yes | yes | diverged |
 | `tissue-no-data-props` | frontend | — | `paths` | yes | yes | diverged |
 | `tissue-no-hooks` | frontend | — | `paths` | yes | yes | diverged |
 | `tissue-no-organelles` | frontend | — | `directionRule` | yes | yes | diverged |
 | `tissue-no-stores` | frontend | — | `directionRule` | yes | yes | diverged |
 | `todo-names-its-plan` | tooling | `markers` | `comments` + `options` | — | — | **written here** (W28) |
-| `unique-query-step-name` | backend-medusa | `queryStepCalls` | `nodes` + `objects` + `options` | — | — | **written here** (dielime scan R4.3) |
-| `worker-handles-are-scoped` | backend-d1 | `within` | `paths` + `options` | — | yes (as `cell-handles-are-scoped`) | during only, de-hardcoded |
+| `unique-query-step-name` | backend-medusa | `queryStepCalls` | `nodes` + `objects` + `options` | — | — | **written here** (a Medusa storefront's scan R4.3) |
+| `worker-handles-are-scoped` | backend-d1 | `within` | `paths` + `options` | — | yes (as `cell-handles-are-scoped`) | a Workers + D1 app only, de-hardcoded |
 | `zustand-v5-best-practices` | frontend | — | — | yes | yes | **identical** |
 
 Preset sizes: frontend 36 · backend-workflows 16 · backend-medusa 12 · tenant-scoping 4 ·
@@ -770,13 +801,13 @@ the retry rule only since its key became an option — so both presets carry the
 of `backend-medusa` would take a live rule away from the repo it was written for, which is a
 downgrade wearing a preset change. `unique-query-step-name` stays Medusa's alone: the collision it
 reports is that framework's step-handler map last-winning, and a repeated step name on the org
-engine is DEFINED rather than lost (`reserve`, `reserve#2`, `engine.ts:124`).
+engine is DEFINED rather than lost (`reserve`, `reserve#2`, the engine's `reserveName`).
 
 ## The build
 
-Two builds existed. during.day's `package.json` resolves `.` through a `bun` condition to
+Two builds existed. A Workers + D1 app's `package.json` resolves `.` through a `bun` condition to
 `src/index.ts` and only falls back to `dist/index.js`; without bun, oxlint gets the fallback anyway.
-dielime's is the plain one — `tsup … --format esm --no-dts --platform node --out-dir dist` with
+A Medusa storefront's is the plain one — `tsup … --format esm --no-dts --platform node --out-dir dist` with
 `"exports": { ".": "./dist/index.js" }` — and that is what this package uses.
 
 It is **source-proven**, not assumed: `src/rules/fixtures.test.ts` runs the real `oxlint` binary with
@@ -787,7 +818,7 @@ fire" case would pass silently without that assertion.
 ## `fixShape`
 
 Every rule exports `{ meta, create, fixShape }`. `fixShape` is a short Markdown string in the voice
-of during.day's `during-code` skill: what the gate rejects and what to write instead.
+of a Workers + D1 app's own code skill: what the gate rejects and what to write instead.
 `pnpm generate:skill` assembles them into `skills/geonosis-code/SKILL.md`, grouped by preset. A
 staleness test fails when the committed skill is not what the rules generate, so the skill and the
 rules cannot drift.
@@ -807,7 +838,7 @@ enforce them on every file — which is what both source repos reported against
 2026-08-30. `@geonosis/doctor`'s `exercised` check reads `probe` off the plugin a config loads,
 writes it into a copy of the corpus, and runs again.
 
-A probe is a CLAIM, so `src/probes.test.ts` tries to break every one of them through the real
+A probe is a CLAIM, so `src/probes.bin.test.ts` tries to break every one of them through the real
 binary, under consumer-shaped options, and requires exactly one finding. Two rules deserve the
 detail:
 
@@ -816,7 +847,7 @@ detail:
   registry, so its probe declares BOTH — the directory under `roots`, and a registry carrying no
   string literal at all, so nothing in it can name the directory beside it. It was a single file
   until 2026-08-30 and fired nothing, which was the truth about the probe and a lie about every
-  consumer: dielime enforces this rule at error over four registries and read as a permanent FAIL
+  consumer: a Medusa storefront enforces this rule at error over four registries and read as a permanent FAIL
   for it.
 - `layer-walls` and the path-regex options are inverted by `lib/probe.ts`'s `pathMatching`, which
   builds a path back out of the pattern and then TESTS it against that pattern, refusing with a
@@ -843,7 +874,7 @@ option not named here is one no rule reads.
 | `compound-must-be-stateless` | — |
 | `compound-no-stores` | — |
 | `constants-in-constants-file` | — |
-| `dialect-through-the-seam` | — |
+| `dialect-through-the-seam` | `exempt`, `seam` |
 | `durable-body-reads-through-steps` | `durableKey`, `durableValue`, `ports`, `stepFactories`, `stepProxies`, `workflowFactories` |
 | `effect-hook-naming` | — |
 | `emit-declares-attempts` | `budgetHelpers`, `emitters` |
@@ -859,7 +890,7 @@ option not named here is one no rule reads.
 | `no-brand-names` | `allowedSubstrings`, `brands` |
 | `no-card-shaped-div` | — |
 | `no-cross-feature-stores` | — |
-| `no-d1-transaction` | — |
+| `no-d1-transaction` | `except`, `transacts` |
 | `no-date-string-compare` | `fieldPattern` |
 | `no-duplicate-jsx-patterns` | — |
 | `no-generic-utility-package` | `entries`, `names` |
@@ -871,36 +902,36 @@ option not named here is one no rule reads.
 | `no-loader-side-effect-in-index-file` | `directories`, `resourceFactories` |
 | `no-logic-in-component-files` | — |
 | `no-mock-db-in-integration` | `dbModules`, `integrationDirs`, `mockNames` |
-| `no-orm-outside-db` | — |
+| `no-orm-outside-db` | `dataLayer` |
 | `no-raw-html-atoms` | (a positional list), `scope` |
-| `no-raw-sql-outside-allowed` | — |
+| `no-raw-sql-outside-allowed` | `allow` |
 | `no-react-namespace` | — |
 | `no-renamed-html-props` | — |
 | `no-render-prop-reader` | — |
 | `no-runtime-dead-affordance` | (a positional list) |
 | `no-swallowed-catch` | `paths` |
 | `no-trivial-wrapper-component` | — |
-| `no-ts-in-bio-folders` | — |
+| `no-ts-in-bio-folders` | `extraFolders` |
 | `no-type-definitions-in-components` | — |
 | `no-unregistered-plugin-dir` | `manifests`, `registry`, `roots` |
-| `no-void-port` | — |
+| `no-void-port` | `engineCallbacks` |
 | `organelle-dependency` | `sharedFeatures` |
 | `organelle-single-source` | — |
 | `plugin-route-namespaced` | `packages`, `scopes` |
-| `queries-require-org-scope` | — |
+| `queries-require-org-scope` | `queries`, `tenantKey` |
 | `queue-loop-is-the-library` | — |
 | `route-no-inline-mutation` | `inlineMutationOk`, `mutationPrefixes`, `paths` |
 | `router-schema-parity` | `ignore`, `mounts`, `routers`, `schemas`, `suffix` |
 | `service-name-not-reserved` | `moduleFactories`, `reserved` |
-| `ssot-no-inline-facts` | `declarationCallees` |
-| `ssot-no-process-env` | — |
+| `ssot-no-inline-facts` | `declarationCallees`, `owners` |
+| `ssot-no-process-env` | `doors` |
 | `step-declares-compensation-or-none` | `stepFactories` |
 | `step-opens-its-own-cell` | `engine`, `hosts`, `scopeKey`, `within`, `wrapper` |
 | `store-route-scopes-tenant-data` | `entities`, `evidenceCalls`, `routes`, `scopingCalls` |
 | `subpath-over-barrel` | `packages` |
 | `subscriber-declares-id` | `paths` |
-| `tables-declare-their-plane` | — |
-| `tenant-tables-carry-org-id` | — |
+| `tables-declare-their-plane` | `schema` |
+| `tenant-tables-carry-org-id` | `tenant`, `tenantKey` |
 | `test-no-clock-polling-for-promise-flips` | `pollers`, `testGlobs` |
 | `time-through-the-door` | `door`, `exempt`, `exemptModules`, `libraries` |
 | `tissue-must-compose` | — |