sinapse-ai 1.25.0 → 1.25.2

package/docs/framework/codex-parity/codex-integration-process.md

@@ -9,7 +9,7 @@ O Codex hoje e alvo de primeira classe no SINAPSE:
 
 - `AGENTS.md` como contrato operacional do projeto no Codex
 - suporte oficial no installer/sync (`codex` em `ide-configs`)
-- skills nativas via `.codex/skills` com estrategia local-first
+- skills nativas via `.agents/skills` com estrategia local-first e raiz unica
 - pipeline canonico de greeting/ativacao compartilhado
 - validadores dedicados para detectar drift rapidamente
 - suporte a notify command e hooks de ferramenta em releases recentes do Codex CLI
@@ -44,7 +44,7 @@ Regra prática para iniciantes:
 ### Artefatos Codex no projeto
 
 - Agentes auxiliares: `.codex/agents/`
-- Skills locais: `.codex/skills/sinapse-*/SKILL.md`
+- Skills locais: `.agents/skills/sinapse-*/SKILL.md`
 
 ## Fluxo Operacional Recomendado
 
@@ -65,8 +65,8 @@ Fallback: atalhos definidos em `AGENTS.md` (`@architect`, `/architect`, etc.).
 
 Este repositorio usa local-first para skills:
 
-- preferir `.codex/skills` versionado no projeto
-- evitar duplicar com `~/.codex/skills`
+- preferir `.agents/skills` versionado no projeto
+- nao gerar espelhos SINAPSE em `.codex/skills` ou `~/.codex/skills`
 - usar `npm run sync:skills:codex:global` apenas quando quiser instalacao global explicitamente
 
 Isso evita menu duplicado no `/skills` e reduz drift entre equipe/CI.
@@ -97,7 +97,7 @@ Criterio de sucesso:
 
 - `AGENTS.md` presente e coerente
 - `.codex/agents/*.md` existente
-- `.codex/skills/sinapse-*/SKILL.md` existente
+- `.agents/skills/sinapse-*/SKILL.md` existente
 - validadores sem erro
 
 ## Recursos Recentes do Codex (SINAPSE 4.0)
@@ -130,7 +130,7 @@ Mitigacao operacional no SINAPSE:
 ### Skills duplicadas no `/skills`
 
 Causa tipica:
-- artefatos duplicados entre `.codex/skills` e `~/.codex/skills`
+- artefatos SINAPSE duplicados entre raizes de skills descobertas pelo Codex
 
 Correcao:
 - manter local-first neste repo
@@ -168,4 +168,3 @@ Se houver divergencia entre estes documentos, a ordem de verdade para operacao d
 2. scripts reais em `package.json`
 3. este documento
 4. docs de overview
-

package/docs/framework/codex-parity/codex-native-runtime-v2.md

@@ -20,9 +20,9 @@ $sinapse-agent meta-ads-specialist
 ```
 
 `.codex/catalog.json` is the registry for this Codex activation surface. The
-native `.agents/skills` tree is mirrored to `.codex/skills` for compatibility
-with older Codex builds. Clean installs and upgrades reconcile managed files
-idempotently without deleting valid user-owned skills.
+native `.agents/skills` tree is the single Codex discovery surface. Clean
+installs and upgrades remove byte-identical legacy mirrors and quarantine
+divergent managed copies outside discovered skill roots without deleting them.
 
 The default tier deliberately exposes aliases, core agents, orchestrators and
 the parametric activator, not one selector entry per specialist. Users who need
@@ -89,9 +89,9 @@ Current Codex skill entrypoints live under `.agents/skills/`:
 - `sinapse-spec-driven` prepares PRD, Epic, Story, Spec, and Plan delivery.
 - `sinapse-loop` runs an explicitly requested bounded correction loop.
 
-Equivalent `.codex/skills/` copies are compatibility entrypoints for existing
-installations. New Codex discovery should use `.agents/skills/`; both locations
-resolve the same canonical SINAPSE sources.
+Legacy `.codex/skills/sinapse-*` copies are migration inputs only. They are not
+generated or shipped. `.agents/skills/` is the only active Codex skill root for
+SINAPSE.
 
 ## Hook and apply_patch bridge
 
@@ -205,8 +205,8 @@ npm run validate:codex-skills
 npx jest tests/integration/codex-native-golden-journey.test.js --runInBand
 ```
 
-`validate:codex-native` checks project TOML, 1:1 native-agent parity, native and
-compatibility skills, command targets, delegation equivalence, hooks, and the
+`validate:codex-native` checks project TOML, 1:1 native-agent parity, the unique
+native skill root, command targets, delegation equivalence, hooks, and the
 absence of nested Claude/Codex execution. `validate:codex-sync` runs both the
 legacy synchronization validator and the stricter native validator.
 

package/docs/framework/codex-parity/codex-parity-program.md

@@ -118,7 +118,7 @@ Requirements:
 ### Codex Skill Export Layer
 
 Purpose:
-Generate `.codex/skills` from the real Codex catalog, not from an incomplete upstream subset.
+Generate `.agents/skills` from the real Codex catalog, not from an incomplete upstream subset.
 
 Requirements:
 
@@ -222,7 +222,7 @@ Ensure all needed orqx and key framework agents are available through Codex skil
 
 Focus:
 
-- local-first `.codex/skills`
+- local-first `.agents/skills`
 - full orqx coverage
 - clean validation
 - no duplicate global/local skill confusion
@@ -492,7 +492,7 @@ Map the real Codex catalog, its upstreams, and current drift.
 Outputs:
 
 - inventory of `.codex/agents`
-- inventory of `.codex/skills`
+- inventory of `.agents/skills`
 - inventory of canonical sync sources
 - gap matrix between exported Codex artifacts and official sync assumptions
 
@@ -526,7 +526,7 @@ Outputs:
 
 - skill coverage matrix
 - export rules for orqx and core agents
-- clean local-first `.codex/skills` state
+- clean local-first `.agents/skills` state
 
 Success checks:
 

package/docs/framework/codex-parity/codex-total-parity-orchestration-plan.md

@@ -252,7 +252,7 @@ Mitigation:
 ### Risk 2 - Catalog/Skill Drift
 
 Risk:
-Expanded `.codex/agents`, `.codex/skills`, and command/delegation registries can drift apart.
+Expanded `.codex/agents`, `.agents/skills`, and command/delegation registries can drift apart.
 
 Mitigation:
 

package/docs/getting-started.md

@@ -27,14 +27,22 @@ Se algo falhar: `npx sinapse-ai doctor --fix` corrige automaticamente.
 
 ## Ativar primeiro agente
 
-No prompt do Claude Code ou Codex:
+No Claude Code:
 
-```
+```text
 @developer
 *help
 ```
 
-`@developer` ativa o agente de implementação. `*help` lista comandos disponíveis.
+No Codex, use o roteador ou a ativação direta:
+
+```text
+$snps
+$sinapse-agent developer
+```
+
+`@developer` e `*help` pertencem à superfície do Claude Code. No Codex, `$snps`
+roteia a solicitação e `$sinapse-agent developer` ativa o agente de implementação.
 
 ## Próximos passos
 
@@ -61,9 +69,9 @@ npx sinapse-ai uninstall               # remove tudo
 ## Conceitos chave (em 30 segundos)
 
 - **Squad**: equipe de agentes especializados (ex: squad-design tem 15 agentes de design/UX)
-- **Agente**: persona de IA com expertise e comandos específicos (`@developer`, `@architect`, etc.)
+- **Agente**: persona de IA com especialização e comandos específicos (`@developer` no Claude Code; `$sinapse-agent developer` no Codex)
 - **Hook**: enforcement runtime que bloqueia violações da Constitution (ex: PR sem story)
-- **Constitution**: 10 artigos que governam o framework (ver `.sinapse-ai/constitution.md`)
+- **Constitution**: 11 artigos que governam o framework (ver `.sinapse-ai/constitution.md`)
 - **Story**: arquivo `.md` que documenta requisitos antes do código (Documentation-First)
 
 ---

package/docs/guides/codex-config.md

@@ -1,6 +1,6 @@
 # AGENTS.md - SINAPSE
 
-Este arquivo configura o comportamento esperado de agentes no Codex CLI neste repositorio.
+Este arquivo configura o comportamento esperado de agentes no Codex CLI neste repositório.
 
 ## Constitution
 
@@ -14,7 +14,7 @@ Siga `.sinapse-ai/constitution.md` como fonte de verdade:
 - Ecosystem Metrics Accuracy (NON-NEGOTIABLE)
 - Mandatory Delegation (NON-NEGOTIABLE)
 
-## Workflow Obrigatorio
+## Workflow Obrigatório
 
 1. Inicie por uma story em `docs/stories/`
 2. Implemente apenas o que os acceptance criteria pedem
@@ -35,31 +35,31 @@ npm test
 - CLI: `bin/`
 - Pacotes: `packages/`
 - Testes: `tests/`
-- Documentacao: `docs/`
+- Documentação: `docs/`
 
 ## IDE/Agent Sync
 
 - Sincronizar regras/agentes: `npm run sync:ide`
 - Validar drift: `npm run sync:ide:check`
-- Rodar paridade multi-IDE (Claude/Codex/Gemini): `npm run validate:parity`
+- Rodar paridade Claude/Codex: `npm run validate:parity`
 - Sync Claude Code: `npm run sync:ide:claude`
-- Sincronizar Gemini CLI: `npm run sync:ide:gemini`
+- Sincronizar Codex: `npm run sync:ide:codex`
 - Validar Codex sync/integration: `npm run validate:codex-sync`; `npm run validate:codex-integration`
 - Validar command/task registry do Codex: `npm run validate:codex-commands`
-- Validar matriz de delegacao do Codex: `npm run validate:codex-delegation`
+- Validar matriz de delegação do Codex: `npm run validate:codex-delegation`
 - Gerar skills locais do Codex: `npm run sync:skills:codex`
-- Este repositorio usa **local-first**: prefira `.codex/skills` versionado no projeto
+- Este repositório usa **local-first**: `.agents/skills` é a única raiz de skills SINAPSE versionada no projeto
 - Use `sync:skills:codex:global` apenas para testes fora deste repo
 
 ## Command Resolution (Codex)
 
-Quando um agente no Codex receber um `*comando`, prefira resolver a execucao por esta ordem:
+Quando um agente no Codex receber um `*comando`, prefira resolver a execução por esta ordem:
 
 1. Consultar `.codex/command-registry.json`
 2. Opcionalmente usar `node .codex/scripts/resolve-codex-command.js <skill-ou-agent> <comando>`
 3. Carregar a task/workflow/checklist/template mapeada
 
-Isso evita "file hunting" manual e torna a execucao de workflows/tasks mais deterministica no Codex.
+Isso evita "file hunting" manual e torna a execução de workflows/tasks mais determinística no Codex.
 
 ## Delegation Resolution (Codex)
 
@@ -72,68 +72,52 @@ Quando um orqx no Codex precisar decidir um handoff:
    - `codex-shim`
    - `exploratory`
 
-No Codex, nao trate handoffs exploratorios como se fossem caminhos garantidos pelo validator.
+No Codex, não trate handoffs exploratórios como se fossem caminhos garantidos pelo validator.
 
-## Agent Shortcuts (Codex)
+## Ativação de agentes (Codex)
 
-Preferencia de ativacao no Codex CLI:
-1. Use `/skills` e selecione `sinapse-<agent-id>` vindo de `.codex/skills` (ex.: `sinapse-architect`)
-2. Se preferir, use os atalhos abaixo (`@architect`, `/architect`, etc.)
-
-Quando a mensagem do usuario for um atalho de agente, carregue o arquivo correspondente em `.sinapse-ai/development/agents/` (fallback: `.codex/agents/`), renderize o greeting via `generate-greeting.js` e assuma a persona ate receber `*exit`.
-
-Atalhos aceitos por agente (nome completo + alias):
-- `@sinapse-orqx` -> `.sinapse-ai/development/agents/sinapse-orqx.md`
-- `@developer` ou `@dev` -> `.sinapse-ai/development/agents/developer.md`
-- `@quality-gate` ou `@qa` -> `.sinapse-ai/development/agents/quality-gate.md`
-- `@project-lead` ou `@pm` -> `.sinapse-ai/development/agents/project-lead.md`
-- `@product-lead` ou `@po` -> `.sinapse-ai/development/agents/product-lead.md`
-- `@sprint-lead` ou `@sm` -> `.sinapse-ai/development/agents/sprint-lead.md`
-- `@analyst` -> `.sinapse-ai/development/agents/analyst.md`
-- `@architect` -> `.sinapse-ai/development/agents/architect.md`
-- `@data-engineer` -> `.sinapse-ai/development/agents/data-engineer.md`
-- `@devops` -> `.sinapse-ai/development/agents/devops.md`
-- `@squad-creator` -> `.sinapse-ai/development/agents/squad-creator.md`
-- `@ux-design-expert` -> `.sinapse-ai/development/agents/ux-design-expert.md`
-
-Resposta esperada ao ativar atalho:
-1. Confirmar agente ativado
-2. Mostrar 3-6 comandos principais (`*help`, etc.)
-3. Seguir na persona do agente
+- Use `$snps` para roteamento pelo orquestrador principal.
+- Use `$sinapse-agent <agent-id>` para ativação direta, por exemplo
+  `$sinapse-agent developer` ou `$sinapse-agent architect`.
+- O ativador paramétrico resolve a fonte canônica e apenas tasks existentes;
+  não interprete `@agent`, slash commands ou aliases curtos como ativação Codex.
 
 ## Orquestradores (18 orqx: 17 squad + 1 master)
 
-Cada orqx coordena um squad completo de agentes especializados. Ative via `/skills` > `sinapse-<orqx>` ou `@<orqx>`:
+Cada orqx coordena um squad completo de agentes especializados. Use `$snps` para
+roteamento ou `$sinapse-agent <orqx-id>` para ativação direta:
 
 | Orqx | Squad | Foco |
 |------|-------|------|
 | `sinapse-orqx` | Core | Orquestrador principal de todos os squads |
-| `brand-orqx` | Brand | Estrategia de marca, arquetipos, auditoria |
-| `copy-orqx` | Copy | Copywriting persuasivo, headlines, conversao |
-| `content-orqx` | Content | Governanca editorial, estrategia de conteudo |
-| `storytelling-orqx` | Storytelling | Narrativa, roteiros, frameworks de historia |
+| `brand-orqx` | Brand | Estratégia de marca, arquétipos, auditoria |
+| `copy-orqx` | Copy | Copywriting persuasivo, headlines, conversão |
+| `content-orqx` | Content | Governança editorial, estratégia de conteúdo |
+| `storytelling-orqx` | Storytelling | Narrativa, roteiros, frameworks de história |
 | `commercial-orqx` | Commercial | Vendas, funil, revenue, pipeline |
 | `paidmedia-orqx` | Paid Media | Meta Ads, Google Ads, campanhas |
 | `growth-orqx` | Growth | Analytics, CRO, SEO, growth hacking |
-| `research-orqx` | Research | Market analysis, inteligencia competitiva |
-| `product-orqx` | Product | Product discovery, estrategia, operacoes |
+| `research-orqx` | Research | Market analysis, inteligência competitiva |
+| `product-orqx` | Product | Product discovery, estratégia, operações |
 | `design-orqx` | Design | Design systems, componentes, tokens |
-| `animations-orqx` | Animations | Motion design, CSS, particulas, 3D |
-| `cyber-orqx` | Cybersecurity | Seguranca, threat intel, pentest |
+| `animations-orqx` | Animations | Motion design, CSS, partículas, 3D |
+| `cyber-orqx` | Cybersecurity | Segurança, threat intel, pentest |
 | `finance-orqx` | Finance | Budget, pricing, profitability |
-| `courses-orqx` | Courses | Curriculos, assessments, launch |
+| `courses-orqx` | Courses | Currículos, assessments, launch |
 | `cloning-orqx` | Cloning | Clonagem cognitiva, mind synthesis |
-| `council-orqx` | Council | Advisors estrategicos (Munger, Dalio, Thiel) |
-| `swarm-orqx` | Mastery | Claude Code, MCP, integracao avancada |
+| `council-orqx` | Council | Advisors estratégicos (Munger, Dalio, Thiel) |
+| `swarm-orqx` | Mastery | Claude Code, MCP, integração avançada |
 
-Agents de arquivo: `.codex/agents/<orqx>.md` ou `.claude/agents/<orqx>.md`
+Adapters de arquivo: `.claude/agents/sinapse-<orqx-id>.md` no Claude Code e
+`.codex/agents/<orqx-id>.toml` (com companion `.md`) no Codex.
 
 ## Agentes Especializados (160)
 
-Existem 172 agentes organizados em 17 squads (160 em squads + 12 framework agents, incluindo o master orchestrator). Eles sao acessiveis via:
-- `.codex/agents/<agent-name>.md` - arquivo direto
+Existem 172 agentes organizados em 17 squads (160 em squads + 12 framework agents, incluindo o master orchestrator). Eles são acessíveis via:
+- `.claude/agents/sinapse-<agent-id>.md` - agent nativo do Claude Code
+- `.codex/agents/<agent-id>.toml` e `.codex/agents/<agent-id>.md` - adapters Codex
 - Chamada interna pelo orqx do squad
 
 Exemplos: `brand-strategist`, `ad-copywriter`, `penetration-tester`, `content-writer`, `ga-analytics-engineer`, etc.
 
-Use `*help` dentro de qualquer orqx para ver os especialistas disponiveis no squad.
+Use `*help` dentro de qualquer orqx para ver os especialistas disponíveis no squad.

package/docs/guides/development-setup.md

@@ -225,7 +225,7 @@ sinapse-ai/
 │       └── checklists/            # Product checklists
 │
 ├── .claude/                       # Claude Code configuration
-│   ├── commands/SINAPSE/agents/      # Agent skill commands
+│   ├── agents/                       # Native Claude agents
 │   ├── hooks/                     # Governance hooks
 │   └── rules/                     # AI behavior rules
 │
@@ -1112,4 +1112,3 @@ node --inspect node_modules/.bin/jest
 
 _SINAPSE Development Setup Guide v1.0.0_
 _Last Updated: 2026-01-29_
-

package/docs/guides/ide-integration.md

@@ -19,40 +19,39 @@ SINAPSE supports the following AI-powered development platforms:
 
 | IDE/CLI | Overall Status | How to Activate an Agent | Auto-Checks Before/After Actions |
 | --- | --- | --- | --- |
-| Claude Code | Works | `/agent-name` commands | Works (full) |
-| Codex CLI | Limited | `/skills` then `sinapse-<agent-id>` | Limited (some checks need manual sync) |
+| Claude Code | Works | `@agent-name` | 20 native hook registrations |
+| Codex CLI | Works | `$snps` or `$sinapse-agent <id>` | 9 lifecycle events through the bridge |
 
 Legend:
-- `Works`: fully recommended for new users.
-- `Limited`: usable with the documented workaround.
+- `Works`: supported by provider-native adapters and release validators.
 
-### What You Lose Without Full Auto-Checks
+### Provider-Native Differences
 
-Some IDEs run automatic checks before and after each action (e.g., validating context, enforcing rules). Where this is not available, you compensate manually:
+Both providers expose native lifecycle surfaces. Their registration models differ, so parity is measured semantically instead of by requiring identical hook files:
 
-| IDE | Auto-Check Level | What Is Reduced | How to Compensate |
-| --- | --- | --- | --- |
-| Claude Code | Full | Nothing | Built-in checks handle everything |
-| Codex CLI | Partial | Less automatic session tracking; some pre/post-action checks need manual trigger | Use `AGENTS.md` + `/skills` + sync/validation scripts |
+| Measured surface | Claude Code | Codex CLI |
+| --- | --- | --- |
+| Native agents | 172 | 172 |
+| Installed skills | 36 | 37 |
+| Registered hooks | 20 native registrations | 9 lifecycle events through the bridge |
+| Activation | `@agent-name` | `$snps` or `$sinapse-agent <id>` |
 
 ### Beginner Decision Guide
 
 If your goal is to get started as fast as possible:
 
-1. **Best option:** Use `Claude Code` -- it has the most automation and fewest manual steps.
-2. **Good option:** Use `Codex CLI` if you prefer a terminal-first workflow and can follow the `/skills` activation flow.
+1. Use **Claude Code** when you want its native `@agent-name` interaction.
+2. Use **Codex CLI** when you want `$snps`, direct parametric activation and its terminal-first workflow.
 
 ### Practical Consequences by Capability
 
 - **Session tracking** (automatic start/end detection):
-  - Automatic on Claude Code.
-  - Manual or partial on Codex CLI.
+  - Registered through native lifecycle adapters on both providers.
 - **Pre/post-action guardrails** (checks that run before and after each tool use):
-  - Full on Claude Code.
-  - Partial on Codex CLI (run sync scripts to compensate).
+  - Claude Code uses native hook registrations.
+  - Codex maps native lifecycle events through the compatibility bridge.
 - **Automatic audit trail** (record of what happened in each session):
-  - Richest on Claude Code.
-  - Reduced on Codex CLI (compensate with manual logging or validator output).
+  - Provider-specific telemetry uses the same canonical SINAPSE governance sources.
 
 ---
 
@@ -60,12 +59,12 @@ If your goal is to get started as fast as possible:
 
 ### Claude Code
 
-**Recommendation Level:** Best SINAPSE integration
+**Recommendation Level:** Native SINAPSE integration
 
 ```yaml
 config_file: .claude/CLAUDE.md
-agent_folder: .claude/commands/SINAPSE/agents
-activation: /agent-name (slash commands)
+agent_folder: .claude/agents
+activation: '@agent-name'
 format: full-markdown-yaml
 mcp_support: native
 special_features:
@@ -79,7 +78,7 @@ special_features:
 **Setup:**
 
 1. SINAPSE automatically creates `.claude/` directory on init
-2. Agents are available as slash commands: `/dev`, `/qa`, `/architect`
+2. Agents are available through `@developer`, `@quality-gate`, `@architect`, etc.
 3. Configure MCP servers in `~/.claude.json`
 
 **Configuration:**
@@ -89,7 +88,7 @@ special_features:
 npm run sync:ide
 
 # Verify setup
-ls -la .claude/commands/SINAPSE/agents/
+ls -la .claude/agents/
 ```
 
 ---
@@ -102,12 +101,12 @@ ls -la .claude/commands/SINAPSE/agents/
 config_file: AGENTS.md
 agent_folder: .codex/agents
 activation: terminal instructions
-skills_folder: .codex/skills (source), ~/.codex/skills (Codex menu)
+skills_folder: .agents/skills (single native source)
 format: markdown
 mcp_support: native via Codex tooling
 special_features:
   - AGENTS.md project instructions
-  - /skills activators (sinapse-<agent-id>)
+  - $snps and $sinapse-agent <id> activators
   - Strong CLI workflow support
   - Easy integration with repository scripts
   - Notify command plus emerging tool hooks in recent Codex releases
@@ -117,8 +116,8 @@ special_features:
 
 1. Keep `AGENTS.md` at repository root
 2. Run `npm run sync:ide:codex` to sync auxiliary agent files
-3. Run `npm run sync:skills:codex` to generate project-local skills in `.codex/skills`
-4. Use `/skills` and choose `sinapse-architect`, `sinapse-dev`, etc.
+3. Run `npm run sync:skills:codex` to generate project-local skills in `.agents/skills`
+4. Use `$snps` or `$sinapse-agent architect`, `$sinapse-agent developer`, etc.
 5. Use `npm run sync:skills:codex:global` only when you explicitly want global installation
 
 **Configuration:**
@@ -132,7 +131,7 @@ npm run validate:codex-integration
 npm run validate:codex-skills
 
 # Verify setup
-ls -la AGENTS.md .codex/agents/ .codex/skills/
+ls -la AGENTS.md .codex/agents/ .agents/skills/
 ```
 
 ---
@@ -194,7 +193,7 @@ npm run sync:ide
 npm run sync:ide:check
 
 # Check platform-specific directory
-ls .claude/commands/SINAPSE/agents/       # Claude Code
+ls .claude/agents/       # Claude Code
 ```
 
 ### Sync Conflicts

package/docs/guides/project-status-feature.md

@@ -26,10 +26,11 @@ This gives you immediate context about your work without manually running `git s
 
 ## Example Display
 
-When you activate an agent (e.g., `/dev`), you'll see:
+When you activate an agent (`@developer` in Claude Code or
+`$sinapse-agent developer` in Codex), you'll see:
 
-```
-💻 Dex (Builder) ready. Let's build something great!
+```text
+💻 Pixel the Builder ready to innovate!
 
 Current Project Status:
   - Branch: main
@@ -46,24 +47,15 @@ Type *help to see available commands!
 ### Prerequisites
 
 - **Git repository** - Project must be initialized with `git init`
-- **SINAPSE-FullStack** framework installed
+- **SINAPSE AI** framework installed
 - **Node.js 18+** with required packages
 
 ### Initial Setup
 
-Run the initialization command via @devops agent:
-
-```bash
-/devops
-*init-project-status
-```
-
-This will:
-1. Detect your git repository
-2. Enable `projectStatus` in `core-config.yaml`
-3. Create `.sinapse/project-status.yaml` cache file
-4. Add cache file to `.gitignore`
-5. Test the status display
+No agent command is required. In current installations, `projectStatus` is
+enabled in `.sinapse-ai/core-config.yaml` and loads automatically during agent
+activation. The loader detects the Git repository and maintains
+`.sinapse/project-status.yaml` as a runtime cache.
 
 **Alternative Manual Setup:**
 
@@ -213,19 +205,24 @@ Only shows stories with status: `InProgress` or `In Progress`.
 
 ## Affected Agents
 
-All 11 SINAPSE agents display project status:
-
-1. **@dev** (Dex - Builder)
-2. **@po** (Pax - Balancer)
-3. **@qa** (Quinn - Guardian)
-4. **@sm** (River - Facilitator)
-5. **@pm** (Morgan - Strategist)
-6. **@architect** (Aria - Visionary)
-7. **@analyst** (Atlas - Decoder)
-8. **@devops** (Gage - Operator)
-9. **@data-engineer** (Dara - Sage)
-10. **@ux-design-expert** (Uma - Empathizer)
-11. **@sinapse-orqx** (Orion - Orchestrator)
+SINAPSE includes 172 specialized agents across 17 squads. Project status is a
+shared framework capability; the list below is the core development subset, not
+the complete agent catalog:
+
+1. `developer` (Pixel)
+2. `product-lead` (Axis)
+3. `quality-gate` (Litmus)
+4. `sprint-lead` (Sync)
+5. `project-lead` (Beacon)
+6. `architect` (Stratum)
+7. `analyst` (Scope)
+8. `devops` (Pipeline)
+9. `data-engineer` (Tensor)
+10. `ux-design-expert` (Mosaic)
+11. `snps-orqx` (Imperator)
+
+Activate these IDs with `@agent-id` in Claude Code or
+`$sinapse-agent agent-id` in Codex; use `$snps` for primary Codex routing.
 
 ---
 
@@ -241,12 +238,9 @@ All 11 SINAPSE agents display project status:
 3. Does `.sinapse-ai/infrastructure/scripts/project-status-loader.js` exist?
 4. Any errors in agent activation output?
 
-**Solution:**
-```bash
-# Re-run initialization
-/devops
-*init-project-status
-```
+**Solution:** Run `npx sinapse-ai@latest doctor`, confirm the checks above, and
+restart the provider session. Project status reloads automatically; there is no
+public Codex `init-project-status` task pointer.
 
 ### Stale Status Data
 
@@ -362,28 +356,15 @@ await clearCache();
 
 ### Complete Removal
 
-To fully remove the feature:
+Do not delete framework scripts, tests, or task files. Disable the feature in
+`.sinapse-ai/core-config.yaml` and remove only its runtime cache:
 
 ```bash
-# Remove script
-rm .sinapse-ai/infrastructure/scripts/project-status-loader.js
-
-# Remove task
-rm .sinapse-ai/tasks/init-project-status.md
-
-# Remove cache
 rm .sinapse/project-status.yaml
-
-# Remove tests
-rm .sinapse-ai/infrastructure/scripts/__tests__/project-status-loader.test.js
-
-# Remove config section from core-config.yaml
-# (manually edit file)
-
-# Revert agent files to pre-6.1.2.4 state
-git revert <commit-hash>
 ```
 
+Set `projectStatus.enabled: false`; protected framework files remain installed.
+
 ---
 
 ## Git Version Compatibility
@@ -457,7 +438,7 @@ A: Yes, all agents use the same cache file (`.sinapse/project-status.yaml`).
 - **Story:** `docs/stories/sinapse migration/story-6.1.2.4-project-status-context.md`
 - **Config:** `.sinapse-ai/core-config.yaml` (projectStatus section)
 - **Script:** `.sinapse-ai/infrastructure/scripts/project-status-loader.js`
-- **Init Task:** `.sinapse-ai/tasks/init-project-status.md`
+- **Initialization:** automatic when `projectStatus.enabled` is true
 - **Tests:** `.sinapse-ai/infrastructure/scripts/__tests__/project-status-loader.test.js`
 
 ---
@@ -465,4 +446,3 @@ A: Yes, all agents use the same cache file (`.sinapse/project-status.yaml`).
 **Version:** 1.0
 **Status:** ✅ Production Ready
 **Last Updated:** 2025-01-14
-

package/docs/guides/quality-gates.md

@@ -162,7 +162,7 @@ layer2:
   quinn:
     enabled: true
     autoReview: true
-    agentPath: '.claude/commands/SINAPSE/agents/quality-gate.md'
+    agentPath: '.claude/agents/quality-gate.md'
     severity:
       block: ['CRITICAL']
       warn: ['HIGH', 'MEDIUM']
@@ -528,7 +528,7 @@ layer2:
   quinn:
     enabled: true
     autoReview: true
-    agentPath: '.claude/commands/SINAPSE/agents/quality-gate.md'
+    agentPath: '.claude/agents/quality-gate.md'
     severity:
       block: [CRITICAL]
       warn: [HIGH, MEDIUM]