sinapse-ai 1.19.1 → 1.20.0

package/.claude/CLAUDE.md

@@ -2,7 +2,7 @@
 
 ## Constitution
 
-Full doc: `.sinapse-ai/constitution.md`. Gates auto-block violations.
+Full doc: `.sinapse-ai/constitution.md`. Gates block on the autonomous path; interactive delegation is prompt-level (hook list: Art. VIII).
 
 | Art. | Principle | Severity |
 |------|-----------|----------|
@@ -86,7 +86,7 @@ Use Grep (not grep), Read (not cat), Edit (not sed), Glob (not find). Prefer nat
 ## Context Management
 
 - Rules with `paths:` frontmatter only load when working on matching files
-- Agent handoff compacts to ~379 tokens on switch
+- Agent handoff passes a compact artifact on switch
 - Agent memory in `.sinapse-ai/development/agents/{id}/MEMORY.md`
 - **Memory as hints:** Memory entries are hints, NOT ground truth. Always verify against actual codebase before acting on remembered facts.
 

package/.claude/hooks/enforce-delegation.cjs

@@ -13,21 +13,24 @@
  *
  * Fail-open: if the active agent is unknown, allow (Hook Design Principle #1).
  *
- * Active-agent signal (first match wins):
- *   1. process.env.SINAPSE_ACTIVE_AGENT — explicit signal set by the
- *      orchestration layer when it activates/spawns an agent. This is the
- *      reliable channel; the session-state file is a secondary fallback.
- *   2. .sinapse/session-state.json → { lastAgent } — written by the session
- *      lifecycle when available.
- *   Neither present → unknown agent → fail-open (allow).
+ * Active-agent signal: process.env.SINAPSE_ACTIVE_AGENT, set by the
+ * orchestration layer (SubagentDispatcher) in the env of every agent it
+ * spawns. This is the ONLY signal this hook reads today — see the note on
+ * getActiveAgent() below for why the old session-state.json fallback is gone.
+ * No signal present → unknown agent → fail-open (allow).
  *
- * NOTE (audit 2026-06-11, Article VIII): the AUTONOMOUS path now populates the
- * signal — the SubagentDispatcher sets SINAPSE_ACTIVE_AGENT in the env of every
- * agent it spawns, so this hook enforces correctly when the engine spawns an
- * orchestrator. The INTERACTIVE path (a human typing `@some-orqx` in chat) is
- * intentionally NOT wired here: enforcing it would block a solo operator's own
- * edits, so it stays opt-in (set SINAPSE_ACTIVE_AGENT yourself, or add a
- * prompt-parsing writer) rather than changing chat behavior by default.
+ * Scope, stated honestly (audit AF-20260702 item 2.5 — supersedes and
+ * replaces the 2026-06-11 note this used to carry): the AUTONOMOUS path
+ * (pipeline/motor `sinapse orchestrate`) is genuinely closed — the
+ * SubagentDispatcher sets SINAPSE_ACTIVE_AGENT for every agent it spawns, so
+ * this hook blocks a spawned orchestrator for real. The INTERACTIVE path (a
+ * human typing `@some-orqx` in the same chat session) has no process
+ * boundary to attach an env var to, so nothing sets SINAPSE_ACTIVE_AGENT
+ * there — delegation in that path is enforced as a prompt instruction
+ * (Constitution Art. VIII text + rules injection), not a deterministic gate.
+ * Inferring the active agent from the last Task/slash-command in interactive
+ * chat is a real option but is new engineering, not a bug fix — tracked as
+ * an Onda 3 candidate, intentionally not built as part of this fix.
  *
  * Exception: sinapse-orqx is allowed Write/Edit in .sinapse-ai/ paths
  *            (framework governance — operates above the story layer).
@@ -36,7 +39,6 @@
  */
 
 const fs = require('fs');
-const path = require('path');
 
 // ---------------------------------------------------------------------------
 // Configuration
@@ -72,29 +74,23 @@ function relativize(filePath, root) {
 }
 
 /**
- * Resolve the active agent id. Explicit env signal wins; session-state file is
- * the fallback. Returns the agent ID string or null if unknown (fail-open).
- * @param {string} root - Project root
+ * Resolve the active agent id from the explicit orchestration-layer signal.
+ * Returns the agent ID string, or null if unknown (fail-open).
+ *
+ * History (audit AF-20260702, item 2.5): this used to also fall back to
+ * reading `.sinapse/session-state.json` → { lastAgent }. That fallback was
+ * removed as verified dead code: its only writer — `onCommandComplete()` in
+ * `.sinapse-ai/development/scripts/agent-exit-hooks.js` — is gated behind
+ * `registerHook(agentFramework)`, which has zero call sites anywhere in the
+ * codebase (grep-verified). A reader with no writer is theater, not a real
+ * fallback. If a real writer is ever wired up, add the fallback back
+ * alongside it — don't resurrect a reader that nothing feeds.
+ *
  * @returns {string|null}
  */
-function getActiveAgent(root) {
-  // 1. Explicit, reliable signal from the orchestration layer.
+function getActiveAgent() {
   const envAgent = (process.env.SINAPSE_ACTIVE_AGENT || '').trim();
-  if (envAgent) return envAgent;
-
-  // 2. Session-state file fallback. Validate the resolved path stays within the
-  //    project (defense-in-depth against a manipulated root — P2-003).
-  const sessionStatePath = path.join(root, '.sinapse', 'session-state.json');
-  const resolvedRoot = path.resolve(root);
-  if (!path.resolve(sessionStatePath).startsWith(resolvedRoot)) {
-    return null;
-  }
-  try {
-    const state = JSON.parse(fs.readFileSync(sessionStatePath, 'utf8'));
-    return state.lastAgent || null;
-  } catch {
-    return null; // fail-open
-  }
+  return envAgent || null;
 }
 
 function isOrchestrator(agentId) {
@@ -125,7 +121,7 @@ function main() {
   }
 
   const root = projectRoot();
-  const agentId = getActiveAgent(root);
+  const agentId = getActiveAgent();
 
   // If no agent tracked or not an orchestrator, allow
   if (!agentId || !isOrchestrator(agentId)) {

package/.claude/rules/agent-handoff.md

@@ -7,7 +7,7 @@ paths:
 
 ## Purpose
 
-Prevent context window accumulation when switching between SINAPSE agents (`@agent` commands). Each agent switch compacts the previous agent's full persona into a structured handoff artifact (~379 tokens) instead of retaining the full definition (~3-5K tokens).
+Preserve working continuity when switching between SINAPSE agents (`@agent` commands). Each agent switch passes forward a structured handoff artifact — active story, key decisions, files touched, blockers, next action — instead of the previous agent's full persona. (Context-window accounting was retired: with 1M-class windows and native auto-compact, the old token arithmetic no longer applies — see DEC-05.)
 
 ## When This Applies
 
@@ -61,15 +61,10 @@ The incoming agent receives:
 2. Include the scratchpad path in the handoff artifact `scratchpad_path` field
 3. Keep each file under 2KB (focused insights, not logs)
 
-### Compaction Limits
+### Artifact discipline
 
-| Limit | Value |
-|-------|-------|
-| Max handoff artifact size | 500 tokens |
-| Max retained agent summaries | 3 (oldest discarded on 4th switch) |
-| Max decisions in artifact | 5 |
-| Max files_modified entries | 10 |
-| Max blockers | 3 |
+Keep the artifact SHORT and factual (a screenful): up to 5 decisions, 10 files,
+3 blockers. It is a signal for the incoming agent, not a log.
 
 ### What to Preserve (ALWAYS include)
 
@@ -91,7 +86,9 @@ The incoming agent receives:
 
 ## Storage
 
-Handoff artifacts are stored at `.sinapse/handoffs/` (runtime, gitignored). Format: `handoff-{from}-to-{to}-{timestamp}.yaml`.
+Persisting the artifact to disk is OPTIONAL (`.sinapse/handoffs/`, runtime,
+gitignored) — measured 2026-07-02: zero artifacts ever written; the artifact's value
+is in the conversation, not the file.
 
 ## Template Reference
 
@@ -101,14 +98,6 @@ Full template: `.sinapse-ai/development/templates/agent-handoff-tmpl.yaml`
 
 Session flow: `@sm` creates story → `@dev` implements → `@qa` reviews
 
-After `@sm` → `@dev` switch:
-- `@sm` full persona (~3K tokens) is **discarded**
-- Handoff artifact (~379 tokens) is **retained**: story ID, decisions, files, next action
-- `@dev` full persona (~5K tokens) is **loaded**
-- **Total context: ~5.4K** instead of ~8K (33% reduction per switch)
-
-After `@dev` → `@qa` switch:
-- `@dev` full persona is **discarded**
-- `@dev` handoff artifact is **retained** alongside `@sm` handoff
-- `@qa` full persona is **loaded**
-- **Total context: ~5.2K** instead of ~12K (57% reduction after 2 switches)
+After `@sm` → `@dev` switch: `@dev` starts from the handoff artifact (story ID,
+decisions, files, next action) — it does not re-derive `@sm`'s reasoning, and it
+does not need `@sm`'s persona.

package/.claude/rules/mandatory-delegation.md

@@ -62,7 +62,7 @@ The orchestrator MUST still delegate. The correct response pattern is:
 | Midia paga, ads | @paidmedia-orqx (Apex) |
 | Produto, roadmap | @product-orqx (Vector) |
 | Pesquisa, inteligencia | @research-orqx (Prism) |
-| Claude Code mastery | @swarm-orqx (Nexus) |
+| Claude Code mastery | @swarm-orqx (Relay) |
 | Conselho estrategico | @council-orqx (Zenith) |
 | Storytelling, pitch | @storytelling-orqx (Arc) |
 | Cybersecurity | @cyber-orqx (Fortress) |

package/.claude/rules/token-economy.md

@@ -14,7 +14,9 @@
 | Manual `/compact` | Troca de agente; pós-leitura de arquivo grande |
 | Pre-agent-switch | Handoff artifact (~379 tok) via `agent-handoff.md` |
 
-60%: acima disso perde coerência sobre instruções iniciais ("context amnesia").
+60%: acima disso perde coerência sobre instruções iniciais ("context amnesia"). Medido/calibrado pra janela **200K**; pra janela **1M** (`models.registry`) o gatilho equivalente está **pendente de medição** — não fixar número novo sem medir primeiro (compactar cedo demais destrói contexto útil).
+
+**Nota (onda2-p4):** o trigger executável em código (`context-tracker.js: shouldCompact`) já é dual — dispara no MENOR entre 60% da janela e um teto absoluto de ~165K tokens de histórico vivo (interino, ponto médio da faixa 150-180K do item 2.12). Em janela 200K o resultado é idêntico ao de sempre (120K < 165K, zero regressão); o valor absoluto segue sujeito a recalibração quando a medição da janela 1M citada acima acontecer.
 
 ---
 
@@ -22,7 +24,7 @@
 
 **Regra zero:** Execute direto sempre que der. Sub-agente custa ~20K mínimo.
 
-**Opus 4.7:** Effort default `xhigh`. `thinking_budget` fixo NÃO suportado — adaptive.
+**Modelo frontier atual (família Opus/Fable):** Effort default `xhigh`.
 
 | Task | Modelo | Effort |
 |---|---|---|
@@ -38,7 +40,7 @@
 
 ---
 
-## 3. Subagent Threshold (Opus 4.7)
+## 3. Subagent Threshold (frontier atual)
 
 Spawn APENAS se: `>= 8 tool calls` previstos OU fan-out paralelo real. Abaixo → inline.
 
@@ -55,7 +57,6 @@ Spawn APENAS se: `>= 8 tool calls` previstos OU fan-out paralelo real. Abaixo
 | Sub-agente pra task <8 tool calls | Inline |
 | Sequential reads independentes | Paralelo (uma mensagem, N calls) |
 | Cole payload bruto no raciocínio | Extrai só relevante |
-| `thinking_budget` fixo em 4.7 | Adaptive — não suportado |
 | Preamble ("Claro!", "Vou te ajudar...") | Ação direta |
 | Trailing summary ("Em resumo...") | Só próximo passo, 1 linha |
 | Narração de plano | Executa em paralelo |
@@ -121,7 +122,9 @@ Default: tabela ou bullet.
 
 ---
 
-## 8. Budget de Contexto (200K)
+## 8. Budget de Contexto — por janela
+
+### Janela 200K (medido)
 
 | Alocação | Target | % |
 |---|---:|---:|
@@ -133,6 +136,10 @@ Default: tabela ou bullet.
 
 Working memory >80K = sinal pra compactar.
 
+### Janela 1M
+
+A mesma distribuição percentual escalaria proporcionalmente (ex.: working memory ~≤400K), mas o gatilho de compactação em si para a janela 1M está **pendente de medição** (ver §1) — não tratar os valores escalados como threshold validado antes de medir.
+
 ---
 
 ## 9. Memory Anti-Patterns

package/.sinapse-ai/constitution.md

@@ -212,6 +212,8 @@ Orquestradores (sinapse-orqx e todos os *-orqx) NUNCA executam trabalho de domí
 
 **Gate:** Qualquer resposta de orquestrador que contenha trabalho de domínio direto sem delegação é uma violação constitucional.
 
+> **Enforcement (honesto):** o bloqueio determinístico deste artigo vale hoje no **caminho autônomo** (pipeline/motor `sinapse orchestrate`) — o `SubagentDispatcher` grava `SINAPSE_ACTIVE_AGENT` no ambiente de cada agente que ele spawna, e `enforce-delegation.cjs` bloqueia Write/Edit/Bash de um `*-orqx` fora da exceção de governança. No **chat interativo** (humano digitando `@algum-orqx` na mesma sessão) não existe esse sinal de agente ativo — a delegação é **instrução de prompt** (reforçada por injeção de contexto), não bloqueio de hook; o hook fica fail-open por design (ver comentário em `enforce-delegation.cjs`). O que É bloqueio determinístico em QUALQUER modo, porque não depende de identidade de agente: `enforce-story-gate.cjs`/`doc-first-gate.cjs` (Art. III), `secret-scanning.cjs` (Art. X), `enforce-git-push-authority.sh` (Art. IX), `enforce-framework-boundary.cjs` (quando `frameworkProtection: true`), `verify-packages.cjs`, `sql-governance.py`, `mind-clone-governance.py`.
+
 **Rule file:** `.claude/rules/mandatory-delegation.md`
 
 ---

package/.sinapse-ai/core/atlas/flows-pt.js

@@ -10,6 +10,12 @@
  * Drift guard: a test asserts every id in FRAMEWORK_FLOWS has an entry here, so
  * adding a flow without translating it fails CI.
  *
+ * Sync note (AF-20260702 item 2.10, CONFIRMED): the 'model-routing' entry's
+ * tiers/efforts must stay consistent with `.claude/rules/token-economy.md` §2
+ * and flows.js/render-markdown.js — verified in sync as of that audit, hand-kept
+ * (no automated cross-check). Recommendation (deferred, Article XI sign-off):
+ * single `.sinapse-ai/data/*.yaml` source for all 3 renderers.
+ *
  * @module core/atlas/flows-pt
  */
 

package/.sinapse-ai/core/atlas/flows.js

@@ -11,6 +11,13 @@
  * is easy to extend. Mermaid is hand-written and kept simple (plain node labels,
  * no reserved chars) so it renders everywhere.
  *
+ * Sync note (AF-20260702 item 2.10, CONFIRMED): the 'model-routing' flow's
+ * tiers/efforts must stay consistent with `.claude/rules/token-economy.md` §2
+ * and render-markdown.js's modelRouting() table — verified in sync as of that
+ * audit, but hand-kept (no automated cross-check). Recommendation (deferred,
+ * Article XI sign-off): single `.sinapse-ai/data/*.yaml` source for all 3
+ * renderers (this file, flows-pt.js, render-markdown.js).
+ *
  * @module core/atlas/flows
  */
 

package/.sinapse-ai/core/atlas/render-markdown.js

@@ -73,6 +73,14 @@ This atlas is itself generated by \`sinapse atlas\`; its counts are read from di
 so they are always exact.`;
 }
 
+// Sync note (AF-20260702 item 2.10, CONFIRMED): this table is hand-kept in
+// sync with `.claude/rules/token-economy.md` §2 — verified consistent (no
+// version pin drift) at the time of that audit. It is duplicated 3x (here,
+// flows.js, flows-pt.js) plus the generated OPERATING-ATLAS.md, and no
+// automated check compares them against the rule, so future drift would pass
+// unnoticed. Recommendation (deferred — L1 change requires Article XI
+// architecture sign-off): extract tiers/efforts into a single
+// `.sinapse-ai/data/*.yaml` consumed by all 3 renderers.
 function modelRouting() {
   return `## 4. Model routing (cheapest model that solves it)
 

package/.sinapse-ai/core/doctor/checks/constitution-consistency.js

@@ -35,11 +35,18 @@ const KEY_ARTICLES = [
 
 /**
  * Files that should reference Constitution articles
+ *
+ * Includes the install template (AF-20260702 item 1.7): the generated
+ * .claude/CLAUDE.md is a MERGE of this template into the user's file, so a
+ * stale/incomplete article table here regresses every fresh install even
+ * when the repo's own .claude/CLAUDE.md is correct. Without this entry the
+ * check was blind to drift in the template itself.
  */
 const CONSUMER_FILES = [
   '.claude/CLAUDE.md',
   'AGENTS.md',
   '.synapse/constitution',
+  '.sinapse-ai/product/templates/ide-rules/claude-rules.md',
 ];
 
 /**

package/.sinapse-ai/core/execution/autonomous-build-loop.js

@@ -535,8 +535,11 @@ class AutonomousBuildLoop extends EventEmitter {
       });
     }
 
-    // Default: simulate execution (for testing)
-    this.log(`Executing subtask ${subtask.id} (iteration ${iteration})`, 'info');
+    // Honesty invariant (epic: orchestration-consolidation, audit AF-20260702
+    // item 1.12) — no executor wired means no real work happened. Do NOT
+    // fabricate success; report a stub so callers never mistake "nothing ran"
+    // for real work (mirrors the same fix already applied to agent-invoker.js).
+    this.log(`No executor wired for subtask ${subtask.id} (iteration ${iteration}) — returning stub`, 'warn');
 
     // Check for verification command
     if (subtask.verification && this.config.verificationEnabled) {
@@ -550,8 +553,11 @@ class AutonomousBuildLoop extends EventEmitter {
     }
 
     return {
-      success: true,
-      filesModified: subtask.files || [],
+      success: false,
+      status: 'stub',
+      stub: true,
+      error: 'No executor wired into AutonomousBuildLoop — subtask not actually executed.',
+      filesModified: [],
     };
   }
 

package/.sinapse-ai/core/execution/build-orchestrator.js

@@ -77,6 +77,10 @@ const DEFAULT_CONFIG = {
   runQA: true,
   autoMerge: true,
   cleanupOnSuccess: true,
+  // Story onda2-p3: stop right after the REAL plan is generated (no build loop,
+  // no QA, no merge). Powers `sinapse plan` — the hybrid's measured value
+  // (spec + plan for ONE story) as its own product surface.
+  planOnly: false,
 
   // Execution
   maxIterations: 10,
@@ -183,14 +187,48 @@ class BuildOrchestrator extends EventEmitter {
       // Phase 1: Initialize
       await this.runPhase(ctx, Phase.INIT, () => this.phaseInit(ctx));
 
-      // Phase 2: Create worktree (optional)
-      if (config.useWorktree && WorktreeManager) {
+      // Phase 2: Create worktree (optional — never for plan-only runs, which
+      // read the story and write the plan but touch no code)
+      if (config.useWorktree && !config.planOnly && WorktreeManager) {
         await this.runPhase(ctx, Phase.WORKTREE, () => this.phaseWorktree(ctx));
       }
 
       // Phase 3: Load/Generate plan
       await this.runPhase(ctx, Phase.PLAN, () => this.phasePlan(ctx));
 
+      // Story onda2-p3 — plan-only phase limit (`sinapse plan`): stop right
+      // after the REAL plan. No build loop, no QA, no merge. The plan is
+      // persisted STORY-SCOPED (docs/stories/<id>/plan/implementation.yaml) —
+      // deliberately not the shared <root>/plan/ path, which is the measured
+      // cross-story contamination vector (see KNOWN-LIMITATIONS.md).
+      if (config.planOnly) {
+        const planPath = this.persistPlan(ctx);
+        await this.runPhase(ctx, Phase.REPORT, () => this.phaseReport(ctx));
+
+        const duration = Date.now() - startTime;
+        this.emit(OrchestratorEvent.BUILD_COMPLETED, {
+          storyId,
+          duration,
+          success: true,
+          report: ctx.reportPath,
+          planOnly: true,
+        });
+
+        return {
+          success: true,
+          planOnly: true,
+          storyId,
+          duration,
+          phases: ctx.phases,
+          reportPath: ctx.reportPath,
+          plan: ctx.plan,
+          planPath,
+          // Honest by construction: a plan-only run writes no implementation
+          // files — downstream gates must never read this as a real build.
+          filesModified: [],
+        };
+      }
+
       // Phase 4: Execute (the actual build) - THIS IS THE KEY PART
       await this.runPhase(ctx, Phase.EXECUTE, () => this.phaseExecute(ctx));
 
@@ -231,6 +269,11 @@ class BuildOrchestrator extends EventEmitter {
         // quality gate can inspect its honesty (degraded/stub/subtasks). Without this
         // the epic4_to_epic6 gate has nothing real to bite on.
         plan: ctx.plan,
+        // epic: empty-build-honesty — surface the REAL files the build wrote/modified
+        // (collected from the build loop's per-subtask results). Without this the
+        // downstream `implementation_exists` gate cannot tell a real build apart from
+        // an empty "success" that touched zero code files.
+        filesModified: this._collectModifiedFiles(ctx),
       };
     } catch (error) {
       ctx.errors.push(error);
@@ -263,6 +306,32 @@ class BuildOrchestrator extends EventEmitter {
     }
   }
 
+  /**
+   * Collect the real files the build wrote/modified from the build-loop result.
+   *
+   * epic: empty-build-honesty — the per-subtask results carry `filesModified`
+   * (extracted from the agent output). This flattens + de-duplicates them into a
+   * single honest list. Returns [] when nothing was touched (an empty build), which
+   * is precisely the signal the `implementation_exists` gate needs to block.
+   *
+   * @param {Object} ctx - Build context ({ result: { results: [...] } })
+   * @returns {string[]} De-duplicated list of modified files
+   * @private
+   */
+  _collectModifiedFiles(ctx) {
+    const results = ctx && ctx.result && Array.isArray(ctx.result.results) ? ctx.result.results : [];
+    const files = [];
+    for (const r of results) {
+      const list = r && Array.isArray(r.filesModified) ? r.filesModified : [];
+      for (const f of list) {
+        if (typeof f === 'string' && f.trim() !== '' && !files.includes(f)) {
+          files.push(f);
+        }
+      }
+    }
+    return files;
+  }
+
   /**
    * Run a phase with event emission and error handling
    */
@@ -388,6 +457,39 @@ class BuildOrchestrator extends EventEmitter {
     return { source: 'generated', subtasks: ctx.plan.phases?.length || 0 };
   }
 
+  /**
+   * Persist the generated plan as YAML, STORY-SCOPED
+   * (docs/stories/<storyId>/plan/implementation.yaml).
+   *
+   * Story onda2-p3: this is the durable artifact `sinapse plan` delivers. The
+   * story-scoped location is the canonical path Epic 4 already searches first
+   * (`_findOrCreatePlan`) — and deliberately NOT the shared `<root>/plan/`
+   * directory, whose non-scoped state is the measured cross-story contamination
+   * vector (KNOWN-LIMITATIONS.md, bug 1).
+   *
+   * @param {Object} ctx - Build context ({ storyId, config, plan })
+   * @returns {string} Absolute path of the persisted plan
+   */
+  persistPlan(ctx) {
+    const yaml = require('js-yaml');
+    const planPath = path.join(
+      this.rootPath,
+      ctx.config.storiesDir || DEFAULT_CONFIG.storiesDir,
+      ctx.storyId,
+      'plan',
+      'implementation.yaml',
+    );
+    fs.mkdirSync(path.dirname(planPath), { recursive: true });
+    const header = `# Implementation Plan: ${ctx.storyId}\n# Generated: ${new Date().toISOString()}\n\n`;
+    fs.writeFileSync(
+      planPath,
+      header + yaml.dump(ctx.plan || {}, { lineWidth: -1, noRefs: true }),
+      'utf-8',
+    );
+    ctx.planPath = planPath;
+    return planPath;
+  }
+
   /**
    * Phase 4: Execute - THE MAIN BUILD LOOP
    */

package/.sinapse-ai/core/execution/context-injector.js

@@ -2,6 +2,8 @@
  * Context Injector
  * Story 10.3 - Parallel Agent Execution
  *
+ * @abandoned-path — ver docs/epics/epic-ultra-optimization/decisions/DEC-03 (2026-07-02)
+ *
  * Injects rich context into subagent prompts including:
  * - Project context
  * - Relevant files

package/.sinapse-ai/core/execution/parallel-executor.js

@@ -2,6 +2,8 @@
  * Parallel Executor (PROVIDER-level)
  * Story GEMINI-INT.17 - Multi-Agent Parallel Execution
  *
+ * @abandoned-path — ver docs/epics/epic-ultra-optimization/decisions/DEC-03 (2026-07-02)
+ *
  * Executes Claude and Gemini in parallel for improved quality and reliability.
  *
  * NOT a duplicate of `core/orchestration/parallel-executor.js` (audit 2026-06-11

package/.sinapse-ai/core/execution/parallel-monitor.js

@@ -2,6 +2,8 @@
  * Parallel Execution Monitor
  * Story 10.6 - Parallel Agent Execution
  *
+ * @abandoned-path — ver docs/epics/epic-ultra-optimization/decisions/DEC-03 (2026-07-02)
+ *
  * Provides real-time visibility into parallel executions
  * with CLI commands and dashboard integration.
  */

package/.sinapse-ai/core/execution/rate-limit-manager.js

@@ -2,6 +2,8 @@
  * Rate Limit Manager
  * Story 11.3 - Enhanced Capabilities
  *
+ * @abandoned-path — ver docs/epics/epic-ultra-optimization/decisions/DEC-03 (2026-07-02)
+ *
  * Handles API rate limits gracefully with exponential backoff,
  * preemptive throttling, and comprehensive metrics.
  */

package/.sinapse-ai/core/execution/result-aggregator.js

@@ -2,6 +2,8 @@
  * Result Aggregator
  * Story 10.5 - Parallel Agent Execution
  *
+ * @abandoned-path — ver docs/epics/epic-ultra-optimization/decisions/DEC-03 (2026-07-02)
+ *
  * Aggregates results from parallel task executions,
  * detects conflicts, and generates consolidated reports.
  */

package/.sinapse-ai/core/execution/semantic-merge-engine.js

@@ -2,6 +2,8 @@
  * Semantic Merge Engine
  * Story 8.3 - Enhanced Implementation
  *
+ * @abandoned-path — ver docs/epics/epic-ultra-optimization/decisions/DEC-03 (2026-07-02)
+ *
  * AI-powered semantic merge system for resolving conflicts between
  * parallel agent work. Analyzes code at semantic level (functions, imports,
  * classes) rather than line-by-line to enable intelligent merge resolution.

package/.sinapse-ai/core/execution/wave-executor.js

@@ -2,6 +2,8 @@
  * Wave Executor
  * Story 10.1 - Parallel Agent Execution
  *
+ * @abandoned-path — ver docs/epics/epic-ultra-optimization/decisions/DEC-03 (2026-07-02)
+ *
  * Executes task waves in parallel, leveraging the WaveAnalyzer
  * for dependency-aware scheduling.
  */

package/.sinapse-ai/core/health-check/checks/project/constitution-consistency.js

@@ -34,11 +34,18 @@ const EXPECTED_ARTICLES = [
 
 /**
  * Files that MUST reference the Constitution articles
+ *
+ * Includes the install template (AF-20260702 item 1.7): the generated
+ * .claude/CLAUDE.md is a MERGE of this template into the user's file, so a
+ * stale/incomplete article table here regresses every fresh install even
+ * when the repo's own .claude/CLAUDE.md is correct. Without this entry the
+ * check was blind to drift in the template itself.
  */
 const CONSTITUTION_CONSUMERS = [
   { path: '.claude/CLAUDE.md', label: 'Project CLAUDE.md' },
   { path: 'AGENTS.md', label: 'AGENTS.md' },
   { path: '.synapse/constitution', label: 'Generated Constitution Domain' },
+  { path: '.sinapse-ai/product/templates/ide-rules/claude-rules.md', label: 'Install Template (claude-rules.md)' },
 ];
 
 /**
@@ -141,7 +148,11 @@ class ConstitutionConsistencyCheck extends BaseCheck {
     }
 
     if (issues.length <= 2) {
-      return this.warn(`${issues.length} minor consistency issue(s) found`, {
+      // BaseCheck exposes warning(), not warn() — this call previously threw
+      // "this.warn is not a function" any time exactly 1-2 issues were found
+      // (uncaught until AF-20260702 item 1.7 added a test that exercises
+      // this branch).
+      return this.warning(`${issues.length} minor consistency issue(s) found`, {
         details,
         recommendation: issues.join('; '),
       });