kataster 0.0.0-stage → 0.2.1

package/.claude/settings.json

@@ -0,0 +1,82 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-settings.json",
+  "permissions": {
+    "allow": [
+      "Bash(node .claude/skills/adopt/scripts/*)",
+      "Bash(node .claude/skills/event-storming/scripts/validate-events.ts)",
+      "Bash(node .claude/skills/event-storming/scripts/render-event-storming.ts)",
+      "Bash(node .claude/skills/user-stories/scripts/validate-stories.ts)",
+      "Bash(node .claude/skills/user-stories/scripts/render-backlog.ts)",
+      "Bash(node .claude/skills/implement/scripts/*)",
+      "Bash(git status *)",
+      "Bash(git diff *)",
+      "Bash(git log *)"
+    ],
+    "deny": [],
+    "ask": []
+  },
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/session-start.ts\""
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Write|Edit|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/protect-files.ts\""
+          }
+        ]
+      },
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/bash-guard.ts\""
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/validate-docs.ts\""
+          },
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/code-check.ts\"",
+            "timeout": 90
+          },
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/project-check.ts\"",
+            "timeout": 60
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/stop-gate.ts\"",
+            "timeout": 600
+          }
+        ]
+      }
+    ]
+  }
+}

package/.claude/skills/adopt/SKILL.md

@@ -0,0 +1,283 @@
+---
+name: adopt
+description: Brownfield entry point – maps the repository, adopts it in slices (one domain plus at most one shared library), drafts the domain model with evidence, grills the user, documents each package where it lives and records the gap; it derives stories only when asked (--stories). Use when the workflow is dropped into a repository that already has code.
+disable-model-invocation: true
+argument-hint: "[scope, e.g. 'apps/billing' or 'the order process' – empty = map the repository and choose a slice; add --stories to derive stories now]"
+---
+
+# Adopt an Existing Repository
+
+The repository already works. Your job is to **recover the domain it encodes** – in slices, not by rewriting it
+and not by documenting the whole monorepo in one pass. Code is evidence of decisions someone already made; the
+user is the only one who can say which of the readings is the intended domain.
+
+Scope: the arguments from the invocation (empty = map the repository and choose a slice). `--stories` is an
+explicit opt-in for Phase 6; without it the adoption records the gap but creates no stories. Pick a short
+kebab-case slug for the adoption (`adoption-<scope>`) for the report file.
+
+## Preconditions
+
+1. Read `.claude/project.json`. If it is missing, tell the user to run `npx kataster init` first and stop.
+2. If the repository has no code yet, this is the wrong command: use `/bootstrap`.
+3. Read what already exists, before analysing anything: `CONTEXT.md`, `docs/product/vision.md`,
+   `docs/domain/events.yaml`, `docs/domain/context-map.md`, `docs/architecture/data-model.md`,
+   `docs/architecture/repo-map.md`, `docs/engineering/conventions.md`, `docs/adr/`, `README*`, existing `docs/`
+   and any `AGENTS.md`/`CLAUDE.md`. Existing documentation is **primary evidence** – it outranks your inference
+   from code. Contradictions between docs and code are findings, not something to resolve silently.
+
+## Phase 0 – Repository map (deterministic, no questions)
+
+Run:
+
+```bash
+node .claude/skills/adopt/scripts/repo-map.ts
+```
+
+It scans manifests and git history and writes:
+
+- `docs/architecture/repo-map.json` – packages, paths, kinds, internal dependencies, consumers, adoption ranking,
+  and the build tool's own graph when it answers (Turbo, Nx, Bazel)
+- `docs/architecture/repo-map.md` – the same as a readable map (never edit it by hand)
+- the generated repository block in `AGENTS.md` – tooling, layout, commands, adopted slices
+- `.claude/project.json` → `repo.tooling` – Nx, Turborepo, Bazel, pnpm/npm/yarn workspaces, Go, Cargo, Gradle, Maven
+
+Read the map yourself. **Do not hand-scan the repository for packages**; if the map is stale, run it again.
+The map is facts, not domain: it says where code lives and what depends on what, never what a word means.
+
+## Phase 1 – Choose the slice (one round, at most three questions)
+
+The map suggests a first slice. Ask, each with a recommended answer:
+
+1. **Slice**: the suggested domain plus its most-used shared library, or a different one? Recommended: the
+   suggestion from `repo-map.md` – it weighs recent churn, fan-in and kind, not size.
+2. **Intent**: a domain model for future work, a map for onboarding, or a backlog for a rewrite? Recommended:
+   the domain model first; the other two follow from it.
+3. **Language**: confirm `languages.ui` and `languages.artifacts` from the profile. Recommended: what the code
+   and UI already use.
+
+Hard rule: **one domain plus at most one shared library per session.** A simple repository without monorepo
+tooling is one slice – then the whole repository is in scope. Never "the whole monorepo"; a shallow map of 80
+packages is worse than a confirmed model of two.
+
+Create `docs/domain/adoption-report.md` with the answers under `## Scope`; fill the rest as you go. If earlier
+slices are already adopted, name the next one and what changed since it was adopted (`git log --since=<date>`).
+
+## Phase 2 – Evidence for the slice
+
+Call the `skill` tool for `grilling`, `domain-model` and `architect` first: grilling sets how you ask,
+domain-model sets what you are looking for, architect decides what becomes an ADR.
+
+Dispatch `repo-analyst` subagents **in one message**, each with the slice path, the repository map path and one
+lens. They are read-only.
+
+- **Monorepo / several packages**: three analysts.
+  | Lens | What it looks for |
+  |---|---|
+  | Structure, data and entry points | Manifests, entry points, schema, migrations, enums, state columns, external services, jobs, the slice's internal dependencies and consumers |
+  | Language, behaviour and tests | Nouns and verbs in types, routes, UI texts, errors; handlers, validations, permissions; tests as executable specifications; candidate events/commands/read models |
+  | Architecture, dependencies and history | Layering and import direction from `repo-map.md`; build tooling and its graph; de-facto decisions in config; `git log` hotspots, reverted changes, TODOs |
+- **Simple repository / no monorepo tooling**: the five lenses from the old adoption (structure and stack,
+  domain language, data and integrations, behaviour and tests, history and decisions) – the slice is the whole
+  repository.
+
+While they run, read the repository's own documentation yourself. Do not block the round on the analysts.
+
+## Phase 3 – Draft the slice
+
+Merge the reports into one picture. Write the artifacts **as a draft**, every uncertain statement marked.
+
+- **`CONTEXT.md`** – only the slice's terms, grouped by guessed bounded context, competing spellings under
+  `_Avoid_`, `[OPEN]` where the meaning is unclear. Do not touch terms of other slices.
+- **`docs/domain/events.yaml`** – 10–25 candidate events/commands/actors/read models/policies/flows for this
+  slice. Every uncertainty becomes a hotspot (`HS-n`, `status: open`).
+- **`docs/domain/context-map.md`** – the boundaries the module structure suggests, marked as a proposal.
+- **`docs/architecture/data-model.md`** – the **as-is** model for the slice, derived from schema and code.
+- **`docs/engineering/conventions.md`** – fill what the slice actually does: module layout, how a command runs,
+  read models, "now", texts, test data, seam catalog. Include how the monorepo tooling is used.
+- **`docs/product/vision.md`** – only if missing or empty, reconstruct and mark `[OPEN]`.
+- **`docs/adr/`** – de-facto decisions worth recording, `status: proposed`. Only the user accepts.
+- **Package docs** – for the domain and the shared library (in a monorepo):
+  ```bash
+  node .claude/skills/adopt/scripts/package-doc.ts apps/billing
+  node .claude/skills/adopt/scripts/package-doc.ts libs/shared-kernel
+  ```
+  A single-package repository has no package file: its root `AGENTS.md` is the package doc (`package-doc.ts .`
+  deliberately refuses). The script writes `<package>/AGENTS.md` (source of truth) and `<package>/CLAUDE.md`
+  (`@AGENTS.md`, for Claude Code's on-demand nested loading). It generates the facts block; **you** fill the prose
+  during the grilling:
+  - domain/service: Purpose, Key entities, External interfaces, Typical pitfalls, Boundaries
+  - shared library: Purpose, Public API, Consumers, Compatibility rules, Typical pitfalls, Boundaries
+  Keep each file under ~80 lines. This file is loaded only when someone works in that package.
+- **Root `AGENTS.md`** – the generated block comes from the map. Below it, add only structure, commands, hard
+  conventions and links. Keep at most ten bullets under `## Hard conventions`, each naming where it is enforced
+  (`lint`, a test, `.claude/rules/<file>.md`, `docs/engineering/checks.yaml`) – a rule without an enforcement
+  point is a wish. **No domain rules, no entities, no business vocabulary** – those belong in `CONTEXT.md` and
+  the package docs.
+- **`.claude/rules/`** – only for path-scoped rules that cannot be a directory document (e.g. `**/*.sql`,
+  `**/migrations/**`), with `paths:` frontmatter. Directory-scoped rules belong in `<dir>/AGENTS.md` because that
+  is the mechanism both harnesses load on demand. A rule for a whole group gets `<group>/AGENTS.md` plus a
+  one-line `<group>/CLAUDE.md` (`@AGENTS.md`) – e.g. `libs/AGENTS.md` for "everything under `libs/**`". Never
+  duplicate the same rule in both mechanisms.
+
+After every write of `events.yaml`, the hook validates and renders it. Fix errors immediately.
+
+### Rules for the draft
+
+- A code name is a *spelling*, never automatically the domain term. `OrderService.place()` is evidence for
+  "Order placed", not proof of the word "order".
+- One concept with three spellings → one candidate term and two `_Avoid_` entries, or a hotspot.
+- Never invent a business rule. If the code enforces something, report it as "the code enforces X (path)"; the
+  user decides whether that is a rule or an accident.
+- If the repository contradicts itself, that is a hotspot, not a choice you make.
+
+## Phase 4 – Grill the user against the draft
+
+This is the core of the adoption. Present the draft, then work the frontier in rounds exactly as the `grilling`
+skill says: numbered questions, each with a recommended answer, whole frontier per round.
+
+Questions brownfield needs, roughly in this order:
+
+1. **Terms** – one question per cluster of competing spellings, worst first.
+2. **Boundaries** – which package owns which state; where a shared library ends and a domain begins.
+3. **Lifecycle** – states the schema allows, transitions it does not block.
+4. **Invariants** – what the code checks only in the UI; what must always hold.
+5. **Missing behaviour** – what has no trace: never needed, or a gap?
+6. **Architecture** – layering, CQRS/read models, dependency direction, cross-context communication. Which are
+   real decisions and which are accidents? Record the real ones as ADRs.
+7. **Build tooling** – how packages are built, tested and filtered; whether affected tests are trustworthy.
+8. **Shared libraries** – public API, consumers, what may not break without a migration.
+9. **Intent** – which of this is deliberate, and which is legacy you want to leave behind.
+
+Every answer updates the draft **immediately**: `CONTEXT.md`, `events.yaml`, the package's `AGENTS.md`, the ADR.
+Resolved hotspots get `status: resolved` + `resolution`. New uncertainty becomes a new hotspot. Do not move on
+until the frontier is empty and the user confirms a shared understanding.
+
+## Phase 5 – Safety net: make the confirmed rules checkable
+
+For every confirmed hard rule or invariant, choose the cheapest deterministic enforcement – in this order:
+
+1. **Type system** (a state that cannot be represented cannot be written)
+2. **Lint / boundary check** (import direction, layer, package visibility – dependency-cruiser, Nx module
+   boundaries, Bazel visibility, ArchUnit, import-linter)
+3. **Architecture or characterization test** (a test pins the rule or the existing behaviour)
+4. **Hook** (only for fast, edit-time checks; full checks belong in Stop/CI)
+5. **Documentation only** (when nothing can check it)
+
+What you may create here:
+
+- 3–5 **characterization tests** for the slice's most important existing behaviour – they pin what is, they do
+  not assert what should be.
+- The architecture boundaries and checks:
+  ```bash
+  node .claude/skills/adopt/scripts/boundary-check.ts --init
+  # edit docs/architecture/boundaries.yaml with the rules the user confirmed, then
+  node .claude/skills/adopt/scripts/boundary-check.ts --update-baseline
+  ```
+  Run `--init` on the first slice only; later slices extend the existing `boundaries.yaml`. It writes a proposal
+  for `docs/architecture/boundaries.yaml`, the default `docs/engineering/checks.yaml` and an empty baseline.
+  Rules are evaluated in order; the first matching `from` → `to` pair decides (no match = allow). The engine is
+  `scan` for JS/TS imports, or `command` for the project's own tool (dependency-cruiser, Nx module boundaries,
+  Bazel, ArchUnit, import-linter).
+- `.claude/rules/` entries for confirmed rules that a directory cannot express:
+  ```bash
+  node .claude/skills/adopt/scripts/rule-doc.ts libs-shared --paths "libs/**" --title "Shared libraries"
+  ```
+  A rule for a whole directory belongs in `<dir>/AGENTS.md` instead; do not duplicate it in both mechanisms.
+- `docs/engineering/checks.yaml` entries with `phase: edit` (fast, changed file only) or `phase: stop` (full set).
+
+What you may **not** do: change production code, or write a test that fails on existing behaviour. On a
+brownfield repository the checks are **report-only first**: record existing violations in a baseline, then let
+only new violations fail (ratchet). A hook that is red on day one gets switched off.
+
+Hooks are wired once, through the `project-check.ts` dispatcher reading `docs/engineering/checks.yaml`, not by
+adding per-package hook entries to `.claude/settings.json`. Keep edit-time checks fast; the full set runs at
+Stop/CI. If a rule needs new behaviour, it becomes a story – not a failing test.
+
+## Phase 6 – The gap register (stories only on request)
+
+Compare the confirmed model with the code. Classify, and show the table to the user:
+
+| Class | Meaning | Default |
+|---|---|---|
+| **Exists and is intended** | Code matches the confirmed model | Documented in the data model/context map. No action. |
+| **Exists but contradicts the model** | Code does something the user says is wrong | Candidate in the gap register |
+| **Missing** | The model needs it, the code has no trace | Candidate in the gap register |
+| **Dead** | Code has no place in the model | Candidate: removal or an explicit "leave it" |
+
+**The default is no stories.** The first adoption pass is about understanding the repo, not about filling a
+backlog. Write the table into `docs/domain/adoption-report.md`; open questions go into
+`docs/stories/OPEN_QUESTIONS.md` or a hotspot. This keeps the model reviewable without committing to work the
+user has not prioritised.
+
+Only when the invocation contains `--stories`, or the user explicitly asks after seeing the table:
+
+- delegate to `requirements-engineer` with the **selected** gaps only, the confirmed IDs from `events.yaml`, the
+  label `adoption:<slug>`, and `ui` for stories with a frontend part;
+- new stories start as `status: draft`; the ones the user wants first go through `/review-stories`.
+
+**Do not write stories for behaviour that already works** – that turns the backlog into a description of the
+past. Existing behaviour is covered by its tests, and the domain model is the map. If an earlier run created
+stories the user does not want, do not delete them silently: ask whether to `supersede` them or keep them.
+
+## Phase 7 – Report and the next slice
+
+Write `docs/domain/adoption-report.md`:
+
+```md
+# Adoption – <scope>
+Date: YYYY-MM-DD · Commit: <sha> · Slice: <paths> · Analysts: <n> lenses
+
+## Scope and intent
+## Repository map (tooling, packages, why this slice)
+## What the repository is (facts)
+## Confirmed domain model
+- contexts, aggregates, glossary changes
+## Package documentation written
+- <path>/AGENTS.md + CLAUDE.md – what was confirmed and what stays [OPEN]
+## Contradictions found and how they were resolved
+## Rules and checks
+- rule → enforcement (type / lint / test / hook / doc) → baseline or green
+## Gap register (candidates – stories only with --stories)
+## Deliberately left alone
+## Open hotspots
+## Next slice
+```
+
+Mark the slice adopted so the next session sees the progress:
+
+```bash
+node .claude/skills/adopt/scripts/repo-map.ts --adopt apps/billing
+```
+
+Then run `node .claude/skills/event-storming/scripts/validate-events.ts` and
+`node .claude/skills/user-stories/scripts/validate-stories.ts`, and show the result.
+
+## Wrap-up
+
+Summarize in a few lines: terms added, contexts/aggregates proposed, hotspots open, package docs written,
+checks created, gap candidates (and stories only if requested), ADRs proposed. Then name the next step:
+
+- `git diff` is the review: no production code changed, only docs, package docs and tooling.
+- `/adopt <next path>` for the next slice.
+- `/feature <idea>` for the next piece of work, now that the domain has a language.
+- `/adopt <scope> --stories` (or `/review-stories` if stories already exist) when the user wants the gap turned
+  into a backlog.
+- `/implement` once a story is `ready`.
+
+## Rules
+
+- **Never change production code in `/adopt`.** Tests and tooling are allowed only as the safety net above.
+- **Never present an inference as a fact.** Confidence and evidence, or a hotspot.
+- **The user owns the language.** You may propose a better word; you may not rename the domain on your own.
+- **Adopt in slices.** One domain plus at most one shared library. Never the whole monorepo in one pass.
+- **The root `AGENTS.md` stays free of domain.** Structure, commands, hard conventions and links only.
+- **Package docs are short and on demand.** `<package>/AGENTS.md` + `<package>/CLAUDE.md`, under ~80 lines.
+- **Directory docs before glob rules.** `.claude/rules/` is for patterns a directory cannot express. Both
+  harnesses see the same file: Claude Code scopes it natively by `paths:`, OpenCode's plugin attaches it when a
+  matching file is read or written. Directory-scoped rules still belong in `<dir>/AGENTS.md`.
+- **No backlog by default.** Adoption produces the model and a gap register; stories are an explicit second step
+  (`--stories`) after the user has prioritised.
+- **Checks are green on day one.** Baseline existing violations, ratchet new ones; no red hook.
+- **The map is generated.** Never hand-edit `repo-map.json`/`repo-map.md` or the generated blocks.
+- **Stop when the frontier is empty.** A model that is 80% confirmed and 20% hotspot is more useful than one
+  that is 100% invented.

package/.claude/skills/adopt/scripts/boundary-check.ts

@@ -0,0 +1,156 @@
+/**
+ * Architecture boundary check with baseline/ratchet.
+ *
+ *   node .claude/skills/adopt/scripts/boundary-check.ts --init
+ *   node .claude/skills/adopt/scripts/boundary-check.ts
+ *   node .claude/skills/adopt/scripts/boundary-check.ts --changed [file]
+ *   node .claude/skills/adopt/scripts/boundary-check.ts --update-baseline
+ *   node .claude/skills/adopt/scripts/boundary-check.ts --json
+ *
+ * `--init` writes a proposal for `docs/architecture/boundaries.yaml`, the default `docs/engineering/checks.yaml`
+ * and an empty baseline. The user confirms the rules during /adopt; `--update-baseline` freezes violations that
+ * already exist, so only new ones fail.
+ */
+import { existsSync } from "node:fs";
+import { join } from "node:path";
+import {
+  BOUNDARIES_FILE, BASELINE_FILE, CHECKS_FILE, adapterHints, baselineFrom, checkBoundaries, defaultChecks, defaultRules,
+  emptyBaseline, evaluateBaseline, formatViolation, loadBaseline, loadBoundaries, relPath, rootMap,
+  writeBaseline, writeBoundaries, writeChecks,
+} from "../../../lib/architecture.ts";
+import { ROOT } from "../../../lib/repo.ts";
+
+const args = process.argv.slice(2);
+const help = args.includes("--help") || args.includes("-h");
+const init = args.includes("--init");
+const update = args.includes("--update-baseline");
+const json = args.includes("--json");
+
+function usage(): void {
+  console.log(
+    [
+      "Usage: node .claude/skills/adopt/scripts/boundary-check.ts [options]",
+      "",
+      "  --init                 write a boundaries.yaml proposal, checks.yaml and an empty baseline",
+      "  --force                with --init: overwrite existing files",
+      "  --changed [file]       check only this file (or $CHANGED_FILE, used by the edit hook)",
+      "  --update-baseline      freeze current violations so only new ones fail",
+      "  --json                 machine-readable result",
+    ].join("\n"),
+  );
+}
+
+if (help) {
+  usage();
+  process.exit(0);
+}
+
+try {
+  if (init) {
+    const map = rootMap(ROOT);
+    const force = args.includes("--force");
+    if (!force) {
+      for (const file of [BOUNDARIES_FILE, CHECKS_FILE, BASELINE_FILE]) {
+        if (existsSync(join(ROOT, file))) throw new Error(`${file} already exists – edit it, or pass --force`);
+      }
+    }
+    const boundaries = { version: 1 as const, engine: "auto" as const, command: "", rules: defaultRules(map) };
+    const boundariesPath = writeBoundaries(ROOT, boundaries, force);
+    const checksPath = writeChecks(ROOT, { version: 1, checks: defaultChecks() }, force);
+    const baselinePath = writeBaseline(ROOT, emptyBaseline());
+    console.log(`Wrote ${relPath(ROOT, boundariesPath)} with ${boundaries.rules.length} proposed rule(s).`);
+    console.log(`Wrote ${relPath(ROOT, checksPath)} and ${relPath(ROOT, baselinePath)}.`);
+    if (!boundaries.rules.length) {
+      console.log("No apps/, services/, libs/ or packages/ directories were found – add the rules by hand.");
+    }
+    for (const hint of adapterHints(map)) console.log(`Hint: ${hint}`);
+    console.log("Review and confirm the rules with the user, then freeze existing violations:");
+    console.log("  node .claude/skills/adopt/scripts/boundary-check.ts --update-baseline");
+    process.exit(0);
+  }
+
+  const changedIndex = args.indexOf("--changed");
+  const changedArg = changedIndex === -1 ? undefined : args[changedIndex + 1];
+  const changed = changedIndex === -1
+    ? undefined
+    : changedArg && !changedArg.startsWith("--")
+      ? relPath(ROOT, changedArg)
+      : process.env.CHANGED_FILE
+        ? relPath(ROOT, process.env.CHANGED_FILE)
+        : undefined;
+
+  if (update && changed) {
+    console.error("--update-baseline must run without --changed – freezing a single file would drop the rest.");
+    process.exit(1);
+  }
+
+  const boundaries = loadBoundaries(ROOT);
+  if (!boundaries) {
+    console.log(`No ${BOUNDARIES_FILE} – architecture boundaries are not configured yet.`);
+    console.log("Run `node .claude/skills/adopt/scripts/boundary-check.ts --init` during /adopt.");
+    process.exit(0);
+  }
+
+  if (!boundaries.rules.length && boundaries.engine !== "command") {
+    console.log("No boundary rules configured – nothing to check.");
+    process.exit(0);
+  }
+
+  const map = rootMap(ROOT);
+  const result = checkBoundaries(ROOT, boundaries, map, changed);
+
+  if (update) {
+    const path = writeBaseline(ROOT, baselineFrom(result));
+    const command = result.command ? ` and the command failure` : "";
+    console.log(`Baseline written to ${relPath(ROOT, path)}: ${result.violations.length} violation(s)${command} frozen.`);
+    process.exit(0);
+  }
+
+  const report = evaluateBaseline(result, loadBaseline(ROOT));
+
+  if (json) {
+    console.log(JSON.stringify({
+      ok: report.ok,
+      engine: report.engine,
+      checked: report.checked,
+      violations: report.violations.length,
+      new: report.newViolations,
+      stale: report.stale,
+      command: report.command ? { name: report.command.name, baselined: report.commandBaselined, output: report.command.output } : undefined,
+      note: report.note,
+    }, null, 2));
+    process.exit(report.ok ? 0 : 1);
+  }
+
+  if (report.note) console.log(report.note);
+  const unit = report.engine === "scan" ? "import edge(s)" : "check(s)";
+  console.log(`Architecture boundaries (${report.engine}): ${report.checked} ${unit}, ${report.violations.length} violation(s).`);
+
+  if (report.command && !report.commandBaselined) {
+    console.error(`\nThe architecture command failed (not baselined):\n${report.command.output}`);
+    process.exit(1);
+  }
+
+  if (report.newViolations.length) {
+    const shown = report.newViolations.slice(0, 50);
+    console.error(`\nNew boundary violations – fix them or, if they are existing debt, freeze them with --update-baseline:\n${shown.map(formatViolation).join("\n")}`);
+    if (report.newViolations.length > shown.length) {
+      console.error(`… and ${report.newViolations.length - shown.length} more (see --json).`);
+    }
+    process.exit(1);
+  }
+
+  if (report.violations.length) {
+    console.log(`${report.violations.length} baselined violation(s) – existing debt, not failing.`);
+  }
+  if (report.stale.length) {
+    console.log(`${report.stale.length} baseline entr${report.stale.length === 1 ? "y" : "ies"} no longer occur – update the baseline to tighten the ratchet.`);
+  }
+  if (report.command && report.commandBaselined) {
+    console.log("The architecture command failure is baselined.");
+  }
+  console.log("OK – no new boundary violations.");
+} catch (error) {
+  console.error(error instanceof Error ? error.message : String(error));
+  process.exit(1);
+}

package/.claude/skills/adopt/scripts/package-doc.ts

@@ -0,0 +1,71 @@
+/**
+ * Writes or refreshes the per-package documentation that is loaded only when an agent works in that package.
+ *
+ *   node .claude/skills/adopt/scripts/package-doc.ts apps/billing
+ *   node .claude/skills/adopt/scripts/package-doc.ts apps/billing --adopt
+ *
+ * It creates `<package>/AGENTS.md` (source of truth) and `<package>/CLAUDE.md` (`@AGENTS.md` for Claude Code).
+ * The generated Facts block is refreshed on every run; the prose sections (Purpose, Key entities, External
+ * interfaces, Typical pitfalls, Boundaries) are never touched. If an existing AGENTS.md has no generated
+ * markers, the script leaves it alone and says so.
+ */
+import {
+  ROOT, findPackage, markAdopted, readRepoMap, scanRepo, updateProjectTooling, writePackageDoc, writeRepoMap, writeRootBlock,
+} from "../../../lib/repo.ts";
+
+const args = process.argv.slice(2).filter((arg) => !arg.startsWith("--"));
+const adopt = process.argv.includes("--adopt");
+const path = args[0];
+
+if (process.argv.includes("--help") || process.argv.includes("-h")) {
+  console.log("Usage: node .claude/skills/adopt/scripts/package-doc.ts <package-path> [--adopt]");
+  process.exit(0);
+}
+if (!path) {
+  console.error("Usage: node .claude/skills/adopt/scripts/package-doc.ts <package-path> [--adopt]");
+  process.exit(1);
+}
+
+try {
+  if (path === "." || path === "./" || path === "") {
+    console.error("The root package is documented in AGENTS.md, not in a package file.");
+    process.exit(1);
+  }
+
+  let map = readRepoMap(ROOT);
+  if (!map) {
+    map = scanRepo(ROOT);
+    writeRepoMap(ROOT, map);
+    updateProjectTooling(ROOT, map.tooling);
+    writeRootBlock(ROOT, map);
+    console.log("Wrote docs/architecture/repo-map.json and the root AGENTS.md block first (they were missing).");
+  }
+
+  const pkg = findPackage(map, path);
+  if (!pkg) {
+    const available = map.packages.map((p) => p.path).slice(0, 25).join(", ");
+    console.error(`Package '${path}' is not in the repository map. Known packages: ${available}${map.packages.length > 25 ? ", …" : ""}`);
+    process.exit(1);
+  }
+
+  const result = writePackageDoc(ROOT, map, pkg);
+  const agentsRel = result.agents.replace(`${ROOT}/`, "");
+  const claudeRel = result.claude.replace(`${ROOT}/`, "");
+
+  if (result.status === "created") {
+    console.log(`Created ${agentsRel} and ${claudeRel}`);
+    console.log("Fill the [OPEN] sections in AGENTS.md during the grilling – do not invent domain meaning.");
+  } else if (result.status === "refreshed") {
+    console.log(`Refreshed the generated block in ${agentsRel}`);
+  } else {
+    console.log(`Kept ${agentsRel}: it has no generated markers, so it is treated as hand-written.`);
+  }
+
+  if (adopt) {
+    markAdopted(ROOT, pkg.path);
+    console.log(`Marked adopted: ${pkg.path}`);
+  }
+} catch (error) {
+  console.error(error instanceof Error ? error.message : String(error));
+  process.exit(1);
+}