sinapse-ai 1.19.2 → 1.20.1

package/.sinapse-ai/product/templates/ide-rules/claude-rules.md

@@ -1,6 +1,6 @@
 # SINAPSE Development Rules for Claude Code
 
-You are working with SINAPSE, an AI-Orchestrated System for Full Stack Development.
+SINAPSE orquestra agentes de IA em squads para fluxos de desenvolvimento complexos.
 
 <!-- SINAPSE-MANAGED-START: core-framework -->
 ## Core Framework Understanding
@@ -11,13 +11,9 @@ SINAPSE is a meta-framework that orchestrates AI agents to handle complex develo
 <!-- SINAPSE-MANAGED-START: constitution -->
 ## Constitution
 
-O SINAPSE possui uma **Constitution formal** com princípios inegociáveis e gates automáticos.
+O SINAPSE possui uma **Constitution formal** com principios inegociaveis (`.sinapse-ai/constitution.md`). Gates automaticos bloqueiam violacoes no caminho autonomo (pipeline/motor); no chat interativo a delegacao (Art. VIII) e instrucao de prompt, nao bloqueio de hook — ver Art. VIII na Constitution para a lista exata do que e deterministico.
 
-**Documento completo:** `.sinapse-ai/constitution.md`
-
-**Princípios fundamentais:**
-
-| Artigo | Princípio | Severidade |
+| Artigo | Principio | Severidade |
 |--------|-----------|------------|
 | I | CLI First | NON-NEGOTIABLE |
 | II | Agent Authority | NON-NEGOTIABLE |
@@ -29,334 +25,109 @@ O SINAPSE possui uma **Constitution formal** com princípios inegociáveis e gat
 | VIII | Mandatory Delegation | NON-NEGOTIABLE |
 | IX | Safe Collaboration | NON-NEGOTIABLE |
 | X | Security & Data Protection | NON-NEGOTIABLE |
-
-**Gates automáticos bloqueiam violações.** Consulte a Constitution para detalhes completos.
+| XI | Conservative Default | MUST |
 <!-- SINAPSE-MANAGED-END: constitution -->
 
 <!-- SINAPSE-MANAGED-START: sistema-de-agentes -->
 ## Sistema de Agentes
 
-### Ativação de Agentes
-Use `@agent-name` ou `/SINAPSE:agents:agent-name`:
-
-| Agente | Persona | Escopo Principal |
-|--------|---------|------------------|
-| `@developer` | Dex | Implementação de código |
-| `@quality-gate` | Quinn | Testes e qualidade |
-| `@architect` | Aria | Arquitetura e design técnico |
-| `@project-lead` | Morgan | Product Management |
-| `@product-lead` | Pax | Product Owner, stories/epics |
-| `@sprint-lead` | River | Scrum Master |
-| `@analyst` | Alex | Pesquisa e análise |
-| `@data-engineer` | Dara | Database design |
-| `@ux-design-expert` | Uma | UX/UI design |
-| `@devops` | Gage | CI/CD, git push (EXCLUSIVO) |
-
-### Comandos de Agentes
-Use prefixo `*` para comandos:
-- `*help` - Mostrar comandos disponíveis
-- `*create-story` - Criar story de desenvolvimento
-- `*task {name}` - Executar task específica
-- `*exit` - Sair do modo agente
+Ative com `@agent-name`; comandos usam prefixo `*`.
+
+| Agente | Persona | Escopo |
+|--------|---------|--------|
+| `@developer` | Pixel | Codigo |
+| `@quality-gate` | Litmus | Qualidade |
+| `@architect` | Stratum | Arquitetura |
+| `@project-lead` | Beacon | Product Management |
+| `@product-lead` | Axis | Product Owner |
+| `@sprint-lead` | Sync | Scrum Master |
+| `@analyst` | Scope | Pesquisa |
+| `@data-engineer` | Tensor | Database |
+| `@ux-design-expert` | Mosaic | UX/UI |
+| `@devops` | Pipeline | CI/CD, git push (EXCLUSIVO) |
 <!-- SINAPSE-MANAGED-END: sistema-de-agentes -->
 
 <!-- SINAPSE-MANAGED-START: agent-system -->
 ## Agent System
 
-### Agent Activation
-- Agents are activated with @agent-name syntax: @developer, @quality-gate, @architect, @project-lead, @product-lead, @sprint-lead, @analyst
-- The master agent is activated with @sinapse-orqx
-- Agent commands use the * prefix: *help, *create-story, *task, *exit
-
-### Agent Context
-When an agent is active:
-- Follow that agent's specific persona and expertise
-- Use the agent's designated workflow patterns
-- Maintain the agent's perspective throughout the interaction
+Master agent: `@sinapse-orqx`. Stay in persona until `*exit`.
 <!-- SINAPSE-MANAGED-END: agent-system -->
 
 ## Development Methodology
 
-### Documentation-First Development (NON-NEGOTIABLE)
-1. **Documentation pipeline is AUTOMATIC** - Every briefing triggers: Epic → Story → Validation → Implementation
-2. **No code without validated story** - Story must be in `docs/stories/` with status >= Ready
-3. **Update progress** - Mark checkboxes as tasks complete: [ ] → [x]
-4. **Track changes** - Maintain the File List section in the story
-5. **Follow criteria** - Implement exactly what the acceptance criteria specify
-6. **Delegation is mandatory** - Orchestrators NEVER execute domain work, they ALWAYS delegate to specialists
-
-### Code Standards
-- Write clean, self-documenting code
-- Follow existing patterns in the codebase
-- Include comprehensive error handling
-- Add unit tests for all new functionality
-- Use TypeScript/JavaScript best practices
-
-### Testing Requirements
-- Run all tests before marking tasks complete
-- Ensure linting passes: `npm run lint`
-- Verify type checking: `npm run typecheck`
-- Add tests for new features
-- Test edge cases and error scenarios
+Documentation-First (NON-NEGOTIABLE): Epic -> Story -> Validation -> Implementation, automatico. No code sem story em `docs/stories/` com status >= Ready.
 
 <!-- SINAPSE-MANAGED-START: framework-structure -->
 ## SINAPSE Framework Structure
 
-```
-sinapse-ai/
-├── agents/         # Agent persona definitions (YAML/Markdown)
-├── tasks/          # Executable task workflows
-├── workflows/      # Multi-step workflow definitions
-├── templates/      # Document and code templates
-├── checklists/     # Validation and review checklists
-└── rules/          # Framework rules and patterns
-
-docs/
-├── stories/        # Development stories (numbered)
-├── prd/            # Product requirement documents
-├── architecture/   # System architecture documentation
-└── guides/         # User and developer guides
-```
+Framework core em `.sinapse-ai/`; trabalho do projeto em `docs/` (stories, prd, architecture).
 <!-- SINAPSE-MANAGED-END: framework-structure -->
 
 <!-- SINAPSE-MANAGED-START: framework-boundary -->
 ## Framework vs Project Boundary
 
-O SINAPSE usa um modelo de 4 camadas (L1-L4) para separar artefatos do framework e do projeto. Deny rules em `.claude/settings.json` reforçam isso deterministicamente.
-
-| Camada | Mutabilidade | Paths | Notas |
-|--------|-------------|-------|-------|
-| **L1** Framework Core | NEVER modify | `.sinapse-ai/core/`, `.sinapse-ai/constitution.md`, `bin/sinapse.js`, `bin/sinapse-init.js` | Protegido por deny rules |
-| **L2** Framework Templates | NEVER modify | `.sinapse-ai/development/tasks/`, `.sinapse-ai/development/templates/`, `.sinapse-ai/development/checklists/`, `.sinapse-ai/development/workflows/`, `.sinapse-ai/infrastructure/` | Extend-only |
-| **L3** Project Config | Mutable (exceptions) | `.sinapse-ai/data/`, `agents/*/MEMORY.md`, `core-config.yaml` | Allow rules permitem |
-| **L4** Project Runtime | ALWAYS modify | `docs/stories/`, `packages/`, `squads/`, `tests/` | Trabalho do projeto |
+Modelo de 4 camadas (L1-L4) separa framework e projeto (`.claude/settings.json` reforca via deny rules).
 
-**Toggle:** `core-config.yaml` → `boundary.frameworkProtection: true/false` controla se deny rules são ativas (default: true para projetos, false para contribuidores do framework).
+| Camada | Mutabilidade | Exemplo |
+|--------|-------------|---------|
+| **L1** Framework Core | NEVER modify | `.sinapse-ai/core/` |
+| **L2** Framework Templates | NEVER modify | `.sinapse-ai/development/tasks/` |
+| **L3** Project Config | Mutable (exceptions) | `core-config.yaml` |
+| **L4** Project Runtime | ALWAYS modify | `docs/stories/`, `packages/` |
 
-> **Referência formal:** `.claude/settings.json` (deny/allow rules), `.claude/rules/agent-authority.md`
+**Toggle:** `boundary.frameworkProtection` em `core-config.yaml` (default true para projetos, false para contribuidores do framework).
 <!-- SINAPSE-MANAGED-END: framework-boundary -->
 
 <!-- SINAPSE-MANAGED-START: rules-system -->
 ## Rules System
 
-O SINAPSE carrega regras contextuais de `.claude/rules/` automaticamente. Regras com frontmatter `paths:` só carregam quando arquivos correspondentes são editados.
-
-| Rule File | Description |
-|-----------|-------------|
-| `agent-authority.md` | Agent delegation matrix and exclusive operations |
-| `agent-handoff.md` | Agent switch compaction protocol for context optimization |
-| `agent-memory-imports.md` | Agent memory lifecycle and CLAUDE.md ownership |
-| `coderabbit-integration.md` | Automated code review integration rules |
-| `ids-principles.md` | Incremental Development System principles |
-| `mcp-usage.md` | MCP server usage rules and tool selection priority |
-| `story-lifecycle.md` | Story status transitions and quality gates |
-| `workflow-execution.md` | 4 primary workflows (SDC, QA Loop, Spec Pipeline, Brownfield) |
+Carregadas de `.claude/rules/` automaticamente:
 
-> **Diretório:** `.claude/rules/` — rules são carregadas automaticamente pelo Claude Code quando relevantes.
+`agent-authority.md` · `agent-handoff.md` · `agent-memory-imports.md` · `coderabbit-integration.md` · `ids-principles.md` · `mcp-usage.md` · `story-lifecycle.md` · `workflow-execution.md`
 <!-- SINAPSE-MANAGED-END: rules-system -->
 
 <!-- SINAPSE-MANAGED-START: code-intelligence -->
 ## Code Intelligence
 
-O SINAPSE possui um sistema de code intelligence opcional que enriquece operações com dados de análise de código.
-
-| Status | Descrição | Comportamento |
-|--------|-----------|---------------|
-| **Configured** | Provider ativo e funcional | Enrichment completo disponível |
-| **Fallback** | Provider indisponível | Sistema opera normalmente sem enrichment — graceful degradation |
-| **Disabled** | Nenhum provider configurado | Funcionalidade de code-intel ignorada silenciosamente |
-
-**Graceful Fallback:** Code intelligence é sempre opcional. `isCodeIntelAvailable()` verifica disponibilidade antes de qualquer operação. Se indisponível, o sistema retorna o resultado base sem modificação — nunca falha.
-
-**Diagnóstico:** `sinapse doctor` inclui check de code-intel provider status.
-
-> **Referência:** `.sinapse-ai/core/code-intel/` — provider interface, enricher, client
+Opcional: **Configured** (ativo), **Fallback** (indisponivel, degrada), **Disabled** (sem provider). `isCodeIntelAvailable()` verifica antes de operar — nunca falha se ausente.
 <!-- SINAPSE-MANAGED-END: code-intelligence -->
 
 <!-- SINAPSE-MANAGED-START: graph-dashboard -->
 ## Graph Dashboard
 
-O CLI `sinapse graph` visualiza dependências, estatísticas de entidades e status de providers.
-
-### Comandos
-
 ```bash
-sinapse graph --deps                        # Dependency tree (ASCII)
-sinapse graph --deps --format=json          # Output como JSON
-sinapse graph --deps --format=html          # Interactive HTML (abre browser)
-sinapse graph --deps --format=mermaid       # Mermaid diagram
-sinapse graph --deps --format=dot           # DOT format (Graphviz)
-sinapse graph --deps --watch                # Live mode com auto-refresh
-sinapse graph --deps --watch --interval=10  # Refresh a cada 10 segundos
-sinapse graph --stats                       # Entity stats e cache metrics
+sinapse graph --deps                        # Dependency tree
+sinapse graph --deps --format=json          # JSON
+sinapse graph --deps --format=html          # Interactive HTML
+sinapse graph --deps --watch                # Auto-refresh
+sinapse graph --stats                       # Entity stats
 ```
-
-**Formatos de saída:** ascii (default), json, dot, mermaid, html
-
-> **Referência:** `.sinapse-ai/core/graph-dashboard/` — CLI, renderers, data sources
 <!-- SINAPSE-MANAGED-END: graph-dashboard -->
 
 ## Workflow Execution
 
-### Task Execution Pattern
-1. Read the complete task/workflow definition
-2. Understand all elicitation points
-3. Execute steps sequentially
-4. Handle errors gracefully
-5. Provide clear feedback
-
-### Interactive Workflows
-- Workflows with `elicit: true` require user input
-- Present options clearly
-- Validate user responses
-- Provide helpful defaults
+Leia a task completa, execute os passos em sequencia, trate erros com mensagens acionaveis.
 
 ## Best Practices
 
-### When implementing features:
-- Check existing patterns first
-- Reuse components and utilities
-- Follow naming conventions
-- Keep functions focused and testable
-- Document complex logic
-
-### When working with agents:
-- Respect agent boundaries
-- Use appropriate agent for each task
-- Follow agent communication patterns
-- Maintain agent context
-
-### When handling errors:
-```javascript
-try {
-  // Operation
-} catch (error) {
-  console.error(`Error in ${operation}:`, error);
-  // Provide helpful error message
-  throw new Error(`Failed to ${operation}: ${error.message}`);
-}
-```
-
-## Git & GitHub Integration
-
-### Commit Conventions
-- Use conventional commits: `feat:`, `fix:`, `docs:`, `chore:`, etc.
-- Reference story ID: `feat: implement IDE detection [Story 2.1]`
-- Keep commits atomic and focused
-
-### GitHub CLI Usage
-- Ensure authenticated: `gh auth status`
-- Use for PR creation: `gh pr create`
-- Check org access: `gh api user/memberships`
+Verifique padroes existentes, reutilize componentes, rode `npm run lint` + `npm run typecheck` antes de concluir.
 
 <!-- SINAPSE-MANAGED-START: sinapse-patterns -->
 ## SINAPSE-Specific Patterns
 
-### Working with Templates
-```javascript
-const template = await loadTemplate('template-name');
-const rendered = await renderTemplate(template, context);
-```
-
-### Agent Command Handling
-```javascript
-if (command.startsWith('*')) {
-  const agentCommand = command.substring(1);
-  await executeAgentCommand(agentCommand, args);
-}
-```
-
-### Story Updates
-```javascript
-// Update story progress
-const story = await loadStory(storyId);
-story.updateTask(taskId, { status: 'completed' });
-await story.save();
-```
+Templates via `loadTemplate()`/`renderTemplate()`; comandos `*` roteados por `executeAgentCommand()`.
 <!-- SINAPSE-MANAGED-END: sinapse-patterns -->
 
-## Environment Setup
-
-### Required Tools
-- Node.js 18+
-- GitHub CLI
-- Git
-- Your preferred package manager (npm/yarn/pnpm)
+## Debugging
 
-### Configuration Files
-- `.sinapse/config.yaml` - Framework configuration
-- `.env` - Environment variables
-- `sinapse.config.js` - Project-specific settings
+Erros devem incluir contexto acionavel e sugestao de correcao. Rode `sinapse doctor` para diagnosticar o ambiente.
 
 <!-- SINAPSE-MANAGED-START: common-commands -->
 ## Common Commands
 
-### SINAPSE Master Commands
-- `*help` - Show available commands
-- `*create-story` - Create new story
-- `*task {name}` - Execute specific task
-- `*workflow {name}` - Run workflow
-
-### Development Commands
-- `npm run dev` - Start development
-- `npm test` - Run tests
-- `npm run lint` - Check code style
-- `npm run build` - Build project
+- `*help` / `*create-story` / `*task {name}` / `*workflow {name}`
+- `npm run dev` / `npm test` / `npm run lint` / `npm run build`
 <!-- SINAPSE-MANAGED-END: common-commands -->
 
-## Debugging
-
-### Enable Debug Mode
-```bash
-export SINAPSE_DEBUG=true
-```
-
-### View Agent Logs
-```bash
-tail -f .sinapse/logs/agent.log
-```
-
-### Trace Workflow Execution
-```bash
-npm run trace -- workflow-name
-```
-
-## Claude Code Specific Configuration
-
-### Performance Optimization
-- Prefer batched tool calls when possible for better performance
-- Use parallel execution for independent operations
-- Cache frequently accessed data in memory during sessions
-
-### Tool Usage Guidelines
-- Always use the Grep tool for searching, never `grep` or `rg` in bash
-- Use the Task tool for complex multi-step operations
-- Batch file reads/writes when processing multiple files
-- Prefer editing existing files over creating new ones
-
-### Session Management
-- Track story progress throughout the session
-- Update checkboxes immediately after completing tasks
-- Maintain context of the current story being worked on
-- Save important state before long-running operations
-
-### Error Recovery
-- Always provide recovery suggestions for failures
-- Include error context in messages to user
-- Suggest rollback procedures when appropriate
-- Document any manual fixes required
-
-### Testing Strategy
-- Run tests incrementally during development
-- Always verify lint and typecheck before marking complete
-- Test edge cases for each new feature
-- Document test scenarios in story files
-
-### Documentation
-- Update relevant docs when changing functionality
-- Include code examples in documentation
-- Keep README synchronized with actual behavior
-- Document breaking changes prominently
-
 ---
-*SINAPSE Claude Code Configuration v2.0*
+*SINAPSE Claude Code Configuration v5.0*

package/.sinapse-ai/product/templates/personalized-agent-template.md

@@ -1,8 +1,6 @@
 # {agent-id}
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -17,7 +15,7 @@ IDE-FILE-RESOLUTION:
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
 
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - STEP 1: Read this entire file - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
   - STEP 3: Greet user using the appropriate greeting level (default: named)
   - STEP 4: Mention `*help` command availability
@@ -27,7 +25,7 @@ activation-instructions:
   - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written
   - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format
   - When listing tasks/templates or presenting options, always show as numbered options list
-  - STAY IN CHARACTER! Use your persona_profile vocabulary and tone consistently
+  - Use your persona_profile vocabulary and tone consistently
   - Use standardized output templates (see .sinapse-ai/docs/standards/AGENT-PERSONALIZATION-STANDARD-V1.md)
   - CRITICAL: On activation, greet user using greeting_level and HALT to await commands
 

package/.sinapse-ai/product/templates/statusline/agent-badges.json

@@ -97,7 +97,7 @@
   "claude-code-mastery/swarm-orqx": {
     "emoji": "🕸️",
     "area": "CLAUDE",
-    "name": "Nexus"
+    "name": "Relay"
   },
   "squad-animations/animation-interpreter": {
     "emoji": "🔮",
@@ -332,7 +332,7 @@
   "squad-content/content-orqx": {
     "emoji": "🔗",
     "area": "CONTENT",
-    "name": "Nexus"
+    "name": "Bulletin"
   },
   "squad-content/editorial-strategist": {
     "emoji": "🧭",

package/.sinapse-ai/product/templates/statusline/statusline-script.js

@@ -39,7 +39,6 @@ function buildStatusLine(data) {
   const white = '\x1b[37m';
   const orange = '\x1b[38;5;208m';
   const boldBlue = `${bold}${blue}`;
-  const boldRed = `${bold}${red}`;
 
   const parts = [];
 
@@ -121,9 +120,12 @@ function buildStatusLine(data) {
     parts.push(`${white}\ud83d\udd22 ${msgCount}${reset}`);
   }
 
-  // 10. Alert >200k
+  // 10. Long-context boundary marker (>200k) \u2014 informational, not an error.
+  // Crossing 200k enters long-context/pricing territory for 1M-window
+  // models; expected behavior on large windows, not a danger signal.
+  // Re-signified by Story onda2-p4 (audit AF-20260702 item 2.12).
   if (data.exceeds_200k_tokens) {
-    parts.push(`${boldRed}\u26a0 >200k!${reset}`);
+    parts.push(`${cyan}\u2139 >200k long-context${reset}`);
   }
 
   return parts.join(' | ');

package/.sinapse-ai/workflow-intelligence/index.js

@@ -2,8 +2,7 @@
  * @module workflow-intelligence
  * @description Workflow Intelligence System (WIS) public API
  * @story WIS-2 - Workflow Registry Enhancement
- * @story WIS-4 - Wave Analysis Engine
- * @version 1.1.0
+ * @version 1.2.0
  *
  * @example
  * const wis = require('./.sinapse-ai/workflow-intelligence');
@@ -20,11 +19,6 @@
  *
  * // Get next steps for a state
  * const nextSteps = wis.getNextSteps('epic_creation', 'stories_created');
- *
- * // Analyze waves for parallel execution (WIS-4)
- * const waves = wis.analyzeWaves('story_development');
- * console.log(waves.waves); // Wave groupings
- * console.log(waves.criticalPath); // Critical path
  */
 
 'use strict';
@@ -49,14 +43,6 @@ const {
   LOW_CONFIDENCE_THRESHOLD,
 } = require('./engine/suggestion-engine');
 
-const {
-  WaveAnalyzer,
-  CircularDependencyError,
-  createWaveAnalyzer,
-  analyzeWaves,
-  DEFAULT_TASK_DURATIONS,
-} = require('./engine/wave-analyzer');
-
 const outputFormatter = require('./engine/output-formatter');
 
 // Learning module (WIS-5)
@@ -297,9 +283,8 @@ module.exports = {
   invalidateCache,
   reset,
 
-  // Wave Analysis API (WIS-4)
-  analyzeWaves,
-  createWaveAnalyzer,
+  // Wave Analysis API (WIS-4) removida — DEC-02/DEC-03 (2026-07-03):
+  // wave-analyzer seguiu o destino do cluster multi-story órfão.
 
   // Pattern Learning API (WIS-5)
   learning: learningModule,
@@ -313,8 +298,6 @@ module.exports = {
   WorkflowRegistry,
   ConfidenceScorer,
   SuggestionEngine,
-  WaveAnalyzer,
-  CircularDependencyError,
 
   // Output formatting (for *next task)
   outputFormatter,
@@ -325,6 +308,5 @@ module.exports = {
   DEFAULT_PATTERNS_PATH,
   SUGGESTION_CACHE_TTL,
   LOW_CONFIDENCE_THRESHOLD,
-  DEFAULT_TASK_DURATIONS,
 };
 

package/AGENTS.md

@@ -1,7 +1,7 @@
 # AGENTS.md
 
 > SINAPSE AI -- AI-Orchestrated System for Full Stack Development
-> 17 squads · 172 agents (all `@`-resolvable in Codex) · 1,412 task files, 1,348 resolvable via the parametric activator
+> 17 squads · 172 agents (all `@`-resolvable in Codex) · 1,411 task files, 1,347 resolvable via the parametric activator
 >
 > Codex resolves every agent and its real tasks at runtime from source (no frozen
 > snapshot): `node .codex/scripts/resolve-codex-agent.js <agent> [command]`.
@@ -75,7 +75,7 @@ Every task pointer the activator emits is verified to exist on disk before it is
 ### @developer (Pixel)
 - **Role:** Full Stack Developer -- code implementation, debugging, refactoring
 - **Capabilities:** Story-driven development (YOLO/Interactive/Pre-Flight modes), CodeRabbit self-healing (max 2 iterations), autonomous build with worktrees, gotchas memory, service scaffolding
-- **Key Commands:** `*develop`, `*build`, `*run-tests`, `*apply-qa-fixes`, `*create-service`, `*waves`
+- **Key Commands:** `*develop`, `*build`, `*run-tests`, `*apply-qa-fixes`, `*create-service`
 - **Constraints:** Cannot `git push` or create PRs (delegate to @devops). Cannot modify story AC/scope/title. Can only update File List, checkboxes, and Dev Agent Record sections.
 
 ### @architect (Stratum)

package/CHANGELOG.md

@@ -1,4 +1,24 @@
-# Changelog
+## [1.20.1](https://github.com/caioimori/sinapse-ai/compare/1.20.0...1.20.1) (2026-07-03)
+
+### Bug Fixes
+
+* **security:** Onda A da triagem AF-20260703 — 4 fixes cirúrgicos ([#337](https://github.com/caioimori/sinapse-ai/issues/337)) ([39f3338](https://github.com/caioimori/sinapse-ai/commit/39f33384aea83df4f609c91eec1ef25acce30d29)), closes [#1](https://github.com/caioimori/sinapse-ai/issues/1) [524-#528](https://github.com/caioimori/524-/issues/528) [#332](https://github.com/caioimori/sinapse-ai/issues/332) [#511](https://github.com/caioimori/sinapse-ai/issues/511) [#32](https://github.com/caioimori/sinapse-ai/issues/32)
+* **security:** Onda B1 — TOCTOU na cadeia de confiança do instalador + git sem shell ([#340](https://github.com/caioimori/sinapse-ai/issues/340)) ([6f0a72b](https://github.com/caioimori/sinapse-ai/commit/6f0a72b89f8a72df741d5e7c94e89c2d3bd7bfd8)), closes [19/#20](https://github.com/19/sinapse-ai/issues/20) [15-#18](https://github.com/caioimori/15-/issues/18) [#22](https://github.com/caioimori/sinapse-ai/issues/22) [#507](https://github.com/caioimori/sinapse-ai/issues/507)
+* **security:** Onda B2 — escrita atômica em todo o caminho de instalação ([#341](https://github.com/caioimori/sinapse-ai/issues/341)) ([0c90216](https://github.com/caioimori/sinapse-ai/commit/0c9021628526ff7cf5ef3dcf41efae3dc629e20a))
+
+### Documentation
+
+* **decisions:** registra Onda A de segurança executada (PR [#337](https://github.com/caioimori/sinapse-ai/issues/337)) ([#338](https://github.com/caioimori/sinapse-ai/issues/338)) ([c2dbe72](https://github.com/caioimori/sinapse-ai/commit/c2dbe72e2c686a9f2db01a85f4e02e444d4eea24))
+* **decisions:** registra Ondas B/C de segurança + rollout da ativação enxuta executados ([#343](https://github.com/caioimori/sinapse-ai/issues/343)) ([0500b56](https://github.com/caioimori/sinapse-ai/commit/0500b56411e44f25cb1729126a3de828ef3f251d))
+
+### Maintenance
+
+* **agents:** rollout da ativação enxuta — pós-piloto aprovado por avaliação ([#342](https://github.com/caioimori/sinapse-ai/issues/342)) ([6815e51](https://github.com/caioimori/sinapse-ai/commit/6815e511e13fb1fa146f0a866d054073075c9212)), closes [#332](https://github.com/caioimori/sinapse-ai/issues/332)
+* **cleanup:** DEC-03 — remove cluster multi-story órfão + split DEC-02 ([#344](https://github.com/caioimori/sinapse-ai/issues/344)) ([359b2fa](https://github.com/caioimori/sinapse-ai/commit/359b2fa2e905eee9be30ea5cac2d7a8bb305a0bd))
+* **release:** sync da main pós-release v1.20.0 ([#336](https://github.com/caioimori/sinapse-ai/issues/336)) ([b3973f0](https://github.com/caioimori/sinapse-ai/commit/b3973f0223173ce570b9ae49878f2d278dc257f8)), closes [#277](https://github.com/caioimori/sinapse-ai/issues/277)
+* **security:** Onda C — higiene do code scanning + 5 fixes de qualidade em produção ([#339](https://github.com/caioimori/sinapse-ai/issues/339)) ([13ae8dd](https://github.com/caioimori/sinapse-ai/commit/13ae8ddd314d2ab923ab019b4e0994be4e1627a1)), closes [#515](https://github.com/caioimori/sinapse-ai/issues/515) [#2](https://github.com/caioimori/sinapse-ai/issues/2) [#409](https://github.com/caioimori/sinapse-ai/issues/409) [#226](https://github.com/caioimori/sinapse-ai/issues/226) [401/#402](https://github.com/401/sinapse-ai/issues/402) [#228](https://github.com/caioimori/sinapse-ai/issues/228)
+
+# Changelog
 
 All notable changes to SINAPSE will be documented in this file.
 
@@ -7,6 +27,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.20.0] — 2026-07-03 — 🧠 Ciclo Fable 5: dieta de contexto, spec/plan de 1ª classe, era de modelo sincronizada
+
+> Minor. Atualização segura via `npx sinapse-ai update`. Consolida o ciclo de upgrade Fable 5 (auditoria AF-20260702 → Onda 1 → Onda 2 → mesa de decisões): 15 PRs (#321–#335).
+
+### Features
+
+- **cli** — `sinapse spec` e `sinapse plan` como comandos de 1ª classe + `orchestrate` no binário canônico + QA honesto no Windows (`PASS_QA_SKIPPED`, exit 0) (#328)
+- **installer** — motor de contexto ativo pós-install: `.synapse/` criado no caminho canônico + models no template; 2º prompt em diante entrega ~−88% de contexto injetado (#334)
+- **synapse** — dieta de contexto: Constitution completa só no 1º prompt (−90,5%/turno) + budgets honestos (#323)
+
+### Bug Fixes
+
+- **cli** — binário canônico honesto: `agents`/`ideate` reais, uninstall de hooksPath, PlanTracker, simulate stub (#321)
+- **context** — dual-trigger de compactação (60% OU 165K) + statusline re-significado pra era 1M (#329)
+- **models** — registry na era Fable 5 (`active: claude-fable-5`) + token-economy sem pin de versão (#322); varredura final de era — atlas sincronizado + squad mastery sem pins (#326)
+
+### Documentation
+
+- **honestidade** — Art. VIII escopado ao caminho real + `docs/framework/workflow-engine-status.md` com status executável dos workflows (#330)
+- **vitrine** — guides públicos no veredito híbrido do motor + README com motor real (#327); docs de vitrine imediata da Onda 1 (#325)
+- **decisions** — mesa de decisões da Onda 2 (5 pareceres) (#333); execução DEC-02/DEC-05 + triagem de segurança (429 alertas, zero crítico-real) (#335)
+
+### Maintenance
+
+- **agents** — piloto de ativação enxuta + 24 colisões de codinome resolvidas (27 renames, reversíveis) (#332)
+- **installer** — bilíngue (troubleshooting i18n) + init sem TTY não crasha (#331)
+- **template** — CLAUDE.md enxuto + guard de codinomes (Nexus→Relay/Bulletin) (#324)
+
 ## [1.19.2] — 2026-07-01 — 🔒 Honestidade do gate (build vazio não passa) + aposta medida
 
 > Patch. Atualização segura via `npx sinapse-ai update`. Fecha o último furo de honestidade do motor achado ao medir a aposta de orquestração multi-story.
@@ -17,7 +65,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Documentation
 
-- **epic** — fecha o épico `orchestration-consolidation` com o **veredito medido do checkpoint "matar ou dobrar"**: HÍBRIDO. Na medição multi-story, o modo nativo entregou 3/3 stories em 64s e 1 chamada, enquanto o motor entregou 1/3 em ~13,5min (a coordenação multi-story corrompeu o estado entre stories). O motor é assumido como **assistente de story isolada** (spec + plano reais); a orquestração autônoma multi-story vira **limitação documentada** (`KNOWN-LIMITATIONS.md`), não promessa. Docs públicos já eram honestos (#318).
+- **epic** — fecha o épico `orchestration-consolidation` com o **veredito medido do checkpoint "matar ou dobrar"**: HÍBRIDO. Na medição multi-story, o modo nativo entregou 3/3 stories em 64s e 1 chamada, enquanto o motor entregou 1/3 em ~13,5min (a coordenação multi-story corrompeu o estado entre stories). O motor é assumido como **assistente de story isolada** (spec + plano reais); a orquestração autônoma multi-story vira **limitação documentada** (`KNOWN-LIMITATIONS.md`), não promessa. Escopo real do #318: atualiza os docs do próprio épico (`docs/epics/`) — a revisão dos guides públicos (user-guide, ade-guide, permission-modes, api-reference) segue pendente e é tratada nas ondas seguintes (Onda 1/Onda 2).
 
 ## [1.19.1] — 2026-06-30 — 🔧 Motor honesto ponta-a-ponta + Windows-safe
 

package/README.md

@@ -423,6 +423,16 @@ npx sinapse-ai chrome-brain install   # Instala browser automation
 
 Todos os comandos são seguros para re-rodar. Para listar agentes ativos depois de instalar, abra o Claude Code ou o Codex CLI e digite `@` para autocompletar.
 
+### Orquestração (avançado)
+
+Além do CLI de instalação acima, o pacote expõe um binário separado (`sinapse`) com um motor de orquestração que gera spec, plano e código para uma story. **Escopo medido: executa 1 story por vez** — orquestração autônoma de múltiplas stories encadeadas foi testada e não é suportada (ver [KNOWN-LIMITATIONS.md](https://github.com/caioimori/sinapse-ai/blob/main/docs/epics/epic-orchestration-consolidation/KNOWN-LIMITATIONS.md)).
+
+```bash
+npx -p sinapse-ai sinapse route "<briefing>"       # Classifica o briefing -> workflow + o que falta
+npx -p sinapse-ai sinapse build "<briefing>"       # Roda o route de forma guiada (--dry-run, --type)
+npx -p sinapse-ai sinapse orchestrate <story-id>   # Gera spec + plano + build para UMA story (--status/--stop/--resume)
+```
+
 ---
 
 ## Contribuindo