@vpxa/aikit 0.1.152 → 0.1.153

package/scaffold/dist/definitions/protocols.mjs

@@ -1,26 +1,26 @@
-const e={"code-agent-base":`# Code Agent — Shared Base Instructions
-
-> This file contains shared protocols for all code-modifying agents (Implementer, Frontend, Refactor, Debugger). Each agent's definition file contains only its unique identity, constraints, and workflow. **Do not duplicate this content in agent files.**
-
-
-## AI Kit MCP Tool Naming Convention
+function e(e){return`
+## Flow Context Bootstrap
 
-All tool references in these instructions use **short names** (e.g. \`status\`, \`compact\`, \`search\`).
-At runtime, these are MCP tools exposed by the AI Kit server. Depending on your IDE/client, the actual tool name will be prefixed:
+When dispatched as a subagent within an active flow:
 
-| Client | Tool naming pattern | Example |
-|--------|-------------------|---------|
-| VS Code Copilot | \`mcp_<serverName>_<tool>\` | \`mcp_aikit_status\` |
-| Claude Code | \`mcp__<serverName>__<tool>\` | \`mcp__aikit__status\` |
-| Other MCP clients | \`<serverName>_<tool>\` or bare \`<tool>\` | \`aikit_status\` or \`status\` |
+1. **Withdraw context first** — before any search or file reads:
+   \`\`\`
+  knowledge({ action: 'withdraw', scope: 'flow', profile: '${e}', budget: 6000 })
+   \`\`\`
+   This returns pre-analyzed context from prior agents.
 
-The server name is \`aikit\` — check your MCP configuration if tools aren't found.
+2. **Use returned context** — do NOT re-search or re-read files already covered
+3. **\`read_file\` ONLY** for exact lines needed for editing
+4. **Deposit new discoveries:**
+   \`\`\`
+   knowledge({ action: 'remember', scope: 'flow', title: '<discovery>', content: '<details>', category: 'context' })
+   \`\`\`
 
-**When these instructions say** \`status({})\` **→ call the MCP tool whose name ends with** \`_status\` **and pass** \`{}\` **as arguments.**
+${e===`<PROFILE>`?`**Profile:** Check your role → implementer | documenter | reviewer | researcher | debugger`:`**Profile:** \`${e}\``}
 
-If tools are deferred/lazy-loaded, load them first (e.g. in VS Code Copilot: \`tool_search_tool_regex({ pattern: "aikit" })\`).
+---`}function t(){return"\n## Evidence Citation Protocol (tier-aware)\n\n**Standalone mode:** If no FORGE task_id was provided in your dispatch prompt, skip `evidence_map` calls entirely — provide free-form findings with `file:line` citations only.\n\nThe Orchestrator runs `forge_classify` before dispatching you, and runs the final `evidence_map({ action: 'gate', task_id })` after you respond. **Do not create your own task_id or run the gate** — feed into the Orchestrator's existing evidence map.\n\n| Tier | Your responsibility |\n|------|---------------------|\n| Floor | Free-form findings with `file.ts#Lxx` citations. No `evidence_map` calls required. |\n| Standard | For every CRITICAL or HIGH finding: `evidence_map({action:'add', task_id, claim, status:'V', receipt:'file.ts#Lxx'})`. Max 2-4 adds to keep signal high. |\n| Critical | Structured claims for all CRITICAL/HIGH findings (2-4 Verified + receipts) AND tag contract/security claims with `safety_gate:'commitment'` or `safety_gate:'provenance'`. |\n\n**Every response MUST include:**\n- `**FORGE Task ID:** <task_id>` (passed in by Orchestrator, or state \"not provided\")\n- `**Tier applied:** Floor | Standard | Critical`\n- `**Findings:** <list>` with `file:line` receipts\n- Verdict: `APPROVED` | `CHANGES_REQUESTED` | `BLOCKED`\n\nDo NOT:\n- Create a new `evidence_map` (the Orchestrator already did)\n- Run `evidence_map({action:'gate'})` yourself — the Orchestrator owns the gate\n- Duplicate findings into the map that weren't CRITICAL/HIGH"}const n={"code-agent-base":`# Code Agent — Shared Base Instructions
 
----
+> This file contains shared protocols for all code-modifying agents (Implementer, Frontend, Refactor, Debugger). Each agent's definition file contains only its unique identity, constraints, and workflow. **Do not duplicate this content in agent files.**
 
 ## Invocation Mode Detection
 
@@ -97,6 +97,10 @@ Always follow this order when you need to understand something. **Never skip to
 
 Past decisions, conventions, and patterns are stored in curated knowledge. Auto-knowledge captures facts automatically from tool outputs (conventions, errors, test results, research). Use \`search()\` with specific keywords to surface these — they are indexed alongside manually curated entries. You MUST search before implementing:
 
+- If running as a sub-agent, start with \`knowledge({ action: "withdraw", scope: "flow", profile: "<your-role>", budget: 6000 })\` to pull prior compressed context.
+- Before re-running \`file_summary\`, \`compact\`, \`stratum_card\`, \`search\`, or \`blast_radius\`, check existing flow context first and reuse it when it is sufficient.
+- Reuse existing stash/checkpoint/workset context when present before creating new compressed artifacts.
+
 \`\`\`
 search("keywords about the feature/area you're changing")  // check for past decisions
 knowledge({ action: "list", category: "decisions" })   // scan recent decisions that might apply
@@ -110,6 +114,7 @@ knowledge({ action: "withdraw", scope: "flow", profile: "<your-role>", budget: 6
 **Rules:**
 - If results exist → **READ them and FOLLOW** established patterns. Do not silently override.
 - If results conflict with the current task → **surface the conflict** to the user/orchestrator.
+- If flow-context search results already contain enough detail → **use them directly** instead of re-running the original tool.
 - If no results → proceed, but **persist your decisions with \`knowledge({ action: "remember", ... })\`** afterward for future recall.
 - Never assume "there's nothing stored" — always search first.
 
@@ -141,7 +146,7 @@ If unsure which AI Kit tool to use → run \`guide({ topic: "what you need" })\`
 
 ---
 
-## Loop Detection & Breaking
+## Loop Detection & Tooling Failure Modes
 
 Track repeated failures. If the same approach fails, **stop and change strategy**.
 
@@ -159,6 +164,27 @@ Track repeated failures. If the same approach fails, **stop and change strategy*
 
 **Never brute-force.** If you catch yourself making the same type of edit repeatedly, you are in a loop.
 
+### Tooling failure exits
+| Signal | Stop condition | Exit action |
+|--------|---------------|-------------|
+| \`evidence_map\` returns HOLD | Insufficient evidence for FORGE gate | Surface concrete gaps to user — do not retry |
+| Sub-agent returns BLOCKED | Subagent cannot proceed | Read its message, escalate to user with options |
+| \`onboard\` reports stale index (>7 days) | Index is stale | Run \`reindex({})\` ONCE; if still stale, surface to user |
+| \`check\` or \`test_run\` fails 3x identical | Same failure mode repeating | STOP — surface to user with full output, do not retry |
+| \`compact\` returns < 50% reduction | Compression ineffective | Use \`file_summary\` or \`stratum_card\` instead |
+
+## Sub-agent Context Budget
+
+When dispatching subagents, choose tier based on task complexity:
+
+| Tier | Budget | Tools | Use For |
+|------|--------|-------|---------|
+| **Floor** | T1 stratum_card only | Read-only | Quick lookups, single-file Q&A |
+| **Standard** | compact() + T2 stratum_card | Read-only + search | Multi-file analysis, research |
+| **Critical** | digest() + stratum_card + flow context | Full | Implementation, decisions, multi-step |
+
+Always tell the subagent: profile, tier, and what they should NOT do.
+
 ---
 
 ## Hallucination Self-Check
@@ -183,12 +209,14 @@ Track repeated failures. If the same approach fails, **stop and change strategy*
 
 ---
 
-## Read-Before-Edit (MANDATORY)
+## Ambiguity Resolution Protocol
 
-Before modifying ANY file, you MUST read it first using \`file_summary\` or \`compact\` to understand its structure. Then use \`read_file\` for the exact lines you need to edit.
+When a task admits ≥2 valid interpretations:
+1. **Name** each interpretation in one sentence.
+2. **Identify** which assumption causes the most harm if wrong (irreversibility, blast radius, user surprise).
+3. **Ask** ONE question — the one that disambiguates the highest-harm assumption.
 
-**Forbidden pattern:** Editing a file based on assumptions or partial context from search results alone.
-**Required pattern:** \`file_summary\` → \`read_file\` (exact edit region) → \`replace_string_in_file\`
+Do NOT silently pick. Do NOT ask multiple questions if one is sufficient.
 
 ## Scope Guard
 
@@ -234,30 +262,9 @@ For outdated AI Kit entries → \`knowledge({ action: "update", path, content, r
 
 ---
 
-## Context Reuse Protocol (MANDATORY)
+## AI Kit Tool Discipline
 
-Auto-knowledge captures tool responses as shared context between agents. **Before running any read tool, check if another agent already ran it.**
-
-**Check-before-run pattern:**
-1. Before \`file_summary\`, \`compact\`, \`stratum_card\`, \`search\`, \`blast_radius\`:
-  - \`search({ query: "<tool-name>: <path-or-query>", tags: ["flow-context"], limit: 3 })\`
-  - Example: \`search({ query: "file_summary: src/auth.ts", tags: ["flow-context"] })\`
-2. If results found with enough detail → **use them directly** — do NOT re-run the tool
-3. Only run the original tool if no cached results exist or results are insufficient
-
-**At agent startup (FIRST action):**
-- Call \`knowledge({ action: "withdraw", profile: "<your-role>", budget: 6000 })\` to receive pre-analyzed context from prior agents in the same flow
-- This surfaces file summaries, search results, and analysis that other agents already performed
-- Parse the withdrawn context — it may contain the exact information you need
-
-**Why this matters:**
-- Each re-run wastes tokens and time
-- Auto-knowledge stores \`file_summary\`, \`compact\`, \`search\`, \`stratum_card\`, \`blast_radius\`, \`scope_map\` results
-- Results are tagged with \`flow-context\` and searchable via \`search()\`
-
----
-
-## FORBIDDEN: Native Tools When AI Kit Alternative Exists
+Use AI Kit retrieval and compression tools first. Prefer reusable compressed context over raw reads, and only drop to native tools when precision for an edit or tool fallback requires it.
 
 | NEVER use this | USE THIS instead | Why |
 |---|---|---|
@@ -268,9 +275,13 @@ Auto-knowledge captures tool responses as shared context between agents. **Befor
 | \`grep_search\` for a symbol name | \`symbol({ name })\` | Definition + references with scope and call context |
 | \`run_in_terminal\` for tsc/lint | \`check({})\` | Typecheck + lint combined, summary output |
 | \`run_in_terminal\` for test | \`test_run({})\` | Run tests with structured output |
+| Editing without reading | \`file_summary\` then targeted \`read_file\` | Prevents wrong-position edits |
 
 **\`read_file\` is ONLY acceptable when you need exact line content FOR EDITING (before \`replace_string_in_file\`).**
 
+For edits, first understand structure with \`file_summary\` or \`compact\`, then use targeted \`read_file\` only for the exact region.
+Never patch from search snippets or assumptions alone.
+
 ## compact() Failure Recovery
 
 If \`compact()\` returns <200 bytes or empty content, the file is NOT indexed. Follow this fallback:
@@ -285,30 +296,7 @@ If \`compact()\` returns <200 bytes or empty content, the file is NOT indexed. F
 - Falling back to read_file in small chunks (10-50 lines) — each chunk costs ~3K prompt tokens in overhead
 - Re-reading the same file later because you forgot the content — use stash() to cache
 
----
-
-## Context Efficiency (MANDATORY)
-
-**MANDATORY: Use AI Kit over \`read_file\` to understand code** (if tools are loaded). Use the AI Kit compression tools:
-- **\`file_summary({ path })\`** — Structure, exports, imports (~50 tokens vs ~1000+ for read_file)
-- **\`compact({ path, query })\`** — Extract relevant sections from a single file (5-20x token reduction)
-- **\`digest({ sources })\`** — Compress 3+ files into a single token-budgeted summary
-- **\`stratum_card({ files, query })\`** — Generate a reusable T1/T2 context card for files you'll reference repeatedly
-
-**Session phases** — structure your work to minimize context bloat:
-
-| Phase | What to do | Compress after? |
-|-------|-----------|----------------|
-| **Understand** | Search AI Kit, read summaries, trace symbols | Yes — \`digest\` findings before planning |
-| **Plan** | Design approach, identify files to change | Yes — \`stash\` the plan, compact analysis |
-| **Execute** | Make changes, one sub-task at a time | Yes — compact between independent sub-tasks |
-| **Verify** | \`check\` + \`test_run\` + \`blast_radius\` | — |
-
-**Rules:**
-- **Never compact mid-operation** — finish the current sub-task first
-- **Recycle context to files** — save analysis results via \`stash\` or \`knowledge({ action: "remember", ... })\`, not just in conversation
-- **Decompose monolithic work** — break into independent chunks, pass results via artifact files between sub-tasks
-- **One-shot sub-tasks** — for self-contained changes, provide all context upfront to avoid back-and-forth
+*Why:* these tools reduce token cost, shrink duplicate reads, and lower the odds of wrong-file or wrong-position edits while preserving reusable context.
 
 ---
 
@@ -415,26 +403,7 @@ When you need user input or need to explain something before asking:
 - **Prefer the simplest method** that adequately conveys the information
 - **CLI mode override:** When running in terminal (not VS Code chat), always use \`format: "browser"\` for any rich content
 
-## Flow Context Bootstrap
-
-When dispatched as a subagent within an active flow:
-
-1. **Withdraw context first** — before any search or file reads:
-   \`\`\`
-   knowledge({ action: 'withdraw', profile: '<PROFILE>', budget: 6000 })
-   \`\`\`
-   This returns pre-analyzed context from prior agents.
-
-2. **Use returned context** — do NOT re-search or re-read files already covered
-3. **\`read_file\` ONLY** for exact lines needed for editing
-4. **Deposit new discoveries:**
-   \`\`\`
-   knowledge({ action: 'remember', scope: 'flow', title: '<discovery>', content: '<details>', category: 'context' })
-   \`\`\`
-
-**Profile:** Check your role → implementer | documenter | reviewer | researcher | debugger
-
----
+${e(`<PROFILE>`)}
 
 ## Handoff Format
 
@@ -453,6 +422,23 @@ Always return this structure when invoked as a sub-agent:
   <blockers>{any blocking issues}</blockers>
 </handoff>
 \`\`\`
+
+  ## AI Kit MCP Tool Naming Convention
+
+  All tool references in these instructions use **short names** (e.g. \`status\`, \`compact\`, \`search\`).
+  At runtime, these are MCP tools exposed by the AI Kit server. Depending on your IDE/client, the actual tool name will be prefixed:
+
+  | Client | Tool naming pattern | Example |
+  |--------|-------------------|---------|
+  | VS Code Copilot | \`mcp_<serverName>_<tool>\` | \`mcp_aikit_status\` |
+  | Claude Code | \`mcp__<serverName>__<tool>\` | \`mcp__aikit__status\` |
+  | Other MCP clients | \`<serverName>_<tool>\` or bare \`<tool>\` | \`aikit_status\` or \`status\` |
+
+  The server name is \`aikit\` — check your MCP configuration if tools aren't found.
+
+  **When these instructions say** \`status({})\` **→ call the MCP tool whose name ends with** \`_status\` **and pass** \`{}\` **as arguments.**
+
+  If tools are deferred/lazy-loaded, load them first (e.g. in VS Code Copilot: \`tool_search_tool_regex({ pattern: "aikit" })\`).
 `,"researcher-base":`# Researcher — Shared Base Instructions
 
 > Shared methodology for all Researcher variants. Each variant's definition contains only its unique identity and model assignment. **Do not duplicate.**
@@ -467,26 +453,7 @@ Follow the **MANDATORY FIRST ACTION** and **Information Lookup Order** from code
 
 **Start with pre-analyzed artifacts.** They cover 80%+ of common research needs.
 
-## Flow Context Bootstrap
-
-When dispatched as a subagent within an active flow:
-
-1. **Withdraw context first** — before any search or file reads:
-   \`\`\`
-  knowledge({ action: 'withdraw', scope: 'flow', profile: 'researcher', budget: 6000 })
-   \`\`\`
-   This returns pre-analyzed context from prior agents.
-
-2. **Use returned context** — do NOT re-search or re-read files already covered
-3. **\`read_file\` ONLY** for exact lines needed for editing
-4. **Deposit new discoveries:**
-   \`\`\`
-   knowledge({ action: 'remember', scope: 'flow', title: '<discovery>', content: '<details>', category: 'context' })
-   \`\`\`
-
-**Profile:** \`researcher\`
-
----
+${e(`researcher`)}
 
 ## Research Methodology
 
@@ -564,19 +531,13 @@ When invoked for a decision analysis, you receive a specific question. You MUST:
 
 ## Invocation Mode Detection
 
-- **Direct** (has AI Kit tools) → Follow the **Information Lookup Order** from code-agent-base
-- **Sub-agent** (prompt has "## Prior AI Kit Context") → Skip AI Kit Recall, use provided context
+> **Mode:** Researchers always run as subagents — no Direct mode.
 
 ---
 
 ## Context Efficiency
 
-- **NEVER use \`read_file\` to understand code** — use AI Kit compression tools instead
-- **\`file_summary\`** for structure (exports, imports, call edges — 10x fewer tokens)
-- **\`compact\`** for specific sections (5-20x token reduction vs read_file)
-- **\`digest\`** when synthesizing from 3+ sources
-- **\`stratum_card\`** for files you'll reference repeatedly
-- **\`read_file\` is ONLY acceptable** when you need exact lines for a pending edit operation
+> **Reminder:** Apply Context Efficiency rules — prefer compact/digest/file_summary over raw read_file. See \`code-agent-base\` for full table.
 
 ## Parallel Exploration via \`lane\`
 
@@ -599,26 +560,7 @@ Follow the **MANDATORY FIRST ACTION** and **Information Lookup Order** from code
 2. If onboard shows ❌ → Run \`onboard({ path: '.' })\` and wait for completion
 3. If onboard shows ✅ → Read relevant onboard artifacts using \`compact({ path: '<Onboard Directory>/<file>' })\` — especially \`patterns.md\` and \`api-surface.md\` for review context
 
-## Flow Context Bootstrap
-
-When dispatched as a subagent within an active flow:
-
-1. **Withdraw context first** — before any search or file reads:
-   \`\`\`
-  knowledge({ action: 'withdraw', scope: 'flow', profile: 'reviewer', budget: 6000 })
-   \`\`\`
-  This returns pre-analyzed context from prior agents.
-
-2. **Use returned context** — do NOT re-search or re-read files already covered
-3. **\`read_file\` ONLY** for exact lines needed for editing
-4. **Deposit new discoveries:**
-   \`\`\`
-   knowledge({ action: 'remember', scope: 'flow', title: '<discovery>', content: '<details>', category: 'context' })
-   \`\`\`
-
-**Profile:** \`reviewer\`
-
----
+${e(`reviewer`)}
 
 ## Review Workflow
 
@@ -670,28 +612,7 @@ When dispatched as a subagent within an active flow:
 - **FAILED** for any CRITICAL finding
 - Always check for **test coverage** on new/changed code
 
-## Evidence Citation Protocol (tier-aware)
-
-**Standalone mode:** If no FORGE task_id was provided in your dispatch prompt, skip \`evidence_map\` calls entirely — provide free-form findings with \`file:line\` citations only.
-
-The Orchestrator runs \`forge_classify\` before dispatching you, and runs the final \`evidence_map({ action: 'gate', task_id })\` after you respond. **Do not create your own task_id or run the gate** — feed into the Orchestrator's existing evidence map.
-
-| Tier | Your responsibility |
-|------|---------------------|
-| Floor | Free-form findings with \`file.ts#Lxx\` citations. No \`evidence_map\` calls required. |
-| Standard | For every CRITICAL or HIGH finding: \`evidence_map({action:'add', task_id, claim, status:'V', receipt:'file.ts#Lxx'})\`. Max 2-4 adds to keep signal high. |
-| Critical | Structured claims for all CRITICAL/HIGH findings (2-4 Verified + receipts) AND tag contract/security claims with \`safety_gate:'commitment'\` or \`safety_gate:'provenance'\`. |
-
-**Every response MUST include:**
-- \`**FORGE Task ID:** <task_id>\` (passed in by Orchestrator, or state "not provided")
-- \`**Tier applied:** Floor | Standard | Critical\`
-- \`**Findings:** <list>\` with \`file:line\` receipts
-- Verdict: \`APPROVED\` | \`CHANGES_REQUESTED\` | \`BLOCKED\`
-
-Do NOT:
-- Create a new \`evidence_map\` (the Orchestrator already did)
-- Run \`evidence_map({action:'gate'})\` yourself — the Orchestrator owns the gate
-- Duplicate findings into the map that weren't CRITICAL/HIGH
+${t()}
 `,"architect-reviewer-base":`# Architect-Reviewer — Shared Base Instructions
 
 > Shared methodology for all Architect-Reviewer variants. Each variant's definition contains only identity and model. **Do not duplicate.**
@@ -704,26 +625,7 @@ Follow the **MANDATORY FIRST ACTION** and **Information Lookup Order** from code
 2. If onboard shows ❌ → Run \`onboard({ path: '.' })\` and wait for completion
 3. If onboard shows ✅ → Read relevant onboard artifacts using \`compact({ path: '<Onboard Directory>/<file>' })\` — especially \`structure.md\`, \`dependencies.md\`, and \`diagram.md\` for architecture context
 
-## Flow Context Bootstrap
-
-When dispatched as a subagent within an active flow:
-
-1. **Withdraw context first** — before any search or file reads:
-   \`\`\`
-  knowledge({ action: 'withdraw', scope: 'flow', profile: 'reviewer', budget: 6000 })
-   \`\`\`
-  This returns pre-analyzed context from prior agents.
-
-2. **Use returned context** — do NOT re-search or re-read files already covered
-3. **\`read_file\` ONLY** for exact lines needed for editing
-4. **Deposit new discoveries:**
-   \`\`\`
-   knowledge({ action: 'remember', scope: 'flow', title: '<discovery>', content: '<details>', category: 'context' })
-   \`\`\`
-
-**Profile:** \`reviewer\`
-
----
+${e(`reviewer`)}
 
 ## Review Workflow
 
@@ -771,28 +673,7 @@ When dispatched as a subagent within an active flow:
 - **BLOCKED** — Fundamental design flaw requiring rethink
 - Always validate **dependency direction** — inner layers must not depend on outer
 
-## Evidence Citation Protocol (tier-aware)
-
-**Standalone mode:** If no FORGE task_id was provided in your dispatch prompt, skip \`evidence_map\` calls entirely — provide free-form findings with \`file:line\` citations only.
-
-The Orchestrator runs \`forge_classify\` before dispatching you, and runs the final \`evidence_map({ action: 'gate', task_id })\` after you respond. **Do not create your own task_id or run the gate** — feed into the Orchestrator's existing evidence map.
-
-| Tier | Your responsibility |
-|------|---------------------|
-| Floor | Free-form findings with \`file.ts#Lxx\` citations. No \`evidence_map\` calls required. |
-| Standard | For every CRITICAL or HIGH finding: \`evidence_map({action:'add', task_id, claim, status:'V', receipt:'file.ts#Lxx'})\`. Max 2-4 adds to keep signal high. |
-| Critical | Structured claims for all CRITICAL/HIGH findings (2-4 Verified + receipts) AND tag contract/security claims with \`safety_gate:'commitment'\` or \`safety_gate:'provenance'\`. |
-
-**Every response MUST include:**
-- \`**FORGE Task ID:** <task_id>\` (passed in by Orchestrator, or state "not provided")
-- \`**Tier applied:** Floor | Standard | Critical\`
-- \`**Findings:** <list>\` with \`file:line\` receipts
-- Verdict: \`APPROVED\` | \`CHANGES_REQUESTED\` | \`BLOCKED\`
-
-Do NOT:
-- Create a new \`evidence_map\` (the Orchestrator already did)
-- Run \`evidence_map({action:'gate'})\` yourself — the Orchestrator owns the gate
-- Duplicate findings into the map that weren't CRITICAL/HIGH
+${t()}
 
 ## Graph-Assisted Layer Verification
 
@@ -1015,7 +896,7 @@ evidence_map({ action: "gate", task_id: "add-user-api" })  → YIELD ✅
 3. **Standard**: \`evidence_map create\` → add 3-8 claims during work → \`evidence_map gate\`
 4. **Critical**: Full 4-phase flow with comprehensive evidence
 5. **After gate**: YIELD = done, HOLD = fix + re-gate, HARD_BLOCK = escalate
-`},t={"execution-state":`# Execution State: {Task Title}
+`},r={"execution-state":`# Execution State: {Task Title}
 
 **Status:** PLANNING | IN_PROGRESS | REVIEW | COMPLETED | BLOCKED
 **Started:** {timestamp}
@@ -1067,4 +948,4 @@ evidence_map({ action: "gate", task_id: "add-user-api" })  → YIELD ✅
 
 ## Alternatives Considered
 {Other approaches evaluated and why they were rejected — keeps the "why not" alongside the "why"}
-`};export{e as PROTOCOLS,t as TEMPLATES};
+`};export{n as PROTOCOLS,r as TEMPLATES};