sinapse-ai 1.8.0 → 1.9.1

package/.sinapse-ai/development/agents/snps-orqx.md

@@ -1,6 +1,6 @@
 # Agent: Imperator — Sinapse Master
 
-> ACTIVATION-NOTICE: You are now Imperator — the supreme orchestrator of the SINAPSE ecosystem. You have authority over all 18 specialized squads (189 agents total). You do not execute domain work yourself — you diagnose, route, coordinate, and synthesize across the entire ecosystem. Every request passes through you first. You are the CEO of this AI workforce.
+> ACTIVATION-NOTICE: You are now Imperator — the supreme orchestrator of the SINAPSE ecosystem. You have authority over all 17 specialized squads (172 agents total). You do not execute domain work yourself — you diagnose, route, coordinate, and synthesize across the entire ecosystem. Every request passes through you first. You are the CEO of this AI workforce.
 
 ## ACTIVATION INSTRUCTIONS — MANDATORY ON LOAD
 
@@ -25,9 +25,9 @@ Then display:
 
 ```
  AI Agent Squads for Claude Code
- 18 squads · 189 agents · 1,213 tasks
+ 17 squads · 172 agents · 1,200 tasks
 
- 👑 Imperator — Sinapse Master activated
+ 👑 [Imperator] — Sinapse Master activated
 
  Describe your goal and I'll diagnose the domain
  and route to the right agent.
@@ -112,7 +112,7 @@ agent:
   whenToUse: "ALWAYS as the default agent. Imperator is the first point of contact for EVERY request. Routes directly to @specialist when clear, or to @{domain}-orqx when complex."
 
 persona:
-  role: "Supreme Orchestrator of all 18 SINAPSE Squads (189 agents)"
+  role: "Supreme Orchestrator of all 17 SINAPSE Squads (172 agents)"
   identity: >
     The strategic mind at the top of the SINAPSE hierarchy. Imperator
     sees across all domains — branding, commerce, content, copy, animations,
@@ -161,7 +161,7 @@ intelligent_routing:
       - '"Assessment de seguranca" -> @cyber-orqx'
 
 # ══════════════════════════════════════════════════════════════════════════════
-# COMPLETE ROUTING TABLE — ALL 18 SQUADS
+# COMPLETE ROUTING TABLE — ALL 17 SQUADS
 # ══════════════════════════════════════════════════════════════════════════════
 
 routing_table:
@@ -211,23 +211,14 @@ routing_table:
       tasks: 73
       keywords: ["animacao", "animation", "Three.js", "shader", "WebGL", "GSAP", "motion", "Framer Motion", "parallax", "3D", "canvas", "particle"]
 
-    - squad: squad-artdir
-      prefix: artdir
-      orchestrator: artdir-orqx (Canvas)
-      invocation: "/artdir:agents:artdir-orqx"
-      domain: "Art direction para landing pages, websites, plataformas SaaS premium. 7 pilares de retencao + conversao. Visual strategy, design system premium, packaging visual."
-      agents: 14
-      tasks: 13
-      keywords: ["art direction", "direcao de arte", "landing page", "LP", "site", "website", "premium", "platform", "SaaS visual", "packaging visual", "visual strategy", "pilar", "retencao", "conversao"]
-
     - squad: squad-design
       prefix: design
       orchestrator: design-orqx (Nexus)
       invocation: "/design:agents:design-orqx"
-      domain: "UX/UI, experiencia digital, wireframes, prototipos, design system, acessibilidade"
-      agents: 8
+      domain: "UX/UI, experiencia digital, wireframes, prototipos, design system, acessibilidade. Art direction para landing pages, websites, plataformas SaaS premium — visual strategy, design system premium, packaging visual, 7 pilares de retencao + conversao."
+      agents: 14
       tasks: 101
-      keywords: ["UX", "UI", "experiencia", "wireframe", "prototipo", "design system", "acessibilidade", "usabilidade", "user research", "interaction design", "figma"]
+      keywords: ["UX", "UI", "experiencia", "wireframe", "prototipo", "design system", "acessibilidade", "usabilidade", "user research", "interaction design", "figma", "art direction", "direcao de arte", "landing page", "LP", "site", "website", "premium", "platform", "SaaS visual", "packaging visual", "visual strategy", "pilar", "retencao", "conversao"]
 
     - squad: squad-finance
       prefix: finance
@@ -276,8 +267,8 @@ routing_table:
 
     - squad: claude-code-mastery
       prefix: claude
-      orchestrator: claude-orqx (Nucleus)
-      invocation: "/claude:agents:claude-orqx"
+      orchestrator: swarm-orqx (Nexus)
+      invocation: "/claude:agents:swarm-orqx"
       domain: "Claude Code mastery, prompt engineering, MCP, automacao, hooks, skills, plugins, agent teams, context engineering"
       agents: 11
       tasks: 51
@@ -522,7 +513,7 @@ commands:
     description: "Design a multi-squad execution plan for a complex initiative"
     args: "{initiative_description}"
   - name: "*status"
-    description: "Report on all 18 squads — capabilities, agents, tasks"
+    description: "Report on all 17 squads — capabilities, agents, tasks"
     args: "[--squad {name}] [--verbose]"
   - name: "*brief"
     description: "Generate a strategic brief leveraging relevant squads"
@@ -568,7 +559,7 @@ relationships:
       context: "All product strategy, discovery, roadmap"
     - agent: research-orqx (Prism)
       context: "All market research, competitive intelligence"
-    - agent: claude-orqx (Nucleus)
+    - agent: swarm-orqx (Nexus)
       context: "All Claude Code mastery, prompt engineering, MCP"
     - agent: council-orqx (Zenith)
       context: "All strategic counsel, mental models, advisory"
@@ -591,7 +582,7 @@ framework_compatibility:
     description: >
       Without any external framework, Imperator is the top-level orchestrator.
       Users invoke /sinapse:agents:sinapse-orqx directly, and Imperator routes
-      to all 18 squads autonomously.
+      to all 17 squads autonomously.
     orchestrator: "sinapse-orqx (Imperator)"
 
   with_sinapse:
@@ -666,17 +657,16 @@ Imperator can provide ecosystem-wide insights by combining capabilities across s
 | 9 | paidmedia | pm | Apex | Midia paga, Meta/Google Ads |
 | 10 | product | product | Vector | Produto, discovery, roadmap |
 | 11 | research | research | Prism | Pesquisa, inteligencia competitiva |
-| 12 | claude | claude | Nucleus | Claude Code, prompt engineering |
+| 12 | claude-code-mastery | claude | Nexus | Claude Code, prompt engineering |
 | 13 | council | council | Zenith | Conselho estrategico, advisory |
 | 14 | storytelling | narrative | Arc | Storytelling, pitch, apresentacao |
 | 15 | cybersecurity | cyber | Fortress | Cybersecurity, compliance, pentest |
 | 16 | cloning | cloning | Helix | Cognitive cloning, mental DNA extraction |
 | 17 | courses | courses | Syllabus | Course creation, workshops, ebooks |
-| 18 | claude-code-mastery | claude | Nucleus | Claude Code mastery, prompt engineering |
 
-**Total ecosystem:** 18 squads, 189 agents, 1,213 tasks
+**Total ecosystem:** 17 squads, 172 agents, 1,200 tasks
 
 ## Cross-Squad Handoffs
 - **Receives from:** Every squad (escalations, cross-squad requests)
 - **Sends to:** Every squad (routed work, coordination directives)
-- **Coordinates with:** All 18 squad orchestrators
+- **Coordinates with:** All 17 squad orchestrators

package/.sinapse-ai/development/tasks/build-autonomous.md

@@ -1,3 +1,11 @@
+---
+task: build-autonomous
+responsavel: '@developer'
+entrada: '`story-id` + opções (`--worktree`, `--timeout`, `--max-retries`)'
+saida: 'Subtasks executadas com retry/self-critique + estado de build + relatório'
+atomic_layer: Task
+---
+
 # Task: Build Autonomous
 
 > **Command:** `*build-autonomous {story-id}`
@@ -192,8 +200,10 @@ The AutonomousBuildLoop emits these events for monitoring:
 _Task file for Story 8.1 - Coder Agent Loop_
 
 ## Handoff
+
 next_agent: @quality-gate
 next_command: *review {story-id}
 condition: Autonomous build completed successfully
 alternatives:
-  - agent: @developer, command: *build-resume {story-id}, condition: Build failed, needs resume
+
+- agent: @developer, command: *build-resume {story-id}, condition: Build failed, needs resume

package/.sinapse-ai/development/tasks/build-resume.md

@@ -1,3 +1,11 @@
+---
+task: build-resume
+responsavel: '@developer'
+entrada: '`story-id` — build a retomar'
+saida: 'Build autônomo retomado a partir do último checkpoint'
+atomic_layer: Task
+---
+
 # Task: Build Resume
 
 > **Command:** `*build-resume {story-id}`

package/.sinapse-ai/development/tasks/build-status.md

@@ -1,3 +1,11 @@
+---
+task: build-status
+responsavel: '@developer'
+entrada: '`story-id` ou `--all`'
+saida: 'Status, progresso, métricas e indicadores de saúde dos builds'
+atomic_layer: Task
+---
+
 # Task: Build Status
 
 > **Command:** `*build-status {story-id}` or `*build-status --all`

package/.sinapse-ai/development/tasks/build.md

@@ -1,3 +1,11 @@
+---
+task: build
+responsavel: '@developer'
+entrada: '`story-id` + flags (`--dry-run`, `--no-merge`, `--no-qa`, `--verbose`, `--timeout`)'
+saida: 'Build autônomo completo + relatório em `plan/build-report-{story-id}.md`'
+atomic_layer: Task
+---
+
 # Task: Build (Autonomous)
 
 > **Command:** `*build {story-id}`

package/.sinapse-ai/development/tasks/cleanup-worktrees.md

@@ -1,3 +1,11 @@
+---
+task: cleanup-worktrees
+responsavel: '@developer'
+entrada: '`--days` — limite de idade em dias (default: 30)'
+saida: 'Worktrees obsoletas removidas com segurança + resumo da limpeza'
+atomic_layer: Task
+---
+
 # cleanup-worktrees
 
 Remove all stale git worktrees older than specified threshold.
@@ -37,4 +45,3 @@ Clean up abandoned worktrees to maintain repository hygiene.
 - `*list-worktrees` - List all worktrees
 - `*remove-worktree` - Remove single worktree
 - `*create-worktree` - Create new worktree
-

package/.sinapse-ai/development/tasks/gotcha.md

@@ -1,3 +1,11 @@
+---
+task: gotcha
+responsavel: '@developer'
+entrada: '`title`, `description` e opções (`--category`, `--severity`, `--workaround`, `--files`)'
+saida: 'Gotcha registrado na memória de gotchas do projeto'
+atomic_layer: Task
+---
+
 # Task: Add Gotcha
 
 > **Command:** `*gotcha {title} - {description}`

package/.sinapse-ai/development/tasks/gotchas.md

@@ -1,3 +1,11 @@
+---
+task: gotchas
+responsavel: '@developer'
+entrada: 'Filtros opcionais (`--category`, `--severity`, `--unresolved`, `search {query}`)'
+saida: 'Lista/busca de gotchas conhecidos com workarounds'
+atomic_layer: Task
+---
+
 # Task: List Gotchas
 
 > **Command:** `*gotchas [options]`

package/.sinapse-ai/development/tasks/ids-health.md

@@ -1,3 +1,11 @@
+---
+task: ids-health
+responsavel: '@data-engineer'
+entrada: '`.sinapse-ai/data/entity-registry.yaml`; flags `--fix` / `--json` opcionais'
+saida: 'Relatório de integridade do registro, correções auto-aplicadas e log de auditoria'
+atomic_layer: Task
+---
+
 # IDS Registry Health Check Task
 
 ## Purpose
@@ -32,6 +40,7 @@ node bin/sinapse-ids.js ids:health --fix
 ```
 
 This will:
+
 - Create a backup of the registry before changes
 - Auto-fix issues: checksum mismatches, orphaned references, missing keywords, stale timestamps
 - Skip non-auto-healable issues (missing files) and emit warnings
@@ -63,10 +72,10 @@ Review the warnings and take manual action as suggested.
 
 ## Exit Codes
 
-| Code | Meaning |
-|------|---------|
-| 0 | No critical issues |
-| 1 | Critical issues found (e.g., missing files) |
+| Code | Meaning                                     |
+| ---- | ------------------------------------------- |
+| 0    | No critical issues                          |
+| 1    | Critical issues found (e.g., missing files) |
 
 ---
 
@@ -86,5 +95,4 @@ if (healthResult.summary.total > 0) {
 
 ---
 
-*Story IDS-4a | Self-Healing Data Integrity*
-
+_Story IDS-4a | Self-Healing Data Integrity_

package/.sinapse-ai/development/tasks/list-mcps.md

@@ -1,3 +1,11 @@
+---
+task: list-mcps
+responsavel: '@developer'
+entrada: 'Nenhuma — lê a configuração do Docker MCP Toolkit'
+saida: 'Lista de servidores MCP habilitados, status e ferramentas disponíveis'
+atomic_layer: Task
+---
+
 # list-mcps
 
 List currently enabled MCP servers and their available tools.
@@ -15,6 +23,7 @@ Display all MCP servers configured in Docker MCP Toolkit with their status and t
 ## Output
 
 Shows:
+
 - Server name and status (enabled/disabled)
 - Available tools per server
 - Connection status
@@ -22,6 +31,7 @@ Shows:
 ## Implementation
 
 Uses Docker MCP Toolkit CLI:
+
 ```bash
 docker mcp tools ls
 ```
@@ -32,3 +42,8 @@ docker mcp tools ls
 - `*remove-mcp` - Remove MCP server
 - `*search-mcp` - Search MCP catalog
 
+## Steps
+
+1. Consultar o toolkit: `docker mcp tools ls`
+2. Agrupar ferramentas por servidor
+3. Exibir nome, status (enabled/disabled) e conexão de cada servidor

package/.sinapse-ai/development/tasks/merge-worktree.md

@@ -1,3 +1,11 @@
+---
+task: merge-worktree
+responsavel: '@developer'
+entrada: '`worktree-name` — nome do worktree a mesclar'
+saida: 'Branch do worktree mesclada na base (após quality gates) + worktree opcionalmente removido'
+atomic_layer: Task
+---
+
 # merge-worktree
 
 Merge a worktree branch back to its base branch.
@@ -40,4 +48,3 @@ Complete worktree workflow by merging changes back to base branch.
 - `*create-worktree` - Create worktree
 - `*remove-worktree` - Remove worktree
 - `*push` - Push merged changes
-

package/.sinapse-ai/development/tasks/qa-review-build.md

@@ -1,3 +1,11 @@
+---
+task: qa-review-build
+responsavel: '@quality-gate'
+entrada: '`storyId`, `spec.md`, `implementation.yaml`'
+saida: 'Relatório QA de 10 fases com sinal claro APPROVE/REJECT'
+atomic_layer: Task
+---
+
 # QA Review Build: 10-Phase Quality Assurance Review
 
 > **Phase:** QA Review
@@ -1222,3 +1230,13 @@ metadata:
     - quality-gate
     - automated-testing
 ```
+
+## Steps
+
+1. Carregar spec e implementação da story
+2. Validar implementação contra a spec
+3. Rodar testes automatizados (lint, unit, typecheck)
+4. Verificação de browser/banco quando aplicável
+5. Code review estruturado
+6. Checagem de regressões
+7. Emitir relatório com sinal APPROVE/REJECT

package/.sinapse-ai/development/tasks/remove-mcp.md

@@ -1,3 +1,11 @@
+---
+task: remove-mcp
+responsavel: '@developer'
+entrada: '`server-name` — nome do servidor MCP a remover'
+saida: 'Servidor MCP removido do Docker MCP Toolkit (com confirmação)'
+atomic_layer: Task
+---
+
 # remove-mcp
 
 Remove an MCP server from Docker MCP Toolkit.
@@ -33,4 +41,3 @@ Disable and remove an MCP server from the toolkit configuration.
 
 - `*list-mcps` - List enabled MCPs
 - `*add-mcp` - Add MCP server
-

package/.sinapse-ai/development/tasks/validate-agents.md

@@ -1,8 +1,16 @@
+---
+task: validate-agents
+responsavel: '@quality-gate'
+entrada: '`scope` (all|agent-id), `strict` (bool), `output` (summary|detailed)'
+saida: 'Relatório de validação estrutural dos agentes (erros e warnings)'
+atomic_layer: Task
+---
+
 # Validate Agents Task
 
 ---
-execution_mode: programmatic  # TOK-3: PTC-eligible — batch-scan all agent files in single Bash block
----
+
+## execution_mode: programmatic # TOK-3: PTC-eligible — batch-scan all agent files in single Bash block
 
 ## Purpose
 
@@ -31,6 +39,7 @@ Expected agents: dev, qa, architect, pm, po, sm, analyst, data-engineer, ux-desi
 ### Step 2: Parse YAML Block
 
 For each agent file:
+
 1. Extract the YAML block between ` ```yaml ` and ` ``` ` fences
 2. Parse using `js-yaml.load()` (safe loader)
 3. If parse fails, try normalizing compact command format first
@@ -38,20 +47,21 @@ For each agent file:
 
 ### Step 3: Validate Required Fields
 
-| Field | Required | Default | Notes |
-|-------|----------|---------|-------|
-| `agent.id` | Yes | - | Must match filename |
-| `agent.name` | Yes | - | Human-readable name |
-| `agent.icon` | No | - | Emoji icon |
-| `persona_profile` | Yes | - | Must have greeting_levels |
-| `persona_profile.greeting_levels` | Yes | - | minimal, named, archetypal |
-| `persona.role` | Yes | - | Role description |
-| `commands` | Yes | [] | Array of command objects |
-| `activation-instructions` | Yes | - | Must include STEP 1-5 |
+| Field                             | Required | Default | Notes                      |
+| --------------------------------- | -------- | ------- | -------------------------- |
+| `agent.id`                        | Yes      | -       | Must match filename        |
+| `agent.name`                      | Yes      | -       | Human-readable name        |
+| `agent.icon`                      | No       | -       | Emoji icon                 |
+| `persona_profile`                 | Yes      | -       | Must have greeting_levels  |
+| `persona_profile.greeting_levels` | Yes      | -       | minimal, named, archetypal |
+| `persona.role`                    | Yes      | -       | Role description           |
+| `commands`                        | Yes      | []      | Array of command objects   |
+| `activation-instructions`         | Yes      | -       | Must include STEP 1-5      |
 
 ### Step 4: Validate Activation Pipeline Reference
 
 Check that STEP 3 in `activation-instructions` references:
+
 - `unified-activation-pipeline.js` (Story ACT-6)
 - NOT the old `greeting-builder.js` direct reference
 
@@ -60,16 +70,19 @@ Report as WARNING if still referencing old path.
 ### Step 5: Validate Dependencies
 
 For each agent's `dependencies.tasks` list:
+
 1. Check that each referenced task file exists in `.sinapse-ai/development/tasks/`
 2. Report missing dependencies as ERRORS
 
 For each agent's `dependencies.checklists` list:
+
 1. Check in `.sinapse-ai/development/checklists/`
 2. Report missing as WARNINGS
 
 ### Step 6: Validate Command Structure
 
 For each command in `commands` array:
+
 1. Must have `name` field (string)
 2. `description` is recommended (WARNING if missing)
 3. `visibility` array is recommended for session-aware filtering
@@ -116,5 +129,4 @@ Summary: 11 passed, 1 warning, 0 failed
 
 ---
 
-*Story ACT-6 | Task: validate-agents | Created 2026-02-06*
-
+_Story ACT-6 | Task: validate-agents | Created 2026-02-06_