sinapse-ai 5.0.8 → 6.0.1

package/docs/guides/workflows/xref-phase3-scripts.md

@@ -33,21 +33,21 @@
 | 9 | `agent-assignment-resolver.js` | Resolves `{TODO: Agent Name}` placeholders in task files based on prefix mapping | `fs`, `path` | `install-manifest.yaml` | One-time migration tool | Low-use |
 | 10 | `agent-exit-hooks.js` | Defines hook system for workflow context persistence on command completion | `context-detector` | `install-manifest.yaml`, docs | Framework integration (Story 6.1.6) | Low-use |
 | 11 | `batch-update-agents-session-context.js` | Batch updates 8 agents with session context loader integration (Story 6.1.2.6.2) | `fs.promises`, `path` | `install-manifest.yaml` | One-time migration tool | Low-use |
-| 12 | `backlog-manager.js` | Manages technical debt, follow-ups, and enhancements backlog with prioritization | `fs.promises` | 28 files: `po-backlog-add.md`, `dev-backlog-debt.md`, `qa-backlog-add-followup.md`, story tasks, docs | @po, @dev, @qa | No |
-| 13 | `decision-context.js` | DecisionContext class tracking decisions, files, tests during yolo mode execution | `child_process`, `path` | 17 files: `decision-recorder.js`, `decision-log-generator.js`, `dev-develop-story.md`, agent dev.md, tests | @dev (yolo mode) | No |
-| 14 | `decision-log-generator.js` | Generates markdown decision logs from DecisionContext data | `fs.promises`, `path` | 17 files: `decision-recorder.js`, dev tasks, tests | @dev (yolo mode) | No |
-| 15 | `decision-log-indexer.js` | Maintains index file of all decision logs for discovery | `fs.promises`, `path`, `js-yaml` | `decision-recorder.js`, tests | @dev (yolo mode) | No |
-| 16 | `decision-recorder.js` | Singleton API for recording decisions during yolo mode -- manages global context | `decision-context`, `decision-log-generator`, `js-yaml` | `dev-develop-story.md`, tests | @dev (yolo mode) | No |
-| 17 | `dev-context-loader.js` | Optimized file loading for @dev agent with smart caching and summarization | `fs.promises`, `path`, `js-yaml` | 9 files: tests, docs, `install-manifest.yaml` | @dev | No |
-| 18 | `story-manager.js` | Handles story file operations and ClickUp synchronization | `fs.promises`, `path`, `js-yaml`, `story-update-hook`, `tool-resolver` | 28 files: `po-sync-story.md`, `po-pull-story.md`, `po-stories-index.md`, various tasks | @po, @pm | No |
-| 19 | `story-update-hook.js` | Detects changes between story versions and syncs to ClickUp | `clickup-helpers`, `js-yaml` | `story-manager.js`, `po-sync-story.md`, tests | @po, @pm | No |
-| 20 | `story-index-generator.js` | Scans `docs/stories/` and generates comprehensive story index with metadata | `fs.promises`, `path` | `po-stories-index.md`, `jest.config.js`, docs | @po | No |
+| 12 | `backlog-manager.js` | Manages technical debt, follow-ups, and enhancements backlog with prioritization | `fs.promises` | 28 files: `po-backlog-add.md`, `dev-backlog-debt.md`, `qa-backlog-add-followup.md`, story tasks, docs | @product-lead, @developer, @quality-gate | No |
+| 13 | `decision-context.js` | DecisionContext class tracking decisions, files, tests during yolo mode execution | `child_process`, `path` | 17 files: `decision-recorder.js`, `decision-log-generator.js`, `dev-develop-story.md`, agent dev.md, tests | @developer (yolo mode) | No |
+| 14 | `decision-log-generator.js` | Generates markdown decision logs from DecisionContext data | `fs.promises`, `path` | 17 files: `decision-recorder.js`, dev tasks, tests | @developer (yolo mode) | No |
+| 15 | `decision-log-indexer.js` | Maintains index file of all decision logs for discovery | `fs.promises`, `path`, `js-yaml` | `decision-recorder.js`, tests | @developer (yolo mode) | No |
+| 16 | `decision-recorder.js` | Singleton API for recording decisions during yolo mode -- manages global context | `decision-context`, `decision-log-generator`, `js-yaml` | `dev-develop-story.md`, tests | @developer (yolo mode) | No |
+| 17 | `dev-context-loader.js` | Optimized file loading for @developer agent with smart caching and summarization | `fs.promises`, `path`, `js-yaml` | 9 files: tests, docs, `install-manifest.yaml` | @developer | No |
+| 18 | `story-manager.js` | Handles story file operations and ClickUp synchronization | `fs.promises`, `path`, `js-yaml`, `story-update-hook`, `tool-resolver` | 28 files: `po-sync-story.md`, `po-pull-story.md`, `po-stories-index.md`, various tasks | @product-lead, @project-lead | No |
+| 19 | `story-update-hook.js` | Detects changes between story versions and syncs to ClickUp | `clickup-helpers`, `js-yaml` | `story-manager.js`, `po-sync-story.md`, tests | @product-lead, @project-lead | No |
+| 20 | `story-index-generator.js` | Scans `docs/stories/` and generates comprehensive story index with metadata | `fs.promises`, `path` | `po-stories-index.md`, `jest.config.js`, docs | @product-lead | No |
 | 21 | `task-identifier-resolver.js` | Resolves `{TODO: task identifier}` placeholders in 114 task files | `fs`, `path` | `install-manifest.yaml` | One-time migration tool | Low-use |
-| 22 | `validate-task-v2.js` | Validates task files against V2.0 specification (11 compliance rules) | `fs`, `path` | 9 files: `migrate-task-to-v2.js`, docs | @qa, @dev | No |
-| 23 | `migrate-task-to-v2.js` | Semi-automated V1.0 to V2.0 task migration helper | `fs`, `path` | 9 files: `validate-task-v2.js`, docs | @dev migration | Low-use |
+| 22 | `validate-task-v2.js` | Validates task files against V2.0 specification (11 compliance rules) | `fs`, `path` | 9 files: `migrate-task-to-v2.js`, docs | @quality-gate, @developer | No |
+| 23 | `migrate-task-to-v2.js` | Semi-automated V1.0 to V2.0 task migration helper | `fs`, `path` | 9 files: `validate-task-v2.js`, docs | @developer migration | Low-use |
 | 24 | `workflow-navigator.js` | Provides intelligent next-step command suggestions from workflow patterns | `fs`, `path`, `js-yaml` | 18 files: `greeting-builder.js`, tasks, docs | All (via greeting-builder) | No |
-| 25 | `workflow-state-manager.js` | File-based state persistence for guided workflow automation across sessions | `fs.promises`, `path`, `js-yaml` | 18 files: `run-workflow.md`, `run-workflow-engine.md`, tasks | @sm, @pm | No |
-| 26 | `workflow-validator.js` | Validates workflow YAML files against SINAPSE conventions (9 checks) | `fs.promises`, `path`, `js-yaml` | 18 files: `validate-workflow.md`, `squad-validator.js`, tasks | @qa, @architect | No |
+| 25 | `workflow-state-manager.js` | File-based state persistence for guided workflow automation across sessions | `fs.promises`, `path`, `js-yaml` | 18 files: `run-workflow.md`, `run-workflow-engine.md`, tasks | @sprint-lead, @project-lead | No |
+| 26 | `workflow-validator.js` | Validates workflow YAML files against SINAPSE conventions (9 checks) | `fs.promises`, `path`, `js-yaml` | 18 files: `validate-workflow.md`, `squad-validator.js`, tasks | @quality-gate, @architect | No |
 | 27 | `verify-workflow-gaps.js` | Verification script for workflow gap fixes (GAP 1, 2, 3) | `fs`, `path`, `js-yaml` | 18 files: docs, `install-manifest.yaml` | Verification tool | Low-use |
 | 28 | `decision-context.js` | (See #13 above -- same file) | -- | -- | -- | -- |
 
@@ -57,7 +57,7 @@
 |---|------|---------|-------------|---------------------|----------|---------|
 | S1 | `index.js` | Central exports aggregator for all squad utilities | All squad modules below | 43 files: `squad-creator.md`, all squad tasks, tests | @squad-creator | No |
 | S2 | `squad-loader.js` | Loads and resolves squad manifests from local directories (SQS-2) | `fs.promises`, `path`, `js-yaml` | `index.js`, `squad-creator-list.md`, tests | @squad-creator | No |
-| S3 | `squad-validator.js` | Validates squad structure against JSON schema, task format, agent defs (SQS-3) | `ajv`, `fs.promises`, `path`, `js-yaml`, squad-schema.json | `index.js`, `squad-creator-validate.md`, tests, `workflow-validator.js` | @squad-creator, @qa | No |
+| S3 | `squad-validator.js` | Validates squad structure against JSON schema, task format, agent defs (SQS-3) | `ajv`, `fs.promises`, `path`, `js-yaml`, squad-schema.json | `index.js`, `squad-creator-validate.md`, tests, `workflow-validator.js` | @squad-creator, @quality-gate | No |
 | S4 | `squad-generator.js` | Generates squad structure following task-first architecture (SQS-4) | `fs.promises`, `path`, `child_process`, `js-yaml` | `index.js`, `squad-creator-create.md`, tests | @squad-creator | No |
 | S5 | `squad-designer.js` | Analyzes documentation and generates squad blueprints with recommendations (SQS-9) | `fs.promises`, `path`, `js-yaml` | `index.js`, `squad-creator-design.md`, tests | @squad-creator | No |
 | S6 | `squad-migrator.js` | Migrates legacy squad formats to SINAPSE 2.1 standard (SQS-7) | `fs.promises`, `path`, `js-yaml` | `index.js`, `squad-creator-migrate.md`, tests | @squad-creator | No |
@@ -123,7 +123,7 @@ The preference is stored in `.sinapse-ai/core-config.yaml` under `agentIdentity.
 All 12 agents reference the greeting system in their `activation-instructions` STEP 3:
 
 **Pattern A: Direct Class Invocation (9 agents)**
-Used by: @dev, @qa, @architect, @pm, @po, @sm, @analyst, @sinapse-master, @squad-creator
+Used by: @developer, @quality-gate, @architect, @project-lead, @product-lead, @sprint-lead, @analyst, @sinapse-orqx, @squad-creator
 
 ```yaml
 activation-instructions:
@@ -201,17 +201,17 @@ All agents share the same GreetingBuilder logic but differ in:
 
 | Agent | Icon | Archetype | Zodiac | Custom Greeting Example |
 |-------|------|-----------|--------|------------------------|
-| @dev (Dex) | `\U0001f4bb` | Builder | Aquarius | "Dex the Builder ready to construct excellence!" |
-| @qa (Quinn) | `\U0001f6e1\ufe0f` | Guardian | Virgo | "Quinn the Guardian ready!" |
-| @po (Pax) | `\u2696\ufe0f` | Balancer | Libra | "Pax the Balancer ready!" |
-| @pm (Morgan) | `\U0001f4cb` | Strategist | Capricorn | "Morgan the Strategist ready!" |
-| @sm (River) | `\U0001f30a` | Facilitator | Sagittarius | "River the Facilitator ready!" |
+| @developer (Dex) | `\U0001f4bb` | Builder | Aquarius | "Dex the Builder ready to construct excellence!" |
+| @quality-gate (Quinn) | `\U0001f6e1\ufe0f` | Guardian | Virgo | "Quinn the Guardian ready!" |
+| @product-lead (Pax) | `\u2696\ufe0f` | Balancer | Libra | "Pax the Balancer ready!" |
+| @project-lead (Morgan) | `\U0001f4cb` | Strategist | Capricorn | "Morgan the Strategist ready!" |
+| @sprint-lead (River) | `\U0001f30a` | Facilitator | Sagittarius | "River the Facilitator ready!" |
 | @architect (Aria) | `\U0001f3d7\ufe0f` | Visionary | Gemini | "Aria the Visionary ready!" |
 | @analyst (Alex) | `\U0001f50d` | Decoder | Scorpio | "Alex the Decoder ready!" |
 | @devops (Gage) | `\u2699\ufe0f` | Automator | Aries | "Gage the Automator ready!" |
 | @data-engineer (Dara) | `\U0001f4ca` | Sage | Taurus | "Dara the Sage ready!" |
 | @ux-design-expert (Uma) | `\U0001f3a8` | Empathizer | Pisces | "Uma the Empathizer ready!" |
-| @sinapse-master | `\U0001f9e0` | Orchestrator | Leo | "SINAPSE Master Orchestrator ready!" |
+| @sinapse-orqx | `\U0001f9e0` | Orchestrator | Leo | "SINAPSE Master Orchestrator ready!" |
 | @squad-creator | `\U0001f4e6` | Assembler | -- | "Squad Creator ready!" |
 
 Each agent's greeting levels are defined in its `.md` persona file under `persona_profile.greeting_levels` (or `persona_profile.communication.greeting_levels`).
@@ -422,12 +422,12 @@ No scripts are truly orphaned -- all have at least one reference in the `install
 | Category | Scripts | Primary Agents |
 |----------|---------|---------------|
 | **Greeting System** (6) | greeting-builder, generate-greeting, greeting-preference-manager, greeting-config-cli, test-greeting-system, apply-inline-greeting-all-agents | All 12 agents |
-| **Decision Logging** (4) | decision-context, decision-log-generator, decision-log-indexer, decision-recorder | @dev (yolo mode) |
-| **Story Management** (3) | story-manager, story-update-hook, story-index-generator | @po, @pm |
-| **Workflow Engine** (4) | workflow-navigator, workflow-state-manager, workflow-validator, verify-workflow-gaps | @sm, @pm, @qa, @architect |
-| **Agent Configuration** (4) | agent-config-loader, audit-agent-config, agent-exit-hooks, dev-context-loader | All (via config pipeline), @dev |
-| **Task Migration** (4) | validate-task-v2, migrate-task-to-v2, task-identifier-resolver, agent-assignment-resolver | @dev, @qa |
-| **Backlog** (1) | backlog-manager | @po, @dev, @qa |
+| **Decision Logging** (4) | decision-context, decision-log-generator, decision-log-indexer, decision-recorder | @developer (yolo mode) |
+| **Story Management** (3) | story-manager, story-update-hook, story-index-generator | @product-lead, @project-lead |
+| **Workflow Engine** (4) | workflow-navigator, workflow-state-manager, workflow-validator, verify-workflow-gaps | @sprint-lead, @project-lead, @quality-gate, @architect |
+| **Agent Configuration** (4) | agent-config-loader, audit-agent-config, agent-exit-hooks, dev-context-loader | All (via config pipeline), @developer |
+| **Task Migration** (4) | validate-task-v2, migrate-task-to-v2, task-identifier-resolver, agent-assignment-resolver | @developer, @quality-gate |
+| **Backlog** (1) | backlog-manager | @product-lead, @developer, @quality-gate |
 | **Batch Updates** (1) | batch-update-agents-session-context | One-time |
 | **Squad Module** (10) | squad/index, squad-loader, squad-validator, squad-generator, squad-designer, squad-migrator, squad-downloader, squad-publisher, squad-analyzer, squad-extender | @squad-creator |
 
@@ -435,17 +435,17 @@ No scripts are truly orphaned -- all have at least one reference in the `install
 
 | Agent | Scripts Used | Count |
 |-------|-------------|-------|
-| @dev | greeting-builder, agent-config-loader, dev-context-loader, decision-context, decision-recorder, decision-log-generator, decision-log-indexer, validate-task-v2, backlog-manager, workflow-navigator | 10 |
-| @qa | greeting-builder, agent-config-loader, validate-task-v2, workflow-validator, backlog-manager | 5 |
-| @po | greeting-builder, agent-config-loader, story-manager, story-update-hook, story-index-generator, backlog-manager | 6 |
-| @pm | greeting-builder, agent-config-loader, story-manager, workflow-state-manager | 4 |
-| @sm | greeting-builder, agent-config-loader, workflow-state-manager | 3 |
+| @developer | greeting-builder, agent-config-loader, dev-context-loader, decision-context, decision-recorder, decision-log-generator, decision-log-indexer, validate-task-v2, backlog-manager, workflow-navigator | 10 |
+| @quality-gate | greeting-builder, agent-config-loader, validate-task-v2, workflow-validator, backlog-manager | 5 |
+| @product-lead | greeting-builder, agent-config-loader, story-manager, story-update-hook, story-index-generator, backlog-manager | 6 |
+| @project-lead | greeting-builder, agent-config-loader, story-manager, workflow-state-manager | 4 |
+| @sprint-lead | greeting-builder, agent-config-loader, workflow-state-manager | 3 |
 | @architect | greeting-builder, agent-config-loader, workflow-validator | 3 |
 | @analyst | greeting-builder, agent-config-loader | 2 |
 | @devops | greeting-builder, generate-greeting, agent-config-loader | 3 |
 | @data-engineer | greeting-builder, generate-greeting, agent-config-loader | 3 |
 | @ux-design-expert | greeting-builder, generate-greeting, agent-config-loader | 3 |
-| @sinapse-master | greeting-builder, agent-config-loader | 2 |
+| @sinapse-orqx | greeting-builder, agent-config-loader | 2 |
 | @squad-creator | greeting-builder, agent-config-loader, squad/* (10 scripts) | 12 |
 
 ---

package/docs/guides/workflows/xref-phase4-infra.md

@@ -51,7 +51,7 @@ These scripts are imported in `.sinapse-ai/infrastructure/index.js` and exposed
 | 19 | `scripts/dependency-impact-analyzer.js` | Analysis | Analyzes impact of dependency changes | -- | tasks (propose-modification, architect-analyze-impact, qa-review) | No |
 | 20 | `scripts/framework-analyzer.js` | Analysis | Discovers and catalogs framework components | `fs`, `yaml`, `chalk` | verify-workflow-gaps, tasks/analyze-framework, core-config | No |
 | 21 | `scripts/capability-analyzer.js` | Analysis | Analyzes agent/component capabilities | security-checker | improvement-validator, tasks/improve-self, elicitation-engine | No |
-| 22 | `scripts/security-checker.js` | Analysis | Security validation for components | -- | component-generator, elicitation-engine, sinapse-master agent | No |
+| 22 | `scripts/security-checker.js` | Analysis | Security validation for components | -- | component-generator, elicitation-engine, sinapse-orqx agent | No |
 | 23 | `scripts/modification-risk-assessment.js` | Analysis | Assesses risk of modifications | -- | tasks/architect-analyze-impact | No |
 | 24 | `scripts/coverage-analyzer.js` | Testing | Test coverage analysis | -- | tasks/qa-generate-tests | No |
 | 25 | `scripts/test-generator.js` | Testing | Test file generation | -- | tasks/qa-generate-tests, getting-started docs | No |
@@ -82,7 +82,7 @@ These scripts are imported in `.sinapse-ai/infrastructure/index.js` and exposed
 | 50 | `scripts/config-cache.js` | Config | Configuration caching layer | -- | config-resolver, agent-config-loader, core modules | No |
 | 51 | `scripts/config-loader.js` | Config | Configuration file loading | -- | index.js internal reference | No |
 | 52 | `scripts/output-formatter.js` | Config | Output formatting utilities | -- | core index, workflow-intelligence, CLI search, many tests | No |
-| 53 | `scripts/yaml-validator.js` | Config | YAML file validation | -- | component-generator, modification-validator, sinapse-master agent | No |
+| 53 | `scripts/yaml-validator.js` | Config | YAML file validation | -- | component-generator, modification-validator, sinapse-orqx agent | No |
 
 ### 1.2 Scripts NOT Exported via `index.js` (28 scripts)
 

package/docs/guides/workflows/xref-phase6-supporting.md

@@ -152,7 +152,7 @@ All layers extend `base-layer.js` and are managed by `quality-gate-manager.js`.
 
 ### External References (30+ files reference this system)
 
-- **Agent definitions:** `development/agents/devops.md`, `development/agents/dev.md` (via quality gate tasks)
+- **Agent definitions:** `development/agents/devops.md`, `development/agents/developer.md` (via quality gate tasks)
 - **Tasks:** `github-devops-pre-push-quality-gate.md`, `qa-gate.md`, `dev-develop-story.md`
 - **Workflows:** `story-development-cycle.yaml`, `brownfield-*.yaml`
 - **CLI commands:** `cli/commands/metrics/*` (show, record, cleanup, seed)

package/docs/guides/workflows-guide.md

@@ -58,7 +58,7 @@ The most common workflow for iterative development:
 ┌─────────────────────────────────────────────────────────────┐
 │                   Story Development Cycle                    │
 │                                                              │
-│  @sm: Create Story → @po: Validate → @dev: Implement → @qa  │
+│  @sm: Create Story → @po: Validate → @dev: Implement → @quality-gate  │
 │         │                  │               │            │    │
 │         ▼                  ▼               ▼            ▼    │
 │     Draft Story       10 Checks       Code + Tests    Gate   │
@@ -284,7 +284,7 @@ steps:
 Workflows persist across Claude Code sessions:
 
 1. User starts new session
-2. Activates @sinapse-master
+2. Activates @sinapse-orqx
 3. Runs `*run-workflow {name} continue`
 4. System loads state, shows current step
 5. User executes step

package/docs/installation/faq.md

@@ -367,7 +367,7 @@ npx sinapse-ai install
 1. **Copy an existing agent:**
 
    ```bash
-   cp .sinapse-ai/agents/dev.md .sinapse-ai/agents/my-agent.md
+   cp .sinapse-ai/agents/developer.md .sinapse-ai/agents/my-agent.md
    ```
 
 2. **Edit the YAML frontmatter:**

package/docs/installation/troubleshooting.md

@@ -610,7 +610,7 @@ YAMLException: bad indentation of a mapping entry
 
 ```bash
 # Validate YAML syntax
-npx yaml-lint .sinapse-ai/agents/dev.md
+npx yaml-lint .sinapse-ai/agents/developer.md
 
 # Common fixes:
 # - Use spaces, not tabs
@@ -618,7 +618,7 @@ npx yaml-lint .sinapse-ai/agents/dev.md
 # - Check for special characters in strings (use quotes)
 
 # Reinstall to get clean agent files
-mv .sinapse-ai/agents/dev.md .sinapse-ai/agents/dev.md.backup
+mv .sinapse-ai/agents/developer.md .sinapse-ai/agents/developer.md.backup
 npx sinapse-ai install --full
 ```
 

package/docs/installation/v4-quick-start.md

@@ -85,7 +85,7 @@ Expected structure:
 SINAPSE uses specialized agents for different tasks. In your AI-powered IDE or Claude Code CLI, type:
 
 ```
-@sinapse-master
+@sinapse-orqx
 ```
 
 The agent will greet you and show available commands:
@@ -137,7 +137,7 @@ The developer agent (Dex) will activate with a greeting showing:
 Stories drive development in SINAPSE. Activate the Product Owner and create one:
 
 ```
-@po *create-story
+@product-lead *create-story
 ```
 
 Follow the prompts to define:

package/docs/prd-cli-graph-dashboard.md

@@ -20,7 +20,7 @@ Este PRD define um CLI Graph Dashboard que expõe essa riqueza de dados de forma
 
 | Date | Version | Description | Author |
 |------|---------|-------------|--------|
-| 2026-02-21 | 1.0 | Initial PRD draft baseado em deep research | Morgan (@pm) |
+| 2026-02-21 | 1.0 | Initial PRD draft baseado em deep research | Morgan (@project-lead) |
 
 ---
 

package/docs/pt/DOCUMENTATION-ROADMAP.md

@@ -168,7 +168,7 @@ Todos os novos documentos devem ser criados em **3 idiomas**:
 **Fluxo de tradução:**
 
 1. Criar versão em inglês primeiro
-2. Usar @dev ou agente de tradução para PT-BR e ES
+2. Usar @developer ou agente de tradução para PT-BR e ES
 3. Revisar traduções para precisão técnica
 
 ---

package/docs/pt/FEATURE_PROCESS.md

@@ -79,7 +79,7 @@ Release (creditado no CHANGELOG.md)
 
 ### Quem Pode Adicionar ao Backlog?
 
-O Product Owner (@po) é a única autoridade para adicionar itens ao backlog interno.
+O Product Owner (@product-lead) é a única autoridade para adicionar itens ao backlog interno.
 Isso garante priorização adequada e alinhamento com os objetivos do projeto.
 
 ### Crédito aos Contribuidores

package/docs/pt/README.md

@@ -101,12 +101,12 @@ docs/
 Seguimos práticas i18n padrão da indústria:
 
 1. Conteúdo em inglês fica na raiz (`docs/`)
-2. Traduções vão nas pastas de idioma (`docs/pt/`, `docs/es/`, `docs/zh/`)
+2. Traduções vão nas pastas de idioma (`docs/pt/`)
 3. Estrutura de arquivos espelha a versão em inglês
 4. Adicione cabeçalho de tradução em cada arquivo:
    ```markdown
    <!--
-     Translation: PT | ES | ZH
+     Translation: PT
      Original: /docs/[filename].md
      Last sync: YYYY-MM-DD
    -->

package/docs/pt/agents/archetype-rationale.md

@@ -139,7 +139,7 @@ Após avaliar múltiplos sistemas de arquétipos, selecionamos os signos do zod
 
 ### Exemplos de Mapeamento
 
-#### Exemplo 1: @dev → Aquário (Dex)
+#### Exemplo 1: @developer → Aquário (Dex)
 **Função do Agente:** Construir código, inovar soluções, resolver problemas técnicos
 
 **Traços de Aquário:**
@@ -153,7 +153,7 @@ Após avaliar múltiplos sistemas de arquétipos, selecionamos os signos do zod
 
 ---
 
-#### Exemplo 2: @qa → Virgem (Quinn)
+#### Exemplo 2: @quality-gate → Virgem (Quinn)
 **Função do Agente:** Garantia de qualidade, testes, perfeccionismo
 
 **Traços de Virgem:**
@@ -167,7 +167,7 @@ Após avaliar múltiplos sistemas de arquétipos, selecionamos os signos do zod
 
 ---
 
-#### Exemplo 3: @po → Libra (Pax)
+#### Exemplo 3: @product-lead → Libra (Pax)
 **Função do Agente:** Equilibrar prioridades, mediar stakeholders, criar harmonia
 
 **Traços de Libra:**
@@ -492,7 +492,7 @@ greeting = `${icon} ${name} the ${role} (${zodiac_symbol} ${archetype}) ready to
 ```
 
 3. **Preservar Funcionalidade Existente:**
-- NÃO mudar IDs de agentes (@dev, @qa, etc.)
+- NÃO mudar IDs de agentes (@developer, @quality-gate, etc.)
 - Manter todos os comandos e dependências existentes
 - Apenas ADICIONAR campos de persona, não remover nada
 

package/docs/pt/agents/persona-definitions.md

@@ -46,7 +46,7 @@ A paleta de 6 cores foi projetada para:
 
 ## 12 Agentes Nomeados
 
-### 1. @dev - Dex (Construtor)
+### 1. @developer - Dex (Construtor)
 
 **Identidade Principal:**
 - **Nome:** Dex
@@ -72,7 +72,7 @@ Aquário representa inovação, pensamento progressivo e domínio técnico - per
 
 ---
 
-### 2. @qa - Quinn (Guardião)
+### 2. @quality-gate - Quinn (Guardião)
 
 **Identidade Principal:**
 - **Nome:** Quinn
@@ -98,7 +98,7 @@ Virgem incorpora atenção aos detalhes, pensamento analítico e perfeccionismo
 
 ---
 
-### 3. @po - Pax (Equilibrador)
+### 3. @product-lead - Pax (Equilibrador)
 
 **Identidade Principal:**
 - **Nome:** Pax
@@ -124,7 +124,7 @@ Libra representa equilíbrio, justiça e mediação - responsabilidades centrais
 
 ---
 
-### 4. @pm - Morgan (Estrategista)
+### 4. @project-lead - Morgan (Estrategista)
 
 **Identidade Principal:**
 - **Nome:** Morgan
@@ -150,7 +150,7 @@ Capricórnio incorpora estrutura, disciplina e planejamento estratégico. "Morga
 
 ---
 
-### 5. @sm - River (Facilitador)
+### 5. @sprint-lead - River (Facilitador)
 
 **Identidade Principal:**
 - **Nome:** River
@@ -338,7 +338,7 @@ Touro representa confiabilidade, construção de fundações sólidas e trabalho
 
 ---
 
-### 12. @sinapse-master - Orion (Comandante)
+### 12. @sinapse-orqx - Orion (Comandante)
 
 **Identidade Principal:**
 - **Nome:** Orion
@@ -355,7 +355,7 @@ Touro representa confiabilidade, construção de fundações sólidas e trabalho
 - **Energia:** Orquestra agentes, toma decisões ousadas, lidera iniciativas
 
 **Exemplos de Saudação:**
-- **Nível 1 (Mínimo):** `🌟 SINAPSE-Master Agent ready`
+- **Nível 1 (Mínimo):** `🌟 SINAPSE-Orqx Agent ready`
 - **Nível 2 (Nomeado):** `🌟 Orion (Comandante) pronto. Vamos orquestrar o sucesso!`
 - **Nível 3 (Arquetípico):** `🌟 Orion o Comandante (♈ Áries) pronto para comandar!`
 
@@ -377,7 +377,7 @@ Touro representa confiabilidade, construção de fundações sólidas e trabalho
 Equilíbrio perfeito entre todos os quatro elementos!
 
 ### Por Cor:
-- **Ciano:** 3 agentes (dev, sm, sinapse-master) - Inovação & fluxo
+- **Ciano:** 3 agentes (dev, sm, sinapse-orqx) - Inovação & fluxo
 - **Verde:** 3 agentes (qa, ux-design-expert, devops) - Qualidade & crescimento
 - **Amarelo:** 2 agentes (po, data-engineer) - Clareza & análise
 - **Vermelho:** 1 agente (analyst) - Intensidade & investigação
@@ -390,7 +390,7 @@ Equilíbrio perfeito entre todos os quatro elementos!
 - **Qualidade:** 2 agentes (qa, ux-design-expert)
 - **Gestão:** 3 agentes (po, pm, sm)
 - **Estratégia:** 3 agentes (architect, analyst, data-engineer)
-- **Meta/Docs:** 2 agentes (docs, sinapse-master)
+- **Meta/Docs:** 2 agentes (docs, sinapse-orqx)
 
 ---
 

package/docs/pt/architecture/ADE-ARCHITECT-HANDOFF.md

@@ -1,6 +1,6 @@
 # ADE Architect Handoff
 
-> **De:** Quinn (@qa) - QA Agent
+> **De:** Quinn (@quality-gate) - QA Agent
 > **Para:** Sage (@architect) - Solution Architect
 > **Data:** 2026-01-28
 > **Projeto:** SINAPSE Autonomous Development Engine (ADE)
@@ -11,7 +11,7 @@
 
 O ADE é um projeto de **Prompt Engineering + Infraestrutura** para habilitar execução autônoma de desenvolvimento no SINAPSE. Aproximadamente **60% do trabalho é criação de tasks .md, workflows .yaml e templates** - não código tradicional.
 
-**Você é o líder técnico deste projeto.** @dev será acionado apenas para scripts JS específicos.
+**Você é o líder técnico deste projeto.** @developer será acionado apenas para scripts JS específicos.
 
 ---
 
@@ -92,7 +92,7 @@ Embora os épicos tenham dependências de **implementação**, você pode **prep
 | 1.4   | Auto-create trigger                   | Workflow    |
 | 1.5   | status.json integration               | JS + Schema |
 
-**@dev necessário:** Stories 1.1, 1.2, 1.5 (scripts)
+**@developer necessário:** Stories 1.1, 1.2, 1.5 (scripts)
 **@architect lidera:** Stories 1.3, 1.4 (prompts/workflows)
 
 ---
@@ -107,10 +107,10 @@ Embora os épicos tenham dependências de **implementação**, você pode **prep
 | 2.2   | path-analyzer.js            | JS Script           |
 | 2.3   | V3 Schemas (agent, task)    | JSON Schema         |
 | 2.4   | migrate-agent.js            | JS Script           |
-| 2.5   | Pilot migration (@dev, @qa) | Manual + Validação  |
+| 2.5   | Pilot migration (@developer, @quality-gate) | Manual + Validação  |
 | 2.6   | Batch migration             | Orquestração        |
 
-**@dev necessário:** Stories 2.1, 2.2, 2.4 (scripts)
+**@developer necessário:** Stories 2.1, 2.2, 2.4 (scripts)
 **@architect lidera:** Stories 2.3, 2.5, 2.6 (schemas/orquestração)
 
 ---
@@ -128,7 +128,7 @@ Embora os épicos tenham dependências de **implementação**, você pode **prep
 | 3.5   | spec-critique.md              | Task .md       |
 | 3.6   | spec-pipeline.yaml            | Workflow .yaml |
 
-**@dev necessário:** Nenhum
+**@developer necessário:** Nenhum
 **@architect lidera:** TODAS as stories (100% prompt engineering)
 
 ---
@@ -146,7 +146,7 @@ Embora os épicos tenham dependências de **implementação**, você pode **prep
 | 4.5   | subtask-verifier.js                | JS Script     |
 | 4.6   | plan-tracker.js                    | JS Script     |
 
-**@dev necessário:** Stories 4.5, 4.6 (scripts)
+**@developer necessário:** Stories 4.5, 4.6 (scripts)
 **@architect lidera:** Stories 4.1, 4.2, 4.3, 4.4 (prompts)
 
 ---
@@ -162,7 +162,7 @@ Embora os épicos tenham dependências de **implementação**, você pode **prep
 | 5.3   | Escalation triggers  | Workflow       |
 | 5.4   | Retry policies       | Config + Logic |
 
-**@dev necessário:** Story 5.1 (script)
+**@developer necessário:** Story 5.1 (script)
 **@architect lidera:** Stories 5.2, 5.3, 5.4
 
 ---
@@ -179,7 +179,7 @@ Embora os épicos tenham dependências de **implementação**, você pode **prep
 | 6.4   | review-qa.md (Dev→QA→Dev) | Task .md             |
 | 6.5   | Quality metrics           | Schema + Aggregation |
 
-**@dev necessário:** Story 6.5 (metrics script, opcional)
+**@developer necessário:** Story 6.5 (metrics script, opcional)
 **@architect lidera:** Stories 6.1, 6.2, 6.3, 6.4
 
 ---
@@ -195,7 +195,7 @@ Embora os épicos tenham dependências de **implementação**, você pode **prep
 | 7.3   | Pattern learning                 | Task .md     |
 | 7.4   | Cross-project insights           | Task .md     |
 
-**@dev necessário:** Stories 7.1, 7.2 (Supabase)
+**@developer necessário:** Stories 7.1, 7.2 (Supabase)
 **@architect lidera:** Stories 7.3, 7.4
 
 ---
@@ -275,10 +275,10 @@ Semanas 9-10: Epic 7 (Memory Layer)
 
 ## Protocolo de Quality Gate
 
-Após completar cada epic, acione @qa para executar o quality gate:
+Após completar cada epic, acione @quality-gate para executar o quality gate:
 
 ```
-@qa *gate epic-{N}-{name}
+@quality-gate *gate epic-{N}-{name}
 ```
 
 **Decisões possíveis:**
@@ -321,18 +321,18 @@ Não há dependência do Dashboard para o ADE funcionar.
 
 1. **Ler o PRD completo** - `docs/prd/sinapse-autonomous-development-engine.md`
 2. **Ler o Auto-Claude Analysis** - `docs/architecture/AUTO-CLAUDE-ANALYSIS-COMPLETE.md`
-3. **Iniciar Epic 1.1** - worktree-manager.js (delegar para @dev)
+3. **Iniciar Epic 1.1** - worktree-manager.js (delegar para @developer)
 4. **Em paralelo, desenhar os schemas V3** (Epic 2.3)
 
 ---
 
 ## Perguntas para @architect Antes de Começar
 
-1. Prefere começar pelo código (Epic 1.1 com @dev) ou pelo design (V3 schemas)?
+1. Prefere começar pelo código (Epic 1.1 com @developer) ou pelo design (V3 schemas)?
 2. Quer criar um agente @prompt-engineer especializado ou assumir esse papel?
 3. Alguma dúvida sobre o escopo ou dependências?
 
 ---
 
-_Handoff preparado por Quinn (@qa) - Guardian of Quality_
+_Handoff preparado por Quinn (@quality-gate) - Guardian of Quality_
 _Data: 2026-01-28_

package/docs/pt/architecture/ADE-EPIC1-HANDOFF.md

@@ -1,6 +1,6 @@
 # ADE Epic 1 Handoff - Worktree Manager
 
-> **De:** Quinn (@qa) - QA Agent
+> **De:** Quinn (@quality-gate) - QA Agent
 > **Para:** Próximo Desenvolvedor
 > **Data:** 2026-01-29
 > **Status:** COMPLETO ✅
@@ -82,4 +82,4 @@ await manager.cleanup();
 
 ---
 
-_Handoff preparado por Quinn (@qa) - Guardião da Qualidade_
+_Handoff preparado por Quinn (@quality-gate) - Guardião da Qualidade_

package/docs/pt/architecture/ADE-EPIC2-HANDOFF.md

@@ -1,6 +1,6 @@
 # ADE Epic 2 Handoff - Migração V2→V3
 
-> **De:** Quinn (@qa) - QA Agent
+> **De:** Quinn (@quality-gate) - QA Agent
 > **Para:** Próximo Desenvolvedor
 > **Data:** 2026-01-29
 > **Status:** COMPLETO ✅
@@ -103,4 +103,4 @@ autoClaude:
 
 ---
 
-_Handoff preparado por Quinn (@qa) - Guardião da Qualidade_
+_Handoff preparado por Quinn (@quality-gate) - Guardião da Qualidade_

package/docs/pt/architecture/ADE-EPIC3-HANDOFF.md

@@ -1,6 +1,6 @@
 # ADE Epic 3 Handoff - Spec Pipeline
 
-> **De:** Quinn (@qa) - QA Agent
+> **De:** Quinn (@quality-gate) - QA Agent
 > **Para:** Aria (@architect) - Solution Architect
 > **Data:** 2026-01-28
 > **Status:** Epic 1+2 COMPLETOS → Epic 3 DESBLOQUEADO
@@ -49,7 +49,7 @@ Solicitação Usuário → Gather → Assess → Research → Write → Critique
 | 3.5   | `spec-critique.md`              | Task .md       | @architect |
 | 3.6   | `spec-pipeline.yaml`            | Workflow .yaml | @architect |
 
-**@dev necessário:** Nenhum
+**@developer necessário:** Nenhum
 **@architect lidera:** TODAS as stories
 
 ---
@@ -199,7 +199,7 @@ autoClaude:
 - Decisão PASS/NEEDS_REVISION
 - Spec revisada (se auto-corrigida)
 
-**Agent:** Capacidades do @qa (canCritique: true)
+**Agent:** Capacidades do @quality-gate (canCritique: true)
 
 **Pattern:**
 
@@ -270,11 +270,11 @@ autoClaude:
 ### Enum de Fases do Pipeline
 
 ```
-spec-gather    # @pm - coletar requisitos
+spec-gather    # @project-lead - coletar requisitos
 spec-assess    # @architect - avaliar complexidade
 spec-research  # @analyst - pesquisar dependências
-spec-write     # @pm - escrever especificação
-spec-critique  # @qa - validar qualidade
+spec-write     # @project-lead - escrever especificação
+spec-critique  # @quality-gate - validar qualidade
 ```
 
 ---
@@ -311,7 +311,7 @@ spec-critique  # @qa - validar qualidade
 Após completar o Epic 3, execute:
 
 ```
-@qa *gate epic-3-spec-pipeline
+@quality-gate *gate epic-3-spec-pipeline
 ```
 
 **Validação:**
@@ -322,6 +322,6 @@ Após completar o Epic 3, execute:
 
 ---
 
-_Handoff preparado por Quinn (@qa) - Guardião da Qualidade_
+_Handoff preparado por Quinn (@quality-gate) - Guardião da Qualidade_
 _Commit: 3fea6ca - feat(ade): complete Epic 1+2_
 _Data: 2026-01-28_

package/docs/pt/architecture/ade-architecture.md

@@ -179,11 +179,11 @@ Componentes:
 
 | Fase       | Agente     | Saída             |
 | ---------- | ---------- | ----------------- |
-| 1. Coletar | @pm        | requirements.json |
+| 1. Coletar | @project-lead        | requirements.json |
 | 2. Avaliar | @architect | complexity.json   |
 | 3. Pesquisar | @analyst | research.json     |
-| 4. Escrever | @pm        | spec.md           |
-| 5. Criticar | @qa        | critique.json     |
+| 4. Escrever | @project-lead        | spec.md           |
+| 5. Criticar | @quality-gate        | critique.json     |
 
 **Adaptação de Complexidade:**
 
@@ -284,7 +284,7 @@ Componentes:
 │          │  APROVADA   │ → Concluído                        │
 │          └─────────────┘                                    │
 │          ┌──────▼──────┐                                    │
-│          │PRECISA_REVISAR│ → Criar Requisição Correção → @dev Corrigir │
+│          │PRECISA_REVISAR│ → Criar Requisição Correção → @developer Corrigir │
 │          └─────────────┘    └────────────────────────┘     │
 │                                      │                      │
 │                 ┌────────────────────┘                      │

package/docs/pt/architecture/adr/adr-hcs-health-check-system.md

@@ -5,9 +5,9 @@
 **ID do ADR:** ADR-HCS-001
 **Status:** Proposto
 **Criado:** 2025-12-30
-**Autor:** @architect (Aria) via @dev (Dex)
+**Autor:** @architect (Aria) via @developer (Dex)
 **Story:** Investigação HCS-1
-**Decisores:** @architect, @po, Tech Lead
+**Decisores:** @architect, @product-lead, Tech Lead
 
 ---
 
@@ -369,7 +369,7 @@ tools/
 
 | Data       | Decisão                         | Autor               |
 | ---------- | ------------------------------- | ------------------- |
-| 2025-12-30 | Proposta inicial de arquitetura | @architect via @dev |
+| 2025-12-30 | Proposta inicial de arquitetura | @architect via @developer |
 
 ---