@nusoft/nuos-build-catalogue 0.17.1 → 0.19.1

package/dist/setup/types.d.ts

@@ -0,0 +1,99 @@
+/**
+ * Shared types for the LLM-setup phase of `init` (WU 135).
+ *
+ * The setup phase runs after the scaffold and is responsible for
+ * detecting Ollama, offering to install it where reliable, and pulling
+ * the default embedding model (`qwen3-embedding:0.6b`, ~600MB) with a
+ * live progress bar.
+ *
+ * @module setup/types
+ */
+/** Node `process.platform` narrowed to the cases we handle. */
+export type Platform = 'darwin' | 'linux' | 'win32' | 'other';
+/** Result of probing for the Ollama CLI binary on PATH. */
+export interface OllamaCliProbe {
+    found: boolean;
+    /** Resolved path when `found`. */
+    path?: string;
+}
+/** Result of probing the Ollama HTTP API. */
+export interface OllamaApiProbe {
+    reachable: boolean;
+    /** Host the probe used (e.g. "http://localhost:11434"). */
+    host: string;
+    /** Error message when `!reachable`. */
+    error?: string;
+}
+/** Result of querying the local model list. */
+export interface ModelProbe {
+    present: boolean;
+    /** Model identifier we probed for (e.g. "qwen3-embedding:0.6b"). */
+    model: string;
+}
+/**
+ * One event from the Ollama `/api/pull` NDJSON stream. The status
+ * strings come straight from Ollama; we treat them as opaque except for
+ * the distinguished cases used to render the progress bar.
+ *
+ * Known status values observed in practice:
+ *   - "pulling manifest"
+ *   - "downloading"          (carries digest + total + completed)
+ *   - "verifying sha256 digest"
+ *   - "writing manifest"
+ *   - "removing any unused layers"
+ *   - "success"
+ *
+ * An `error` field is set instead of `status` on failure.
+ */
+export interface PullEvent {
+    status?: string;
+    digest?: string;
+    total?: number;
+    completed?: number;
+    error?: string;
+}
+/**
+ * Outcome of the LLM-setup phase. Returned to the caller (init or the
+ * standalone `setup-llm` command) so the surrounding UX can render an
+ * appropriate summary line.
+ */
+export type LlmSetupResult = {
+    kind: 'already_ready';
+} | {
+    kind: 'installed_and_pulled';
+} | {
+    kind: 'pulled_only';
+} | {
+    kind: 'install_offered_declined';
+} | {
+    kind: 'install_failed';
+    error: string;
+} | {
+    kind: 'ollama_installed_but_not_running';
+} | {
+    kind: 'pull_failed';
+    error: string;
+} | {
+    kind: 'skipped';
+    reason: string;
+};
+/**
+ * Per-platform install offer the CLI can present to the user. The
+ * `canAutoInstall` flag is the gate for offering to run the install
+ * command directly — false on Windows (no reliable CLI install path).
+ */
+export interface InstallOffer {
+    platform: Platform;
+    /** The shell command the offer would run (empty string when !canAutoInstall). */
+    primaryCommand: string;
+    /** Plain-English description of the primary path. */
+    primaryDescription: string;
+    /** Download page URL — always present as the safe fallback. */
+    fallbackUrl: string;
+    /** Whether we have a reliable CLI install path to offer running. */
+    canAutoInstall: boolean;
+    /** Whether the primary command needs sudo. Used to phrase the prompt. */
+    requiresElevation: boolean;
+}
+/** Narrow Node's process.platform string to our Platform union. */
+export declare function narrowPlatform(p: NodeJS.Platform): Platform;

package/dist/setup/types.js

@@ -0,0 +1,20 @@
+/**
+ * Shared types for the LLM-setup phase of `init` (WU 135).
+ *
+ * The setup phase runs after the scaffold and is responsible for
+ * detecting Ollama, offering to install it where reliable, and pulling
+ * the default embedding model (`qwen3-embedding:0.6b`, ~600MB) with a
+ * live progress bar.
+ *
+ * @module setup/types
+ */
+/** Narrow Node's process.platform string to our Platform union. */
+export function narrowPlatform(p) {
+    if (p === 'darwin')
+        return 'darwin';
+    if (p === 'linux')
+        return 'linux';
+    if (p === 'win32')
+        return 'win32';
+    return 'other';
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nusoft/nuos-build-catalogue",
-  "version": "0.17.1",
+  "version": "0.19.1",
   "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": {
@@ -19,7 +19,7 @@
     "build": "rm -rf dist && tsc && chmod +x dist/cli.js",
     "prepublishOnly": "npm run build",
     "verify-storage": "tsx scripts/verify-persistence.ts",
-    "test": "tsx --test tests/chunk.test.ts tests/metadata.test.ts tests/crawl.test.ts tests/migrate.test.ts tests/commands-read.test.ts tests/regenerate.test.ts tests/commands-write.test.ts tests/ac-parse.test.ts tests/create.test.ts tests/init.test.ts tests/wu-111-soak-findings.test.ts tests/plan.test.ts tests/swarm.test.ts",
+    "test": "tsx --test tests/chunk.test.ts tests/metadata.test.ts tests/crawl.test.ts tests/migrate.test.ts tests/commands-read.test.ts tests/regenerate.test.ts tests/commands-write.test.ts tests/ac-parse.test.ts tests/create.test.ts tests/init.test.ts tests/wu-111-soak-findings.test.ts tests/plan.test.ts tests/swarm.test.ts tests/setup-progress-bar.test.ts tests/setup-ollama-pull.test.ts tests/setup-run-llm-setup.test.ts",
     "typecheck": "tsc --noEmit",
     "index": "tsx src/cli.ts index",
     "search": "tsx src/cli.ts search"

package/scripts/hooks/post-commit

@@ -0,0 +1,96 @@
+#!/usr/bin/env bash
+#
+# NuOS catalogue post-commit hook — auto-refresh the semantic-search index
+# after every commit that touched docs/build/**.
+#
+# Why this hook:
+#   `nuos-catalogue search` only finds what's in the NuVector index. The
+#   index is hash-based and incremental, but it doesn't update itself —
+#   you have to run `nuos-catalogue index` after meaningful changes for
+#   new content to be searchable. Running it manually is too easy to
+#   forget; the discipline argument that gave us the pre-commit hook
+#   (index-drift, accepted-decision immutability) applies equally here.
+#
+# Behaviour:
+#   - Skip if the just-landed commit did NOT touch docs/build/** (most
+#     code commits don't need a reindex)
+#   - Skip if `nuos-catalogue` isn't resolvable (the CLI may not be
+#     installed yet on a fresh clone; this hook should never block)
+#   - Otherwise: run the index in the BACKGROUND so the user's terminal
+#     isn't held while we embed. All output goes to .nuos-enforcement.log.
+#
+#   The hook respects two env vars:
+#     NUOS_CATALOGUE_INDEX_DIR   default: <repo>/.nuos-catalogue
+#     NUOS_CATALOGUE_OLLAMA_MODEL  passed through to the CLI
+#
+# This hook never blocks. If indexing fails (Ollama not running, model
+# not pulled, dimension mismatch with existing index), the error goes
+# to the log and the user can investigate. The commit itself already
+# landed by the time post-commit fires.
+
+set -uo pipefail
+
+REPO_ROOT="$(git rev-parse --show-toplevel)"
+LOG="$REPO_ROOT/.nuos-enforcement.log"
+
+dim()    { printf '\033[2m%s\033[0m\n' "$*"; }
+yellow() { printf '\033[33m%s\033[0m\n' "$*"; }
+
+# ---- Skip-paths --------------------------------------------------------
+
+# Skip if this project doesn't have a catalogue at all.
+if [[ ! -d "$REPO_ROOT/docs/build" ]]; then
+  exit 0
+fi
+
+# Skip if the just-landed commit didn't touch docs/build/**.
+if ! git diff-tree --no-commit-id --name-only -r HEAD 2>/dev/null | grep -q '^docs/build/'; then
+  exit 0
+fi
+
+# Resolve the CLI: prefer globally-installed `nuos-catalogue`; fall back
+# to `npx --yes` which fetches from npm on demand.
+INDEX_CMD=""
+if command -v nuos-catalogue >/dev/null 2>&1; then
+  INDEX_CMD="nuos-catalogue"
+elif command -v npx >/dev/null 2>&1; then
+  INDEX_CMD="npx --yes @nusoft/nuos-build-catalogue"
+else
+  yellow "[nuos:post-commit] neither nuos-catalogue nor npx found; skipping index refresh"
+  printf '%s | post-commit-skip | no CLI available\n' "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" >> "$LOG"
+  exit 0
+fi
+
+# ---- Background index refresh ------------------------------------------
+
+# Default the index dir to project-local if the user hasn't set one.
+: "${NUOS_CATALOGUE_INDEX_DIR:=$REPO_ROOT/.nuos-catalogue}"
+export NUOS_CATALOGUE_INDEX_DIR
+
+# Detach from the terminal so the post-commit returns immediately. All
+# output (stdout + stderr) goes to the enforcement log so the user can
+# tail it if they want to see progress.
+(
+  start=$(date +%s)
+  printf '%s | post-commit-index | start (model=%s, dir=%s)\n' \
+    "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" \
+    "${NUOS_CATALOGUE_OLLAMA_MODEL:-default}" \
+    "$NUOS_CATALOGUE_INDEX_DIR" \
+    >> "$LOG"
+
+  if cd "$REPO_ROOT" && $INDEX_CMD index >> "$LOG" 2>&1; then
+    end=$(date +%s)
+    printf '%s | post-commit-index | done in %ss\n' \
+      "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" \
+      $((end - start)) \
+      >> "$LOG"
+  else
+    printf '%s | post-commit-index | FAILED (see lines above in %s)\n' \
+      "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" \
+      "$(basename "$LOG")" \
+      >> "$LOG"
+  fi
+) </dev/null >/dev/null 2>&1 &
+disown 2>/dev/null || true
+
+dim "[nuos:post-commit] index refresh started in background — see .nuos-enforcement.log"

package/scripts/hooks/pre-commit

@@ -0,0 +1,162 @@
+#!/usr/bin/env bash
+#
+# NuOS catalogue pre-commit hook (WU 111 enforcement phase).
+#
+# Catches drift before commit. After WU 111's Phase J ship, the
+# accepted-decision rule has flipped from warning → block (per the
+# pack's narrower-than-originally-planned enforcement scope, recorded
+# in WU 111's "Forward-compatibility commitments" section). Other
+# rules described in WU 128's original aggressive list are NOT shipping
+# — distinguishing tool-written from human-written content was deemed
+# overengineering for a planning-artefact catalogue.
+#
+# Active rules:
+#   1. index-drift detection — every WU/decision/open-question/risk file
+#      must have a matching row in its _index.md (and vice versa)
+#   2. active-decision modification block — modifying a committed
+#      `accepted` decision file is BLOCKED (not just warned). The
+#      discipline is to write a superseding D-NNN+1 and link forward.
+#      To deliberately fix a typo or link in an accepted decision,
+#      use `git commit --no-verify` (CLAUDE.md prohibits this for
+#      substantive changes; reserve it for typo-only fixes).
+#
+# Sentinel-protected sections (e.g. STATE.md's `nuos:sentinel`) remain
+# protected via the existing `.claude/hooks/check-catalogue-write.sh`
+# Claude Code hook. That rule continues unchanged at WU 111 ship.
+#
+# Bypass: this hook respects --no-verify like any other. The CLAUDE.md
+# policy explicitly prohibits --no-verify use for substantive changes;
+# the technical block fires at the CI server-side check (a future WU).
+
+set -uo pipefail
+
+REPO_ROOT="$(git rev-parse --show-toplevel)"
+ENFORCEMENT_LOG="$REPO_ROOT/.nuos-enforcement.log"
+EXIT_CODE=0
+
+red()    { printf '\033[31m%s\033[0m\n' "$*"; }
+yellow() { printf '\033[33m%s\033[0m\n' "$*"; }
+green()  { printf '\033[32m%s\033[0m\n' "$*"; }
+dim()    { printf '\033[2m%s\033[0m\n' "$*"; }
+
+log_event() {
+  printf '%s | %s | %s\n' "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" "$1" "$2" >> "$ENFORCEMENT_LOG"
+}
+
+# ---------- Generic index-drift checker ---------------------------------
+#
+# Args:
+#   $1 — kind label (for messages)
+#   $2 — directory (relative to repo root)
+#   $3 — _index.md path (relative to repo root)
+#   $4 — filename regex (matches IDs the directory contains)
+#   $5 — index-row ID regex (a Perl-compatible regex that anchors on the
+#        leftmost column of an index table row)
+#
+# The two regexes must extract the SAME set of IDs (e.g. "001", "030g",
+# "D042") so set comparison works.
+
+check_index_drift() {
+  local kind="$1" dir="$2" index="$3" file_regex="$4" row_regex="$5"
+
+  if [[ ! -d "$REPO_ROOT/$dir" ]]; then return 0; fi
+  if [[ ! -f "$REPO_ROOT/$index" ]]; then return 0; fi
+
+  # IDs extracted from filenames in the directory (top-level + one subdir
+  # like done/, resolved/, superseded/)
+  local ids_in_tree
+  ids_in_tree=$(cd "$REPO_ROOT/$dir" && {
+    find . -maxdepth 2 -type f -name "*.md" \
+      -not -name "_index.md" \
+      -not -name "*-template.md" 2>/dev/null \
+      | sed -nE "$file_regex" \
+      | sort -u
+  })
+
+  # IDs extracted from leftmost column of table rows in the index
+  local ids_in_index
+  ids_in_index=$(sed -nE "$row_regex" "$REPO_ROOT/$index" | sort -u)
+
+  local missing_from_index
+  missing_from_index=$(comm -23 <(printf '%s\n' "$ids_in_tree") <(printf '%s\n' "$ids_in_index"))
+
+  if [[ -n "$missing_from_index" ]]; then
+    red "✖ index-drift ($kind): on disk but missing from $index:"
+    while IFS= read -r id; do echo "    — $id"; done <<< "$missing_from_index"
+    log_event "index-drift" "$kind missing from index: $(echo "$missing_from_index" | tr '\n' ',')"
+    EXIT_CODE=1
+  fi
+}
+
+dim "[nuos:pre-commit] index-drift check"
+
+# Note: BSD sed (macOS default) is fussy about `|` as both delimiter and
+# regex content. Using `#` as the s/// delimiter sidesteps the collision.
+
+# Work units: filenames are NNN-slug.md or NNNa-slug.md (with optional letter).
+# Index rows are `| NNN |` or `| NNNa |` in the leftmost column.
+check_index_drift \
+  "work-units" \
+  "docs/build/work-units" \
+  "docs/build/work-units/_index.md" \
+  's#^\./(done/)?([0-9]{3}[a-z]?)-[^/]*\.md$#\2#p' \
+  's#^\| ([0-9]{3}[a-z]?) \|.*$#\1#p'
+
+# Decisions: filenames are DNNN-slug.md.
+# Index rows: `| DNNN |` or `| [DNNN](...) |`.
+check_index_drift \
+  "decisions" \
+  "docs/build/decisions" \
+  "docs/build/decisions/_index.md" \
+  's#^\./(done/|superseded/)?(D[0-9]{3})-[^/]*\.md$#\2#p' \
+  's#^\| \[?(D[0-9]{3}).*$#\1#p'
+
+# Open questions: filenames are QNNN-slug.md.
+check_index_drift \
+  "open-questions" \
+  "docs/build/open-questions" \
+  "docs/build/open-questions/_index.md" \
+  's#^\./(resolved/)?(Q[0-9]{3})-[^/]*\.md$#\2#p' \
+  's#^\| \[?(Q[0-9]{3}).*$#\1#p'
+
+# Risks: per current convention, individual risk files are inline in
+# risks/_index.md (no per-risk .md files yet). Skip the check entirely
+# until that pattern changes.
+if compgen -G "$REPO_ROOT/docs/build/risks/R[0-9][0-9][0-9]-*.md" > /dev/null; then
+  check_index_drift \
+    "risks" \
+    "docs/build/risks" \
+    "docs/build/risks/_index.md" \
+    's#^\./(R[0-9]{3})-[^/]*\.md$#\1#p' \
+    's#^\| \[?(R[0-9]{3}).*$#\1#p'
+fi
+
+# ---------- Rule 2: active-decision modification block (WU 111 ship) ---
+
+dim "[nuos:pre-commit] active-decision modification check"
+modified_decisions=$(git diff --cached --name-only --diff-filter=M \
+  | grep -E '^docs/build/decisions/D[0-9]+.*\.md$' \
+  | grep -v '/superseded/' \
+  || true)
+
+if [[ -n "$modified_decisions" ]]; then
+  red "✖ active-decision modification — BLOCKED (WU 111 enforcement):"
+  while IFS= read -r f; do echo "    — $f"; done <<< "$modified_decisions"
+  red "  Decisions are immutable once accepted. The discipline is to write a"
+  red "  superseding D-NNN+1 and link forward. Use:"
+  red "    nuos-catalogue decision supersede <target> --by=<new-D> --reason=\"...\""
+  red ""
+  red "  If this edit is a non-substantive typo fix or link cleanup that does"
+  red "  not change the decision's meaning, you may bypass this block with"
+  red "  --no-verify. CLAUDE.md prohibits --no-verify for substantive changes."
+  log_event "active-decision-block" "$(echo "$modified_decisions" | tr '\n' ',')"
+  EXIT_CODE=1
+fi
+
+# ---------- Result ------------------------------------------------------
+
+if [[ $EXIT_CODE -eq 0 ]]; then
+  green "[nuos:pre-commit] all rules pass (WU 111 enforcement)"
+  log_event "pre-commit-pass" "$(git diff --cached --name-only | wc -l | tr -d ' ') files"
+fi
+exit $EXIT_CODE

package/scripts/install-hooks.sh

@@ -0,0 +1,44 @@
+#!/usr/bin/env bash
+#
+# Install the catalogue's git hooks into .git/hooks/.
+#
+# Why this script (not husky):
+#   The nuos repo is a markdown catalogue, not an npm package. Adding a
+#   package.json + node_modules just to install hooks would be infrastructure
+#   tax for what is otherwise a doc repo. A small bash installer copies the
+#   hooks from the version-controlled scripts/hooks/ into .git/hooks/.
+#
+# Usage:
+#   bash scripts/install-hooks.sh
+#
+# Re-run any time scripts/hooks/ changes; the installer is idempotent.
+
+set -euo pipefail
+
+REPO_ROOT="$(git rev-parse --show-toplevel)"
+SOURCE="$REPO_ROOT/scripts/hooks"
+TARGET="$REPO_ROOT/.git/hooks"
+
+if [[ ! -d "$SOURCE" ]]; then
+  echo "✖ scripts/hooks/ not found; nothing to install" >&2
+  exit 1
+fi
+
+mkdir -p "$TARGET"
+
+installed=0
+for hook in "$SOURCE"/*; do
+  name="$(basename "$hook")"
+  cp "$hook" "$TARGET/$name"
+  chmod +x "$TARGET/$name"
+  installed=$((installed + 1))
+done
+
+echo "✓ installed $installed hook(s) into .git/hooks/"
+echo
+echo "Active rules (WU 111 enforcement):"
+echo "  • index-drift detection (work-units, decisions, open-questions, risks)"
+echo "  • active-decision modification BLOCK (was warning under WU 128 light-touch)"
+echo
+echo "To verify the install: \`git hook list\` (git ≥2.36) or \`ls .git/hooks/\`"
+echo "To uninstall: \`rm .git/hooks/pre-commit\`"

package/templates/agents/architect.md

@@ -9,6 +9,22 @@ You are the **architect** for a project using the NuOS Build Method catalogue. Y
 
 **You design. You do not implement.** You produce decisions, contract files, architecture files, and the structural outline for work units — never source code.
 
+## Cross-agent memory
+
+Before you start: search for prior relevant design decisions across all past swarm runs.
+
+```bash
+nuos-catalogue memory search --query="<the design problem you're about to solve>" --agent=architect
+nuos-catalogue memory search --query="<the module or contract name>" --limit=5
+```
+
+After you finish: store your key findings so future architects (and the debugger) can find them.
+
+```bash
+nuos-catalogue memory store --value="<what you decided and why>" --wu=<handle> --agent=architect --key="<short label>"
+# Store one entry per load-bearing decision. Include the alternatives you rejected.
+```
+
 ## What you read before you decide
 
 Always start by reading:

package/templates/agents/coder.md

@@ -9,6 +9,21 @@ You are the **coder** for a project using the NuOS Build Method catalogue. Your
 
 You write code. You stay narrow. You do not redesign mid-flight.
 
+## Cross-agent memory
+
+Before you start: search for how similar work was done before (idioms, gotchas, prior solutions).
+
+```bash
+nuos-catalogue memory search --query="<what you're about to implement>" --agent=coder
+nuos-catalogue memory search --query="<the module or pattern name>" --limit=5
+```
+
+After you finish: store patterns that will save the next coder time — particularly anything surprising.
+
+```bash
+nuos-catalogue memory store --value="<what worked and why, or what to avoid>" --wu=<handle> --agent=coder --key="<short label>"
+```
+
 ## What you read before you start
 
 - The work unit you've been assigned (in `docs/build/work-units/`)

package/templates/agents/debugger.md

@@ -9,6 +9,21 @@ You are the **debugger** for a project using the NuOS Build Method catalogue. Yo
 
 You investigate. You bisect. You read code at the point of failure. **You write only the minimum change required to fix the root cause.** No drive-by refactors.
 
+## Cross-agent memory
+
+Before you investigate: search for prior debugging sessions on similar failures. This is the most valuable search you'll run — root causes recur.
+
+```bash
+nuos-catalogue memory search --query="<the error message or failure symptom>" --agent=debugger
+nuos-catalogue memory search --query="<the module or component name> bug" --limit=5
+```
+
+After you fix: store the root cause and the signal that pointed to it. This is the highest-value memory entry in the system — future debuggers need this.
+
+```bash
+nuos-catalogue memory store --value="<symptom> → root cause: <what was actually wrong> → fix: <what changed>" --wu=<handle> --agent=debugger --key="<short label>"
+```
+
 ## What you read before you investigate
 
 - The work unit where the failure surfaced

package/templates/agents/researcher.md

@@ -9,6 +9,20 @@ You are the **researcher** for a project using the NuOS Build Method catalogue.
 
 You search. You read. You summarise. **You do not write production code, design decisions, or tests.** Your output is findings.
 
+## Cross-agent memory
+
+Before you search the web: check whether this was already looked up. Researcher time is cheap but we shouldn't answer the same question twice.
+
+```bash
+nuos-catalogue memory search --query="<what you're about to look up>" --agent=researcher
+```
+
+After you finish: store your findings so the architect or coder can retrieve them without re-fetching.
+
+```bash
+nuos-catalogue memory store --value="<your findings summary with source URLs>" --wu=<handle> --agent=researcher --key="<library or topic name>"
+```
+
 ## What you typically look up
 
 - Current documentation for libraries and APIs (the canonical source, not blog posts)

package/templates/agents/reviewer.md

@@ -9,6 +9,22 @@ You are the **reviewer** for a project using the NuOS Build Method catalogue. Yo
 
 You read. You report. **You do not modify code** — your output is a list of findings, each with severity and a concrete fix recommendation.
 
+## Cross-agent memory
+
+Before you start: search for prior review findings in related areas — patterns the project has flagged before.
+
+```bash
+nuos-catalogue memory search --query="<what's being reviewed>" --agent=reviewer
+nuos-catalogue memory search --query="design system violations <area>" --limit=5
+```
+
+After you finish: store recurring patterns — things that keep coming up across reviews.
+
+```bash
+nuos-catalogue memory store --value="<the pattern and why it matters>" --wu=<handle> --agent=reviewer --key="<short label>"
+# Only store new patterns, not every individual finding (those live in the work unit notes).
+```
+
 ## What you read before you write the review
 
 - The work unit being reviewed (in `docs/build/work-units/`)

package/templates/agents/tester.md

@@ -9,6 +9,21 @@ You are the **tester** for a project using the NuOS Build Method catalogue. Your
 
 You write tests. You run tests. You report results. **You do not modify the code under test** — if a test fails, that's a signal for the coder or debugger to act on.
 
+## Cross-agent memory
+
+Before you start: search for prior test patterns and known flaky areas.
+
+```bash
+nuos-catalogue memory search --query="<what you're testing>" --agent=tester
+nuos-catalogue memory search --query="test patterns <module name>" --limit=5
+```
+
+After you finish: store what you discovered about testability — particularly failure modes that were harder to verify than expected.
+
+```bash
+nuos-catalogue memory store --value="<what you learned about testing this area>" --wu=<handle> --agent=tester --key="<short label>"
+```
+
 ## What you read before you write tests
 
 - The work unit you're testing (in `docs/build/work-units/`)

package/templates/protocols/build-wu.md

@@ -8,7 +8,7 @@ You are the **swarm coordinator** for a project using the NuOS Build Method cata
 
 ---
 
-## Step 1 — Read the work unit
+## Step 1 — Read the work unit and search memory
 
 The handle comes from the operator (e.g. `WU 007`, `wu-007`, or `007`). Normalise to canonical (`wu-007`), then read the file at `docs/build/work-units/NNN-slug.md` (or `done/` if completed).
 
@@ -21,6 +21,15 @@ Also read:
 - The relevant design-system pieces if the work unit ships a UI surface
 - Run `nuos-catalogue search "<work unit title or outcome>"` to find related prior work
 
+Before spawning any agents, search the cross-agent memory for relevant prior findings:
+
+```bash
+nuos-catalogue memory search --query="<work unit title>"
+nuos-catalogue memory search --query="<the module or contract name being worked on>"
+```
+
+Surface any high-score memories (> 0.8) to the relevant agents as additional context in their spawn prompt. Prior debugger memories about the same module are especially valuable — pass them to the coder and architect.
+
 ## Step 2 — Classify the work
 
 Decide what shape this work is. Most work units fall into one of these patterns:
@@ -78,6 +87,26 @@ Write an audit entry at `docs/build/swarm/YYYY-MM-DD-wu-<handle>.md`. Use the te
 
 Add a row to `docs/build/swarm/_index.md`.
 
+After writing the audit entry, store a swarm-level memory so future coordinators can find this run's learnings by topic:
+
+```bash
+nuos-catalogue memory store \
+  --value="WU <handle>: <one sentence on what was built and the key decision or finding>" \
+  --wu=<handle> \
+  --agent=coordinator \
+  --key="swarm-summary"
+```
+
+If the architect filed a non-obvious decision, store it separately so it's findable by future architects:
+
+```bash
+nuos-catalogue memory store \
+  --value="<the decision: what was chosen and why; alternatives rejected>" \
+  --wu=<handle> \
+  --agent=architect \
+  --key="<decision slug>"
+```
+
 ## Step 7 — Update the work unit + STATE
 
 If the swarm produced a complete outcome (reviewer approved), the work unit promotes:

package/templates/starter-kit/methodfile.json

@@ -53,9 +53,9 @@
     "comment": "Default model routing for swarm agents. Opus for design + debugging (reasoning-heavy, ~20% of work). Sonnet for coding + tests + review (the 80%). Haiku for research + lookups. Override per-spawn by passing `model: '...'` to the Task tool. See docs/build/WELCOME.md for the rationale."
   },
   "harness": {
-    "wired": false,
+    "wired": true,
     "runtime": {
-      "nuvector": null,
+      "nuvector": ".nuos-catalogue/index.nv",
       "nuflow": null,
       "nuwiki": null
     },