continuous-improvement 3.11.0 → 3.12.3

package/plugins/continuous-improvement/instinct-packs/go.json

@@ -1,58 +1,58 @@
-[
-  {
-    "id": "go-error-handling",
-    "trigger": "when calling functions that return errors",
-    "body": "Always check returned errors immediately. Never use _ to discard errors unless you've explicitly decided it's safe and documented why.",
-    "confidence": 0.7,
-    "domain": "patterns"
-  },
-  {
-    "id": "go-defer-cleanup",
-    "trigger": "when opening files, connections, or acquiring locks",
-    "body": "Use defer immediately after acquiring a resource for cleanup. Place defer right after the error check for the acquisition.",
-    "confidence": 0.7,
-    "domain": "patterns"
-  },
-  {
-    "id": "go-interface-consumer",
-    "trigger": "when defining Go interfaces",
-    "body": "Define interfaces at the consumer side, not the producer side. Keep interfaces small (1-3 methods). Accept interfaces, return structs.",
-    "confidence": 0.65,
-    "domain": "patterns"
-  },
-  {
-    "id": "go-table-driven-tests",
-    "trigger": "when writing Go tests",
-    "body": "Use table-driven tests with subtests (t.Run) for functions with multiple input/output cases. Name test cases descriptively.",
-    "confidence": 0.7,
-    "domain": "testing"
-  },
-  {
-    "id": "go-context-propagation",
-    "trigger": "when writing HTTP handlers or long-running operations",
-    "body": "Accept context.Context as the first parameter. Propagate it to all downstream calls. Use it for cancellation and timeouts.",
-    "confidence": 0.65,
-    "domain": "patterns"
-  },
-  {
-    "id": "go-goroutine-lifecycle",
-    "trigger": "when spawning goroutines",
-    "body": "Always ensure goroutines have a way to exit (context cancellation, done channel, or WaitGroup). Never fire-and-forget goroutines without cleanup.",
-    "confidence": 0.7,
-    "domain": "patterns"
-  },
-  {
-    "id": "go-struct-zero-values",
-    "trigger": "when designing Go structs",
-    "body": "Design structs so their zero value is useful. Use pointer fields only when nil is a meaningful distinct state from zero value.",
-    "confidence": 0.6,
-    "domain": "patterns"
-  },
-  {
-    "id": "go-mod-tidy",
-    "trigger": "when adding or removing dependencies",
-    "body": "Run 'go mod tidy' after adding or removing imports to keep go.mod and go.sum clean.",
-    "confidence": 0.65,
-    "domain": "workflow"
-  }
-]
+[
+  {
+    "id": "go-error-handling",
+    "trigger": "when calling functions that return errors",
+    "body": "Always check returned errors immediately. Never use _ to discard errors unless you've explicitly decided it's safe and documented why.",
+    "confidence": 0.7,
+    "domain": "patterns"
+  },
+  {
+    "id": "go-defer-cleanup",
+    "trigger": "when opening files, connections, or acquiring locks",
+    "body": "Use defer immediately after acquiring a resource for cleanup. Place defer right after the error check for the acquisition.",
+    "confidence": 0.7,
+    "domain": "patterns"
+  },
+  {
+    "id": "go-interface-consumer",
+    "trigger": "when defining Go interfaces",
+    "body": "Define interfaces at the consumer side, not the producer side. Keep interfaces small (1-3 methods). Accept interfaces, return structs.",
+    "confidence": 0.65,
+    "domain": "patterns"
+  },
+  {
+    "id": "go-table-driven-tests",
+    "trigger": "when writing Go tests",
+    "body": "Use table-driven tests with subtests (t.Run) for functions with multiple input/output cases. Name test cases descriptively.",
+    "confidence": 0.7,
+    "domain": "testing"
+  },
+  {
+    "id": "go-context-propagation",
+    "trigger": "when writing HTTP handlers or long-running operations",
+    "body": "Accept context.Context as the first parameter. Propagate it to all downstream calls. Use it for cancellation and timeouts.",
+    "confidence": 0.65,
+    "domain": "patterns"
+  },
+  {
+    "id": "go-goroutine-lifecycle",
+    "trigger": "when spawning goroutines",
+    "body": "Always ensure goroutines have a way to exit (context cancellation, done channel, or WaitGroup). Never fire-and-forget goroutines without cleanup.",
+    "confidence": 0.7,
+    "domain": "patterns"
+  },
+  {
+    "id": "go-struct-zero-values",
+    "trigger": "when designing Go structs",
+    "body": "Design structs so their zero value is useful. Use pointer fields only when nil is a meaningful distinct state from zero value.",
+    "confidence": 0.6,
+    "domain": "patterns"
+  },
+  {
+    "id": "go-mod-tidy",
+    "trigger": "when adding or removing dependencies",
+    "body": "Run 'go mod tidy' after adding or removing imports to keep go.mod and go.sum clean.",
+    "confidence": 0.65,
+    "domain": "workflow"
+  }
+]

package/plugins/continuous-improvement/instinct-packs/meta.json

@@ -1,16 +1,16 @@
-[
-  {
-    "id": "skip-thin-observation-schema",
-    "trigger": "when running /continuous-improvement and observations.jsonl entries contain only tool_start events with no inputs/outputs/errors",
-    "body": "Skip instinct fabrication and report the schema gap instead. With only ts/event/session/tool/project_id/project_name fields, the stream cannot distinguish a `git status` Bash call from a `rm -rf` Bash call. Tool-name bigrams (Bash→Bash, Edit→Edit, Read→Edit) reflect parallel-call artifacts and harness-enforced read-before-edit, not learned preferences. Recommend enhancing PostToolUse/PreToolUse hooks to log tool inputs (Bash command head, Skill name) and tool_end with success flag before retrying analysis.",
-    "confidence": 0.6,
-    "domain": "meta"
-  },
-  {
-    "id": "parallelize-independent-tool-calls",
-    "trigger": "when issuing 2+ tool calls with no data dependency between them in the same turn",
-    "body": "Batch independent tool calls into a single message instead of issuing them sequentially. Independent reads, independent greps, independent git inspections, independent file edits in unrelated files belong in one message with multiple tool blocks. Dependent calls (output of A determines input of B) stay sequential. Exception: when a single check would short-circuit the whole task (e.g., `git status` returning empty), one call first is fine. Sequential issuing of independent calls wastes wall-clock time and burns context per round-trip.",
-    "confidence": 0.6,
-    "domain": "workflow"
-  }
-]
+[
+  {
+    "id": "skip-thin-observation-schema",
+    "trigger": "when running /continuous-improvement and observations.jsonl entries contain only tool_start events with no inputs/outputs/errors",
+    "body": "Skip instinct fabrication and report the schema gap instead. With only ts/event/session/tool/project_id/project_name fields, the stream cannot distinguish a `git status` Bash call from a `rm -rf` Bash call. Tool-name bigrams (Bash→Bash, Edit→Edit, Read→Edit) reflect parallel-call artifacts and harness-enforced read-before-edit, not learned preferences. Recommend enhancing PostToolUse/PreToolUse hooks to log tool inputs (Bash command head, Skill name) and tool_end with success flag before retrying analysis.",
+    "confidence": 0.6,
+    "domain": "meta"
+  },
+  {
+    "id": "parallelize-independent-tool-calls",
+    "trigger": "when issuing 2+ tool calls with no data dependency between them in the same turn",
+    "body": "Batch independent tool calls into a single message instead of issuing them sequentially. Independent reads, independent greps, independent git inspections, independent file edits in unrelated files belong in one message with multiple tool blocks. Dependent calls (output of A determines input of B) stay sequential. Exception: when a single check would short-circuit the whole task (e.g., `git status` returning empty), one call first is fine. Sequential issuing of independent calls wastes wall-clock time and burns context per round-trip.",
+    "confidence": 0.6,
+    "domain": "workflow"
+  }
+]

package/plugins/continuous-improvement/instinct-packs/python.json

@@ -1,58 +1,58 @@
-[
-  {
-    "id": "python-virtual-env",
-    "trigger": "when starting work on a Python project",
-    "body": "Check for virtual environment (venv, .venv, conda) before installing packages. Never install to system Python.",
-    "confidence": 0.7,
-    "domain": "workflow"
-  },
-  {
-    "id": "python-type-hints",
-    "trigger": "when writing Python functions",
-    "body": "Add type hints to function parameters and return values. Use Optional[], list[], dict[] (Python 3.10+) or typing module for older versions.",
-    "confidence": 0.6,
-    "domain": "code-style"
-  },
-  {
-    "id": "python-pathlib",
-    "trigger": "when working with file paths in Python",
-    "body": "Use pathlib.Path instead of os.path for file operations. It's more readable and cross-platform.",
-    "confidence": 0.65,
-    "domain": "patterns"
-  },
-  {
-    "id": "python-context-managers",
-    "trigger": "when opening files or database connections",
-    "body": "Always use context managers (with statement) for files, database connections, and locks. Never rely on manual .close() calls.",
-    "confidence": 0.7,
-    "domain": "patterns"
-  },
-  {
-    "id": "python-list-comprehension",
-    "trigger": "when writing simple for loops that build lists",
-    "body": "Prefer list comprehensions for simple transformations. Use regular for loops when the logic is complex or has side effects.",
-    "confidence": 0.6,
-    "domain": "code-style"
-  },
-  {
-    "id": "python-requirements-check",
-    "trigger": "when adding a new import",
-    "body": "Check if the package is already in requirements.txt, pyproject.toml, or Pipfile before adding. Search for existing usage in the codebase.",
-    "confidence": 0.65,
-    "domain": "workflow"
-  },
-  {
-    "id": "python-pytest-fixtures",
-    "trigger": "when writing Python tests",
-    "body": "Use pytest fixtures for test setup/teardown instead of unittest setUp/tearDown. Use conftest.py for shared fixtures.",
-    "confidence": 0.6,
-    "domain": "testing"
-  },
-  {
-    "id": "python-dataclass",
-    "trigger": "when creating classes that primarily hold data",
-    "body": "Use @dataclass or Pydantic BaseModel instead of plain classes for data containers. They provide __init__, __repr__, and comparison for free.",
-    "confidence": 0.65,
-    "domain": "patterns"
-  }
-]
+[
+  {
+    "id": "python-virtual-env",
+    "trigger": "when starting work on a Python project",
+    "body": "Check for virtual environment (venv, .venv, conda) before installing packages. Never install to system Python.",
+    "confidence": 0.7,
+    "domain": "workflow"
+  },
+  {
+    "id": "python-type-hints",
+    "trigger": "when writing Python functions",
+    "body": "Add type hints to function parameters and return values. Use Optional[], list[], dict[] (Python 3.10+) or typing module for older versions.",
+    "confidence": 0.6,
+    "domain": "code-style"
+  },
+  {
+    "id": "python-pathlib",
+    "trigger": "when working with file paths in Python",
+    "body": "Use pathlib.Path instead of os.path for file operations. It's more readable and cross-platform.",
+    "confidence": 0.65,
+    "domain": "patterns"
+  },
+  {
+    "id": "python-context-managers",
+    "trigger": "when opening files or database connections",
+    "body": "Always use context managers (with statement) for files, database connections, and locks. Never rely on manual .close() calls.",
+    "confidence": 0.7,
+    "domain": "patterns"
+  },
+  {
+    "id": "python-list-comprehension",
+    "trigger": "when writing simple for loops that build lists",
+    "body": "Prefer list comprehensions for simple transformations. Use regular for loops when the logic is complex or has side effects.",
+    "confidence": 0.6,
+    "domain": "code-style"
+  },
+  {
+    "id": "python-requirements-check",
+    "trigger": "when adding a new import",
+    "body": "Check if the package is already in requirements.txt, pyproject.toml, or Pipfile before adding. Search for existing usage in the codebase.",
+    "confidence": 0.65,
+    "domain": "workflow"
+  },
+  {
+    "id": "python-pytest-fixtures",
+    "trigger": "when writing Python tests",
+    "body": "Use pytest fixtures for test setup/teardown instead of unittest setUp/tearDown. Use conftest.py for shared fixtures.",
+    "confidence": 0.6,
+    "domain": "testing"
+  },
+  {
+    "id": "python-dataclass",
+    "trigger": "when creating classes that primarily hold data",
+    "body": "Use @dataclass or Pydantic BaseModel instead of plain classes for data containers. They provide __init__, __repr__, and comparison for free.",
+    "confidence": 0.65,
+    "domain": "patterns"
+  }
+]

package/plugins/continuous-improvement/instinct-packs/react.json

@@ -1,58 +1,58 @@
-[
-  {
-    "id": "react-check-existing-components",
-    "trigger": "when creating a new React component",
-    "body": "Search the codebase for existing components that solve the same problem before creating new ones. Check shared/, components/, and ui/ directories.",
-    "confidence": 0.65,
-    "domain": "workflow"
-  },
-  {
-    "id": "react-prefer-server-components",
-    "trigger": "when creating components in Next.js App Router",
-    "body": "Default to Server Components. Only add 'use client' when the component needs useState, useEffect, event handlers, or browser APIs.",
-    "confidence": 0.7,
-    "domain": "patterns"
-  },
-  {
-    "id": "react-key-prop-lists",
-    "trigger": "when rendering lists with .map()",
-    "body": "Always use a stable, unique key prop. Never use array index as key unless the list is static and never reordered.",
-    "confidence": 0.7,
-    "domain": "patterns"
-  },
-  {
-    "id": "react-effect-cleanup",
-    "trigger": "when writing useEffect with subscriptions or timers",
-    "body": "Always return a cleanup function from useEffect when setting up subscriptions, event listeners, or timers to prevent memory leaks.",
-    "confidence": 0.7,
-    "domain": "patterns"
-  },
-  {
-    "id": "react-memo-expensive",
-    "trigger": "when a component re-renders with expensive calculations",
-    "body": "Use useMemo for expensive computations and React.memo for components that receive the same props frequently. Don't memo everything — only what's measurably slow.",
-    "confidence": 0.6,
-    "domain": "patterns"
-  },
-  {
-    "id": "react-form-validation",
-    "trigger": "when building forms",
-    "body": "Check if react-hook-form or zod is already in the project before building custom form validation. Prefer library solutions over hand-rolled validation.",
-    "confidence": 0.65,
-    "domain": "tooling"
-  },
-  {
-    "id": "react-error-boundary",
-    "trigger": "when adding a new page or route",
-    "body": "Ensure error boundaries exist around new pages/routes. In Next.js App Router, add error.tsx. In other React apps, wrap with ErrorBoundary component.",
-    "confidence": 0.6,
-    "domain": "patterns"
-  },
-  {
-    "id": "react-test-user-behavior",
-    "trigger": "when writing React component tests",
-    "body": "Test user behavior, not implementation details. Use @testing-library/react. Query by role, label, or text — not by class name or test ID.",
-    "confidence": 0.65,
-    "domain": "testing"
-  }
-]
+[
+  {
+    "id": "react-check-existing-components",
+    "trigger": "when creating a new React component",
+    "body": "Search the codebase for existing components that solve the same problem before creating new ones. Check shared/, components/, and ui/ directories.",
+    "confidence": 0.65,
+    "domain": "workflow"
+  },
+  {
+    "id": "react-prefer-server-components",
+    "trigger": "when creating components in Next.js App Router",
+    "body": "Default to Server Components. Only add 'use client' when the component needs useState, useEffect, event handlers, or browser APIs.",
+    "confidence": 0.7,
+    "domain": "patterns"
+  },
+  {
+    "id": "react-key-prop-lists",
+    "trigger": "when rendering lists with .map()",
+    "body": "Always use a stable, unique key prop. Never use array index as key unless the list is static and never reordered.",
+    "confidence": 0.7,
+    "domain": "patterns"
+  },
+  {
+    "id": "react-effect-cleanup",
+    "trigger": "when writing useEffect with subscriptions or timers",
+    "body": "Always return a cleanup function from useEffect when setting up subscriptions, event listeners, or timers to prevent memory leaks.",
+    "confidence": 0.7,
+    "domain": "patterns"
+  },
+  {
+    "id": "react-memo-expensive",
+    "trigger": "when a component re-renders with expensive calculations",
+    "body": "Use useMemo for expensive computations and React.memo for components that receive the same props frequently. Don't memo everything — only what's measurably slow.",
+    "confidence": 0.6,
+    "domain": "patterns"
+  },
+  {
+    "id": "react-form-validation",
+    "trigger": "when building forms",
+    "body": "Check if react-hook-form or zod is already in the project before building custom form validation. Prefer library solutions over hand-rolled validation.",
+    "confidence": 0.65,
+    "domain": "tooling"
+  },
+  {
+    "id": "react-error-boundary",
+    "trigger": "when adding a new page or route",
+    "body": "Ensure error boundaries exist around new pages/routes. In Next.js App Router, add error.tsx. In other React apps, wrap with ErrorBoundary component.",
+    "confidence": 0.6,
+    "domain": "patterns"
+  },
+  {
+    "id": "react-test-user-behavior",
+    "trigger": "when writing React component tests",
+    "body": "Test user behavior, not implementation details. Use @testing-library/react. Query by role, label, or text — not by class name or test ID.",
+    "confidence": 0.65,
+    "domain": "testing"
+  }
+]

package/plugins/continuous-improvement/lib/goal-state.mjs

@@ -19,10 +19,10 @@ const STOPWORDS = new Set([
     "make", "made", "adds", "new", "get", "got", "set", "also", "only", "each",
     "task", "goal", "plan", "work", "working", "build", "building", "code",
 ]);
-// 4 suits Latin/Cyrillic prose, but it silently drops most Korean/Thai words
-// (typically 2 chars) even though the Unicode splitter now keeps them — so the
-// goal-state half of the tokenizer fix is only partial for those scripts. A
-// script-aware floor is a logged follow-up (see CLAUDE.md Deferred).
+// 4 suits Latin/Cyrillic/Thai prose (Thai combining marks are now kept; see
+// extractKeywordsFromProse regex), but it silently drops most Korean words
+// (typically 2 chars). A script-aware floor for Korean is a logged follow-up
+// (see CLAUDE.md Deferred).
 const KEYWORD_MIN_LENGTH = 4;
 const KEYWORD_CAP = 20;
 const DEFAULT_WINDOW = 30;
@@ -52,14 +52,14 @@ export function getSection(markdown, heading) {
 }
 /**
  * Tokenize prose into goal keywords: lowercase, split on any non-letter /
- * non-number (Unicode-aware, so accented Latin / Cyrillic / CJK survive), drop
- * stopwords, pure-digit tokens, and tokens shorter than KEYWORD_MIN_LENGTH.
- * Deduped, capped at KEYWORD_CAP.
+ * non-number / non-mark (Unicode-aware, so accented Latin / Cyrillic / CJK /
+ * Thai survive), drop stopwords, pure-digit tokens, and tokens shorter than
+ * KEYWORD_MIN_LENGTH. Deduped, capped at KEYWORD_CAP.
  */
 export function extractKeywordsFromProse(prose) {
     const seen = new Set();
     const out = [];
-    for (const raw of prose.toLowerCase().split(/[^\p{L}\p{N}]+/u)) {
+    for (const raw of prose.toLowerCase().split(/[^\p{L}\p{N}\p{M}]+/u)) {
         const word = raw.trim();
         if (word.length < KEYWORD_MIN_LENGTH)
             continue;

package/plugins/continuous-improvement/lib/plugin-metadata.mjs

@@ -26,7 +26,7 @@ const KEYWORDS = [
     "transcript-linter",
 ];
 const CLAUDE_PLUGIN_CATEGORY = "productivity";
-const SHARED_PLUGIN_DESCRIPTION = "Stops Claude Code from skipping research, claiming 'done' without verifying, and repeating yesterday's mistakes. The 7 Laws of AI Agent Discipline — 25 bundled skills, gating hooks, the Mulahazah auto-leveling instinct engine, and a GitHub Action transcript linter.";
+const SHARED_PLUGIN_DESCRIPTION = "Makes Claude Code reason harder, recall past corrections, and learn from every session so its competence compounds run over run. The Mulahazah engine turns each fix into a reusable instinct, so a lesson learned once is applied automatically next time — no re-teaching. Built on the 7 Laws of AI Agent Discipline (research, plan, verify, reflect, learn) and shipped as 25 bundled skills, instinct-aware hooks, an MCP toolset for recall and reflection, and a GitHub Action transcript linter that feeds real work history back into sharper instincts.";
 // Four vendored upstream companions registered alongside the CI plugin.
 // Each entry points at a pinned-SHA snapshot under third-party/<name>/.
 // See third-party/MANIFEST.md for refresh recipes and per-snapshot
@@ -76,7 +76,7 @@ const THIRD_PARTY_COMPANIONS = [
     },
     {
         name: "oh-my-claudecode",
-        description: "Multi-agent orchestration system for Claude Code — 39 skills + 19 agents covering audit, plan, build, verify, ship, release, retrospective, and ops. Includes ralph (autonomous PRD loop), release, ultrawork, ultraqa, team, trace, visual-verdict, debug, deep-dive, deep-interview, autopilot, autoresearch. Vendored snapshot at third-party/oh-my-claudecode/ pinned to upstream SHA aacde3e (v4.13.6). Heavy overlap with continuous-improvement /ralph and /superpowers — pick per task.",
+        description: "Multi-agent orchestration system for Claude Code — 38 skills + 19 agents covering audit, plan, build, verify, ship, release, retrospective, and ops. Includes ralph (autonomous PRD loop), release, ultrawork, ultraqa, team, trace, visual-verdict, debug, deep-dive, deep-interview, autopilot, autoresearch. Vendored snapshot at third-party/oh-my-claudecode/ pinned to upstream SHA aacde3e (v4.13.6). Heavy overlap with continuous-improvement /ralph and /superpowers — pick per task.",
         version: "4.13.6",
         source: "./third-party/oh-my-claudecode",
         author: {
@@ -376,12 +376,12 @@ const EXPERT_TOOL_ENTRIES = [
 ];
 const MODE_METADATA = {
     beginner: {
-        description: "Beginner mode: see what your agent learned, list its instincts, and request a session reflection. Bundles four discipline skills (gateguard, para-memory-files, tdd-workflow, verification-loop) so research, memory, tests, and verification happen by default.",
+        description: "Beginner mode: see what your agent learned, list its instincts, and request a session reflection. Bundles four grounding skills (gateguard, para-memory-files, tdd-workflow, verification-loop) so research, memory, tests, and verification happen by default — every edit starts from facts, not guesses.",
         hooks: ["PreToolUse", "PostToolUse", "UserPromptSubmit"],
-        hookDescription: "Silently captures every tool call as observations and routes prompts to the matching discipline skill via the route table. Lightweight and non-blocking.",
+        hookDescription: "Silently captures every tool call as observations and routes prompts to the matching skill via the route table. Lightweight and non-blocking.",
     },
     expert: {
-        description: "Expert mode: tune confidence, manage instincts, and persist plans on disk. Adds safety, token-budget, and strategic-compact skills plus the /learn-eval command so long sessions stay disciplined and learnings survive context resets.",
+        description: "Expert mode: tune confidence, manage instincts, and persist plans on disk. Adds safety, token-budget, and strategic-compact skills plus the /learn-eval command so long sessions stay sharp and learnings survive context resets.",
         hooks: ["PreToolUse", "PostToolUse", "UserPromptSubmit", "SessionStart", "SessionEnd"],
         hookDescription: "Full hook suite: observation capture, lazy prompt routing, session-level instinct loading, and auto-reflection.",
     },
@@ -482,8 +482,13 @@ export function getPluginHooksConfig() {
         command: "node \"${CLAUDE_PLUGIN_ROOT}/hooks/route-prompt.mjs\"",
         timeout: 5,
     };
+    const recallBriefingCommand = {
+        type: "command",
+        command: "node \"${CLAUDE_PLUGIN_ROOT}/hooks/recall-briefing.mjs\"",
+        timeout: 5,
+    };
     return {
-        description: "Gateguard fact-forcing PreToolUse, companion-preference enforcement, observation, session lifecycle, 3-section-close discipline, goal-drift Stop gate, and UserPromptSubmit lazy-routing hooks for continuous-improvement.",
+        description: "Gateguard fact-forcing PreToolUse, companion-preference enforcement, observation, session lifecycle, 3-section-close discipline, goal-drift Stop gate, and UserPromptSubmit lazy-routing plus opt-in proactive recall-briefing hooks for continuous-improvement.",
         hooks: {
             // gateguard runs FIRST on PreToolUse so its block decision short-circuits
             // before companion-preference sees the call. companion-preference runs
@@ -498,7 +503,7 @@ export function getPluginHooksConfig() {
                 { hooks: [gateguardCommand, companionPreferenceCommand] },
             ],
             PostToolUse: [{ hooks: [observeCommand] }],
-            UserPromptSubmit: [{ hooks: [routePromptCommand] }],
+            UserPromptSubmit: [{ hooks: [routePromptCommand, recallBriefingCommand] }],
             SessionStart: [{ hooks: [sessionCommand] }],
             SessionEnd: [{ hooks: [sessionCommand] }],
             Stop: [{ hooks: [threeSectionCloseCommand, goalDriftStopCommand] }],

package/plugins/continuous-improvement/lib/recall-briefing.mjs

@@ -0,0 +1,57 @@
+// recall-briefing.mts — Pure decision core for the proactive recall-briefing hook.
+//
+// No I/O. Given (enabled, already-briefed, prompt, ranked recall hits), decides
+// whether to inject a one-time-per-session "you've touched related work before"
+// system-reminder and renders it. The hook (src/hooks/recall-briefing.mts) does
+// the filesystem work — read the prompt, read observations.jsonl, build the BM25
+// index (recall-index.mts), track per-session state — then calls decideBriefing.
+// Keeping the decision pure lets the unit tests cover every gate and boundary
+// (disabled / already-briefed / empty-or-short prompt / no hits / malformed
+// input) without touching the filesystem, per the repo lesson that green gates
+// do not prove boundary safety.
+//
+// This is an amplifier, not a gate: it never blocks a prompt. It only surfaces
+// prior context so the agent reuses a past fix instead of re-deriving it. It is
+// opt-in (the hook checks an env flag) and fires at most once per session.
+export const DEFAULT_MAX_HITS = 3;
+export const DEFAULT_MIN_PROMPT_LENGTH = 12;
+/** Render ranked hits as a compact UserPromptSubmit system-reminder. Pure string. */
+export function formatBriefing(hits) {
+    const lines = [
+        "<system-reminder>",
+        "Recall briefing: this project has prior sessions that touched related work. Before re-deriving a fix, consider the `ci_recall` MCP tool (or `/recall`) for full context. Most relevant past activity:",
+    ];
+    for (const h of hits) {
+        const stamp = h && h.ts ? `[${h.ts}] ` : "";
+        const tool = (h && h.tool) || "(tool?)";
+        const snippet = ((h && h.snippet) || "").replace(/\s+/g, " ").trim();
+        lines.push(`- ${stamp}${tool}: ${snippet || "(no summary)"}`);
+    }
+    lines.push("</system-reminder>");
+    return lines.join("\n");
+}
+/**
+ * Decide whether to inject a recall briefing. Fails closed: any disabling
+ * condition (opted out, already briefed, prompt below the noise floor, no hits,
+ * malformed input) returns shouldBrief=false and never throws.
+ */
+export function decideBriefing(params) {
+    const none = { shouldBrief: false, reminder: null };
+    if (!params || params.enabled !== true)
+        return none;
+    if (params.alreadyBriefed === true)
+        return none;
+    const prompt = typeof params.prompt === "string" ? params.prompt : "";
+    const minLen = typeof params.minPromptLength === "number" && params.minPromptLength >= 0
+        ? params.minPromptLength
+        : DEFAULT_MIN_PROMPT_LENGTH;
+    if (prompt.trim().length < minLen)
+        return none;
+    const maxHits = typeof params.maxHits === "number" && params.maxHits > 0
+        ? Math.floor(params.maxHits)
+        : DEFAULT_MAX_HITS;
+    const hits = Array.isArray(params.hits) ? params.hits.slice(0, maxHits) : [];
+    if (hits.length === 0)
+        return none;
+    return { shouldBrief: true, reminder: formatBriefing(hits) };
+}

package/plugins/continuous-improvement/lib/recall-index.mjs

@@ -19,10 +19,10 @@ const BM25_K1 = 1.5;
 const BM25_B = 0.75;
 const DEFAULT_K = 5;
 const SNIPPET_RADIUS = 60;
-/** Lowercase, split on any non-letter / non-number (Unicode-aware), drop stopwords and tokens shorter than TOKEN_MIN_LENGTH. */
+/** Lowercase, split on any non-letter / non-number / non-mark (Unicode-aware), drop stopwords and tokens shorter than TOKEN_MIN_LENGTH. */
 export function tokenize(text) {
     const out = [];
-    for (const raw of text.toLowerCase().split(/[^\p{L}\p{N}]+/u)) {
+    for (const raw of text.toLowerCase().split(/[^\p{L}\p{N}\p{M}]+/u)) {
         if (raw.length < TOKEN_MIN_LENGTH)
             continue;
         if (STOPWORDS.has(raw))

package/plugins/continuous-improvement/skills/continuous-improvement/SKILL.md

@@ -6,7 +6,7 @@ description: "Install structured self-improvement loops with instinct-based lear
 
 # continuous-improvement
 
-You follow the continuous-improvement framework. These 7 laws govern all your work.
+You follow the continuous-improvement framework. These 7 laws make every task sharper — each is a capability that compounds: research deeper, plan tighter, verify with evidence, reflect, and learn so the same lesson is never re-taught.
 
 ## Law 1: Research Before Executing
 

package/plugins/continuous-improvement/skills/superpowers/SKILL.md

@@ -21,7 +21,7 @@ The dispatcher now routes across **four registered marketplaces** instead of rel
 /plugin install superpowers@continuous-improvement       # Obra's 14 workflow skills
 /plugin install agent-skills@continuous-improvement      # Addy's 21 SDLC skills
 /plugin install ruflo-swarm@continuous-improvement       # Agent swarm + Monitor stream
-/plugin install oh-my-claudecode@continuous-improvement  # 39 skills + 19 agents
+/plugin install oh-my-claudecode@continuous-improvement  # 38 skills + 19 agents
 ```
 
 The CI plugin (this dispatcher + `tdd-workflow`, `verification-loop`, `gateguard`, `ralph`, `deploy-receipt`, etc.) installs by default. The four companions are opt-in — install only what you need.