@nusoft/nuos-build-catalogue 0.30.1 → 0.30.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nusoft/nuos-build-catalogue",
-  "version": "0.30.1",
+  "version": "0.30.3",
   "description": "NuOS build-catalogue tooling: semantic search (WU 110) + migration runner that lifts markdown artefacts into JSON-backed workflow records (WU 111, Phase G).",
   "type": "module",
   "bin": {

package/templates/hooks/install-hooks.sh

@@ -15,6 +15,64 @@
 
 set -euo pipefail
 
+# ---- Ensure nuos-catalogue CLI is installed --------------------------------
+#
+# The CLI is a global npm tool with no presence in any package.json — it
+# disappears silently when global packages are cleared. Install it here so
+# the build memory system is always ready after a post-clone setup run.
+
+if ! command -v nuos-catalogue &>/dev/null; then
+  echo "▶ nuos-catalogue not found — installing @nusoft/nuos-build-catalogue globally..."
+  npm install -g @nusoft/nuos-build-catalogue
+  echo "✓ nuos-catalogue installed"
+else
+  echo "✓ nuos-catalogue present ($(nuos-catalogue --version 2>/dev/null | head -1 || echo 'version unknown'))"
+fi
+echo
+
+# ---- Patch ~/.claude/settings.json with the Playwright singleton hook ------
+#
+# Each VS Code Claude Code window spawns its own playwright-mcp process. They
+# all share one Chrome profile, and Chrome's singleton lock means only the first
+# one to open Chrome succeeds — every later session gets "browser already in use".
+# This PreToolUse hook kills the locked Chrome before each browser_navigate so
+# the current session always gets a clean launch.
+
+CLAUDE_SETTINGS="$HOME/.claude/settings.json"
+PLAYWRIGHT_HOOK_MARKER="mcp__plugin_playwright_playwright__browser_navigate"
+
+if [[ -f "$CLAUDE_SETTINGS" ]] && ! grep -q "$PLAYWRIGHT_HOOK_MARKER" "$CLAUDE_SETTINGS"; then
+  echo "▶ Patching ~/.claude/settings.json with Playwright singleton hook..."
+  node -e "
+    const fs = require('fs');
+    const path = '$CLAUDE_SETTINGS';
+    const settings = JSON.parse(fs.readFileSync(path, 'utf8'));
+    settings.hooks = settings.hooks || {};
+    settings.hooks.PreToolUse = settings.hooks.PreToolUse || [];
+    const alreadySet = settings.hooks.PreToolUse.some(h => h.matcher === '$PLAYWRIGHT_HOOK_MARKER');
+    if (!alreadySet) {
+      settings.hooks.PreToolUse.push({
+        matcher: '$PLAYWRIGHT_HOOK_MARKER',
+        hooks: [{
+          type: 'command',
+          command: \"pkill -f 'user-data-dir.*mcp-chrome' 2>/dev/null; sleep 0.5; exit 0\",
+          timeout: 5,
+          statusMessage: 'Clearing stale Playwright browser...'
+        }]
+      });
+      fs.writeFileSync(path, JSON.stringify(settings, null, 2) + '\n');
+      console.log('✓ Playwright singleton hook added');
+    } else {
+      console.log('✓ Playwright singleton hook already present');
+    }
+  "
+elif [[ ! -f "$CLAUDE_SETTINGS" ]]; then
+  echo "⚠ ~/.claude/settings.json not found — skipping Playwright hook patch (Claude Code not installed?)"
+else
+  echo "✓ Playwright singleton hook already present in ~/.claude/settings.json"
+fi
+echo
+
 REPO_ROOT="$(git rev-parse --show-toplevel)"
 SOURCE="$REPO_ROOT/scripts/hooks"
 TARGET="$REPO_ROOT/.git/hooks"

package/templates/protocols/start-of-session.md

@@ -34,7 +34,7 @@ Read `docs/build/STATE.md`. Look at the **Planning progress** section:
 
   If yes, **switch to the `plan-orientation` protocol** (invoke `/plan-orientation` if available; otherwise read `.claude/commands/plan-orientation.md` and follow it). If no, point them at `docs/build/WELCOME.md` and `docs/build/GLOSSARY.md` so they can read about the catalogue first, then wait.
 
-- If **any planning phase is in progress or marked `🟡 next`**, route to the appropriate protocol. Read the most recent session log's "Resume hint" to know exactly where to pick up within the phase.
+- If **any planning phase is in progress or marked `🟡 next`**, route to the appropriate protocol. Read STATE.md's `## Last session resume` section to know exactly where to pick up within the phase. Do not open the session log file.
 
   | Phase | Protocol |
   |---|---|
@@ -50,12 +50,13 @@ Read `docs/build/STATE.md`. Look at the **Planning progress** section:
 
 ## Step 2 — Read where the project is
 
-Read these files in order:
+Read only what is necessary — no more:
 
-1. `docs/build/STATE.md` in full — the always-current snapshot
-2. The most recent file in `docs/build/sessions/` — what happened last session
-3. The active work unit named in STATE.md, including its notes section at the bottom
-4. Skim `docs/build/open-questions/_index.md` and `docs/build/risks/_index.md` for anything blocking the active work unit
+1. `docs/build/STATE.md` in full — the always-current snapshot. **This is the primary source.** The `## Last session resume` section contains the pickup point from the previous session; you do not need to open any session log file.
+2. The active work unit named in STATE.md — read the **header** (status, persona, last updated), `## What's done when this ships`, and only the **most recent dated entry** in `## Notes / log`. Do not read earlier note entries; they are history, not orientation.
+3. **Only if** STATE.md's `## Open questions blocking progress` section lists actual entries (not "None"): read `docs/build/open-questions/_index.md` and `docs/build/risks/_index.md`.
+
+Do not open session log files. They are archives. The resume block in STATE.md is authoritative.
 
 ## Step 3 — Tell the operator where they are
 
@@ -83,4 +84,4 @@ If STATE.md still has placeholder text, references a work unit that doesn't exis
 
 - **Don't make decisions in conversation without filing them.** If the operator says "let's do X" and X is a real architectural choice, file it as a decision in `docs/build/decisions/` before moving on. Decisions made in conversation that aren't filed produce drift — and drift is the failure mode that makes the catalogue worthless.
 - **Don't start work that needs an open question resolved.** Surface the blocker; ask the operator how they want to proceed.
-- **Don't read past your tasks.** STATE, last session log, active work unit, blockers — then stop. Surface those, wait for direction.
+- **Don't read past your tasks.** STATE.md and the scoped active work unit — then stop. Do not open session log files; the resume block in STATE.md is sufficient. Surface what you know, wait for direction.

package/templates/starter-kit/docs/build/STATE.md

@@ -30,6 +30,12 @@ Nothing yet — this catalogue was just adopted on {{TODAY}}.
 
 Run `/start-of-session` to begin. The AI will read this file and walk you through Phase A of planning.
 
+## Last session resume
+
+No sessions have run yet.
+
+_end-of-session writes here: what the last session accomplished (1–2 sentences), exactly where to pick up, and any mid-task context needed. start-of-session reads this instead of opening the session log file._
+
 ## Open questions blocking progress
 
 None currently filed. Filed questions live in [`open-questions/_index.md`](open-questions/_index.md).
@@ -56,6 +62,7 @@ None currently filed. Filed risks live in [`risks/_index.md`](risks/_index.md).
 - **What is currently in flight** describes ongoing work; updated when work changes shape
 - **What just shipped** notes the most recent completion(s)
 - **What is next** points at the immediate concrete action
+- **Last session resume** is the pickup block written by end-of-session — start-of-session reads this instead of opening a session log file
 - Below: open questions, risks, decisions, and active work units — pulled from their respective registers for quick scanning
 
 This file is the project's executive summary. The detail lives in the register files; this is the one-screen view that says where the project is.