create-agent-rig 0.2.0 → 0.3.1

package/CHANGELOG.md

@@ -0,0 +1,170 @@
+# Changelog
+
+Notable changes per release. The generated projects are the product, so an entry
+says what a **newly scaffolded project** gains or loses — not what moved inside
+the generator.
+
+Versions are published to npm as [`create-agent-rig`](https://www.npmjs.com/package/create-agent-rig);
+`npx github:serhii-baksheiev/create-agent-rig` keeps working for either path.
+
+## 0.3.1
+
+`create-agent-rig init` shipped a rig that looked installed and enforced
+nothing. Everything below is that one failure, in its four parts — a repo
+`init`ed with 0.3.0 should be re-run with this version (`--force` to replace the
+CLAUDE.md it wrote).
+
+### Fixed
+
+- **The hooks are wired.** `init` laid the hook files down and stopped there: no
+  `.claude/settings.json` meant `guard-bash`, `block-no-verify`, `gate-stop-dod`
+  and `inject-rules` were never called, while the installed `CLAUDE.md` claimed
+  they were enforced at the tool layer. The wiring is now _derived_ from the
+  shipped settings, so it names exactly the hooks that travelled — never one that
+  did not. Where the repo already has a `settings.json`, `init` keeps it and
+  prints the entries to merge rather than failing silently.
+- **The kill switch works.** `init` copied templates byte-for-byte, leaving
+  `__PROJECT_NAME__` in six places — including `stop-flag.mjs`, so the brake
+  looked for `~/.claude/__PROJECT_NAME__-loop-STOP` while the operator, following
+  the instructions in the same install, created `~/.claude/<repo>-loop-STOP`. It
+  never fired, and never said so.
+- **The installed `CLAUDE.md` describes the repo it landed in.** It used to be
+  the generated monorepo's map — `packages/core/`, `apps/web/`, links to an
+  `architecture.md` and two guards that `init` deliberately does not install. It
+  is now its own document: what was installed, what was not, and that the
+  architecture rules are yours to write.
+- **The elevated-path block names paths that exist.** It seeded
+  `packages/db/src/` into repos that have no such directory, so the Tier-2 gate
+  sweep reported "clean" while looking at nothing.
+
+### Added
+
+- A template test that fails if anything `init` installs references a `.claude`
+  file `init` does not install — the drift that produced three of the four
+  findings above, now mechanical.
+
+## 0.3.0
+
+The factory extraction: a scaffolded project now arrives with a working
+autonomous loop and the mechanisms that watch it, rather than an empty `.claude/`.
+
+### Added
+
+- **`guard-bash` hook** — the "Never" tier made mechanical: force-pushing or
+  deleting a shared branch, a direct push to the default branch, a production
+  deploy trigger, a catastrophic delete. It **parses** the command (quotes
+  honoured) instead of pattern-matching, so a commit message that mentions a
+  forbidden flag is prose, not a bypass.
+- **A kill switch that is a real file.** `touch ~/.claude/<project>-loop-STOP`
+  and no merge lands until it is removed. Everything short of the merge stays
+  allowed on purpose — stopping cleanly must not mean losing work.
+- **The queue seam.** `loop` no longer reads one tracker: selection goes through
+  `.claude/scripts/queue/`, with a pure core (filters, blocker resolution, tier
+  ration, sort, stop conditions) and three adapters — `plan-md` (the default; the
+  only one that works before a project has a remote), `github-issues`, `jira`.
+- **Two sweeps that run outside any session** — `detect-missed-gate` finds merges
+  that crossed an elevated path with no recorded reviewer verdict;
+  `reconcile-external-prs` accounts for work that reached the default branch
+  outside the queue. Both exist because a run cannot report its own missed gate.
+- **`preflight`** — the pre-run checks, which also print the items it did _not_
+  check, every time.
+- **Skills** — `worktree-task` (isolation when a second session may run) and
+  `new-invariant` (a generator for the invariant→hook→test pattern, with a
+  working example and its test).
+- **`rules/invariants.md`** — the pattern behind every hook here, stated once, so
+  the hooks read as examples rather than as laws.
+- **`aws-cdk` target extras** — the `ro-debug` skill (read-only runtime
+  investigation, with the traps that produce confident wrong diagnoses) and the
+  transferable AWS rules.
+- **`elevated-paths`** — a declaration in `CLAUDE.md`, composed with any block in
+  `.claude/rules/`, naming the paths where Tier-2 changes live.
+
+### Changed
+
+- The governance summary counts `.mjs` hooks only — a config file listed as an
+  enforced hook overstated the one number this tool exists to make credible.
+- `autonomy.md`: the tier is decided by what a change **touches**, not by what
+  the task predicted it would touch.
+
+### Fixed
+
+Four review rounds, ten reviewers, on this release's own code. What they caught,
+each reproduced before the fix and re-verified after:
+
+- a PR body could **forge its own reviewer verdict** and suppress the gate sweep
+  — the body is written by the actor being audited, so only the `human-review`
+  label (which needs repository permission) suppresses now;
+- the `plan-md` adapter's close **deleted the wrong line**, destroying a human's
+  Operator-queue entry and leaving the shipped item selectable;
+- every `github-issues` write **threw on success** (those `gh` subcommands print
+  text, not JSON) — `escalate` posted its diagnosis and then died before applying
+  the label that stops the item being re-picked;
+- the kill switch could be **disarmed by an env variable**, and was fixed in the
+  hook while the identical hole sat in `preflight` — the brake now has one
+  implementation;
+- three **total bypasses** in the guard, each an exception inside its own work
+  that the fail-open catch turned into "allow": an unbounded spread, a recursive
+  brace expansion, and a quadratic path collapse;
+- a heredoc pre-pass that could **hide any command** from every rule;
+- a ReDoS in the blocker parser reachable by anyone able to open an issue.
+
+Rounds 4 and 5, on the fixes themselves:
+
+- a here-string (`cat <<<X`) and an arithmetic left shift (`$((1<<n))`) were each
+  read as heredoc markers, **hiding every command up to the next matching line**;
+- `git commit -nm "msg"` bypassed the pre-commit gate outright — the one thing
+  that hook exists to stop, in the spelling people actually type;
+- with the kill switch armed, `git merge feat/x && git push` still landed a merge
+  on the default branch; a push must now name its ref while stopped;
+- pointing `HOME` at an empty directory disarmed the brake; it is now found
+  through the password database as well as the environment;
+- `gh --json files` truncates at 100 with **no marker**, and the gate sweep read
+  the short list as "touched nothing elevated" — a PR padded past 100 files hid
+  its elevated change. The sweep now compares against `changedFiles`;
+- declaring `.claude/` elevated was a no-op, because every `.md` under it counted
+  as inert — so a merge rewriting the autonomy tiers passed the gate meant to
+  catch exactly that;
+- a quadratic reviewer-name regex cost ~4 s per crafted PR body, minutes across a
+  sweep that reports nothing when killed.
+
+The README's enforcement claims were overstated and are now scoped to what the
+guard actually inspects, with the omissions listed in the hook itself: only `rm`
+for deletes, only a workflow dispatch for deploys, only a push that names its
+branch, and nothing carried as a flag value.
+
+The lesson that generalises is now a rule (`invariants.md`): **a guard that fails
+open must do provably bounded work**, because fail-open makes every line of work
+a potential total bypass — and prefer deleting a rule to adding one.
+
+## 0.2.0
+
+Distribution hardening (file modes, the `gitignore`→`.gitignore` trick, a
+pack-path e2e per target), agent-os v2 (`pr-ship`, `post-deploy-verify`,
+`cdk-diff-reviewer`, review-context isolation, session staleness), the `apps/web`
+frontend proving core purity across the wire, the `gate-stop-dod` and
+`inject-rules` hooks, `agent-rig init`, the `loop` skill, and the dev deploy
+workflows.
+
+## 0.1.0
+
+First release: the CLI, `agent-os/universal` + the `node-ts`/`aws-cdk` stack
+layers, and the `aws-serverless` and `node-service` targets.
+
+---
+
+## Releasing
+
+`npm publish` needs 2FA and cannot be undone, so an agent prepares a release and
+**stops at that command**. Everything before it is mechanical:
+
+1. `pnpm test` — the full suite, including the e2e that generates both targets
+   cold and runs their own checks through the git path **and** the pack path.
+2. `npm pack --dry-run` — confirm the templates, including the dotted `.claude/`
+   tree, are in the tarball. This is where scaffolders break, and the git path
+   cannot catch it.
+3. Version in `package.json` (and the private inner package, kept in step).
+4. This file, and `PLAN.md` if the plan's claims changed.
+5. `git tag v<version> && git push --tags`.
+6. **Owner:** `npm publish`.
+7. **Owner:** smoke the published artifact — `npx create-agent-rig@<version>` in
+   an empty directory, then `pnpm install && pnpm check` inside it.

package/README.md

@@ -22,7 +22,15 @@ npx create-agent-rig init --dry-run  # print the plan, write nothing
 ```
 
 `init` drops in the autonomy tiers, stop rules, workflow, and the enforcement
-hooks, and refuses to clobber an existing `CLAUDE.md`.
+hooks — **wired**, in a `.claude/settings.json` that names exactly the hooks it
+installed — plus a `CLAUDE.md` that describes that rig rather than the generated
+monorepo. It refuses to clobber an existing `CLAUDE.md`; if the repo already has
+a `.claude/settings.json`, it keeps it and prints the entries to merge, because a
+hook nothing calls is not enforcement.
+
+Two things it deliberately leaves to you, and says so in the installed
+`CLAUDE.md`: the Definition-of-Done gate has no `dod-checks.json` (it cannot know
+your commands), and the elevated-path list names only what every repo has.
 
 ## What you get
 
@@ -39,19 +47,55 @@ never inflated). The hooks live in `.claude/hooks/` and are wired in
 - **`block-no-verify`** — refuses bypassing pre-commit checks (and knows the
   difference between using the `--no-verify`/`-n` flag and merely mentioning it
   in a message);
+- **`guard-bash`** — refuses the part of the "Never" tier a text scan can decide:
+  a force-push or `--delete` naming a shared branch, a push that names the default
+  branch, `gh workflow run`/`gh api …/dispatches` against a production workflow,
+  and `rm` on a catastrophic target. It **parses** the command rather than
+  pattern-matching it, so a commit message mentioning a forbidden flag is prose,
+  not a bypass — and the file states exactly what it does **not** inspect
+  (`cdk deploy`, `find -delete`, a bare `git push`, and more);
 - **`gate-stop-dod`** — refuses to end the session while a Definition-of-Done
   check is red; it fails open (a missing or corrupt config never makes the
   session unquittable) and never blocks twice in a row;
 - **`inject-rules`** — re-injects the autonomy rules at session start, so they
   survive compaction and resumes.
 
-Around the hooks, the operating system: **autonomy tiers** (what an agent does
-alone / after review / never), **stop rules** (three strikes, flaky ≠ retry,
-session staleness), **subagent gates** (`test-writer`, `code-reviewer`,
-`security-scanner`, and `cdk-diff-reviewer` on the AWS target), **skills**
-(`pr-ship` pre-merge gate; `loop` queue driver; `post-deploy-verify` with its
-binary HEALTHY/REGRESSION verdict on the AWS target), and a one-page
-`CLAUDE.md` map a fresh session orients by.
+**A brake that is a real file.** `touch ~/.claude/<project>-loop-STOP` and no
+merge lands until it is removed — enforced at the tool layer, so it holds even if
+nothing reads the rule. Everything short of the merge stays allowed on purpose:
+finish the task, push the branch, open the PR, write the journal. Stopping
+cleanly must not mean losing work.
+
+**Two sweeps meant to run outside any session** — nothing schedules them for you;
+that is deliberate, because a check a run performs on itself is one a hurried run
+skips. `detect-missed-gate` finds merges
+that crossed an elevated path with no recorded reviewer verdict;
+`reconcile-external-prs` accounts for work that reached the default branch outside
+the queue. They exist because the one failure a run cannot report is its own
+missed gate — the run that skipped it is exactly the run that will not mention it.
+
+**A queue behind an adapter.** The `loop` driver selects through
+`.claude/scripts/queue/`: a pure core (filters in order, blocker resolution, the
+elevated-tier ration, stop conditions) with adapters for `PLAN.md` (the default,
+working before a project has a remote), GitHub Issues, and Jira. Two rules are
+load-bearing and tested from both directions — **blockers resolve from links,
+never labels**, and **the agent never files its own work items**.
+
+Around all of it: **autonomy tiers** (what an agent does alone / after review /
+never), **stop rules** (three strikes, flaky ≠ retry, session staleness),
+**subagent gates** (`test-writer`, `code-reviewer`, `security-scanner`, and
+`cdk-diff-reviewer` on the AWS target), **skills** (`pr-ship` pre-merge gate;
+`loop` queue driver; `worktree-task` for concurrent sessions; `new-invariant`, a
+generator for the invariant→hook→test pattern; `post-deploy-verify` and
+`ro-debug` on the AWS target), and a one-page `CLAUDE.md` map a fresh session
+orients by.
+
+**The hooks are examples, not laws.** `.claude/rules/invariants.md` states the
+pattern behind each one — a stated invariant, a mechanical check, a test for the
+check — so you can delete the ones whose invariant your project does not have and
+spend the slot on one it does. An inherited rule nobody chose is worse than an
+empty rule file: the empty one is visibly incomplete, the inherited one is
+invisibly wrong.
 
 The skeleton around it is real and runnable — pure core shared by server _and_
 browser (one schema validates on both sides of the wire), a mandatory usecase
@@ -117,5 +161,17 @@ dependencies fresh to catch upstream breakage early. This repo dogfoods its own
 rulebook — `CLAUDE.md` and `.claude/` are composed from the templates, and
 drift fails the suite.
 
-Development: `pnpm test` (full), `pnpm test:unit` (fast loop),
-`pnpm template:check` (templates in place). The plan of record is `PLAN.md`.
+**And the enforcement layer is adversarially reviewed, not just tested.** The
+Bash guard went through four review rounds with ten reviewers, who executed it
+rather than read it. They found a PR body that could forge its own reviewer
+verdict, a queue write that deleted the wrong line, and three ways to make the
+guard crash into permitting everything. Each round's findings — including the
+ones introduced by the previous round's _fix_ — are in the git history and in
+`CHANGELOG.md`. The rule that came out of it is now part of what ships: a guard
+that fails open must do provably bounded work, because fail-open turns every line
+of its own work into a potential bypass.
+
+Development (from a clone — `PLAN.md` and `demo.sh` live in the repository, not
+in the published tarball): `pnpm test` (full), `pnpm test:unit` (fast loop),
+`pnpm template:check` (templates in place). The plan of record is `PLAN.md`;
+release notes and the release checklist ship in `CHANGELOG.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-agent-rig",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "Scaffold a new project with an agent operating system (rules, gates, hooks) and a runnable code skeleton",
   "keywords": [
     "create",
@@ -15,6 +15,12 @@
     "node-service"
   ],
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/serhii-baksheiev/create-agent-rig.git"
+  },
+  "homepage": "https://github.com/serhii-baksheiev/create-agent-rig#readme",
+  "bugs": "https://github.com/serhii-baksheiev/create-agent-rig/issues",
   "type": "module",
   "bin": {
     "create-agent-rig": "packages/cli/dist/index.js"
@@ -22,7 +28,8 @@
   "files": [
     "packages/cli/dist",
     "templates",
-    "scripts/prepare.mjs"
+    "scripts/prepare.mjs",
+    "CHANGELOG.md"
   ],
   "engines": {
     "node": ">=20"

package/packages/cli/dist/commands/init.js

@@ -1,37 +1,93 @@
 import { access, mkdir, readFile, writeFile } from 'node:fs/promises';
 import path from 'node:path';
-import { agentOsUniversalDir } from '../templates.js';
+import { settingsForInstalledHooks } from '../lib/init-settings.js';
+import { substituteContent } from '../lib/substitute.js';
+import { agentOsInitDir, agentOsUniversalDir } from '../templates.js';
 /** A user-facing failure: message is printed as-is, no stack trace. */
 export class InitError extends Error {
 }
+const SETTINGS = '.claude/settings.json';
 async function loadManifest() {
     const raw = await readFile(path.join(agentOsUniversalDir(), 'layers.json'), 'utf8');
     return JSON.parse(raw);
 }
+async function exists(p) {
+    try {
+        await access(p);
+        return true;
+    }
+    catch {
+        return false;
+    }
+}
+/**
+ * The name this repo is known by inside the rig. It ends up in a *filename* —
+ * `~/.claude/<name>-loop-STOP`, the kill switch — so it is reduced to
+ * characters an operator can type into a shell without quoting.
+ */
+export function projectNameFor(repoDir) {
+    const base = path.basename(path.resolve(repoDir));
+    const slug = base
+        .toLowerCase()
+        .replace(/[^a-z0-9._-]+/g, '-')
+        .replace(/^[-.]+|[-.]+$/g, '');
+    return slug === '' ? 'project' : slug;
+}
 /**
  * `init` installs only the PROCESS layer (hooks-and-reach brief §3/§4): rules
  * that assume nothing about the codebase shape. Architecture rules reference
  * `packages/core` and friends — installing them into an arbitrary repo would
  * describe a structure that does not exist, which is worse than no rule.
  *
- * CLAUDE.md is the meta file we bring, but never over an existing one.
+ * It also installs two things the process manifest does not name, because both
+ * are meaningless in the generated shape and load-bearing here:
+ *
+ * - `CLAUDE.md` — the map, taken from the init override layer, which describes
+ *   the rig this command installs rather than the generated monorepo;
+ * - `.claude/settings.json` — the wiring, derived from the shipped settings so
+ *   it names exactly the hooks that travelled.
  */
-async function processFiles(manifest) {
-    // the process layer, plus CLAUDE.md as the map (guarded separately)
-    return [...manifest.process, 'CLAUDE.md'];
-}
-async function exists(p) {
-    try {
-        await access(p);
-        return true;
+export async function initManifest() {
+    const manifest = await loadManifest();
+    const universal = agentOsUniversalDir();
+    const override = agentOsInitDir();
+    const files = [];
+    for (const rel of [...manifest.process, 'CLAUDE.md']) {
+        const overridden = path.join(override, rel);
+        files.push({
+            rel,
+            source: (await exists(overridden)) ? overridden : path.join(universal, rel),
+        });
     }
-    catch {
-        return false;
+    files.push({ rel: SETTINGS, source: null });
+    return files;
+}
+/**
+ * Exactly the bytes `init` would write, keyed by destination path — the single
+ * source the plan, the install and the template tests all read.
+ *
+ * Every file the process layer carries is text (asserted by a template test),
+ * so substitution can be applied unconditionally: an unsubstituted
+ * `__PROJECT_NAME__` in `stop-flag.mjs` is a kill switch that silently never
+ * fires.
+ */
+export async function initFileContents(repoDir) {
+    const projectName = projectNameFor(repoDir);
+    const ctx = { projectName, projectScope: projectName, region: '' };
+    const files = await initManifest();
+    const contents = new Map();
+    for (const { rel, source } of files) {
+        if (source === null)
+            continue;
+        contents.set(rel, substituteContent(await readFile(source, 'utf8'), ctx));
     }
+    const installedHooks = new Set(files.map((f) => f.rel).filter((rel) => rel.startsWith('.claude/hooks/')));
+    const shipped = JSON.parse(await readFile(path.join(agentOsUniversalDir(), SETTINGS), 'utf8'));
+    contents.set(SETTINGS, `${JSON.stringify(settingsForInstalledHooks(shipped, installedHooks), null, 2)}\n`);
+    return contents;
 }
 export async function planInit(repoDir) {
-    const manifest = await loadManifest();
-    const files = await processFiles(manifest);
+    const files = (await initManifest()).map((f) => f.rel);
     const conflicts = [];
     for (const rel of files) {
         if (await exists(path.join(repoDir, rel)))
@@ -40,9 +96,7 @@ export async function planInit(repoDir) {
     return { files: files.map((p) => ({ path: p })), conflicts };
 }
 export async function initProject(repoDir, options) {
-    const manifest = await loadManifest();
-    const files = await processFiles(manifest);
-    const universal = agentOsUniversalDir();
+    const files = (await initManifest()).map((f) => f.rel);
     // Refuse to clobber an existing CLAUDE.md unless forced — init edits
     // someone's working repository (brief §4, non-negotiable).
     if (!options.force && files.includes('CLAUDE.md')) {
@@ -51,6 +105,7 @@ export async function initProject(repoDir, options) {
                 'Merge the agent-os map in by hand, or re-run with --force to replace it.');
         }
     }
+    const contents = await initFileContents(repoDir);
     const written = [];
     const skipped = [];
     const plannedCount = files.length;
@@ -65,7 +120,7 @@ export async function initProject(repoDir, options) {
         if (options.dryRun)
             continue;
         await mkdir(path.dirname(dest), { recursive: true });
-        await writeFile(dest, await readFile(path.join(universal, rel)));
+        await writeFile(dest, contents.get(rel) ?? '');
         written.push(rel);
     }
     return { written, skipped, plannedCount };

package/packages/cli/dist/index.js

@@ -4,7 +4,7 @@ import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { parseArgs } from 'node:util';
 import { CreateError, createProject } from './commands/create.js';
-import { InitError, initProject, planInit } from './commands/init.js';
+import { InitError, initFileContents, initProject, planInit } from './commands/init.js';
 import { makePalette } from './lib/colors.js';
 import { promptTarget } from './lib/prompts.js';
 import { collectGovernance, renderSummary } from './lib/summary.js';
@@ -65,6 +65,16 @@ async function runInit(rawArgs) {
     process.stdout.write(`\nInstalled ${result.written.length} files` +
         (result.skipped.length ? `, kept ${result.skipped.length} existing` : '') +
         '.\n');
+    // The one kept file that silently disables everything else: without this
+    // wiring the hooks sit on disk and are never called, while the rules claim
+    // they are enforced. Say so loudly, and hand over the exact entries.
+    if (result.skipped.includes('.claude/settings.json')) {
+        const wiring = (await initFileContents(cwd)).get('.claude/settings.json') ?? '';
+        process.stdout.write(`\n!  .claude/settings.json already exists — it was kept, so the rig's hooks are NOT wired.\n` +
+            `   Until you merge these entries into it, nothing enforces the rules:\n\n` +
+            wiring.replace(/^/gm, '   ') +
+            '\n');
+    }
     return 0;
 }
 async function main() {

package/packages/cli/dist/lib/init-settings.js

@@ -0,0 +1,52 @@
+/**
+ * `init` installs the PROCESS layer only — a subset of the hooks the generated
+ * shape gets. The wiring it writes has to match that subset exactly:
+ *
+ * - wiring a hook file that was not installed makes every matching tool call
+ *   fail on a missing module;
+ * - wiring nothing at all is worse and quieter — the hooks sit on disk, the
+ *   rules claim they are enforced, and nothing ever calls them.
+ *
+ * So the wiring is *derived* from the shipped settings.json rather than
+ * maintained as a second copy: add a process hook and wire it once, upstream,
+ * and init picks it up.
+ */
+/** Matches the hook file a wired command runs, e.g. `.claude/hooks/guard-bash.mjs`. */
+const HOOK_REFERENCE = /\.claude\/hooks\/[A-Za-z0-9._-]+\.mjs/;
+function isRecord(value) {
+    return typeof value === 'object' && value !== null && !Array.isArray(value);
+}
+/** An entry survives unless it names a hook file that is not installed. */
+function keepEntry(entry, installed) {
+    if (!isRecord(entry) || typeof entry.command !== 'string')
+        return true;
+    const referenced = HOOK_REFERENCE.exec(entry.command);
+    return referenced === null || installed.has(referenced[0]);
+}
+/** A group survives only with at least one entry left — never as an empty shell. */
+function keepGroup(group, installed) {
+    if (!isRecord(group) || !Array.isArray(group.hooks))
+        return group;
+    const hooks = group.hooks.filter((entry) => keepEntry(entry, installed));
+    return hooks.length === 0 ? null : { ...group, hooks };
+}
+/**
+ * The shipped settings, narrowed to the hooks actually installed. Shapes this
+ * function does not understand are passed through untouched — it filters, it
+ * never rewrites.
+ */
+export function settingsForInstalledHooks(settings, installed) {
+    if (!isRecord(settings) || !isRecord(settings.hooks))
+        return settings;
+    const events = {};
+    for (const [event, groups] of Object.entries(settings.hooks)) {
+        if (!Array.isArray(groups)) {
+            events[event] = groups;
+            continue;
+        }
+        const kept = groups.map((group) => keepGroup(group, installed)).filter((g) => g !== null);
+        if (kept.length > 0)
+            events[event] = kept;
+    }
+    return { ...settings, hooks: events };
+}

package/packages/cli/dist/lib/summary.js

@@ -1,21 +1,35 @@
 import { readdir } from 'node:fs/promises';
 import path from 'node:path';
-const names = async (dir, strip) => {
+const names = async (dir, strip, keep) => {
     try {
-        return (await readdir(dir)).map((entry) => entry.replace(strip, '')).sort();
+        return (await readdir(dir))
+            .filter((entry) => !keep || keep.test(entry))
+            .map((entry) => entry.replace(strip, ''))
+            .sort();
     }
     catch {
         return [];
     }
 };
+/**
+ * Hooks whose filename names the *tool* they intercept rather than the
+ * invariant they enforce. Stripping the prefix would print "bash", which tells
+ * the reader nothing — and a screen that sells enforcement may not be vague.
+ */
+const HOOK_LABELS = {
+    'guard-bash': 'never tier',
+};
 export async function collectGovernance(projectDir) {
     const claude = path.join(projectDir, '.claude');
     return {
         rules: await names(path.join(claude, 'rules'), /\.md$/),
         agents: await names(path.join(claude, 'agents'), /\.md$/),
-        hooks: (await names(path.join(claude, 'hooks'), /\.mjs$/))
-            // guard-core-purity → "core purity": the mechanism, not the filename
-            .map((hook) => hook.replace(/^(guard|block)-/, '').replaceAll('-', ' ')),
+        // `.mjs` only: the stack layer also drops config (dod-checks.json) in this
+        // directory, and counting a config file as an enforced hook would make the
+        // screen overstate the one thing this tool actually sells.
+        hooks: (await names(path.join(claude, 'hooks'), /\.mjs$/, /\.mjs$/)).map(
+        // guard-core-purity → "core purity": the mechanism, not the filename
+        (hook) => HOOK_LABELS[hook] ?? hook.replace(/^(guard|block)-/, '').replaceAll('-', ' ')),
         skills: await names(path.join(claude, 'skills'), /$^/),
     };
 }

package/packages/cli/dist/templates.js

@@ -19,3 +19,11 @@ export function agentOsUniversalDir() {
 export function agentOsStackDir(stack) {
     return path.join(templatesRoot(), 'agent-os', 'stack', stack);
 }
+/**
+ * Overrides `init` applies on top of the universal layer. A file here replaces
+ * its universal namesake when the rig is installed into an existing repo whose
+ * shape the generator knows nothing about. `create` never reads this directory.
+ */
+export function agentOsInitDir() {
+    return path.join(templatesRoot(), 'agent-os', 'init');
+}