create-claude-cabinet 0.11.2 → 0.12.1

package/README.md

@@ -185,7 +185,7 @@ source code.
 └── settings.json    # hook configuration
 
 scripts/
-├── pib-db.js        # work tracking CLI (if installed)
+├── pib-db.mjs        # work tracking CLI (if installed)
 └── ...              # triage tools (if audit installed)
 
 .ccrc.json           # installation metadata

package/lib/cli.js

@@ -304,7 +304,7 @@ const MODULES = {
     name: 'Session Loop (orient + debrief)',
     description: 'The briefing cycle. Claude starts each session informed, ends by preparing the next briefing.',
     mandatory: true,
-    templates: ['skills/orient', 'skills/orient-quick', 'skills/debrief', 'skills/debrief-quick', 'skills/debrief/phases/upstream-feedback.md', 'skills/menu', 'hooks/stop-hook.md'],
+    templates: ['skills/orient', 'skills/orient-quick', 'skills/debrief', 'skills/debrief-quick', 'skills/debrief/phases/upstream-feedback.md', 'skills/menu'],
   },
   'hooks': {
     name: 'Git Guardrails + Telemetry',
@@ -320,7 +320,7 @@ const MODULES = {
     mandatory: false,
     default: true,
     lean: false,
-    templates: ['scripts/pib-db.js', 'scripts/pib-db-schema.sql', 'scripts/work-tracker-server.mjs', 'scripts/work-tracker-ui.html', 'skills/work-tracker'],
+    templates: ['scripts/pib-db.mjs', 'scripts/pib-db-schema.sql', 'scripts/work-tracker-server.mjs', 'scripts/work-tracker-ui.html', 'skills/work-tracker'],
     needsDb: true,
   },
   'planning': {
@@ -390,7 +390,7 @@ const MODULES = {
     default: true,
     lean: false,
     needsOmega: true,
-    templates: ['skills/memory', 'scripts/cabinet-memory-adapter.py', 'rules/memory-capture.md'],
+    templates: ['skills/memory', 'scripts/cabinet-memory-adapter.py', 'rules/memory-capture.md', 'hooks/omega-memory-guard.sh'],
   },
 };
 
@@ -621,7 +621,7 @@ async function run() {
     selectedModules = Object.keys(MODULES);
     if (flags.noDb) {
       includeDb = false;
-      // work-tracking templates are still copied (pib-db.js, schema) but
+      // work-tracking templates are still copied (pib-db.mjs, schema) but
       // the DB isn't initialized. Mark it as skipped so /onboard knows
       // to ask about the alternative work tracking system.
       selectedModules = selectedModules.filter(m => m !== 'work-tracking');
@@ -845,7 +845,8 @@ async function run() {
 
   // --- Merge hooks into settings.json ---
   if (selectedModules.includes('hooks') && !flags.dryRun) {
-    const settingsPath = mergeSettings(projectDir, { includeDb });
+    const includeMemory = selectedModules.includes('memory');
+    const settingsPath = mergeSettings(projectDir, { includeDb, includeMemory });
     console.log(`  ⚙️  Merged hooks into ${path.relative(projectDir, settingsPath)}`);
   }
 
@@ -856,7 +857,7 @@ async function run() {
       for (const r of dbResults) console.log(`  🗄️  ${r}`);
     } catch (err) {
       console.log(`  ⚠ Database setup failed: ${err.message}`);
-      console.log('    You can set it up later: node scripts/pib-db.js init');
+      console.log('    You can set it up later: node scripts/pib-db.mjs init');
     }
   }
 

package/lib/db-setup.js

@@ -4,7 +4,7 @@ const path = require('path');
 
 /**
  * Set up the PIB database in the target project.
- * - Copies pib-db.js and schema to scripts/
+ * - Copies pib-db.mjs and schema to scripts/
  * - Runs npm init if no package.json
  * - Installs better-sqlite3
  * - Runs pib-db init
@@ -21,14 +21,8 @@ function setupDb(projectDir) {
     results.push('Created package.json');
   }
 
-  // pib-db.js uses ESM imports — ensure package.json has "type": "module"
-  // Skip this for the CC source repo itself (its CLI uses CommonJS)
-  const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf8'));
-  if (pkg.type !== 'module' && pkg.name !== 'create-claude-cabinet') {
-    pkg.type = 'module';
-    fs.writeFileSync(pkgPath, JSON.stringify(pkg, null, 2) + '\n');
-    results.push('Set package.json type to "module"');
-  }
+  // pib-db.mjs uses ESM imports — .mjs extension lets Node treat it as ESM
+  // regardless of the project's package.json type field
 
   // Install better-sqlite3 if not already installed
   const nodeModules = path.join(projectDir, 'node_modules', 'better-sqlite3');
@@ -39,7 +33,7 @@ function setupDb(projectDir) {
   }
 
   // Initialize the database
-  const dbScript = path.join(scriptsDir, 'pib-db.js');
+  const dbScript = path.join(scriptsDir, 'pib-db.mjs');
   if (fs.existsSync(dbScript)) {
     console.log('  Initializing database...');
     execSync(`node ${dbScript} init`, { cwd: projectDir, stdio: 'pipe' });

package/lib/settings-merge.js

@@ -1,6 +1,20 @@
 const fs = require('fs');
 const path = require('path');
 
+const MEMORY_HOOKS = {
+  PreToolUse: [
+    {
+      matcher: 'Edit|Write',
+      hooks: [
+        {
+          type: 'command',
+          command: '.claude/hooks/omega-memory-guard.sh',
+        },
+      ],
+    },
+  ],
+};
+
 const DEFAULT_HOOKS = {
   PreToolUse: [
     {
@@ -50,7 +64,7 @@ const DEFAULT_HOOKS = {
  * Merge PIB hooks into the project's .claude/settings.json.
  * Creates the file if it doesn't exist. Preserves existing hooks.
  */
-function mergeSettings(projectDir, { includeDb = true } = {}) {
+function mergeSettings(projectDir, { includeDb = true, includeMemory = false } = {}) {
   const settingsDir = path.join(projectDir, '.claude');
   const settingsPath = path.join(settingsDir, 'settings.json');
 
@@ -81,8 +95,20 @@ function mergeSettings(projectDir, { includeDb = true } = {}) {
     });
   }
 
+  // Build the full hook set — include memory hooks if memory module is selected
+  const allHooks = { ...DEFAULT_HOOKS };
+  if (includeMemory) {
+    for (const [event, hooks] of Object.entries(MEMORY_HOOKS)) {
+      if (!allHooks[event]) {
+        allHooks[event] = hooks;
+      } else {
+        allHooks[event] = [...allHooks[event], ...hooks];
+      }
+    }
+  }
+
   // Merge each hook event type
-  for (const [event, newHooks] of Object.entries(DEFAULT_HOOKS)) {
+  for (const [event, newHooks] of Object.entries(allHooks)) {
     if (!settings.hooks[event]) {
       settings.hooks[event] = newHooks;
     } else {
@@ -106,4 +132,4 @@ function mergeSettings(projectDir, { includeDb = true } = {}) {
   return settingsPath;
 }
 
-module.exports = { mergeSettings, DEFAULT_HOOKS };
+module.exports = { mergeSettings, DEFAULT_HOOKS, MEMORY_HOOKS };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-cabinet",
-  "version": "0.11.2",
+  "version": "0.12.1",
   "description": "Claude Cabinet — opinionated process scaffolding for Claude Code projects",
   "bin": {
     "create-claude-cabinet": "bin/create-claude-cabinet.js"

package/templates/README.md

@@ -11,12 +11,11 @@ templates, see [EXTENSIONS.md](EXTENSIONS.md).
 
 ## What's Here
 
-### Hooks (5)
+### Hooks (4)
 
 | Artifact | What It Does |
 |----------|-------------|
 | `hooks/git-guardrails.sh` | PreToolUse hook that blocks destructive git operations (force push to main, hard reset, git clean). Zero configuration. |
-| `hooks/stop-hook.md` | Stop event hook that checks whether the session-closing skill ran. Prompt-type (advisory, not blocking). |
 | `hooks/skill-telemetry.sh` | UserPromptSubmit hook that detects /skill-name invocations and logs to JSONL. Configurable via env vars. |
 | `hooks/skill-tool-telemetry.sh` | PostToolUse hook that captures programmatic Skill tool invocations. Configurable via env vars. |
 | `hooks/cc-upstream-guard.sh` | PreToolUse hook that blocks edits to manifest-tracked upstream files. Prevents downstream drift. |
@@ -115,7 +114,7 @@ mandates and scoped directives.
 | `scripts/finding-schema.json` | JSON Schema for audit finding validation. |
 | `scripts/load-triage-history.js` | Build suppression lists from triage history. Tries pib-db first, falls back to filesystem. |
 | `scripts/merge-findings.js` | Merge per-cabinet-member JSON outputs into unified run-summary. Optional `--db` flag for pib-db ingestion. |
-| `scripts/pib-db.js` | Reference data layer CLI. SQLite for work tracking (actions, projects) and audit findings. |
+| `scripts/pib-db.mjs` | Reference data layer CLI. SQLite for work tracking (actions, projects) and audit findings. |
 | `scripts/pib-db-schema.sql` | Database schema: projects, actions, audit_runs, audit_findings. |
 | `scripts/resolve-committees.cjs` | Merge upstream `committees.yaml` with project `committees-project.yaml`. Deterministic output. |
 | `scripts/triage-server.mjs` | Self-contained Node.js HTTP server for triage UI. Zero external dependencies. |
@@ -171,7 +170,7 @@ into your project's `.claude/` directory. The minimum viable adoption:
 
 You now have git safety and skill discovery. Add more modules as needed:
 
-- **Session loop:** `skills/orient/`, `skills/debrief/`, `hooks/stop-hook.md`
+- **Session loop:** `skills/orient/`, `skills/debrief/`
 - **Planning:** `skills/plan/`, `skills/execute/`
 - **Audit:** `skills/audit/`, `skills/pulse/`, `skills/triage-audit/`, plus `cabinet/` infrastructure and `scripts/`
 - **Cabinet members:** Copy individual `skills/cabinet-*/` directories for the experts you want

package/templates/hooks/omega-memory-guard.sh

@@ -0,0 +1,83 @@
+#!/bin/bash
+# Omega Memory Guard — PreToolUse hook for Edit and Write tool calls
+#
+# When omega is available, blocks writes to flat markdown memory files.
+# Semantic memories belong in omega (searchable, deduplicated, graph-linked).
+# Flat markdown is the fallback ONLY when omega is unavailable.
+#
+# Scope:
+#   BLOCKS:  .claude/memory/*.md, .claude/projects/*/memory/*.md
+#   ALLOWS:  MEMORY.md index files (structural, not memory content)
+#   ALLOWS:  memory/patterns/*.md (enforcement pipeline artifacts)
+#   ALLOWS:  Everything if omega is unavailable (flat markdown IS correct fallback)
+#
+# ROLLBACK: Comment out the PreToolUse entry for this hook in
+# .claude/settings.json to disable it immediately.
+#
+# Hook contract:
+#   Input: $CLAUDE_TOOL_INPUT has the tool use JSON with "file_path" field
+#   Output: JSON on stdout with { "decision": "block"|"allow", "reason": "..." }
+
+# Extract file_path from tool input
+FILE_PATH=$(echo "$CLAUDE_TOOL_INPUT" | python3 -c "import sys,json; print(json.load(sys.stdin).get('file_path',''))" 2>/dev/null)
+
+if [ -z "$FILE_PATH" ]; then
+  echo '{"decision":"allow"}'
+  exit 0
+fi
+
+# Only care about memory directory paths
+case "$FILE_PATH" in
+  */.claude/memory/*|*/.claude/projects/*/memory/*)
+    ;;
+  *)
+    echo '{"decision":"allow"}'
+    exit 0
+    ;;
+esac
+
+# Allow MEMORY.md index files (structural, not memory content)
+BASENAME=$(basename "$FILE_PATH")
+if [ "$BASENAME" = "MEMORY.md" ]; then
+  echo '{"decision":"allow"}'
+  exit 0
+fi
+
+# Allow pattern files (enforcement pipeline artifacts, not semantic memories)
+case "$FILE_PATH" in
+  */memory/patterns/*)
+    echo '{"decision":"allow"}'
+    exit 0
+    ;;
+esac
+
+# Check if omega is available
+OMEGA_PYTHON="$HOME/.claude-cabinet/omega-venv/bin/python3"
+if [ ! -x "$OMEGA_PYTHON" ]; then
+  # Omega not available — flat markdown IS the correct fallback
+  echo '{"decision":"allow"}'
+  exit 0
+fi
+
+# Find the adapter script
+find_adapter() {
+  local dir="$PWD"
+  while [ "$dir" != "/" ]; do
+    if [ -f "$dir/scripts/cabinet-memory-adapter.py" ]; then
+      echo "$dir/scripts/cabinet-memory-adapter.py"
+      return 0
+    fi
+    dir=$(dirname "$dir")
+  done
+  return 1
+}
+
+ADAPTER=$(find_adapter)
+if [ -z "$ADAPTER" ]; then
+  # No adapter found — flat markdown fallback is correct
+  echo '{"decision":"allow"}'
+  exit 0
+fi
+
+# Omega is available — block the flat markdown write
+echo "{\"decision\":\"block\",\"reason\":\"Omega is active — use omega_store() or the adapter instead of writing to flat markdown memory files. Run: echo '{\\\"text\\\": \\\"your memory\\\", \\\"type\\\": \\\"lesson\\\"}' | $OMEGA_PYTHON $ADAPTER store\"}"

package/templates/scripts/merge-findings.js

@@ -117,7 +117,7 @@ console.log(`  critical: ${severityCounts.critical}, warn: ${severityCounts.warn
 // ---------------------------------------------------------------------------
 if (useDb) {
   try {
-    const pibDb = join(__dirname, 'pib-db.js');
+    const pibDb = join(__dirname, 'pib-db.mjs');
     execSync(`node "${pibDb}" ingest-findings "${runDir}"`, { stdio: 'inherit' });
   } catch (err) {
     console.error(`DB ingest failed: ${err.message}`);

package/templates/scripts/pib-db-schema.sql

@@ -3,8 +3,8 @@
 -- This is the default persistence layer. Projects that outgrow it
 -- override via phase files (pointing to their own API, DB, or service).
 --
--- Initialize: node scripts/pib-db.js init
--- Query:      node scripts/pib-db.js query "SELECT ..."
+-- Initialize: node scripts/pib-db.mjs init
+-- Query:      node scripts/pib-db.mjs query "SELECT ..."
 
 CREATE TABLE IF NOT EXISTS projects (
   fid           TEXT PRIMARY KEY CHECK(fid GLOB 'prj:*'),

package/templates/scripts/{pib-db.js → pib-db.mjs}

@@ -6,17 +6,17 @@
 // override via phase files (pointing to their own API, DB, or service).
 //
 // Usage:
-//   node scripts/pib-db.js init                        # Create/migrate DB
-//   node scripts/pib-db.js query "SELECT * FROM ..."   # Run a query
-//   node scripts/pib-db.js create-action "Do the thing" --area dev
-//   node scripts/pib-db.js list-actions [--status X]   # Open actions (or filtered)
-//   node scripts/pib-db.js update-action act:abc --status in-progress
-//   node scripts/pib-db.js complete-action act:abc123
-//   node scripts/pib-db.js create-project "My Project" --area dev
-//   node scripts/pib-db.js list-projects               # Active projects
-//   node scripts/pib-db.js ingest-findings <run-dir>   # Ingest audit findings
-//   node scripts/pib-db.js triage <finding-id> <status> [notes]
-//   node scripts/pib-db.js triage-history              # Suppression list JSON
+//   node scripts/pib-db.mjs init                        # Create/migrate DB
+//   node scripts/pib-db.mjs query "SELECT * FROM ..."   # Run a query
+//   node scripts/pib-db.mjs create-action "Do the thing" --area dev
+//   node scripts/pib-db.mjs list-actions [--status X]   # Open actions (or filtered)
+//   node scripts/pib-db.mjs update-action act:abc --status in-progress
+//   node scripts/pib-db.mjs complete-action act:abc123
+//   node scripts/pib-db.mjs create-project "My Project" --area dev
+//   node scripts/pib-db.mjs list-projects               # Active projects
+//   node scripts/pib-db.mjs ingest-findings <run-dir>   # Ingest audit findings
+//   node scripts/pib-db.mjs triage <finding-id> <status> [notes]
+//   node scripts/pib-db.mjs triage-history              # Suppression list JSON
 //
 // Environment:
 //   PIB_DB_PATH  — path to SQLite file (default: ./pib.db)
@@ -44,9 +44,16 @@ function getDb() {
     db.pragma('journal_mode = WAL');
     db.pragma('foreign_keys = ON');
     return db;
-  } catch {
-    console.error('Error: better-sqlite3 not found. Install it:');
-    console.error('  npm install better-sqlite3');
+  } catch (err) {
+    if (err.code === 'ERR_DLOPEN_FAILED') {
+      console.error('Error: better-sqlite3 native module version mismatch.');
+      console.error('  Rebuild it for your current Node version:');
+      console.error('  npm rebuild better-sqlite3');
+    } else {
+      console.error('Error: better-sqlite3 not found. Install it:');
+      console.error('  npm install better-sqlite3');
+    }
+    if (err.message) console.error(`  (${err.message.split('\n')[0]})`);
     process.exit(1);
   }
 }
@@ -344,7 +351,7 @@ switch (command) {
     triageHistory();
     break;
   default:
-    console.log(`Usage: pib-db.js <command>
+    console.log(`Usage: pib-db.mjs <command>
 
 Commands:
   init                              Create/migrate the database

package/templates/scripts/work-tracker-server.mjs

@@ -18,7 +18,7 @@ const DB_PATH = resolve(process.argv.find((_, i, a) => a[i - 1] === '--db') || '
 
 if (!existsSync(DB_PATH)) {
   console.error(`Database not found: ${DB_PATH}`);
-  console.error('Run: node scripts/pib-db.js init');
+  console.error('Run: node scripts/pib-db.mjs init');
   process.exit(1);
 }
 

package/templates/skills/audit/SKILL.md

@@ -40,7 +40,7 @@ related:
     path: scripts/load-triage-history.js
     role: "Builds suppression lists from triage history"
   - type: file
-    path: scripts/pib-db.js
+    path: scripts/pib-db.mjs
     role: "Reference data layer for finding persistence"
 ---
 

package/templates/skills/cabinet-cc-health/SKILL.md

@@ -222,7 +222,7 @@ drift between the two:
   - Work tracking specifically: the pib-db scripts ship with both the
     work-tracking and audit modules, so `.ccrc.json` alone doesn't tell
     you if work tracking is active. Check whether `pib.db` exists AND
-    has projects/actions with real data (`node scripts/pib-db.js
+    has projects/actions with real data (`node scripts/pib-db.mjs
     list-projects`). If it does but the briefing says "no work tracking,"
     that's a direct contradiction.
   - `.ccrc.json` version vs `package.json` version — they should match.

package/templates/skills/debrief/SKILL.md

@@ -268,9 +268,9 @@ anything that future sessions need to know? A new pattern, a gotcha,
 a process gap, a user preference? Lessons are perishable — capture
 them now while context is fresh.
 
-**Omega-primary:** If `~/.claude-cabinet/omega-venv/bin/python3` and
+**Omega-only:** If `~/.claude-cabinet/omega-venv/bin/python3` and
 `scripts/cabinet-memory-adapter.py` both exist, write lessons to omega
-as the primary destination — not flat markdown. Use the adapter:
+— never to flat markdown. A guard hook enforces this. Use the adapter:
 
 ```bash
 echo '{"text": "the lesson", "type": "lesson"}' | \
@@ -278,7 +278,7 @@ echo '{"text": "the lesson", "type": "lesson"}' | \
 ```
 
 Types: `decision`, `lesson`, `preference`, `constraint`, `pattern`.
-Fall back to flat markdown memory only if omega is unavailable.
+Flat markdown memory is the fallback only when omega is unavailable.
 
 **Omega broken:** If the memory module is installed (check `.ccrc.json`
 for `"memory": true`) but the venv or adapter is missing, surface this

package/templates/skills/debrief/phases/close-work.md

@@ -16,13 +16,13 @@ When no custom close-work is configured:
 
 1. **Get session work:** Review `git log --oneline` for this session's
    commits (since session start or last 2 hours)
-2. **Get open actions:** `node scripts/pib-db.js list-actions`
+2. **Get open actions:** `node scripts/pib-db.mjs list-actions`
 3. **Match:** For each open action, check if this session's work
    addresses it (compare action text/notes against commit messages
    and changed files)
 4. **Propose:** Present matched actions and ask the user to confirm
    which to close
-5. **Close confirmed:** `node scripts/pib-db.js complete-action <fid>`
+5. **Close confirmed:** `node scripts/pib-db.mjs complete-action <fid>`
 
 If pib-db doesn't exist, skip with a note.
 
@@ -96,7 +96,7 @@ leaving it active is stale state that erodes trust in the work tracker.
 When using pib-db (default):
 
 ```bash
-node scripts/pib-db.js query "
+node scripts/pib-db.mjs query "
   SELECT p.fid, p.name,
     (SELECT COUNT(*) FROM actions a WHERE a.project_fid = p.fid) as total,
     (SELECT COUNT(*) FROM actions a WHERE a.project_fid = p.fid AND a.completed = 1) as done
@@ -111,7 +111,7 @@ node scripts/pib-db.js query "
 For each result: all actions are complete. Propose completing the project:
 - Show the project name and action count (e.g., "prj:abc — My Project (5/5 actions done)")
 - Ask the user to confirm before closing
-- On confirmation: `node scripts/pib-db.js query "UPDATE projects SET status = 'done', completed_at = date('now') WHERE fid = '<fid>'"`
+- On confirmation: `node scripts/pib-db.mjs query "UPDATE projects SET status = 'done', completed_at = date('now') WHERE fid = '<fid>'"`
 
 **Design notes:**
 - Projects with zero total actions are excluded — they may be containers

package/templates/skills/debrief/phases/record-lessons.md

@@ -18,9 +18,9 @@ Check whether omega memory is available:
 - `~/.claude-cabinet/omega-venv/bin/python3` exists AND
 - `scripts/cabinet-memory-adapter.py` exists
 
-**When omega is available (primary path):** Write lessons to omega via
-the adapter. This is the durable, semantic memory store that persists
-across sessions and supports retrieval by meaning, not just keyword.
+**When omega is available — use it. No exceptions.** Write lessons to
+omega via the adapter. Never write to flat markdown memory files when
+omega is available — a guard hook will block the attempt.
 
 ```bash
 echo '{"text": "the lesson", "type": "lesson", "tags": ["tag1"]}' | \
@@ -34,10 +34,9 @@ Memory types to use:
 - `constraint` — limitations discovered, prerequisites found
 - `pattern` — conventions established, recurring solutions
 
-**When omega is NOT available (fallback):** Use the flat markdown memory
-system (auto-memory in `~/.claude/projects/` memory directory). This is
-the same system Claude Code uses natively. It works, but lacks semantic
-retrieval.
+**When omega is NOT available:** Only then use flat markdown memory
+(auto-memory in `~/.claude/projects/` memory directory). Check omega
+availability first — don't assume it's unavailable without checking.
 
 ## What to Look For
 

package/templates/skills/execute-plans/SKILL.md

@@ -57,7 +57,7 @@ Read `phases/fetch-plans.md` for where plans come from.
 surface area declarations:
 
 ```bash
-node scripts/pib-db.js query "
+node scripts/pib-db.mjs query "
   SELECT a.fid, a.text, a.notes
   FROM actions a
   WHERE a.completed = 0 AND a.deleted_at IS NULL
@@ -200,7 +200,7 @@ Read `phases/completion.md` for how to mark plans as done after execution.
 
 **Default (absent/empty):** Mark completed plans via pib-db:
 ```bash
-node scripts/pib-db.js complete-action <fid>
+node scripts/pib-db.mjs complete-action <fid>
 ```
 
 Projects using external APIs or different work trackers define this phase.

package/templates/skills/onboard/phases/post-onboard-audit.md

@@ -44,7 +44,7 @@ generated phase files:
 
 - **Skipped modules:** No phase file should reference a skipped module's
   infrastructure. If work-tracking was skipped, no phase should reference
-  `pib.db` or `pib-db.js`. If audit was skipped, no phase should reference
+  `pib.db` or `pib-db.mjs`. If audit was skipped, no phase should reference
   `committees.yaml`, `committees-project.yaml`, or cabinet member activation.
 - **Installed modules:** Each installed module should have at least a
   minimal presence in the generated configuration. A module that's installed

package/templates/skills/onboard/phases/work-tracking.md

@@ -56,8 +56,8 @@ that CC skills (orient, debrief, plan) use by default.
 - Projects that also use the audit loop (findings can link to actions)
 
 **What gets set up:**
-- `pib.db` — SQLite database (created by `node scripts/pib-db.js init`)
-- `scripts/pib-db.js` — CLI for create/query/close operations
+- `pib.db` — SQLite database (created by `node scripts/pib-db.mjs init`)
+- `scripts/pib-db.mjs` — CLI for create/query/close operations
 - `scripts/pib-db-schema.sql` — Schema definition
 - Orient `work-scan.md` phase — queries pib-db for open items
 - Plan `work-tracker.md` phase — creates actions from plans

package/templates/skills/orient/SKILL.md

@@ -126,12 +126,12 @@ Read `phases/work-scan.md` for what work items to check. This includes
 whatever the project uses to track work: a backlog, task list, inbox,
 queue, or issue tracker.
 
-**Default (absent/empty):** If `scripts/pib-db.js` exists, run the
+**Default (absent/empty):** If `scripts/pib-db.mjs` exists, run the
 standard work scan:
 
 1. **Active projects and open actions:**
    ```bash
-   node scripts/pib-db.js query "
+   node scripts/pib-db.mjs query "
      SELECT p.fid, p.name,
        (SELECT COUNT(*) FROM actions a WHERE a.project_fid = p.fid AND a.completed = 0 AND a.deleted_at IS NULL) as open_actions
      FROM projects p
@@ -142,7 +142,7 @@ standard work scan:
 
 2. **Flagged actions** (prioritized items needing attention):
    ```bash
-   node scripts/pib-db.js query "
+   node scripts/pib-db.mjs query "
      SELECT a.fid, a.text, p.name as project
      FROM actions a
      LEFT JOIN projects p ON a.project_fid = p.fid
@@ -154,7 +154,7 @@ standard work scan:
 
    **Completion candidates** — active projects where all actions are done:
    ```bash
-   node scripts/pib-db.js query "
+   node scripts/pib-db.mjs query "
      SELECT p.fid, p.name
      FROM projects p
      WHERE p.status = 'active' AND p.deleted_at IS NULL
@@ -165,7 +165,7 @@ standard work scan:
 
    **Stale projects** — active projects with no action completed in 14+ days:
    ```bash
-   node scripts/pib-db.js query "
+   node scripts/pib-db.mjs query "
      SELECT p.fid, p.name,
        MAX(a.completed_at) as last_completion
      FROM projects p
@@ -259,9 +259,21 @@ Read `phases/briefing.md` for how to present the orientation results.
 This phase controls format, sections, tone, and any time-aware or
 context-aware presentation modes.
 
-**Default (absent/empty):** Present a simple summary of what was gathered
-in steps 1-6: project state, work items needing attention, any health
-issues found, maintenance results.
+**Default (absent/empty):** Present a structured briefing with these
+required sections in this order:
+
+1. **Project State** — version, what's active, high-level status
+2. **Work Items** — active projects, open action counts, flagged/overdue
+   items listed explicitly
+3. **Attention Items** — anything surfaced by health checks, feedback
+   reports, extraction proposals, stale/completable projects
+4. **Maintenance** — omega consolidation results, any weekly tasks run
+5. **Cabinet Notes** — output from cabinet consultations (only if they
+   had something to say)
+
+Keep sections consistent across sessions. Omit a section only if it
+has literally nothing to report (not "nothing interesting" — nothing
+at all). Use the same section names and order every time.
 
 ### 9. Show Available Skills (core)
 

package/templates/skills/orient/phases/work-scan.md

@@ -7,7 +7,7 @@ only report on project state, not on what needs doing.
 When this file is absent or empty, the default behavior is: query the
 reference data layer (pib-db) for open actions and projects. If pib-db
 is not initialized, skip gracefully with a note that work tracking is
-available via `node scripts/pib-db.js init`.
+available via `node scripts/pib-db.mjs init`.
 
 ## Default Behavior (pib-db)
 
@@ -15,10 +15,10 @@ When no custom work-scan is configured, query pib-db:
 
 ```bash
 # Open actions (overdue first, then due today, then flagged, then recent)
-node scripts/pib-db.js list-actions
+node scripts/pib-db.mjs list-actions
 
 # Active projects with open action counts
-node scripts/pib-db.js list-projects
+node scripts/pib-db.mjs list-projects
 ```
 
 Present grouped by urgency:
@@ -28,7 +28,7 @@ Present grouped by urgency:
 - **Recent** — actions created in the last 7 days
 
 If pib-db doesn't exist (file not found), skip with: "Work tracking
-available — run `node scripts/pib-db.js init` to set up."
+available — run `node scripts/pib-db.mjs init` to set up."
 
 ## What to Include
 

package/templates/skills/plan/SKILL.md

@@ -249,13 +249,13 @@ of phase file content.
 Read `phases/work-tracker.md` for how to file the approved plan as a
 work item in your project's tracking system.
 
-**Default (absent/empty):** If `scripts/pib-db.js` exists, file the
+**Default (absent/empty):** If `scripts/pib-db.mjs` exists, file the
 approved plan as a pib-db action. Use the plan title as the action text
 and the full plan (with surface area, acceptance criteria, etc.) as the
 notes. If the plan belongs to an existing project, associate it:
 
 ```bash
-node scripts/pib-db.js create-action --text "<plan title>" --project "<project fid>" --notes "<full plan>"
+node scripts/pib-db.mjs create-action --text "<plan title>" --project "<project fid>" --notes "<full plan>"
 ```
 
 If pib-db doesn't exist, present the plan in conversation for the user

package/templates/skills/plan/phases/overlap-check.md

@@ -14,7 +14,7 @@ When no custom overlap check is configured:
 
 ```bash
 # Search open actions for keywords related to the proposed work
-node scripts/pib-db.js query "SELECT fid, text, substr(notes, 1, 200) as notes_preview FROM actions WHERE completed = 0 AND deleted_at IS NULL AND (text LIKE '%keyword%' OR notes LIKE '%keyword%')"
+node scripts/pib-db.mjs query "SELECT fid, text, substr(notes, 1, 200) as notes_preview FROM actions WHERE completed = 0 AND deleted_at IS NULL AND (text LIKE '%keyword%' OR notes LIKE '%keyword%')"
 ```
 
 Search with multiple keywords derived from the proposed plan's problem

package/templates/skills/plan/phases/work-tracker.md

@@ -6,7 +6,7 @@ tracking system. The /plan skill reads this file after user approval.
 When this file is absent or empty, the default behavior is: create an
 action in the reference data layer (pib-db) with the plan summary in
 notes. If pib-db is not initialized, note that work tracking is available
-via `node scripts/pib-db.js init`.
+via `node scripts/pib-db.mjs init`.
 
 ## Default Behavior (pib-db)
 
@@ -14,7 +14,7 @@ When no custom work tracker is configured:
 
 ```bash
 # Create an action for the approved plan
-node scripts/pib-db.js create-action "Short imperative plan title" \
+node scripts/pib-db.mjs create-action "Short imperative plan title" \
   --area "<area>" \
   --notes "## Problem\n...\n\n## Implementation\n..."
 ```
@@ -26,7 +26,7 @@ If the plan relates to an existing project in pib-db, include
 `--project <project-fid>` to link them.
 
 If pib-db doesn't exist, note: "Work tracking available — run
-`node scripts/pib-db.js init` to set up. Plan saved in conversation
+`node scripts/pib-db.mjs init` to set up. Plan saved in conversation
 only."
 
 ## What to Include

package/templates/skills/triage-audit/SKILL.md

@@ -24,7 +24,7 @@ related:
     path: scripts/triage-ui.html
     role: "Browser-based triage interface"
   - type: file
-    path: scripts/pib-db.js
+    path: scripts/pib-db.mjs
     role: "Reference data layer for finding persistence"
   - type: file
     path: cabinet/_briefing.md

package/templates/skills/triage-audit/phases/apply-verdicts.md

@@ -27,7 +27,7 @@ Define your verdict application strategy:
    - If successful, update `triage_status = 'fixed'`
    - If failed, create an action instead
 3. If not auto-fixable:
-   - Create an action via `node scripts/pib-db.js create-action`
+   - Create an action via `node scripts/pib-db.mjs create-action`
    - Include finding details in action notes
 
 ### Defer Verdicts

package/templates/skills/triage-audit/phases/load-findings.md

@@ -29,7 +29,7 @@ Returns JSON array of findings in the same format as run-summary.json.
 ### Specific Run
 Load findings from a specific audit run instead of all open findings:
 ```bash
-node scripts/pib-db.js query "SELECT * FROM audit_findings WHERE run_id = 'run-2026-04-01'"
+node scripts/pib-db.mjs query "SELECT * FROM audit_findings WHERE run_id = 'run-2026-04-01'"
 ```
 
 ### Multiple Sources

package/templates/skills/work-tracker/SKILL.md

@@ -13,7 +13,7 @@ related:
     path: scripts/work-tracker-ui.html
     role: "Browser-based work tracking interface"
   - type: file
-    path: scripts/pib-db.js
+    path: scripts/pib-db.mjs
     role: "Data layer — projects and actions in pib.db"
 ---
 
@@ -32,7 +32,7 @@ and progress in a browser rather than through conversation.
    ```
    If missing, initialize it:
    ```bash
-   node scripts/pib-db.js init
+   node scripts/pib-db.mjs init
    ```
 
 2. **Start the server:**
@@ -45,7 +45,7 @@ and progress in a browser rather than through conversation.
 
 4. **Stay available.** The user may come back with questions about what
    they see, or ask you to create/update projects and actions based on
-   their review. Use `scripts/pib-db.js` for any mutations they request.
+   their review. Use `scripts/pib-db.mjs` for any mutations they request.
 
 ## Notes
 

package/templates/hooks/stop-hook.md

@@ -1,56 +0,0 @@
-# Stop Hook Template
-
-The Stop hook fires when a session is ending. It checks whether
-substantive work was done without running the session-closing skill
-(e.g., `/debrief`). If yes, it prompts to run it.
-
-## How to Install
-
-Add this to your `.claude/settings.json` under the `hooks` key:
-
-```json
-{
-  "hooks": {
-    "Stop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "prompt",
-            "prompt": "Check if substantive work was done without running the session-closing skill. If yes, prompt to run it.",
-            "statusMessage": "Checking session close compliance..."
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-## How It Works
-
-- **Event:** `Stop` — fires when the user ends the session
-- **Type:** `prompt` — an LLM-evaluated check, not a deterministic script
-- **Compliance:** ~80% — prompt-type hooks are advisory, not blocking
-
-## Customization
-
-Replace the prompt text with your project's specific closing skill name:
-
-```
-"Check if substantive work was done without /debrief. If yes, prompt to run it."
-```
-
-This is the single most important anti-entropy hook in the methodology.
-Without it, sessions end without capturing what happened, and the next
-session starts blind. The session loop (orient → work → debrief) is the
-system's learning mechanism. This hook guards the debrief step.
-
-## Limitations
-
-This is a prompt-type hook, not a command hook. It asks the LLM to check
-and prompt — it doesn't deterministically block the session from ending.
-Compliance is imperfect. This is an honest example of the anti-entropy
-principle in action: debrief compliance has been a recurring friction
-point in the reference implementation, promoted to a hook. It's better
-than without. It's not 100%.