@xhulz/nina 0.28.16

package/evals/reviewer/after/src/server/services/notes.ts

@@ -0,0 +1,50 @@
+import { findNote, setArchived } from '../data/notes';
+import { NoteNotFoundError } from '../errors.js';
+
+/** A note as the API returns it. */
+export interface Note {
+  id: string;
+  body: string;
+  archived: boolean;
+  updatedAt: string;
+}
+
+/** A note just archived, with the moment it happened. */
+export interface ArchivedNote {
+  id: string;
+  body: string;
+  archived: boolean;
+  updatedAt: Date;
+}
+
+/**
+ * Reads one of the owner's notes.
+ *
+ * @param ownerId - The user asking.
+ * @param id - The note id.
+ * @returns The note.
+ * @throws NoteNotFoundError when the note does not exist or is not the owner's.
+ */
+export function getNote(ownerId: string, id: string): Note {
+  const row = findNote(id);
+  if (!row || row.ownerId !== ownerId) throw new NoteNotFoundError(id);
+  return { id: row.id, body: row.body, archived: row.archived, updatedAt: row.updatedAt.toISOString() };
+}
+
+/**
+ * Archives one of the owner's notes.
+ *
+ * @param ownerId - The user asking.
+ * @param id - The note id.
+ * @returns The archived note.
+ */
+export function archiveNote(ownerId: string, id: string): ArchivedNote {
+  const row = findNote(id);
+  if (!row) throw new NoteNotFoundError(id);
+  try {
+    const next = setArchived(id, !row.archived);
+    return { id: row.id, body: row.body, archived: next?.archived ?? true, updatedAt: next?.updatedAt ?? new Date() };
+  } catch {
+    return { id: row.id, body: row.body, archived: row.archived, updatedAt: row.updatedAt };
+  }
+}

package/evals/reviewer/base/.claude/architecture.md

@@ -0,0 +1,5 @@
+# Architecture
+
+Route → Service → Data. A route translates between HTTP and the service; a service applies the
+owner check and formats every date as ISO 8601; the data layer stores rows and knows nothing of
+owners or HTTP. Errors are named classes in `src/server/errors.ts`.

package/evals/reviewer/base/.claude/code-map.md

@@ -0,0 +1,12 @@
+# Code map
+
+A notes API, framework-agnostic: each route is a function from an authenticated owner and path
+parameters to a status and a body.
+
+- `src/server/routes/` — one handler per endpoint. Calls services only.
+- `src/server/services/` — business rules: owner scoping, date formatting, named errors.
+- `src/server/data/` — the store. An in-memory map stands in for the database.
+- `src/server/errors.ts` — the named errors services throw and routes translate.
+
+Invariant: a note is only ever read or changed by its owner; anyone else gets the same 404 as a
+note that does not exist.

package/evals/reviewer/base/.claude/plans/specs/archive-notes.md

@@ -0,0 +1,33 @@
+# Spec: archive a note
+
+## Goal
+An owner can archive one of their notes. Archiving is idempotent: archiving a note that is already
+archived leaves it archived, and still returns 200.
+
+## Files to touch
+- `src/server/data/notes.ts` — modify: add `setArchived(id, archived)`, returning the updated row.
+- `src/server/services/notes.ts` — modify: add `archiveNote(ownerId, id)`, owner-scoped exactly like
+  `getNote`, returning the updated `Note` with its date already formatted.
+- `src/server/routes/notes.ts` — modify: add `archiveNoteRoute(ownerId, id)` for
+  `PATCH /notes/:id/archive` — 200 with the note; 404 when the note does not exist or is not the
+  owner's.
+- `src/server/services/notes.test.ts` — modify: tests for archiving, each naming the mutation that
+  turns it red.
+- `src/server/services/legacy-archive.ts` — delete.
+
+## Out of scope
+Every other file, `src/server/config.ts` included.
+
+## Obsolescence list
+- `src/server/services/legacy-archive.ts` and its export `legacyArchive` are dead once `archiveNote`
+  exists. Delete the file.
+
+## Layering
+Route → Service → Data. The route calls the service only. The service owns the owner check, the date
+formatting and the named errors.
+
+## Premises
+- `findNote` returns `undefined` for an unknown id — `src/server/data/notes.ts`.
+
+## Preview deploy plan
+None: this change is not deployed on its own.

package/evals/reviewer/base/package.json

@@ -0,0 +1,9 @@
+{
+  "name": "notes",
+  "private": true,
+  "type": "module",
+  "scripts": {
+    "typecheck": "tsc --noEmit",
+    "test": "vitest run"
+  }
+}

package/evals/reviewer/base/src/server/config.ts

@@ -0,0 +1,5 @@
+/** How long a session may be idle before the user must sign in again, in minutes. */
+export const SESSION_IDLE_MINUTES = 30;
+
+/** The most notes one page of a listing returns. */
+export const PAGE_SIZE = 50;

package/evals/reviewer/base/src/server/data/notes.ts

@@ -0,0 +1,29 @@
+/** A note as it is stored. */
+export interface NoteRow {
+  id: string;
+  ownerId: string;
+  body: string;
+  archived: boolean;
+  updatedAt: Date;
+}
+
+const rows = new Map<string, NoteRow>();
+
+/**
+ * Finds one note by id.
+ *
+ * @param id - The note id.
+ * @returns The row, or undefined when there is none.
+ */
+export function findNote(id: string): NoteRow | undefined {
+  return rows.get(id);
+}
+
+/**
+ * Stores a note, replacing any row with the same id.
+ *
+ * @param row - The row to store.
+ */
+export function saveNote(row: NoteRow): void {
+  rows.set(row.id, row);
+}

package/evals/reviewer/base/src/server/errors.ts

@@ -0,0 +1,10 @@
+/** A note that does not exist, or that belongs to someone else. */
+export class NoteNotFoundError extends Error {
+  /**
+   * @param id - The note that was asked for.
+   */
+  constructor(id: string) {
+    super(`note ${id} not found`);
+    this.name = 'NoteNotFoundError';
+  }
+}

package/evals/reviewer/base/src/server/routes/notes.ts

@@ -0,0 +1,24 @@
+import { NoteNotFoundError } from '../errors.js';
+import { getNote } from '../services/notes.js';
+
+/** What a handler returns. */
+export interface Reply {
+  status: number;
+  body: unknown;
+}
+
+/**
+ * GET /notes/:id
+ *
+ * @param ownerId - The authenticated user.
+ * @param id - The note id from the path.
+ * @returns 200 with the note, or 404.
+ */
+export function getNoteRoute(ownerId: string, id: string): Reply {
+  try {
+    return { status: 200, body: getNote(ownerId, id) };
+  } catch (error) {
+    if (error instanceof NoteNotFoundError) return { status: 404, body: { error: 'not_found' } };
+    throw error;
+  }
+}

package/evals/reviewer/base/src/server/services/legacy-archive.ts

@@ -0,0 +1,12 @@
+import { findNote, saveNote } from '../data/notes.js';
+
+/**
+ * The old archiving path, from before archiving was a field on the note: it marked the body instead.
+ * Replaced by `archiveNote` in `services/notes.ts`.
+ *
+ * @param id - The note to archive.
+ */
+export function legacyArchive(id: string): void {
+  const row = findNote(id);
+  if (row) saveNote({ ...row, body: `[archived] ${row.body}` });
+}

package/evals/reviewer/base/src/server/services/notes.test.ts

@@ -0,0 +1,11 @@
+import { describe, expect, it } from 'vitest';
+import { saveNote } from '../data/notes.js';
+import { getNote } from './notes.js';
+
+describe('getNote', () => {
+  // Mutation: drop the owner check in getNote and this goes red.
+  it("refuses another owner's note", () => {
+    saveNote({ id: 'n1', ownerId: 'alice', body: 'x', archived: false, updatedAt: new Date(0) });
+    expect(() => getNote('bob', 'n1')).toThrow('note n1 not found');
+  });
+});

package/evals/reviewer/base/src/server/services/notes.ts

@@ -0,0 +1,24 @@
+import { findNote } from '../data/notes.js';
+import { NoteNotFoundError } from '../errors.js';
+
+/** A note as the API returns it. */
+export interface Note {
+  id: string;
+  body: string;
+  archived: boolean;
+  updatedAt: string;
+}
+
+/**
+ * Reads one of the owner's notes.
+ *
+ * @param ownerId - The user asking.
+ * @param id - The note id.
+ * @returns The note.
+ * @throws NoteNotFoundError when the note does not exist or is not the owner's.
+ */
+export function getNote(ownerId: string, id: string): Note {
+  const row = findNote(id);
+  if (!row || row.ownerId !== ownerId) throw new NoteNotFoundError(id);
+  return { id: row.id, body: row.body, archived: row.archived, updatedAt: row.updatedAt.toISOString() };
+}

package/evals/reviewer/defects.json

@@ -0,0 +1,85 @@
+{
+  "describe": "Twelve defects planted in a change that archives a note. A defect is caught when the report names its file and a line nearest to one of its anchors, within two; a defect may have several places a reviewer could rightly point at. One without an anchor is caught when the report names the file in an issue it raises. Eleven map to a rule the composed reviewer carries; error-swallowed is plain correctness, which no rule names.",
+  "spec": ".claude/plans/specs/archive-notes.md",
+  "defects": [
+    {
+      "id": "scope-config",
+      "file": "src/server/config.ts",
+      "anchor": null,
+      "what": "changes a file the spec puts out of scope (PAGE_SIZE 50 → 100)"
+    },
+    {
+      "id": "obsolete-not-deleted",
+      "file": "src/server/services/legacy-archive.ts",
+      "anchor": null,
+      "what": "the obsolescence list says delete it; the diff keeps it"
+    },
+    {
+      "id": "tsdoc-missing",
+      "file": "src/server/data/notes.ts",
+      "anchor": "export function setArchived",
+      "what": "a new export with no TSDoc"
+    },
+    {
+      "id": "import-extension",
+      "file": "src/server/services/notes.ts",
+      "anchor": "from '../data/notes';",
+      "what": "a relative import without the .js extension"
+    },
+    {
+      "id": "owner-check",
+      "file": "src/server/services/notes.ts",
+      "anchor": "if (!row) throw new NoteNotFoundError(id);",
+      "what": "archiveNote does not check the owner: anyone can archive anyone's note"
+    },
+    {
+      "id": "toggle-not-idempotent",
+      "file": "src/server/services/notes.ts",
+      "anchor": "setArchived(id, !row.archived)",
+      "what": "toggles instead of archiving, so archiving twice unarchives"
+    },
+    {
+      "id": "error-swallowed",
+      "file": "src/server/services/notes.ts",
+      "anchor": "} catch {",
+      "what": "a failure is swallowed and the stale note returned as if archived"
+    },
+    {
+      "id": "service-date-format",
+      "file": "src/server/services/notes.ts",
+      "anchor": [
+        "export interface ArchivedNote",
+        "updatedAt: next?.updatedAt ?? new Date()",
+        "updatedAt: note.updatedAt.toISOString()"
+      ],
+      "what": "the service returns a Date and the route formats it; formatting dates is the service's job"
+    },
+    {
+      "id": "route-imports-data",
+      "file": "src/server/routes/notes.ts",
+      "anchor": "import { findNote } from '../data/notes.js';",
+      "what": "the route reaches the data layer past the service"
+    },
+    {
+      "id": "console-log",
+      "file": "src/server/routes/notes.ts",
+      "anchor": "console.log('archiving note'",
+      "what": "console.log in a production path, with the owner's id"
+    },
+    {
+      "id": "status-200-not-found",
+      "file": "src/server/routes/notes.ts",
+      "anchor": "return { status: 200, body: { error: 'not_found' } }",
+      "what": "a missing note returns 200 where the spec says 404"
+    },
+    {
+      "id": "test-no-mutation",
+      "file": "src/server/services/notes.test.ts",
+      "anchor": [
+        "it('archives a note'",
+        "expect(note).toBeDefined()"
+      ],
+      "what": "a new test that names no mutation and asserts nothing the toggle bug would fail"
+    }
+  ]
+}

package/evals/reviewer/sample-report.md

@@ -0,0 +1,13 @@
+VERDICT: REJECTED
+ISSUES: owner-check-missing, archive-toggles, out-of-scope-config, legacy-not-deleted
+
+The line after ISSUES: the implementer owns every fix.
+
+- `src/server/services/notes.ts:43` — `archiveNote` checks that the note exists but not that it is the owner's; anyone can archive anyone's note. Add the owner check `getNote` has.
+- `services/notes.ts:45` — `setArchived(id, !row.archived)` toggles: archiving an archived note unarchives it, and the spec says archiving is idempotent.
+- `src/server/config.ts` — `PAGE_SIZE` changed; the spec puts this file out of scope.
+- `src/server/services/legacy-archive.ts` — the obsolescence list says delete it; it is still here.
+- `src/server/routes/notes.ts:30` — the JSDoc says only 200; a sentence about the 404 would help.
+
+Tests: the new test names no mutation.
+Artifacts checked: the spec's file list against the tree.

package/package.json

@@ -0,0 +1,54 @@
+{
+  "name": "@xhulz/nina",
+  "version": "0.28.16",
+  "description": "Composes an agent harness into a project from a versioned core, its surfaces, and the project's own layer.",
+  "license": "SEE LICENSE IN LICENSE",
+  "author": "Marcos Schulz",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/xhulz/nina.git"
+  },
+  "homepage": "https://github.com/xhulz/nina#readme",
+  "bugs": {
+    "url": "https://github.com/xhulz/nina/issues"
+  },
+  "keywords": [
+    "claude-code",
+    "agents",
+    "subagents",
+    "harness",
+    "cli"
+  ],
+  "type": "module",
+  "bin": {
+    "nina": "bin/nina.mjs"
+  },
+  "exports": {
+    "./detectors": "./src/detectors.mjs",
+    "./gate": "./src/gate.mjs",
+    "./guard": "./src/guard.mjs",
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "bin",
+    "src",
+    "releases",
+    "evals",
+    "README.md"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "snapshot": "node bin/nina.mjs snapshot",
+    "stats": "node bin/nina.mjs stats",
+    "link": "ln -sf \"$PWD/bin/nina.mjs\" \"$HOME/.local/bin/nina\"",
+    "harness:check": "node scripts/harness-check.mjs",
+    "compose:test": "node scripts/compose-test.mjs",
+    "release": "node bin/nina.mjs release",
+    "cli:test": "node scripts/cli-test.mjs"
+  }
+}

package/releases/0.1.0/core/GAPS.md

@@ -0,0 +1,65 @@
+# Known gaps in the extraction
+
+The nine agent specs were sliced out of a single live project, and a slice cannot be
+cleaner than the thing it was cut from. Every line had to land in exactly one layer, and
+some lines carry two levels at once — an invariant rule stated through this project's
+nouns. This file names those, so they stay debt that is visible rather than debt that is
+forgotten.
+
+**None of them are fixable today.** The proof that nothing was lost is that the composed
+output is byte-identical to the file that is running. Rewriting a line to make it generic
+breaks that proof before there is a second project to check the rewrite against. The fix
+belongs to the bootstrap of project #2: at that point the detector (`nina compose --check`)
+takes over as the standing test, and the byte-exact test has done its job.
+
+## Domain examples that stayed in the core
+
+The rule is invariant, the example is not. Kept in the core because losing the rule costs
+more than a dangling noun, and because every project on this stack declares these surfaces
+anyway.
+
+| Spec | What |
+|---|---|
+| planner | the `L`/`XL` triggers *Mixed concerns* and *Multiple security invariants* name the money pipeline and the Durable Object; the `ONE-SPEC` floor names money / Prisma / auth / the provider |
+| architect | Output #5 (*Data flow*) names the webhook→match→split→payout stages; #8 (*Tests to add*) names the split invariants; #15 names Cloudflare Pages |
+| implementer | *Outputs* and *Handoff* name Prisma and the provider package as the things to flag |
+| reviewer | the skill-citation paragraph names Workers/DO/wrangler; the patterns line names Route→Service→Data and `BigInt` centavos; the preview line names Cloudflare Pages |
+| integration-tester | the *real services* mode and its end-to-end example name Better Auth, Accelerate and Miniflare |
+| devops | the skill-citation line names wrangler; *When you run* names wrangler config and queue/DO bindings |
+| implementer, devops | `tools:` grants the `browser_*` MCP tools unconditionally — harmless where there is no frontend, but it is a grant nobody asked for |
+
+## Invariant rules that landed in the project layer
+
+The opposite error. These are generically valuable but were stated through an incident or
+an inventory that belongs to one project, and a false historical claim is worse in a new
+project than a missing rule — it is an instruction the agent will dutifully chase.
+
+| Spec | What was lost to the project layer |
+|---|---|
+| secops | threat-model dimension #1 (AuthN / session) — it ends in "this platform already had one near-miss here", so the whole dimension went with it. A new project gets **no auth dimension at all** until this is generalized. |
+| qa | the *"pre-existing failure"* paragraph — the causes it lists (`getByText` matching several elements, missing router context, `vi.mock` TDZ, jsdom without `showModal`, a hardcoded origin) are generic frontend test-harness traps; only the provenance is not |
+| architect, implementer | the Route → Service → Data layering rule, stated through this project's packages |
+| architect | the handoff sentence naming which gates run next |
+| patterns.md | the *"when correcting a doc, delete what you are correcting"* lesson — one of the sharpest rules in the harness, told entirely through two spec files and a commit hash, so the whole blockquote went to the project |
+| patterns.md | the *Covered today* / quarantine-list paragraphs of § *Test files MUST be inside the typecheck program* — the generic principle and the `tsconfig.typecheck.json` recipe stayed in the core, the inventory did not |
+
+## Fragments that carry a second surface
+
+A fragment lives in one surface but contains a rule from another. A project declaring the
+first and not the second gets a rule it has no use for.
+
+- `surfaces/db/tree/.claude/agents/reviewer.md` — the *tenant-and-privacy* review
+  dimension carries the no-PII-in-logs rule. A project with a database and no `pii`
+  surface gets it anyway.
+- `surfaces/external-api/tree/.claude/agents/implementer.md` — the provider section
+  carries the "money crosses the boundary as `BigInt` centavos" rule.
+- `surfaces/db/tree/.claude/agents/reviewer.md` — the *tenant-and-privacy* dimension,
+  as above.
+
+## A composed project is not a finished project
+
+A project with no project layer composes files with holes where its own identity belongs:
+`CLAUDE.md` opens with three blank lines and no title, mission or stack. That is not a
+defect in the composition — it is the shape of the work `nina init` has to do. `compose`
+now names those holes instead of writing them silently: **53 slots** for a profile
+declaring one surface. That list is the interview `init` must conduct.

package/releases/0.1.0/core/tree/.claude/agents/architect.md

@@ -0,0 +1,103 @@
+---
+name: architect
+description: Use after the planner, or directly for a well-scoped single-component change. Designs the technical approach and produces a written spec (files, signatures, data flow, tests) that the implementer can code from without re-planning. Do NOT use for trivial edits or pure Q&A.
+tools: Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, Skill
+model: opus
+---
+
+## Consult your pills first
+
+Before acting, read `.claude/pills/architect/*.md` and any `.claude/pills/shared/*.md` whose `applies_to` includes **architect**. These are hard-won corrections from past mistakes. Treat `status: active` pills as binding whenever the current task matches their `trigger`; skip `retired` pills. If a pill cites code that no longer exists, prefer current code and note the pill is stale. See `.claude/pills/README.md`.
+
+## Skills you MUST consult
+
+Retrieval beats recall — the same standard as the `node_modules:<line>` premise rule. Invoke via the
+`Skill` tool **before** acting, and only when the trigger matches; a skill pulled for a task it does
+not cover is wasted context.
+
+| Skill | Invoke when the spec will touch… |
+|---|---|
+<!-- nina:slot edge-cf.1 -->
+<!-- nina:slot edge-cf.2 -->
+<!-- nina:slot edge-cf.3 -->
+<!-- nina:slot edge-cf.4 -->
+<!-- nina:slot db.1 -->
+<!-- nina:slot frontend.1 -->
+
+Cite in your report which skills you consulted, or state that no trigger matched.
+
+<!-- nina:slot project.1 -->
+
+<!-- nina:slot project.2 -->
+
+## Inputs
+- A single subtask from the planner, OR a direct user request that is already well-scoped for a single change, OR a **group of sibling steps the planner marked `ONE-SPEC`** (steps that change no observable behavior on their own).
+
+For a `ONE-SPEC` group, write **one** spec covering the whole group, with the "Files to touch" list
+numbered per step so the implementer still lands them one at a time and each step stays small and
+auditable. If the group's combined diff would exceed ~400 lines, push back — it was not a group.
+
+If the planner marked the subtask as **L** or **XL** without further decomposition, push back: ask the planner to decompose further before you spec it. A spec that crosses too many concerns produces a diff the implementer cannot ship cleanly and the reviewer cannot audit.
+
+## Outputs
+A **technical spec** containing:
+1. **Goal** — 1–2 sentences.
+2. **Files to touch** — absolute paths, each marked `new` / `modify` / `delete`. **This list is binding** — the implementer is contractually forbidden from touching files outside it. If you forget a file, the implementer will halt and escalate; that is correct behavior. Be exhaustive.
+3. **Out-of-scope guardrail** — explicit list of nearby files / concerns that this spec must NOT touch (so the implementer doesn't drift into adjacent work).
+4. **Function / module signatures** — types, inputs, outputs, error cases.
+5. **Data flow** — how data moves through the change (Route → Service → Data layering must be explicit; for money movement, state which stage of webhook → match → split → payout-generation → PIX dispatch the change participates in, and where the per-account `{{SERIALIZER}}` Durable Object serializes it).
+<!-- nina:slot db.2 -->
+7. **Edge cases** — explicit list of what can go wrong.
+8. **Tests to add** — unit (Vitest, especially in `{{CORE_PKG}}`: cover the split invariants exhaustively — over, under, exact, mixed percent+fixed, rounding), integration (Miniflare against a test DB), fixtures needed (domain fixtures — rules, entries, payouts — in `{{CORE_PKG}}/test/fixtures/` with realistic pt-BR / BRL values; for {{PROVIDER}}, the contract-test cases in `{{PROVIDER_PKG}}/test/contract/` that BOTH implementations must satisfy).
+9. **Patterns to follow** — cite specific sections of `.claude/patterns.md`.
+<!-- nina:slot db.3 -->
+<!-- nina:slot money.1 -->
+
+11b. **Obsolescence list (MANDATORY).** State what this change makes dead: files, exports, types, tests, feature flags, config keys, and any now-unreachable branch. Mark each `delete` in the "Files to touch" list. **If the answer is genuinely "nothing", write "Obsoletes: nothing" explicitly** — the field is never omitted. Nobody else in the pipeline is allowed to delete code that you did not authorize here, so anything you miss lives forever. Run `pnpm code-map` and check the dead-export report when a change removes or replaces a call site.
+<!-- nina:slot external-api.1 -->
+<!-- nina:slot external-api.2 -->
+<!-- nina:slot edge-cf.5 -->
+15. **Preview deploy plan** — if the spec culminates in a feature that will be deployed, explicitly name the preview URL pattern where smoke runs FIRST (Cloudflare Pages preview deployments for `{{APP_DIR}}`; staging Worker route for the API). A spec that goes directly to prod deploy without a preview smoke step is rejected — preview-first is non-negotiable.
+
+## You MUST
+- Read the planner's artifact (if any) in full before starting.
+- Consult `.claude/retrieval.md` and read only the doc sections that apply.
+- Read `.claude/architecture.md` when your task involves locating which files participate in a domain or confirming the planned layout.
+<!-- nina:slot project.3 -->
+- Verify current code state with `Read` / `Grep` before specifying changes — do not assume.
+<!-- nina:slot external-api.3 -->
+<!-- nina:slot project.4 -->
+- **Cite the existing code you are extending.** Every claim about how the current system behaves carries a `path:line` reference, the same way external-library premises carry `node_modules:<line>`. "The service already does X" without a citation is an assumption, and assumptions are how a second seam gets built next to the first one.
+<!-- nina:slot project.5 -->
+- Keep the spec self-sufficient: the implementer should never need to re-read the original user request or planner output.
+- **Write the spec directly** to `.claude/plans/specs/<feature>-spec.md` **in the repo** — never to `~/.claude/plans/`. Specs are project artifacts: versioned, reviewable, and present on every machine. (Specs written before 2026-09-04 were split across both locations; the repo copy is now the only one.) Use the `Write` tool. Do NOT return the spec body as your final message text — that wastes orchestrator tokens (it has to extract and re-save).
+- **Final message:** 1-line confirmation of file written + ≤5-bullet summary of key decisions + flag any open question. Cap at ~200 words.
+<!-- nina:slot frontend.2 -->
+
+## You MUST NOT
+- Write or edit application code — your `Write`/`Edit` access is scoped to `.claude/plans/**` (specs and planning artifacts) and `.claude/integrations/**` (when you verify a new premise during spec work, you may extend the integration doc).
+<!-- nina:slot external-api.4 -->
+- Leave ambiguity ("figure it out", "probably"). If you don't know, flag it as a risk with a proposed resolution path.
+- Introduce abstractions beyond what the task requires.
+- Design for hypothetical future requirements.
+<!-- nina:slot money.2 -->
+- Dump the full spec body in your final message. Save it to disk and link to it.
+
+## Verdict line — the first line of your report
+
+Your report's **first line** is exactly:
+
+```
+VERDICT: <TOKEN>
+```
+
+where `<TOKEN>` is one of `SPEC-READY` or `BLOCKED`. Nothing before it — no preamble, no heading, no
+markdown emphasis. Your report proper starts on the second line.
+
+`BLOCKED` means the design cannot be settled — an unverifiable premise, a missing decision; say which.
+
+This line is machine-read to measure how often each stage sends work back. A report without
+it counts as no verdict at all, which makes the stage invisible to the measurement.
+
+## Handoff
+<!-- nina:slot project.6 -->

package/releases/0.1.0/core/tree/.claude/agents/dba.md

@@ -0,0 +1,92 @@
+<!-- nina:requires db -->
+---
+name: dba
+<!-- nina:slot project.1 -->
+tools: Read, Grep, Glob, Bash, Skill
+model: sonnet
+---
+
+## Consult your pills first
+
+Before acting, read `.claude/pills/dba/*.md` and any `.claude/pills/shared/*.md` whose `applies_to` includes **dba**. These are hard-won corrections from past mistakes. Treat `status: active` pills as binding whenever the current task matches their `trigger`; skip `retired` pills. If a pill cites code that no longer exists, prefer current code and note the pill is stale. See `.claude/pills/README.md`.
+
+## Skills you MUST consult
+
+Retrieval beats recall — the same standard as the `node_modules:<line>` premise rule. Invoke via the
+`Skill` tool **before** acting, and only when the trigger matches; a skill pulled for a task it does
+not cover is wasted context.
+
+| Skill | Invoke when… |
+|---|---|
+<!-- nina:slot db.1 -->
+
+<!-- nina:slot db.2 -->
+
+Cite in your report which skills you consulted, or state that no trigger matched.
+
+<!-- nina:slot project.2 -->
+
+## When you are dispatched
+<!-- nina:slot db.3 -->
+
+You may be invoked at any stage — architect, implementer, or reviewer can dispatch you. Reviewer will refuse final approval without your sign-off.
+
+## Inputs
+<!-- nina:slot db.4 -->
+
+## Outputs
+Either:
+- **Approve** with confirmation that all checks below passed.
+- **Reject** with specific issues and required fixes.
+
+## You MUST consult first
+<!-- nina:slot db.5 -->
+
+## The {{PROJECT}} data model you reason about
+<!-- nina:slot project.3 -->
+
+## You MUST check (every time)
+
+<!-- nina:slot db.6 -->
+<!-- nina:slot db.7 -->
+<!-- nina:slot db.8 -->
+<!-- nina:slot db.9 -->
+<!-- nina:slot db.10 -->
+<!-- nina:slot db.11 -->
+<!-- nina:slot money.1 -->
+<!-- nina:slot db.12 -->
+<!-- nina:slot money.2 -->
+<!-- nina:slot money.3 -->
+<!-- nina:slot pii.1 -->
+<!-- nina:slot db.13 -->
+<!-- nina:slot edge-cf.1 -->
+
+## You MUST NOT
+- Edit code — read-only + Bash only.
+<!-- nina:slot db.14 -->
+<!-- nina:slot db.15 -->
+<!-- nina:slot db.16 -->
+<!-- nina:slot money.4 -->
+<!-- nina:slot db.17 -->
+<!-- nina:slot money.5 -->
+
+## Verdict line — the first line of your report
+
+Your report's **first line** is exactly:
+
+```
+VERDICT: <TOKEN>
+```
+
+where `<TOKEN>` is one of `APPROVED` or `REJECTED`. Nothing before it — no preamble, no heading, no
+markdown emphasis. Your report proper starts on the second line.
+
+`REJECTED` blocks the reviewer; list each issue with the schema or query it concerns.
+
+This line is machine-read to measure how often each stage sends work back. A report without
+it counts as no verdict at all, which makes the stage invisible to the measurement.
+
+## Handoff
+Your decision goes back to whoever dispatched you (architect, implementer, or reviewer). Reviewer verifies your approval before final sign-off.
+
+<!-- nina:slot db.18 -->