sinapse-ai 5.0.8 → 6.0.1

package/docs/guides/agents/SM-SYSTEM.md

@@ -2,14 +2,14 @@
 
 > **Versao:** 1.0.0
 > **Criado:** 2026-02-04
-> **Owner:** @sm (River - Facilitator)
+> **Owner:** @sprint-lead (River - Facilitator)
 > **Status:** Documentacao Oficial
 
 ---
 
 ## Visao Geral
 
-O agente **@sm (River)** e o Scrum Master tecnico do SINAPSE, especializado em preparacao de stories e facilitacao de processos ageis. Seu papel principal e criar stories detalhadas e acionaveis que agentes desenvolvedores possam implementar com minima necessidade de pesquisa adicional.
+O agente **@sprint-lead (River)** e o Scrum Master tecnico do SINAPSE, especializado em preparacao de stories e facilitacao de processos ageis. Seu papel principal e criar stories detalhadas e acionaveis que agentes desenvolvedores possam implementar com minima necessidade de pesquisa adicional.
 
 **Responsabilidades Principais:**
 - Criacao e refinamento de user stories
@@ -42,8 +42,8 @@ O agente **@sm (River)** e o Scrum Master tecnico do SINAPSE, especializado em p
 
 | Arquivo | Proposito |
 |---------|-----------|
-| `.sinapse-ai/development/agents/sm.md` | Definicao core do agente SM |
-| `.claude/commands/SINAPSE/agents/sm.md` | Comando Claude Code para ativar @sm |
+| `.sinapse-ai/development/agents/sprint-lead.md` | Definicao core do agente SM |
+| `.claude/commands/SINAPSE/agents/sprint-lead.md` | Comando Claude Code para ativar @sprint-lead |
 | `.cursor/rules/sm.md` | Regras para Cursor IDE |
 | `.cursor/rules/sm.mdc` | Regras compiladas para Cursor |
 
@@ -60,11 +60,11 @@ O agente **@sm (River)** e o Scrum Master tecnico do SINAPSE, especializado em p
 
 | Arquivo | Agente | Proposito |
 |---------|--------|-----------|
-| `.sinapse-ai/development/agents/po.md` | @po | Coordena com @sm em backlog e sprint planning |
-| `.sinapse-ai/development/agents/dev.md` | @dev | Recebe stories do @sm para implementacao |
-| `.sinapse-ai/development/agents/pm.md` | @pm | Cria epics que @sm quebra em stories |
+| `.sinapse-ai/development/agents/product-lead.md` | @product-lead | Coordena com @sprint-lead em backlog e sprint planning |
+| `.sinapse-ai/development/agents/developer.md` | @developer | Recebe stories do @sprint-lead para implementacao |
+| `.sinapse-ai/development/agents/project-lead.md` | @project-lead | Cria epics que @sprint-lead quebra em stories |
 | `.sinapse-ai/development/agents/devops.md` | @github-devops | Recebe stories completas para push/PR |
-| `.sinapse-ai/development/agents/qa.md` | @qa | Coordena em risk profiling |
+| `.sinapse-ai/development/agents/quality-gate.md` | @quality-gate | Coordena em risk profiling |
 
 ### Arquivos de Workflows que Utilizam @sm
 
@@ -93,12 +93,12 @@ O agente **@sm (River)** e o Scrum Master tecnico do SINAPSE, especializado em p
 ```mermaid
 flowchart TB
     subgraph INPUTS["📥 INPUTS"]
-        PRD["📄 PRD/Epic<br/>(from @pm)"]
-        BACKLOG["📋 Backlog Priorizado<br/>(from @po)"]
+        PRD["📄 PRD/Epic<br/>(from @project-lead)"]
+        BACKLOG["📋 Backlog Priorizado<br/>(from @product-lead)"]
         ARCH["🏗️ Arquitetura<br/>(docs/architecture/)"]
     end
 
-    subgraph SM_AGENT["🌊 @sm (River) - Scrum Master"]
+    subgraph SM_AGENT["🌊 @sprint-lead (River) - Scrum Master"]
         direction TB
 
         subgraph COMMANDS["Comandos Disponiveis"]
@@ -145,8 +145,8 @@ flowchart TB
     CLICKUP --> HANDOFF
 
     subgraph COLLABORATION["👥 COLABORACAO"]
-        DEV_AGENT["@dev (Dex)<br/>Recebe stories"]
-        PO_AGENT["@po (Pax)<br/>Valida stories"]
+        DEV_AGENT["@developer (Dex)<br/>Recebe stories"]
+        PO_AGENT["@product-lead (Pax)<br/>Valida stories"]
         DEVOPS_AGENT["@github-devops (Gage)<br/>Push/PR apos conclusao"]
     end
 
@@ -199,7 +199,7 @@ flowchart TD
 
 ```mermaid
 flowchart LR
-    subgraph SM_SCOPE["🌊 @sm - Escopo Local"]
+    subgraph SM_SCOPE["🌊 @sprint-lead - Escopo Local"]
         CREATE_BRANCH["git checkout -b<br/>feature/X.Y-story-name"]
         LIST_BRANCH["git branch<br/>Listar branches"]
         SWITCH_BRANCH["git checkout<br/>Trocar branch"]
@@ -242,17 +242,17 @@ flowchart LR
 ```mermaid
 flowchart TB
     subgraph UPSTREAM["⬆️ UPSTREAM - Fornece para @sm"]
-        PM_UP["@pm (Morgan)<br/>Cria estrutura de epics"]
-        PO_UP["@po (Pax)<br/>Prioriza backlog"]
+        PM_UP["@project-lead (Morgan)<br/>Cria estrutura de epics"]
+        PO_UP["@product-lead (Pax)<br/>Prioriza backlog"]
         ANALYST_UP["@analyst (Sage)<br/>Pesquisa e insights"]
     end
 
-    SM_CENTRAL["🌊 @sm (River)<br/>Scrum Master"]
+    SM_CENTRAL["🌊 @sprint-lead (River)<br/>Scrum Master"]
 
     subgraph DOWNSTREAM["⬇️ DOWNSTREAM - Recebe de @sm"]
-        DEV_DOWN["@dev (Dex)<br/>Implementa stories"]
-        PO_DOWN["@po (Pax)<br/>Valida stories"]
-        QA_DOWN["@qa (Quinn)<br/>Risk profiling"]
+        DEV_DOWN["@developer (Dex)<br/>Implementa stories"]
+        PO_DOWN["@product-lead (Pax)<br/>Valida stories"]
+        QA_DOWN["@quality-gate (Quinn)<br/>Risk profiling"]
     end
 
     subgraph LATERAL["↔️ LATERAL - Coordena com @sm"]
@@ -279,16 +279,16 @@ flowchart TB
 
 | Agente | Relacionamento | Acao |
 |--------|----------------|------|
-| **@pm (Morgan)** | Recebe de | Epic structure, PRD shardado |
-| **@po (Pax)** | Coordena com | Backlog prioritization, sprint planning |
-| **@dev (Dex)** | Entrega para | Stories prontas para implementacao |
-| **@qa (Quinn)** | Solicita | Risk profiling para stories |
+| **@project-lead (Morgan)** | Recebe de | Epic structure, PRD shardado |
+| **@product-lead (Pax)** | Coordena com | Backlog prioritization, sprint planning |
+| **@developer (Dex)** | Entrega para | Stories prontas para implementacao |
+| **@quality-gate (Quinn)** | Solicita | Risk profiling para stories |
 | **@github-devops (Gage)** | Delega para | Push branches, criar PRs |
 | **@analyst (Sage)** | Consulta | Pesquisa e insights tecnicos |
 
 ### Delegacao para @github-devops
 
-O @sm gerencia APENAS operacoes locais de Git. Para operacoes remotas, **sempre** delegar para @github-devops:
+O @sprint-lead gerencia APENAS operacoes locais de Git. Para operacoes remotas, **sempre** delegar para @github-devops:
 
 **Operacoes Permitidas para @sm:**
 - `git checkout -b feature/X.Y-story-name` - Criar branch local
@@ -326,7 +326,7 @@ qaLocation: docs/qa
 
 # CodeRabbit Integration
 coderabbit_integration:
-  enabled: true  # Controla se @sm popula secao CodeRabbit nas stories
+  enabled: true  # Controla se @sprint-lead popula secao CodeRabbit nas stories
 ```
 
 ### Dependencies do Agente
@@ -369,7 +369,7 @@ dependencies:
 ### Colaboracao com Outros Agentes
 
 1. **Respeite limites** - Nao implemente codigo, nao crie PRs
-2. **Documente handoffs** - Deixe claro o que @dev precisa fazer
+2. **Documente handoffs** - Deixe claro o que @developer precisa fazer
 3. **Coordene com @po** - Backlog prioritization antes de criar stories
 4. **Notifique @github-devops** - Quando story estiver pronta para push
 
@@ -444,7 +444,7 @@ dependencies:
 ## Referencias
 
 ### Arquivos do Agente
-- [Agent: sm.md](.sinapse-ai/development/agents/sm.md)
+- [Agent: sm.md](.sinapse-ai/development/agents/sprint-lead.md)
 - [Task: create-next-story.md](.sinapse-ai/development/tasks/create-next-story.md)
 - [Task: execute-checklist.md](.sinapse-ai/development/tasks/execute-checklist.md)
 - [Task: correct-course.md](.sinapse-ai/development/tasks/correct-course.md)
@@ -471,14 +471,14 @@ dependencies:
 
 | Aspecto | Detalhes |
 |---------|----------|
-| **Agente** | @sm (River) - Scrum Master |
+| **Agente** | @sprint-lead (River) - Scrum Master |
 | **Arquetipo** | Facilitator (Pisces) |
 | **Total de Task Files** | 6 tasks core |
 | **Comandos Disponiveis** | 7 (`*draft`, `*story-checklist`, `*correct-course`, `*help`, `*guide`, `*session-info`, `*exit`) |
 | **Checklists Utilizados** | 4 checklists |
 | **Workflows que Usam @sm** | 7 workflows |
 | **Ferramentas** | git (local), clickup, context7 |
-| **Colabora com** | @pm, @po, @dev, @qa, @github-devops, @analyst |
+| **Colabora com** | @project-lead, @product-lead, @developer, @quality-gate, @github-devops, @analyst |
 | **Delega para** | @github-devops (operacoes remotas) |
 | **Responsabilidade Principal** | Criacao de stories detalhadas e acionaveis |
 
@@ -488,7 +488,7 @@ dependencies:
 
 | Data | Autor | Descricao |
 |------|-------|-----------|
-| 2026-02-04 | @dev | Documento inicial criado |
+| 2026-02-04 | @developer | Documento inicial criado |
 
 ---
 

package/docs/guides/agents/SQUAD-CREATOR-SYSTEM.md

@@ -434,12 +434,12 @@ flowchart LR
         SC_MIGRATE["*migrate-to-v2"]
     end
 
-    subgraph DEV["💻 @dev (Dex)"]
+    subgraph DEV["💻 @developer (Dex)"]
         DEV_IMPL["Implementa funcionalidade"]
         DEV_CODE["Escreve codigo de squad"]
     end
 
-    subgraph QA["🔍 @qa (Quinn)"]
+    subgraph QA["🔍 @quality-gate (Quinn)"]
         QA_REVIEW["Review de codigo"]
         QA_TEST["Testa squad"]
     end

package/docs/guides/agents/UX-DESIGN-EXPERT-SYSTEM.md

@@ -453,10 +453,10 @@ flowchart TB
 | Pesquisa de usuario, personas | @ux-design-expert |
 | Wireframes e prototipos | @ux-design-expert |
 | Auditoria de design system | @ux-design-expert |
-| Construcao de componentes | @ux-design-expert ou @dev |
+| Construcao de componentes | @ux-design-expert ou @developer |
 | Arquitetura frontend | @architect |
-| Implementacao de codigo | @dev |
-| Review de acessibilidade | @ux-design-expert ou @qa |
+| Implementacao de codigo | @developer |
+| Review de acessibilidade | @ux-design-expert ou @quality-gate |
 | Analise de ROI | @ux-design-expert ou @analyst |
 
 ### Handoffs Tipicos
@@ -465,9 +465,9 @@ flowchart TB
 |----|------|----------|-----------|
 | @ux-design-expert | @architect | front-end-spec.md | Especificacao para arquitetura |
 | @architect | @ux-design-expert | architecture.md | Constrains tecnicas |
-| @ux-design-expert | @dev | Component specs + tokens | Implementacao |
-| @dev | @ux-design-expert | Feedback de implementacao | Ajustes de design |
-| @qa | @ux-design-expert | A11y report | Remediacoes |
+| @ux-design-expert | @developer | Component specs + tokens | Implementacao |
+| @developer | @ux-design-expert | Feedback de implementacao | Ajustes de design |
+| @quality-gate | @ux-design-expert | A11y report | Remediacoes |
 
 ---
 
@@ -611,11 +611,11 @@ graph TD
 
 Workflow completo para projetos UI existentes:
 1. **Analyze** - @architect analisa projeto
-2. **PRD** - @pm cria PRD
+2. **PRD** - @project-lead cria PRD
 3. **Spec** - @ux-design-expert cria front-end-spec
 4. **Architecture** - @architect cria arquitetura
-5. **Validate** - @po valida artefatos
-6. **Development Cycle** - @sm, @dev, @qa
+5. **Validate** - @product-lead valida artefatos
+6. **Development Cycle** - @sprint-lead, @developer, @qa
 
 ---
 
@@ -817,7 +817,7 @@ flowchart BT
 | **Total de Comandos** | 19 comandos + 4 universais |
 | **Fases do Workflow** | 5 (Research, Audit, Tokens, Build, Quality) |
 | **Workflows Relacionados** | 4 (design-system-build-quality, brownfield-ui, brownfield-discovery, greenfield-ui) |
-| **Agentes Colaboradores** | 4 (@architect, @dev, @qa, @analyst) |
+| **Agentes Colaboradores** | 4 (@architect, @developer, @quality-gate, @analyst) |
 | **Metodologia Central** | Atomic Design (Brad Frost) |
 | **Nivel de Acessibilidade** | WCAG AA minimo, AAA ideal |
 

package/docs/guides/agents/traces/00-shared-activation-pipeline.md

@@ -481,7 +481,7 @@ Each agent has specific config requirements defined in `.sinapse-ai/data/agent-c
 
 | Agent | Config Sections | Files Loaded | Performance Target |
 |-------|----------------|--------------|-------------------|
-| `sinapse-master` | dataLocation, registry | sinapse-kb.md (lazy) | <30ms |
+| `sinapse-orqx` | dataLocation, registry | sinapse-kb.md (lazy) | <30ms |
 | `dev` | devLoadAlwaysFiles, devStoryLocation, dataLocation | coding-standards.md, tech-stack.md, source-tree.md, technical-preferences.md | <50ms |
 | `qa` | qaLocation, dataLocation, storyBacklog | technical-preferences.md, test-levels-framework.md, test-priorities-matrix.md | <50ms |
 | `devops` | dataLocation, cicdLocation | technical-preferences.md | <50ms |
@@ -622,7 +622,7 @@ Activation → loadUserProfile() → validateUserProfile() → resolveConfig(L5
 | 7 | `.sinapse-ai/core/config/migrate-config.js` | Config | Categorizes `user_profile` as USER_FIELD during migration | Same categorization |
 | 8 | `.sinapse-ai/core/config/schemas/user-config.schema.json` | Schema | `enum: ["bob", "advanced"]` validation | Same validation |
 | 9 | `.sinapse-ai/core/config/templates/user-config.yaml` | Template | Default template value: `bob` | N/A (template default is bob) |
-| 10 | `.sinapse-ai/development/agents/pm.md` | Agent | PM becomes sole orchestrator; bob mode session detection; orchestrates other agents internally | PM operates as normal PM with standard workflow |
+| 10 | `.sinapse-ai/development/agents/project-lead.md` | Agent | PM becomes sole orchestrator; bob mode session detection; orchestrates other agents internally | PM operates as normal PM with standard workflow |
 | 11 | `packages/installer/src/wizard/questions.js` | Install | Presents bob/advanced choice during setup | Same prompt |
 | 12 | `packages/installer/src/wizard/index.js` | Install | Writes `user_profile: bob`; idempotent on re-install | Writes `user_profile: advanced` |
 | 13 | `packages/installer/src/wizard/i18n.js` | Install | Translated "Assisted Mode" text (en/pt/es) | Translated "Advanced Mode" text |
@@ -634,24 +634,24 @@ Activation → loadUserProfile() → validateUserProfile() → resolveConfig(L5
 
 ### 13.3 Impact Matrix: Agent Command Visibility
 
-In `bob` mode, non-PM agents return **empty command lists** (redirect to @pm shown instead). PM agent shows all commands normally.
+In `bob` mode, non-PM agents return **empty command lists** (redirect to @project-lead shown instead). PM agent shows all commands normally.
 
 | Agent | `key` Commands Count | Bob Mode Result | Advanced Mode (`new` session) |
 |-------|---------------------|-----------------|-------------------------------|
 | `@pm` | 4 (`help`, `status`, `run`, `exit`) | All commands shown (PM is primary interface) | Full visibility commands |
-| `@dev` | 4 (`help`, `apply-qa-fixes`, `run-tests`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@qa` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@architect` | 3 (`help`, `create-doc`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@po` | 4 (`help`, `validate`, `gotcha`, `gotchas`) | Empty (redirect to @pm) | Full visibility commands |
-| `@sm` | 2 (`help`, `draft`) | Empty (redirect to @pm) | Full visibility commands |
-| `@analyst` | 2 (`help`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@data-engineer` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@devops` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@ux-design-expert` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@squad-creator` | 7 (most have `key`) | Empty (redirect to @pm) | Full visibility commands |
-| `@sinapse-master` | 0 (uses string visibility) | Empty (redirect to @pm) | Fallback: first 12 commands |
-
-**Note:** Agents with 0 `key` commands (`qa`, `data-engineer`, `devops`, `ux-design-expert`, `sinapse-master`) lack `visibility` array metadata on their commands. In `advanced` mode `workflow` sessions, they fall back to showing first 12 commands. This is a known gap tracked for future improvement.
+| `@dev` | 4 (`help`, `apply-qa-fixes`, `run-tests`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@qa` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@architect` | 3 (`help`, `create-doc`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@po` | 4 (`help`, `validate`, `gotcha`, `gotchas`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@sm` | 2 (`help`, `draft`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@analyst` | 2 (`help`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@data-engineer` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@devops` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@ux-design-expert` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@squad-creator` | 7 (most have `key`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@sinapse-orqx` | 0 (uses string visibility) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+
+**Note:** Agents with 0 `key` commands (`qa`, `data-engineer`, `devops`, `ux-design-expert`, `sinapse-orqx`) lack `visibility` array metadata on their commands. In `advanced` mode `workflow` sessions, they fall back to showing first 12 commands. This is a known gap tracked for future improvement.
 
 ### 13.4 Validation Pipeline Integration
 

package/docs/guides/agents/traces/00-shared-activation-pipeline.v1-act8.md

@@ -481,7 +481,7 @@ Each agent has specific config requirements defined in `.sinapse-ai/data/agent-c
 
 | Agent | Config Sections | Files Loaded | Performance Target |
 |-------|----------------|--------------|-------------------|
-| `sinapse-master` | dataLocation, registry | sinapse-kb.md (lazy) | <30ms |
+| `sinapse-orqx` | dataLocation, registry | sinapse-kb.md (lazy) | <30ms |
 | `dev` | devLoadAlwaysFiles, devStoryLocation, dataLocation | coding-standards.md, tech-stack.md, source-tree.md, technical-preferences.md | <50ms |
 | `qa` | qaLocation, dataLocation, storyBacklog | technical-preferences.md, test-levels-framework.md, test-priorities-matrix.md | <50ms |
 | `devops` | dataLocation, cicdLocation | technical-preferences.md | <50ms |
@@ -622,7 +622,7 @@ Activation → loadUserProfile() → validateUserProfile() → resolveConfig(L5
 | 7 | `.sinapse-ai/core/config/migrate-config.js` | Config | Categorizes `user_profile` as USER_FIELD during migration | Same categorization |
 | 8 | `.sinapse-ai/core/config/schemas/user-config.schema.json` | Schema | `enum: ["bob", "advanced"]` validation | Same validation |
 | 9 | `.sinapse-ai/core/config/templates/user-config.yaml` | Template | Default template value: `bob` | N/A (template default is bob) |
-| 10 | `.sinapse-ai/development/agents/pm.md` | Agent | PM becomes sole orchestrator; bob mode session detection; orchestrates other agents internally | PM operates as normal PM with standard workflow |
+| 10 | `.sinapse-ai/development/agents/project-lead.md` | Agent | PM becomes sole orchestrator; bob mode session detection; orchestrates other agents internally | PM operates as normal PM with standard workflow |
 | 11 | `packages/installer/src/wizard/questions.js` | Install | Presents bob/advanced choice during setup | Same prompt |
 | 12 | `packages/installer/src/wizard/index.js` | Install | Writes `user_profile: bob`; idempotent on re-install | Writes `user_profile: advanced` |
 | 13 | `packages/installer/src/wizard/i18n.js` | Install | Translated "Assisted Mode" text (en/pt/es) | Translated "Advanced Mode" text |
@@ -634,24 +634,24 @@ Activation → loadUserProfile() → validateUserProfile() → resolveConfig(L5
 
 ### 13.3 Impact Matrix: Agent Command Visibility
 
-In `bob` mode, non-PM agents return **empty command lists** (redirect to @pm shown instead). PM agent shows all commands normally.
+In `bob` mode, non-PM agents return **empty command lists** (redirect to @project-lead shown instead). PM agent shows all commands normally.
 
 | Agent | `key` Commands Count | Bob Mode Result | Advanced Mode (`new` session) |
 |-------|---------------------|-----------------|-------------------------------|
 | `@pm` | 4 (`help`, `status`, `run`, `exit`) | All commands shown (PM is primary interface) | Full visibility commands |
-| `@dev` | 4 (`help`, `apply-qa-fixes`, `run-tests`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@qa` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@architect` | 3 (`help`, `create-doc`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@po` | 4 (`help`, `validate`, `gotcha`, `gotchas`) | Empty (redirect to @pm) | Full visibility commands |
-| `@sm` | 2 (`help`, `draft`) | Empty (redirect to @pm) | Full visibility commands |
-| `@analyst` | 2 (`help`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@data-engineer` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@devops` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@ux-design-expert` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@squad-creator` | 7 (most have `key`) | Empty (redirect to @pm) | Full visibility commands |
-| `@sinapse-master` | 0 (uses string visibility) | Empty (redirect to @pm) | Fallback: first 12 commands |
-
-**Note:** Agents with 0 `key` commands (`qa`, `data-engineer`, `devops`, `ux-design-expert`, `sinapse-master`) lack `visibility` array metadata on their commands. In `advanced` mode `workflow` sessions, they fall back to showing first 12 commands. This is a known gap tracked for future improvement.
+| `@dev` | 4 (`help`, `apply-qa-fixes`, `run-tests`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@qa` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@architect` | 3 (`help`, `create-doc`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@po` | 4 (`help`, `validate`, `gotcha`, `gotchas`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@sm` | 2 (`help`, `draft`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@analyst` | 2 (`help`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@data-engineer` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@devops` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@ux-design-expert` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@squad-creator` | 7 (most have `key`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@sinapse-orqx` | 0 (uses string visibility) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+
+**Note:** Agents with 0 `key` commands (`qa`, `data-engineer`, `devops`, `ux-design-expert`, `sinapse-orqx`) lack `visibility` array metadata on their commands. In `advanced` mode `workflow` sessions, they fall back to showing first 12 commands. This is a known gap tracked for future improvement.
 
 ### 13.4 Validation Pipeline Integration
 

package/docs/guides/agents/traces/README.md

@@ -21,15 +21,15 @@ This directory contains comprehensive runtime execution trace documentation for
 | Agent | Persona | Commands | Activation Path | Trace Document |
 |-------|---------|----------|-----------------|----------------|
 | @architect | Aria (Visionary) | 21 | Direct | [architect-execution-trace.md](./architect-execution-trace.md) |
-| @dev | Dex (Builder) | 36 | Direct | [dev-execution-trace.md](./dev-execution-trace.md) |
-| @qa | Quinn (Guardian) | 25 | Direct | [qa-execution-trace.md](./qa-execution-trace.md) |
-| @sinapse-master | Nova (Orchestrator) | 33 | Direct | [sinapse-master-execution-trace.md](./sinapse-master-execution-trace.md) |
+| @developer | Dex (Builder) | 36 | Direct | [dev-execution-trace.md](./dev-execution-trace.md) |
+| @quality-gate | Quinn (Guardian) | 25 | Direct | [qa-execution-trace.md](./qa-execution-trace.md) |
+| @sinapse-orqx | Nova (Orchestrator) | 33 | Direct | [sinapse-orqx-execution-trace.md](./sinapse-orqx-execution-trace.md) |
 | @devops | Gage (Pipeline) | 30 | CLI Wrapper | [devops-execution-trace.md](./devops-execution-trace.md) |
 | @data-engineer | Dara (Architect) | 27 | CLI Wrapper | [data-engineer-execution-trace.md](./data-engineer-execution-trace.md) |
 | @ux-design-expert | Uma (Harmonizer) | 24 | CLI Wrapper | [ux-design-expert-execution-trace.md](./ux-design-expert-execution-trace.md) |
-| @po | Pax (Balancer) | 17 | Direct | [po-execution-trace.md](./po-execution-trace.md) |
-| @pm | Morgan (Strategist) | 13 | Direct | [pm-execution-trace.md](./pm-execution-trace.md) |
-| @sm | River (Flow) | 6 | Direct | [sm-execution-trace.md](./sm-execution-trace.md) |
+| @product-lead | Pax (Balancer) | 17 | Direct | [po-execution-trace.md](./po-execution-trace.md) |
+| @project-lead | Morgan (Strategist) | 13 | Direct | [pm-execution-trace.md](./pm-execution-trace.md) |
+| @sprint-lead | River (Flow) | 6 | Direct | [sm-execution-trace.md](./sm-execution-trace.md) |
 | @analyst | Alex (Explorer) | 14 | Direct | [analyst-execution-trace.md](./analyst-execution-trace.md) |
 | @squad-creator | Forge (Creator) | 13 | Direct | [squad-creation-execution-trace.md](./squad-creation-execution-trace.md) |
 
@@ -43,7 +43,7 @@ graph LR
         A1[@architect] --> GB[GreetingBuilder.buildGreeting]
         A2[@dev] --> GB
         A3[@qa] --> GB
-        A4[@sinapse-master] --> GB
+        A4[@sinapse-orqx] --> GB
         A5[@po] --> GB
         A6[@pm] --> GB
         A7[@sm] --> GB
@@ -71,7 +71,7 @@ graph LR
 ```mermaid
 graph TD
     subgraph "Orchestration Layer"
-        MASTER[@sinapse-master<br/>Nova]
+        MASTER[@sinapse-orqx<br/>Nova]
     end
 
     subgraph "Management Layer"
@@ -135,15 +135,15 @@ graph TD
 
 | Agent | Priority | Config Sections | Files Loaded | Perf Target |
 |-------|----------|-----------------|--------------|-------------|
-| @sinapse-master | Critical | dataLocation, registry | sinapse-kb.md (lazy) | <30ms |
-| @dev | High | devLoadAlwaysFiles, devStoryLocation, dataLocation | coding-standards.md, tech-stack.md, source-tree.md, technical-preferences.md | <50ms |
-| @qa | High | qaLocation, dataLocation, storyBacklog | technical-preferences.md, test-levels-framework.md, test-priorities-matrix.md | <50ms |
+| @sinapse-orqx | Critical | dataLocation, registry | sinapse-kb.md (lazy) | <30ms |
+| @developer | High | devLoadAlwaysFiles, devStoryLocation, dataLocation | coding-standards.md, tech-stack.md, source-tree.md, technical-preferences.md | <50ms |
+| @quality-gate | High | qaLocation, dataLocation, storyBacklog | technical-preferences.md, test-levels-framework.md, test-priorities-matrix.md | <50ms |
 | @devops | High | dataLocation, cicdLocation | technical-preferences.md | <50ms |
 | @architect | Medium | architecture, dataLocation, templatesLocation | technical-preferences.md | <75ms |
-| @po | Medium | devStoryLocation, prd, storyBacklog, templatesLocation | elicitation-methods.md | <75ms |
-| @sm | Medium | devStoryLocation, storyBacklog, dataLocation | mode-selection-best-practices.md, workflow-patterns.yaml | <75ms |
+| @product-lead | Medium | devStoryLocation, prd, storyBacklog, templatesLocation | elicitation-methods.md | <75ms |
+| @sprint-lead | Medium | devStoryLocation, storyBacklog, dataLocation | mode-selection-best-practices.md, workflow-patterns.yaml | <75ms |
 | @data-engineer | Medium | dataLocation, etlLocation | technical-preferences.md | <75ms |
-| @pm | Low | devStoryLocation, storyBacklog | (none) | <100ms |
+| @project-lead | Low | devStoryLocation, storyBacklog | (none) | <100ms |
 | @analyst | Low | dataLocation, analyticsLocation | brainstorming-techniques.md | <100ms |
 | @ux-design-expert | Low | dataLocation, uxLocation | (none) | <100ms |
 | @squad-creator | Default | dataLocation | (none) | <150ms |
@@ -219,12 +219,12 @@ Multiple agents reference dependencies using `development/{templates,checklists}
 
 | Agent | Affected Dependencies |
 |-------|-----------------------|
-| @qa | Templates in `product/templates/` |
+| @quality-gate | Templates in `product/templates/` |
 | @devops | github-actions-ci.yml, github-actions-cd.yml, github-pr-template.md, changelog-template.md, pre-push-checklist.md, release-checklist.md |
 | @ux-design-expert | 9 templates, 4 checklists, 7 data files all in `product/` |
-| @po | story-tmpl.yaml, po-master-checklist.md, change-checklist.md |
-| @pm | prd-tmpl.yaml, brownfield-prd-tmpl.yaml, pm-checklist.md, change-checklist.md |
-| @sm | story-draft-checklist.md in `product/checklists/` |
+| @product-lead | story-tmpl.yaml, po-master-checklist.md, change-checklist.md |
+| @project-lead | prd-tmpl.yaml, brownfield-prd-tmpl.yaml, pm-checklist.md, change-checklist.md |
+| @sprint-lead | story-draft-checklist.md in `product/checklists/` |
 | @analyst | 4 templates in `product/templates/` |
 
 **Resolution:** The `AgentConfigLoader` resolves dependencies by searching multiple paths: `development/`, `product/`, and root `.sinapse-ai/` directories. The path mismatch does not cause runtime failures but is documented for accuracy.
@@ -235,8 +235,8 @@ Each trace documents files referenced but not found on disk:
 
 | Agent | Missing File | Impact |
 |-------|--------------|--------|
-| @dev | 9 scripts (recovery-tracker.js, stuck-detector.js, etc.), 1 checklist | Non-functional commands |
-| @sinapse-master | add-tech-doc.md | `*add-tech-doc` command non-functional |
+| @developer | 9 scripts (recovery-tracker.js, stuck-detector.js, etc.), 1 checklist | Non-functional commands |
+| @sinapse-orqx | add-tech-doc.md | `*add-tech-doc` command non-functional |
 | @ux-design-expert | integrate-Squad.md | Only `integrate-squad.md` exists |
 | @devops | gitignore-manager, version-tracker | Referenced tools not found |
 

package/docs/guides/agents/traces/analyst-execution-trace.md

@@ -476,16 +476,16 @@ graph TD
 
 | Interaction | Direction | Trigger |
 |-------------|-----------|---------|
-| @pm -> @analyst | Delegates | Market research, competitive analysis, feasibility studies |
+| @project-lead -> @analyst | Delegates | Market research, competitive analysis, feasibility studies |
 | @architect -> @analyst | Delegates | Technical research, dependency analysis |
-| @po -> @analyst | Delegates | Market insights, user research, competitive intelligence |
-| @analyst -> @pm | Handoff | Research findings for PRD creation |
-| @analyst -> @po | Handoff | Market insights for story prioritization |
+| @product-lead -> @analyst | Delegates | Market insights, user research, competitive intelligence |
+| @analyst -> @project-lead | Handoff | Research findings for PRD creation |
+| @analyst -> @product-lead | Handoff | Market insights for story prioritization |
 | @analyst -> @devops | Delegate | Git push operations, PR creation |
 
 ### Delegation Rules (from agent definition)
 
-**Receives from @pm when:**
+**Receives from @project-lead when:**
 - Market research required for PRD creation
 - Competitive landscape analysis needed
 - Feasibility studies for new features
@@ -496,7 +496,7 @@ graph TD
 - Library/framework evaluation required
 - Technology comparison analysis
 
-**Receives from @po when:**
+**Receives from @product-lead when:**
 - Market insights needed for epic/story prioritization
 - User research for feature validation
 - Competitive analysis for backlog grooming

package/docs/guides/agents/traces/architect-execution-trace.md

@@ -528,10 +528,10 @@ graph TD
 |-------------|-----------|---------|
 | @architect -> @data-engineer | Delegate | Database schema design, query optimization |
 | @architect -> @ux-design-expert | Collaborate | Frontend architecture, user flows |
-| @pm -> @architect | Receives | Requirements and strategic direction |
+| @project-lead -> @architect | Receives | Requirements and strategic direction |
 | @architect -> @devops | Delegate | Git push operations, PR creation |
-| @architect -> @dev | Handoff | Architecture documents for implementation |
-| @qa -> @architect | Validate | Architecture checklists (execute-checklist) |
+| @architect -> @developer | Handoff | Architecture documents for implementation |
+| @quality-gate -> @architect | Validate | Architecture checklists (execute-checklist) |
 
 ### Delegation Rules (from agent definition)
 

package/docs/guides/agents/traces/data-engineer-execution-trace.md

@@ -963,11 +963,11 @@ graph TD
 | Interaction | Direction | Trigger |
 |-------------|-----------|---------|
 | @architect -> @data-engineer | Receives | Database schema design, query optimization, RLS policies |
-| @data-engineer -> @dev | Handoff | Migrations, schema definitions, database access patterns |
-| @dev -> @data-engineer | Feedback | Data layer issues, query performance problems |
+| @data-engineer -> @developer | Handoff | Migrations, schema definitions, database access patterns |
+| @developer -> @data-engineer | Feedback | Data layer issues, query performance problems |
 | @data-engineer -> @devops | Delegate | Git push operations, PR creation for migration files |
-| @qa -> @data-engineer | Validate | Database checklists (execute-checklist) |
-| @pm -> @data-engineer | Receives | Data requirements from stories |
+| @quality-gate -> @data-engineer | Validate | Database checklists (execute-checklist) |
+| @project-lead -> @data-engineer | Receives | Data requirements from stories |
 
 ### Delegation Rules (from agent definition)
 

package/docs/guides/agents/traces/dev-execution-trace.md

@@ -1,7 +1,7 @@
-# @dev (Dex) - Execution Trace
+# @developer (Dex) - Execution Trace
 
 > Traced from source code, not documentation.
-> Agent definition: `.sinapse-ai/development/agents/dev.md`
+> Agent definition: `.sinapse-ai/development/agents/developer.md`
 
 ## 1. Activation Trace
 
@@ -9,7 +9,7 @@
 
 | Order | File | Loader | Purpose |
 |-------|------|--------|---------|
-| 1 | `.sinapse-ai/development/agents/dev.md` | AgentConfigLoader.loadAgentDefinition() | Agent definition (YAML block) |
+| 1 | `.sinapse-ai/development/agents/developer.md` | AgentConfigLoader.loadAgentDefinition() | Agent definition (YAML block) |
 | 2 | `.sinapse-ai/core-config.yaml` | GreetingBuilder._loadConfig() | Core configuration + devLoadAlwaysFiles list |
 | 3 | `.sinapse-ai/data/agent-config-requirements.yaml` | AgentConfigLoader.loadRequirements() | Config sections: devLoadAlwaysFiles, devStoryLocation, dataLocation |
 | 4 | `.sinapse-ai/data/workflow-patterns.yaml` | WorkflowNavigator._loadPatterns() | Workflow state detection |
@@ -365,7 +365,7 @@ flowchart TD
 | File | Type | Status |
 |------|------|--------|
 | `qa-fix-issues.md` | Task | EXISTS |
-| `QA_FIX_REQUEST.md` | Input | Dynamic (from @qa) |
+| `QA_FIX_REQUEST.md` | Input | Dynamic (from @quality-gate) |
 
 **Execution flow:**
 
@@ -444,7 +444,7 @@ flowchart TD
 
 | Command | Task File | Behavior |
 |---------|-----------|----------|
-| `*apply-qa-fixes` | apply-qa-fixes.md | Apply QA feedback from @qa review |
+| `*apply-qa-fixes` | apply-qa-fixes.md | Apply QA feedback from @quality-gate review |
 | `*run-tests` | (built-in) | Execute `npm run lint` + `npm test` |
 | `*backlog-debt` | po-manage-story-backlog.md | Elicit debt details, register in backlog |
 
@@ -620,20 +620,20 @@ graph TD
 
 | Interaction | Direction | Trigger |
 |-------------|-----------|---------|
-| @sm -> @dev | Receives | Story assignment for implementation |
-| @dev -> @qa | Handoff | Story "Ready for Review" triggers QA review |
-| @qa -> @dev | Receives | QA feedback via `*apply-qa-fixes` or `QA_FIX_REQUEST.md` |
-| @dev -> @github-devops | Delegate | Git push, PR creation, remote operations |
-| @pm -> @dev | Receives | Requirements and strategic direction via stories |
+| @sprint-lead -> @developer | Receives | Story assignment for implementation |
+| @developer -> @quality-gate | Handoff | Story "Ready for Review" triggers QA review |
+| @quality-gate -> @developer | Receives | QA feedback via `*apply-qa-fixes` or `QA_FIX_REQUEST.md` |
+| @developer -> @github-devops | Delegate | Git push, PR creation, remote operations |
+| @project-lead -> @developer | Receives | Requirements and strategic direction via stories |
 
 ### Delegation Rules (from agent definition)
 
-**Collaborates with @qa when:**
+**Collaborates with @quality-gate when:**
 - Code review feedback received via `*apply-qa-fixes`
 - QA fix requests arrive via `QA_FIX_REQUEST.md`
 - Quality validation during story completion
 
-**Collaborates with @sm when:**
+**Collaborates with @sprint-lead when:**
 - Receiving story assignments
 - Reporting story completion
 

package/docs/guides/agents/traces/devops-execution-trace.md

@@ -700,21 +700,21 @@ graph TD
 
 | Interaction | Direction | Trigger |
 |-------------|-----------|---------|
-| @dev -> @devops | Delegate | Git push and PR creation after story completion |
-| @sm -> @devops | Delegate | Push operations during sprint workflow |
+| @developer -> @devops | Delegate | Git push and PR creation after story completion |
+| @sprint-lead -> @devops | Delegate | Push operations during sprint workflow |
 | @architect -> @devops | Delegate | Repository operations, PR creation |
-| @devops -> @dev | Redirect | Code development tasks (not in scope) |
-| @devops -> @sm | Redirect | Story management tasks (not in scope) |
+| @devops -> @developer | Redirect | Code development tasks (not in scope) |
+| @devops -> @sprint-lead | Redirect | Story management tasks (not in scope) |
 | @devops -> @architect | Redirect | Architecture design tasks (not in scope) |
 
 ### Delegation Rules (from agent definition)
 
-**Receives delegation from @dev (Dex) when:**
+**Receives delegation from @developer (Dex) when:**
 - Story implementation is complete and needs pushing
 - Pull request creation is required
 - Release tagging is needed after merge
 
-**Receives delegation from @sm (River) when:**
+**Receives delegation from @sprint-lead (River) when:**
 - Sprint push workflow is triggered
 - Coordinated multi-story push is needed