@xhulz/nina 0.83.0 → 0.85.0

package/releases/0.84.0/surfaces/money/tree/.claude/patterns.md

@@ -0,0 +1,49 @@
+<!-- nina:slot money.1 -->
+
+---
+
+## Monetary values & percentages
+
+- **Money is an integer of the currency's minor unit**, end to end — {{MINOR_UNIT}}, never a float, never a type that can hold a fraction of one. Source of precision: `{{MONEY_MODULE}}`.
+- **Percentages are basis points** (`40% → 4000`, `100% → 10000`) so a distribution is exact without floating point.
+- **Parsing, formatting and percentage arithmetic live in one module and nowhere else.** A second place that turns a string into money is a second rounding rule, and the two will disagree on a value somebody is owed.
+- **Never** convert to a floating-point type before formatting, and never let a display format round a stored value.
+- Monetary database columns are integer. JSON responses serialize them as **strings**, not numbers, so no client parses them into a float. The service owns the conversion.
+
+<!-- nina:slot money.2 -->
+
+---
+
+## Distribution invariants (enforced by reviewer + unit tests)
+
+The distribution engine lives in `{{CORE_PKG}}`. It is pure and total over integer {{MINOR_UNIT}}:
+
+- A destination is either a percentage (basis points of the amount) or a fixed value.
+- `total = Σ destinations`, computed in {{MINOR_UNIT}}.
+- `total > amount` → **reject.** Never clamp, never distribute what is not there.
+- `total < amount` → **allow**, surface the shortfall, and leave the remainder **parked**. Silence is the defect here: an unexplained remainder is indistinguishable from a bug.
+- `total = amount` → OK.
+- A retention is just another destination — the same arithmetic applies to it, with no special case.
+
+<!-- nina:slot money.3 -->
+
+---
+
+## State machines & idempotency (enforced by reviewer)
+
+- **Every money-moving entity is a state machine.** Its states and legal transitions are declared in `.claude/architecture.md`; the code follows the declaration, not the other way round. Illegal transitions throw; they are never silently coerced.
+- **Every transition writes an audit row** (entity type, entity id, from, to, actor). No transition without a trail — the trail is what makes a money bug diagnosable after the money has moved.
+- **Outbound transfers are idempotent.** Each carries a unique key, and dedupe happens before the side effect, at the serialization point.
+- **One serialization point per balance.** Whatever computes and dispatches against a single balance never runs concurrently with itself. Two concurrent runs over one balance is how a double send happens even when every individual write is correct.
+
+<!-- nina:slot money.4 -->
+- **Money computation and dispatch go through the serialization point.** Routes, queue consumers and tools never run a distribution or a transfer synchronously in the request path.
+
+<!-- nina:slot money.5 -->
+- **The distribution engine lives in `{{CORE_PKG}}`.** Services call it as a pure function; they do not embed money logic inline.
+
+<!-- nina:slot money.6 -->
+- Idempotency on money-moving writes: the record carries an idempotency key, and the serialization point refuses the second attempt *before* the side effect.
+
+<!-- nina:slot money.7 -->
+- `{{CORE_PKG}}` is the most-tested package — pure functions over fixtures. Cover the distribution invariants exhaustively: over, under, exact, mixed percentage and fixed, and rounding.

package/releases/0.84.0/surfaces/money/tree/.claude/pipeline.md

@@ -0,0 +1,2 @@
+<!-- nina:slot money.1 -->
+  - **Money invariants respected** — a distribution never exceeds the amount; a shortfall is parked, not distributed; transfers idempotent; every transition audited.

package/releases/0.84.0/surfaces/money/tree/.claude/retrieval.md

@@ -0,0 +1,2 @@
+<!-- nina:slot money.1 -->
+| New distribution / transfer logic | `.claude/architecture.md` § *Money*, `.claude/patterns.md` § *Distribution invariants*, `{{CORE_PKG}}/` | architect → implementer → reviewer → qa |

package/releases/0.84.0/surfaces/money/tree/CLAUDE.md

@@ -0,0 +1,11 @@
+<!-- nina:slot money.1 -->
+3. **An outbound transfer is idempotent — it is NEVER sent twice.** Every transfer carries an idempotency key, and deduplication happens at a single serialization point **before** the side effect, never after it. A retry, a re-delivered queue message, a double-click and a replayed webhook must all collapse to one transfer. This is the highest-blast-radius invariant in the system: almost everything else can be corrected afterwards, and a duplicated transfer cannot.
+
+<!-- nina:slot money.2 -->
+4. **Conservation — what comes in equals what goes out plus what is retained.** A distribution may NEVER exceed the amount it distributes → **block**. If it is **less**, **alert** and leave the remainder **parked** and visible — never silently distributed, never silently absorbed. All arithmetic is integer {{MINOR_UNIT}}; percentages are basis points. The LLM never computes a monetary value.
+
+<!-- nina:slot money.3 -->
+5. **State-machine integrity.** Every money-moving entity has an explicit set of states and legal transitions, declared in `.claude/architecture.md` § *State machines* — not inferred from whatever code happens to exist. Only declared transitions are legal; an illegal one throws and is never silently coerced. **Every transition writes an audit row** (entity, id, from → to, actor, when). Skipping a state, inventing one, or landing a transition with no audit row is a hard reject.
+
+<!-- nina:slot money.4 -->
+- **money movement**: anything that creates, moves, settles or records a balance

package/releases/0.84.0/surfaces/pii/tree/.claude/agents/dba.md

@@ -0,0 +1,2 @@
+<!-- nina:slot pii.1 -->
+- **Privacy.** No sensitive value in clear text where it must not be. The categories are declared in `.claude/architecture.md` § *Privacy* — they are not decided per query, and not decided by you. **Document bytes live only in the object store, referenced by key: the column holds the key, never the bytes.** Any column the architect's spec flagged for masking must be encrypted at rest. Reject a schema that widens what is stored in the clear.

package/releases/0.84.0/surfaces/pii/tree/.claude/agents/devops.md

@@ -0,0 +1,8 @@
+<!-- nina:slot pii.1 -->
+
+**Point it at an UNAUTHENTICATED route — a sign-in page is the right one.** Never sign in, and never
+screenshot a signed-in page. Accounts on deployed environments hold real personal data, and a
+screenshot or a console dump pulls it into agent transcripts and logs, where it persists and nobody
+ever looks for it again. That is a privacy leak with no upside here: the sign-in page proves
+everything this check is for. It renders from the same bundle, it exercises the same build-time env
+inlining (a missing variable blanks it identically), and it needs no session.

package/releases/0.84.0/surfaces/pii/tree/.claude/agents/reviewer.md

@@ -0,0 +1,8 @@
+<!-- nina:slot pii.1 -->
+- Check for privacy regressions: **no sensitive value in a log, an error message — a library's own included — a URL or a test fixture**, per the categories in `.claude/architecture.md` § *Privacy*; document bytes only in the object store, never plaintext in the database; no leaked secret.
+
+<!-- nina:slot pii.2 -->
+- **privacy** — the privacy check above, in full: no sensitive value in a log, an error message, a
+  URL or a test fixture; document bytes only in the object store; no leaked secret. Where
+  **tenant-and-privacy** is dispatched, its reviewer owns this too and there is no separate one; where
+  it is not, this is a dimension of its own. Either way it is never nobody's.

package/releases/0.84.0/surfaces/pii/tree/.claude/agents/secops.md

@@ -0,0 +1,2 @@
+<!-- nina:slot pii.1 -->
+- **Privacy (Hard Rule #8)** — the categories declared in `.claude/architecture.md` § *Privacy* must never appear in logs, in responses that do not need them, in error paths, or in the database in clear text. Check every endpoint that returns a person's record for fields it includes by accident: a `select` that quietly grew a column is the usual way this leaks. Check the error paths too — they are written last and reviewed least — and what the libraries on them print or carry in their own errors, bound values included.

package/releases/0.84.0/surfaces/pii/tree/.claude/agents/solidity-auditor.md

@@ -0,0 +1,5 @@
+<!-- nina:slot pii.1 -->
+- **Nothing personal reaches the chain.** What is written on-chain is public, permanent, and beyond
+  deletion by anyone — including by you, and including after a subject asks. A hash of a personal
+  identifier is not a protection: it is a lookup table for whoever holds the input set. Reject a
+  personal datum stored in state, emitted in an event, or passed as calldata.

package/releases/0.84.0/surfaces/pii/tree/CLAUDE.md

@@ -0,0 +1,5 @@
+<!-- nina:slot pii.1 -->
+8. **Sensitive personal data is classified, and the classification is enforced.** What counts as sensitive here — identity documents, financial identifiers, anything a person would not expect to be readable by whoever can read a log — is declared in `.claude/architecture.md` § *Privacy*, along with the regime that governs it ({{PRIVACY_REGIME}}). Encrypted at rest. **No sensitive value in a log, an error message, a URL, an analytics event, or an agent transcript** — the places nobody thinks about are exactly the ones that persist. That includes what a library puts in its own errors and prints itself: a database client's error can carry the query and every bound value, and a framework can log a whole error past the logger it was given. A database error is mapped at the data layer to a typed error from a closed list before anything logs or returns it, and a test proves that a bound value it writes reaches no thrown error. **A value absent from an error that never held it proves nothing:** each test that shows a mapper or a sanitizer keeps a value out drives a failure whose raw error carries it — the spec names that failure class and cites where it renders bound values, an error that prints the call or a violation that echoes the input, never one that names only its constraint — and asserts first that the raw, unmapped error of the same operation contains the value, a control kept in memory and never printed; the mutant that copies the raw error's `message`, `cause` or details across turns it red.<!-- nina:why --> In one project a spec proved its error mapper on a foreign-key failure, whose message and details name only the constraint, so no mapper that copied them could turn the test red.<!-- /nina:why --> **A test that proves a value stays out matches by containment** (`String(v).includes(value)`), never by equality: a leak arrives inside an id, a message or a key. It gives each log call in the source a run, counts the console's calls by method and asserts each method the path must not use at zero, and reads at least what the console prints of each entry and each error the runs produce, recursively: every own key, symbols and non-enumerable ones too (`Reflect.ownKeys`), and the entries of every `Map`, `Set`, `Headers` and `URLSearchParams`, unless the spec rules one out in writing. Its controls put their value where the real emitter puts its own, past a call's first argument and among several, and the spec names the window its spy covers and why nothing logs after it. Its forbidden values are the run's own that § *Privacy* keeps out — where it lists what may be logged, every other value the run carries — each with a control that embeds it in a longer string under an allowed key and must fail the check — the values one run adds as much as a shared list's, since a check that folds accents passes every control written in ASCII — and no fixture value inside another's.<!-- nina:why --> In one project an allowlist check that refused only equal values passed a mutant logging `${id}:${amount}`; the next read `Object.keys` and missed an amount on a non-enumerable property and an info log no row inspected; the one after left out a class and four log paths.<!-- /nina:why --> Where what it claims to keep out names a class — an attribute, an amount — it covers every member: a surface with open-ended slots is read whole, never through a list of them — every attribute of every element a rendered page carries, just as every property of an error is — and a sweep that read nothing fails; each forbidden value is looked for in every form the code can give it, formatted and raw; and each state that shows, hides or replaces a value is swept on its own, the one built to withhold it most of all. One mutant puts the value in a slot the check does not name — `data-x` on a page; on an object or an error, a non-enumerable key, a symbol key, a nested object, a `Map` entry, `cause`, the end of `message` or `stack` — and one per field puts that field's raw value in each such slot, on every error the code throws, not only one it builds: one left green is a slot or a form the check misses. The implementer runs them on its mirror, as one block it reuses, before `DIFF-READY`, whatever the step lists, and reports one left green as the row the spec lacks (Hard Rule #17), adding it only in a file the step authorizes.<!-- nina:why --> In one project a walk of own keys missed a `Map`, a symbol key and a nested object, and every control put its value in a call's first argument, where the runtime's loggers put theirs second; then three steps in two days went back from review for a slot no listed mutant tried — an error's `cause`, its `stack`, a hidden key.<!-- /nina:why --><!-- nina:why --> In one project a sweep of `data-testid`, `aria-label` and `title`, proven by mutants in those three, stayed green with the label in a `data-label`; the next swept every attribute for the formatted amounts and missed their raw centavos; the one after swept only the state that shows the figure, and the row built to show none carried it in a `title`.<!-- /nina:why --> Document bytes live only in the object store, referenced by key, never in the database in clear text.
+
+<!-- nina:slot pii.2 -->
+- **personal data**: where it is collected, stored, logged or sent

package/releases/0.84.0/surfaces/prisma/tree/.claude/agents/architect.md

@@ -0,0 +1,2 @@
+<!-- nina:slot prisma.1 -->
+| `prisma-client-api` | a new or changed Prisma query |

package/releases/0.84.0/surfaces/prisma/tree/.claude/agents/dba.md

@@ -0,0 +1,42 @@
+<!-- nina:slot prisma.1 -->
+| `prisma-cli` | **before ANY `prisma` CLI command** — `validate`, `format`, `migrate dev`, `migrate diff`, `migrate deploy`. Flags differ between versions, and one of them (`migrate diff --shadow-database-url` against a live database) destroys the database it points at |
+| `prisma-client-api` | auditing a new or changed query — filters, operators, `$transaction` semantics. Through a driver adapter, cite the adapter's installed source for what a transaction does: the skill describes the default engine, and an adapter can roll back less |
+
+<!-- nina:slot prisma.2 -->
+Neither skill covers a **caching or edge layer sitting on top of the client** — cache strategy,
+edge-client behaviour and the rule about never caching a read that authorizes a write belong to that
+layer's own integration doc, declared like any other integration. A skill does not replace it.
+
+<!-- nina:slot prisma.3 -->
+- **With Prisma, both offline.** Run `pnpm --filter {{DB_PKG_NAME}} exec prisma validate`; it must pass. Then run `prisma migrate diff` in its **offline, file-only form** and read the generated SQL, not just the Prisma delta. Its flags changed in Prisma 7, so read the installed major (`prisma --version`) before writing the command:
+
+   ```
+   # Prisma 6. Compare the PREVIOUS schema against the working one — pure file-to-file, no database.
+   git show HEAD:{{DB_PKG}}/prisma/schema.prisma > /tmp/schema-head.prisma
+   pnpm --filter {{DB_PKG_NAME}} exec prisma migrate diff \
+     --from-schema-datamodel /tmp/schema-head.prisma \
+     --to-schema-datamodel prisma/schema.prisma \
+     --script
+   ```
+
+   From Prisma 7 the two flags are `--from-schema` and `--to-schema`, and the schema engine starts from the
+   datasource in `prisma.config.ts` even for this diff: with none there, it prints nothing and exits 0. For
+   SQLite a placeholder the diff never opens is enough, a `file:` URL under a gitignored directory; for any
+   other provider, find out what the diff opens before you give it one. Never a real database's URL. A first schema has nothing at `HEAD`: diff it `--from-empty`. Compare the output against the
+   hand-written `migration.sql` to confirm the declarative parts match.
+
+   ⚠️ **Do NOT reach for `--from-migrations`.** It looks like the natural choice and it is a trap:
+   Prisma refuses it without a shadow database (`--shadow-database-url`, or from Prisma 7 a
+   `shadowDatabaseUrl` in `prisma.config.ts`), which pushes you toward supplying a database URL — the exact move that destroys databases (below). The file-to-file form above answers the
+   same question with no database involved.
+
+   ⛔ **NEVER point `--shadow-database-url`, `--from-url`, `--to-url`, `--from-schema-datasource` — or, from Prisma 7, a `shadowDatabaseUrl` or the config datasource behind `--from-config-datasource` — at a real database, most of all not the one `{{SECRETS_LOCAL}}` names.** Prisma **executes** the entire migration history against whatever database those flags name, which **DESTROYS ALL DATA** in it. A shadow database must be a disposable, empty database and nothing else. It does not announce itself: the command completes with a reassuring "empty migration" result and no error, having already destroyed everything in the database it was pointed at. If the offline form above cannot answer your question, **STOP and report that to the orchestrator** instead of reaching for a database URL.
+
+<!-- nina:slot prisma.4 -->
+- **Where reads are cached through Prisma Accelerate,** every `findUnique` / `findMany` on a hot read path names its `cacheStrategy` (`ttl` / `swr`), and one that feeds a correctness-critical write names none.
+
+<!-- nina:slot prisma.5 -->
+- **On an edge runtime,** new Prisma code paths use the edge client of the installed major: `@prisma/client/edge` up to Prisma 6; from 7, the client the `prisma-client` generator writes with the platform's `runtime` set, imported from where it is generated — `@prisma/client/edge` fails there with `MODULE_NOT_FOUND`.
+
+<!-- nina:slot prisma.6 -->
+- Run a Prisma command that writes to a real database — `prisma migrate dev`, `migrate deploy`, `migrate reset`, `migrate resolve`, `db push`, `db execute`, `$executeRaw*` — or **any `prisma migrate diff` variant carrying a database URL**, which silently wipes the database it points at.

package/releases/0.84.0/surfaces/prisma/tree/.claude/agents/devops.md

@@ -0,0 +1,11 @@
+<!-- nina:slot prisma.1 -->
+- **`prisma-cli`** — before `migrate deploy` or any other Prisma CLI command against a real database.
+
+<!-- nina:slot prisma.2 -->
+- **Prisma migrations go out with `prisma migrate deploy`**, and nothing else changes a shared database's schema.
+
+<!-- nina:slot prisma.3 -->
+- Run `prisma migrate diff --shadow-database-url <url>` against any live database. It **executes** the migration history against that database, destroying everything in it, and reports success. Use a disposable shadow database or don't run it.
+
+<!-- nina:slot prisma.4 -->
+- Run `prisma migrate reset` against a shared database, ever.

package/releases/0.84.0/surfaces/prisma/tree/.claude/agents/implementer.md

@@ -0,0 +1,2 @@
+<!-- nina:slot prisma.1 -->
+| `prisma-client-api` | a new or changed Prisma query |

package/releases/0.84.0/surfaces/prisma/tree/.claude/agents/integration-tester.md

@@ -0,0 +1,2 @@
+<!-- nina:slot prisma.1 -->
+| `prisma-cli` | a Prisma CLI command |

package/releases/0.84.0/surfaces/prisma/tree/.claude/agents/reviewer.md

@@ -0,0 +1,2 @@
+<!-- nina:slot prisma.1 -->
+| `prisma-client-api` | a new or changed Prisma query |

package/releases/0.84.0/surfaces/prisma/tree/.claude/patterns.md

@@ -0,0 +1,15 @@
+<!-- nina:slot prisma.1 -->
+- **Database table/column names** (Prisma `@map` / `@@map`): `snake_case` in SQL, `camelCase` in TS.
+
+<!-- nina:slot prisma.2 -->
+- Where Prisma reads are cached through Accelerate, `cacheStrategy` lives in `{{DB_PKG}}`: services do not add, strip, or override cache policies.
+
+<!-- nina:slot prisma.3 -->
+
+### Prisma
+
+- Schema lives in `{{DB_PKG}}/prisma/schema.prisma`. Nowhere else.
+- **Never write raw SQL** unless justified in a code comment with perf data.
+- N+1 is solved with `include` / `select`, chosen deliberately.
+- Where reads are cached through Accelerate, every `findUnique` / `findMany` on a hot path defines its `cacheStrategy`, and no direct connection string is embedded in code.
+- Tests run a real Prisma client against a real database; the client is never mocked.

package/releases/0.84.0/surfaces/prisma/tree/CLAUDE.md

@@ -0,0 +1,5 @@
+<!-- nina:slot prisma.1 -->
+| Run any `prisma` CLI command (the database gate, devops, and the integration gate where there is one) | `prisma-cli` | flags differ between versions; `migrate diff --shadow-database-url` against a live DB wiped dev/staging once |
+
+<!-- nina:slot prisma.2 -->
+| Write or audit a Prisma query (architect, implementer, the database gate, reviewer) | `prisma-client-api` | filters, operators, `$transaction` semantics. a caching or edge layer on top of the client is **NOT covered** — its cache strategy belongs to that layer's own integration doc |

package/releases/0.85.0/core/GAPS.md

@@ -0,0 +1,125 @@
+# Known gaps
+
+The harness was extracted by slicing one live project, and a slice cannot be cleaner than the
+thing it was cut from. This file tracks what is still shaped by that origin.
+
+## Closed
+
+**Domain examples in the core.** The extraction had to leave money and PII nouns in otherwise
+invariant rules, because byte-exact recomposition was the proof that nothing was lost and
+rewriting a line broke it. Once projects started pinning a release, that constraint lifted:
+the core no longer names payouts, escrow, KYC, PIX, CPF or a single provider, and the
+`db` surface no longer assumes the write it protects is a money movement. `fixtures/acme`
+holds the line — it declares no `money` and no `pii` surface, and the test fails on any of
+those words reappearing.
+
+**The single-provider assumption.** `external-api` became `integrations`, plural, cut by how
+a premise is settled (`installed-library` / `live-api` / `platform-binding`) rather than by
+one project's payment provider.
+
+**The `money` surface was one project's money path.** It shipped that project's state machine
+(`DETECTADA → CASADA | DIVERGENTE | SEM_REGRA`) as a harness rule, named its models, its
+currency and its escrow vocabulary, and assumed one payment provider. It now states the
+invariants and nothing else: conservation, idempotency of an irreversible send, one
+serialization point per balance, integer minor units, and a state machine the **project**
+declares in its own `.claude/architecture.md`. `fixtures/ledger` holds that line — a money
+project whose minor unit is `cents`, whose engine is `packages/settlement`, and whose deny
+list fails on `escrow`, `centavos`, `Payout`, `DETECTADA` or any of the rest reappearing.
+
+**The `pii` surface was one country's regime.** It named CPF/CNPJ, PIX keys, KYC documents, LGPD,
+R2 and Postgres as if they were universal categories. It now says that sensitive categories are
+**declared by the project** in its own `.claude/architecture.md`, and states what is invariant:
+classified, encrypted at rest, never in a log, an error, a URL, an analytics event or an agent
+transcript, and document bytes only in the object store. `fixtures/ledger` declares `pii` with a
+`GDPR` regime and fails on any of the old words returning.
+
+**Incident dates that read as false history.** Five places told a rule through a date it happened
+on — a wiped database on 2026-09-16, a blocked deploy on 2026-09-21, specs split across two
+directories before 2026-09-04. In the project where it happened that is provenance; in a new one it
+is a claim about a past it does not have, and an agent will go looking for it. The rules keep their
+force without the date: *"the command completes with a reassuring 'empty migration' result and no
+error, having already destroyed everything in the database it was pointed at."*
+
+**A rule cross-reference that pointed at nothing.** The hard rules are one numbered list assembled
+from several layers, so a project that declares no `integrations` surface has no rule 12 — while the
+core still said "the premise rule (#12 below)". `compose-test` now checks every `Hard Rule #N`
+against the rules the project actually composed, and `fixtures/plain` declares no surface at all, so
+the most reduced case is exercised on every run.
+
+**Invariant rules that landed in the project layer.** Four rules were generically valuable but were
+stated through an incident or an inventory belonging to one project, so the project layer swallowed
+them and a new project got nothing. Each was restated in the layer that actually owns it:
+
+| Spec | What it got back |
+|---|---|
+| secops | the **AuthN / session** dimension is now core: credential issuance and consumption, cookie flags, fixation across a privilege change, origin allowlist, and any dev bypass that could reach production. The project slot survives for the auth library and the bypasses that project actually has. |
+| qa | the *"pre-existing failure"* traps moved to `surfaces/frontend` — they are facts about a jsdom + vitest harness, not about one feature. The project slot held only the provenance, so it was dropped. |
+| architect, implementer | both specs now state the Route → Service → Data rule themselves instead of only `patterns.md` stating it. The project slot survives for the package names. |
+| patterns | *"when correcting a document, delete what you are correcting"* is now a core section. |
+
+**The threat model was numbered, and the numbers came from slots.** Dimensions 1–8 lived in surface
+fragments and 9–10 in the core, so a project declaring every surface got 1–10 and everyone else got
+a list with holes: `acme` read `2, 3, 6, 8, 9, 10`, and a surfaceless project began at **9**. The
+list is bullets now, valid under any combination. The core's rate-limiting dimension also named one
+project's auth strategy (`magic-link request, dev routes`); it says `issues a credential` instead.
+
+**A surface's technology was named in files nothing gated.** The item above used to bundle two
+different things under "stack-specific", and only one of them was a choice. `Prisma` appeared in 7
+ungated core files and Cloudflare's runtime in 10 — technologies that already *have* surfaces, named
+in text every project composes. A frontend-only project read a `CLAUDE.md` that discussed Prisma, a
+`patterns.md` headed *API (Cloudflare Worker / Hono) conventions*, and a qa spec telling it to kill
+stray `workerd` processes that could not exist. The reviewer even pointed at `CLAUDE.md` §
+*Cloudflare plugin skills*, a section that lives in the edge-cf surface — a dangling cross-reference
+of exactly the kind already closed once here.
+
+42 sites were fixed by saying what the rule means rather than which product implements it: "if the
+database was touched" instead of "if Prisma touched", "deploy config" instead of "wrangler config",
+"the local emulator" instead of "Miniflare". None of it lost precision, because the instruction was
+never about the product. Where a genuine specific was worth keeping it moved into `surfaces/edge-cf`
+behind a slot.
+
+The deny lists never caught this, and could not: they guard one fixture's output against *domain*
+leaks, and a substring match makes a word like `Hono` unusable because it fires on `Honor`. The
+guard is now a layer audit in `compose:test` — for every core file, a surface's technology may be
+named only if the file is gated on that surface. It asks the question once, of everything, instead
+of only of what a fixture happens to compose.
+
+**Money in the core, and the heavy-gate list that carried it.** The extraction closed money's nouns
+(payout, escrow, the state machine) but not the word itself: ten places in the core listed "money, the
+database, auth, an integration" as the changes that are always gated in full, so a project with no
+money was told that under-gating a money movement was a protocol violation, and its devops that a
+production deploy "moves real money". The audit now holds `money` like a technology, and found 19 of
+them. The list is one definition of **critical paths** in `CLAUDE.md` — auth in the core, and the
+database, an integration boundary, money movement, personal data and contract code each added by its
+own surface — and the ten places say "a critical path". Two copies of money's own rules had also
+landed in `surfaces/db` (`BigInt` columns, a money-integrity check in the dba's report), contradicting
+the money surface's integer minor unit; they are gone, since the money surface already says it better.
+The same pass found Cloudflare's `Pages`, `Worker` and a capitalised `Wrangler` in the core and in
+two surfaces, and the leftovers no audit could name: a model called `DestinationAccount` and a spec
+set called `retention-spec1..8` in the router's examples, "all nine stages" where a profile composes
+seven to eleven, `userId` as the name of owner scoping, and "the harness's first three months" told
+as the history of whichever project was reading it.
+
+## Open
+
+**The core is domain-agnostic, not stack-agnostic — deliberately.** The stack's own commands are
+vocabulary now, with the release's defaults (`core/vocabulary.json`): the typecheck, lint and build
+commands a spec tells a stage to run, and the test command every stage but qa is told not to run. qa's
+own targeted `vitest run` stays literal. What remains is the stack's substance, not its commands:
+`vitest` and its memory discipline, `TSDoc`, `TypeScript`, `turbo`, and `pnpm` wherever a sentence
+describes the workspace rather than a command to run. That is the single track
+this harness is for, and most of it is load-bearing: the qa spec's memory discipline is a fact about
+vitest, not about testing. Unlike the surface leak above, this is not a defect — there is no
+`pnpm` surface a project could decline. It becomes a gap only when a project on another stack
+appears. The `.js`-extension and barrel-export rules are the sharpest case — they assume a
+TypeScript monorepo that emits `dist/`, and `fixtures/plain` needs `PKG_SCOPE` and `EMITTING_PKGS`
+in its vocabulary to compose at all. If a second stack ever arrives, those are a `ts-monorepo`
+surface, not core.
+
+**A composed project is not a finished project — by design.** With no project layer, `CLAUDE.md`
+still opens with blank lines and no title, mission or stack. That is not a defect to fix in the
+core: the missing text is the part only this project can say. `init` conducts the interview and
+writes it to `.nina/TODO.md`, and it deliberately writes **no stub fragments**, because a stub is
+a filled slot as far as every tool is concerned — a tree of TODOs would compose and check clean
+while saying nothing. So `compose` keeps naming the unfilled slots until a person fills them, and
+the blank opening is that list being honest rather than the core being incomplete.

package/releases/0.85.0/core/answered.json

@@ -0,0 +1,137 @@
+{
+  "2026-09-22-integration-tester__regenerate-the-premise-index-after-editing-an-integration-doc": {
+    "in": "core/tree/.claude/agents/integration-tester.md"
+  },
+  "2026-09-22-qa__exit-code-is-the-verdict": {
+    "in": "core/tree/.claude/agents/qa.md"
+  },
+  "2026-09-22-shared__test-must-name-the-mutation-that-fails-it": {
+    "in": "core/tree/.claude/agents/reviewer.md"
+  },
+  "2026-09-25-shared__docs-match-final-code": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-09-25-shared__fail-closed-on-every-branch": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-09-25-shared__test-must-fail-under-its-mutation": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-09-25-shared__tsdoc-covers-members": {
+    "in": "core/tree/CLAUDE.md"
+  },
+  "2026-09-26-architect__revision-sweeps-contradicted-text": {
+    "in": "core/tree/.claude/agents/architect.md"
+  },
+  "2026-09-26-shared__run-the-mutation-not-only-the-assertion": {
+    "in": "core/tree/.claude/agents/qa.md"
+  },
+  "2026-09-26-shared__validate-patterns-against-real-samples": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-09-28-shared__docs-match-final-code": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-09-28-shared__fail-closed-on-every-branch": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-09-28-shared__test-must-fail-under-its-mutation": {
+    "in": "core/tree/.claude/agents/qa.md"
+  },
+  "2026-10-08-implementer__spike-result-claims-only-what-ran": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-10-architect__mirrored-parsers-cite-the-whole-input-path": {
+    "in": "core/tree/.claude/agents/architect.md"
+  },
+  "2026-10-10-architect__rule-checkers-cover-every-form-the-rule-names": {
+    "in": "core/tree/.claude/agents/architect.md"
+  },
+  "2026-10-10-architect__security-filters-list-their-bypasses": {
+    "in": "core/tree/.claude/agents/architect.md"
+  },
+  "2026-10-10-implementer__fails-if-mutations-are-run": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-10-shared__controls-drive-the-code-they-guard": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-11-implementer__a-miss-in-your-mutation-log-is-a-claim-to-fix": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-11-implementer__tsdoc-covers-fake-members-and-local-functions": {
+    "in": "core/tree/CLAUDE.md"
+  },
+  "2026-10-11-shared__doc-claims-match-the-recorded-premises": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-13-architect__source-scanners-match-lexer-tokens": {
+    "in": "core/tree/.claude/agents/architect.md"
+  },
+  "2026-10-13-implementer__batteries-drop-each-guard-conjunct": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-13-shared__scratch-dirs-are-named-for-your-stage": {
+    "in": "core/tree/CLAUDE.md"
+  },
+  "2026-10-15-implementer__tsdoc-sweep-includes-edited-test-stub-members": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-18-architect__spike-checks-fail-closed": {
+    "in": "core/tree/.claude/agents/architect.md"
+  },
+  "2026-10-20-shared__dictated-tsdoc-for-unbuilt-consumer-is-a-contract": {
+    "in": "core/tree/.claude/patterns.md"
+  },
+  "2026-10-20-shared__network-controls-use-a-local-listener": {
+    "in": "core/tree/CLAUDE.md"
+  },
+  "2026-10-20-shared__wrangler-update-check-stays-local": {
+    "in": "surfaces/edge-cf/tree/CLAUDE.md"
+  },
+  "2026-10-21-harness__sizes-names-matches-a-step-number-anywhere-in-the-subject": {
+    "in": "core/tree/.claude/router.md"
+  },
+  "2026-10-21-implementer__size-cap-is-checked-before-writing-not-after": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-21-implementer__tsdoc-sweep-includes-edited-test-stub-members": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-21-shared__leak-check-matches-by-containment-and-covers-every-privacy-class": {
+    "in": "surfaces/pii/tree/CLAUDE.md"
+  },
+  "2026-10-23-implementer__a-never-in-an-attribute-check-sweeps-every-attribute": {
+    "in": "surfaces/pii/tree/CLAUDE.md"
+  },
+  "2026-10-23-shared__invisible-or-lookalike-characters-are-written-as-escapes": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-23-shared__scratch-files-live-in-your-mktemp-dir-never-the-scratchpad-root": {
+    "in": "core/tree/CLAUDE.md"
+  },
+  "2026-10-24-shared__scratch-root-holds-no-path-note": {
+    "in": "core/tree/CLAUDE.md"
+  },
+  "2026-10-25-architect__pass-through-inputs-vary-across-cases": {
+    "in": "core/tree/.claude/agents/architect.md"
+  },
+  "2026-10-25-implementer__survivors-are-equivalent-or-killed": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-27-architect__leak-walk-reads-what-the-console-prints": {
+    "in": "surfaces/pii/tree/CLAUDE.md"
+  },
+  "2026-10-28-architect__no-leak-test-needs-a-control-that-the-raw-error-carries-it": {
+    "in": "surfaces/pii/tree/CLAUDE.md"
+  },
+  "2026-10-28-implementer__a-leak-row-is-tried-with-unnamed-slot-mutants-before-diff-ready": {
+    "in": "surfaces/pii/tree/CLAUDE.md"
+  },
+  "2026-10-28-implementer__fails-if-comment-from-the-per-test-red-list": {
+    "in": "core/tree/.claude/agents/implementer.md"
+  },
+  "2026-10-29-architect__a-row-for-a-behaviour-at-two-call-sites-runs-at-each": {
+    "in": "core/tree/.claude/agents/architect.md"
+  }
+}

package/releases/0.85.0/core/defaults/tree/.claude/agents/architect.md

@@ -0,0 +1 @@
+<!-- nina:slot project.7 -->

package/releases/0.85.0/core/defaults/tree/.claude/agents/dba.md

@@ -0,0 +1,3 @@
+<!-- nina:slot project.1 -->
+description: Use when a diff touches the schema, a migration or a query, in the same message as the reviewer. Architect and implementer may also ask it while designing one. Checks migration safety, query cost and indexes, cache and freshness rules, and data integrity, and returns APPROVED or REJECTED. The reviewer does not approve without its sign-off. Never writes application code.
+<!-- nina:slot project.4 -->

package/releases/0.85.0/core/defaults/tree/.claude/agents/devops.md

@@ -0,0 +1 @@
+<!-- nina:slot project.4 -->

package/releases/0.85.0/core/defaults/tree/.claude/agents/implementer.md

@@ -0,0 +1 @@
+<!-- nina:slot project.4 -->

package/releases/0.85.0/core/defaults/tree/.claude/agents/integration-tester.md

@@ -0,0 +1,3 @@
+<!-- nina:slot project.1 -->
+description: Use when a diff touches an integration boundary, meaning a service, library or platform binding whose behavior this project does not define. Verifies each premise against the real dependency rather than the mock, and returns APPROVED or REJECTED. A wrong premise goes back to the architect, code that does not honor a premise to the implementer.
+<!-- nina:slot project.5 -->

package/releases/0.85.0/core/defaults/tree/.claude/agents/qa.md

@@ -0,0 +1,7 @@
+<!-- nina:slot project.1 -->
+description: Use after the reviewer approves. Runs the tests of the packages the diff touched, once and never beside another test run, and returns PASS or FAIL with the exit code as the verdict. A failure loops back to the implementer, or to the architect when the test is right and the spec was wrong. Never writes code.
+
+<!-- nina:slot project.5 package-run -->
+  ```bash
+  cd <package-path> && pnpm exec vitest run [--reporter=verbose] > /tmp/qa-<dir>.txt 2>&1; echo "EXIT=$?"
+  ```

package/releases/0.85.0/core/defaults/tree/.claude/agents/reviewer.md

@@ -0,0 +1,3 @@
+<!-- nina:slot project.1 -->
+description: Use after the implementer produces a diff, in the same message as every gate the diff triggered. Audits the diff against the architect's spec, runs typecheck, lint and build (never the tests, which qa runs after approval), and names every gate the diff triggers, which run beside it; qa waits for all of them. Returns APPROVED or REJECTED. Read-only, never fixes.
+<!-- nina:slot project.3 -->

package/releases/0.85.0/core/defaults/tree/.claude/agents/secops.md

@@ -0,0 +1,3 @@
+<!-- nina:slot project.1 -->
+description: Use after the last step of a milestone passes qa, or when the owner asks for a security pass. Audits the assembled system as an attacker and as a privacy and compliance auditor, scoped to the milestone's diff, and returns SECURE or BLOCKED with each finding's severity. Not a substitute for the reviewer. Writes nothing to the repo.
+<!-- nina:slot project.7 -->

package/releases/0.85.0/core/defaults/tree/.claude/agents/solidity-auditor.md

@@ -0,0 +1,3 @@
+<!-- nina:slot project.1 -->
+description: Use on any diff that touches a contract, a deploy script, or a library version the contracts import, wherever the pipeline is. Audits the diff as an attacker before anything deploys, and returns APPROVED or REJECTED with the path and call sequence of each finding. The reviewer does not approve, and devops does not deploy, without its sign-off.
+<!-- nina:slot project.5 -->

package/releases/0.85.0/core/defaults/tree/.claude/agents/solidity-dev.md

@@ -0,0 +1,3 @@
+<!-- nina:slot project.1 -->
+description: Use when the architect's spec changes contract code. Writes the contract change and its adversarial tests, treating deployed code as immutable, so work that cannot be made safe as specified is BLOCKED rather than merged with a follow-up. Hands its diff to the solidity-auditor.
+<!-- nina:slot project.5 -->

package/releases/0.85.0/core/tiers.json

@@ -0,0 +1,5 @@
+{
+  "low": { "DEEP_MODEL": "claude-sonnet-5-5", "WORK_EFFORT": "medium" },
+  "medium": { "DEEP_MODEL": "claude-sonnet-5-5", "DEEP_EFFORT": "xhigh", "WORK_EFFORT": "high" },
+  "high": {}
+}