@orchestrator-claude/cli 3.0.1 → 3.1.0

package/dist/templates/base/claude/agents/planner.md

@@ -275,29 +275,11 @@ O artefato deve:
 
 **ATENCAO:** Alem de gerar o artefato, voce DEVE manter a governanca do workflow.
 
-### 1. Registrar Artefato em orchestrator-index.json
-
-Apos criar o `plan.md`, atualize `.orchestrator/orchestrator-index.json`:
-
-```json
-{
-  "activeWorkflow": {
-    "currentPhase": "plan",
-    "status": "in_progress"
-  },
-  "artifacts": [
-    {
-      "id": "art-XXX",
-      "type": "plan",
-      "path": ".orchestrator/artifacts/plan/plan.md",
-      "status": "draft",
-      "createdAt": "{timestamp}",
-      "workflowId": "{workflowId}",
-      "phase": "plan"
-    }
-  ]
-}
-```
+### 1. Artifact Registration (automatic via MCP tools)
+
+Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. Sub-agents MUST NOT edit `.orchestrator/orchestrator-index.json` directly.
+
+The CLI will use MCP tools to update workflow state in PostgreSQL after artifact storage.
 
 ### 2. Validar Artefato
 
@@ -321,28 +303,17 @@ Parametros:
   - description: "Complete PLAN phase - [nome da feature]"
 ```
 
-### 4. Atualizar Gate
+### 4. Return Structured Output
 
-Atualize o gate da fase plan:
-
-```json
-{
-  "gates": {
-    "plan": {
-      "passed": true,
-      "evaluatedAt": "{timestamp}"
-    }
-  }
-}
-```
+Return structured output to the CLI for state update. The CLI will use MCP tools to update the phase gate in PostgreSQL.
 
 ### Checklist de Governanca (OBRIGATORIO)
 
 Antes de considerar a fase PLAN finalizada:
 
 - [ ] plan.md criado em .orchestrator/artifacts/plan/
-- [ ] Artefato registrado em orchestrator-index.json
+- [ ] Structured output returned to CLI for state update
 - [ ] Validacao executada via artifact-validator
 - [ ] Status do artefato = "validated"
 - [ ] Checkpoint criado via MCP
-- [ ] Gate plan.passed = true
+- [ ] Gate plan.passed = true (updated via CLI)

package/dist/templates/base/claude/agents/researcher.md

@@ -301,29 +301,11 @@ Limites de uso:
 
 **ATENCAO:** Alem de gerar o artefato, voce DEVE manter a governanca do workflow.
 
-### 1. Registrar Artefato em orchestrator-index.json
-
-Apos criar o `research-context.md`, atualize `.orchestrator/orchestrator-index.json`:
-
-```json
-{
-  "activeWorkflow": {
-    "currentPhase": "research",
-    "status": "in_progress"
-  },
-  "artifacts": [
-    {
-      "id": "art-XXX",
-      "type": "research",
-      "path": ".orchestrator/artifacts/research/research-context.md",
-      "status": "completed",
-      "createdAt": "{timestamp}",
-      "workflowId": "{workflowId}",
-      "phase": "research"
-    }
-  ]
-}
-```
+### 1. Artifact Registration (automatic via MCP tools)
+
+Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. Sub-agents MUST NOT edit `.orchestrator/orchestrator-index.json` directly.
+
+The CLI will use MCP tools to update workflow state in PostgreSQL after artifact storage.
 
 ### 2. Criar Checkpoint (se pesquisa for significativa)
 
@@ -336,27 +318,16 @@ Parametros:
   - description: "Complete RESEARCH phase - [topico pesquisado]"
 ```
 
-### 3. Atualizar Gate (se fase RESEARCH for usada)
+### 3. Return Structured Output
 
-Se o workflow incluir fase RESEARCH explicita:
-
-```json
-{
-  "gates": {
-    "research": {
-      "passed": true,
-      "evaluatedAt": "{timestamp}"
-    }
-  }
-}
-```
+Return structured output to the CLI for state update. The CLI will use MCP tools to update the phase gate in PostgreSQL if RESEARCH is an explicit workflow phase.
 
 ### Checklist de Governanca (OBRIGATORIO)
 
 Antes de considerar a pesquisa finalizada:
 
 - [ ] research-context.md criado em .orchestrator/artifacts/research/
-- [ ] Artefato registrado em orchestrator-index.json
+- [ ] Structured output returned to CLI for state update
 - [ ] Findings sao acionaveis e relevantes
 - [ ] Sources documentadas
 - [ ] Cache information registrada

package/dist/templates/base/claude/agents/reviewer.md

@@ -361,62 +361,20 @@ Formato:
 }
 ```
 
-### 2. Registrar em orchestrator-index.json
+### 2. Artifact Registration (automatic via MCP tools)
 
-Apos criar validation report, registre no index:
+Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. Sub-agents MUST NOT edit `.orchestrator/orchestrator-index.json` directly.
 
-```json
-{
-  "artifacts": [
-    {
-      "id": "val-XXX",
-      "type": "validation_report",
-      "path": ".orchestrator/artifacts/{phase}/validation-report.json",
-      "status": "completed",
-      "createdAt": "{timestamp}",
-      "workflowId": "{workflowId}",
-      "phase": "{phase}"
-    }
-  ]
-}
-```
-
-### 3. Atualizar Status do Artefato Revisado
-
-Se aprovado, atualize o status do artefato original:
-
-```json
-{
-  "artifacts": [
-    {
-      "id": "art-XXX",
-      "status": "validated",  // era "draft"
-      "validatedAt": "{timestamp}",
-      "validationReport": "val-XXX"
-    }
-  ]
-}
-```
+### 3. Return Structured Output for Validation Status
 
-### 4. Avaliar Gate da Fase
+Return structured output to the CLI indicating the validation result. The CLI will use MCP tools to:
+- Update artifact status to "validated" in PostgreSQL
+- Link validation report to original artifact
+- Update phase gate if applicable
 
-Se revisao for a ultima da fase, avalie o gate:
+### 4. Comunicar Resultado ao Orchestrator
 
-```json
-{
-  "gates": {
-    "{phase}": {
-      "passed": true,  // ou false se rejeitado
-      "evaluatedAt": "{timestamp}",
-      "evaluatedBy": "reviewer-agent"
-    }
-  }
-}
-```
-
-### 5. Comunicar Resultado ao Orchestrator
-
-Ao finalizar revisao, retorne status estruturado para o orchestrator:
+Ao finalizar revisao, retorne status estruturado para o CLI:
 
 ```markdown
 ## Review Result
@@ -431,14 +389,17 @@ Ao finalizar revisao, retorne status estruturado para o orchestrator:
 - Se REJECTED: Escalar para usuario
 ```
 
+The CLI will handle updating PostgreSQL via MCP tools.
+
 ### Checklist de Governanca (OBRIGATORIO)
 
 Antes de considerar a revisao finalizada:
 
 - [ ] Todos os criterios de qualidade verificados
-- [ ] Validation report criado e registrado
-- [ ] Status do artefato atualizado (validated/rejected)
-- [ ] Gate da fase avaliado
+- [ ] Validation report criado
+- [ ] Structured output returned to CLI for state update
+- [ ] Status do artefato will be updated via CLI (validated/rejected)
+- [ ] Gate da fase will be evaluated via CLI
 - [ ] Resultado comunicado ao orchestrator
 - [ ] Condicoes para aprovacao documentadas (se houver)
 ```

package/dist/templates/base/claude/agents/schema-extractor.md

@@ -584,7 +584,7 @@ $posts = Post::with('user')->get();
 4. MUST document column types and nullability
 5. MUST generate database-schema.md using template
 6. MUST include table catalog with all columns
-7. MUST update orchestrator-index.json after completion
+7. MUST return structured output to CLI for state update (workflow state managed via PostgreSQL)
 8. MUST create checkpoint after MAP phase fully complete (with api-extractor)
 
 ### MUST NOT (Forbidden)
@@ -650,30 +650,9 @@ After completing MAP phase (Database portion):
 
 2. Validate Mermaid syntax (paste in Mermaid Live Editor or use CLI if available)
 
-3. Update orchestrator-index.json:
-   ```json
-   {
-     "activeWorkflow": {
-       "currentPhase": "map",
-       "status": "completed"
-     },
-     "artifacts": [
-       {
-         "id": "art-map-002",
-         "type": "database-schema",
-         "path": ".orchestrator/artifacts/legacy-analysis/{workflowId}/database-schema.md",
-         "status": "completed",
-         "createdAt": "{timestamp}",
-         "phase": "map",
-         "format": "markdown-mermaid",
-         "validated": true,
-         "tableCount": 15,
-         "relationshipCount": 22,
-         "accuracyPercent": 95
-       }
-     ]
-   }
-   ```
+3. Return structured output to CLI for state update:
+
+   Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. The CLI will use MCP tools to update workflow state after artifact storage.
 
 4. Create checkpoint (MANDATORY after MAP phase complete):
    ```
@@ -753,7 +732,7 @@ Before claiming phase complete, MUST provide evidence:
 - [ ] Junction tables identified for many-to-many
 - [ ] Query patterns analyzed (if applicable)
 - [ ] Artifact saved to correct path
-- [ ] orchestrator-index.json updated
+- [ ] Structured output returned to CLI for state update
 - [ ] Checkpoint created (after MAP phase complete)
 
 **FORBIDDEN**: Claiming completion without valid Mermaid ER diagram.

package/dist/templates/base/claude/agents/specifier.md

@@ -258,29 +258,11 @@ O artefato deve:
 
 **ATENCAO:** Alem de gerar o artefato, voce DEVE manter a governanca do workflow.
 
-### 1. Registrar Artefato em orchestrator-index.json
-
-Apos criar o `spec.md`, atualize `.orchestrator/orchestrator-index.json`:
-
-```json
-{
-  "activeWorkflow": {
-    "currentPhase": "specify",
-    "status": "in_progress"
-  },
-  "artifacts": [
-    {
-      "id": "art-XXX",
-      "type": "specification",
-      "path": ".orchestrator/artifacts/specify/spec.md",
-      "status": "draft",
-      "createdAt": "{timestamp}",
-      "workflowId": "{workflowId}",
-      "phase": "specify"
-    }
-  ]
-}
-```
+### 1. Artifact Registration (automatic via MCP tools)
+
+Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. Sub-agents MUST NOT edit `.orchestrator/orchestrator-index.json` directly.
+
+The CLI will use MCP tools to update workflow state in PostgreSQL after artifact storage.
 
 ### 2. Validar Artefato
 
@@ -304,28 +286,17 @@ Parametros:
   - description: "Complete SPECIFY phase - [nome da feature]"
 ```
 
-### 4. Atualizar Gate
+### 4. Return Structured Output
 
-Atualize o gate da fase specify:
-
-```json
-{
-  "gates": {
-    "specify": {
-      "passed": true,
-      "evaluatedAt": "{timestamp}"
-    }
-  }
-}
-```
+Return structured output to the CLI for state update. The CLI will use MCP tools to update the phase gate in PostgreSQL.
 
 ### Checklist de Governanca (OBRIGATORIO)
 
 Antes de considerar a fase SPECIFY finalizada:
 
 - [ ] spec.md criado em .orchestrator/artifacts/specify/
-- [ ] Artefato registrado em orchestrator-index.json
+- [ ] Structured output returned to CLI for state update
 - [ ] Validacao executada via artifact-validator
 - [ ] Status do artefato = "validated"
 - [ ] Checkpoint criado via MCP
-- [ ] Gate specify.passed = true
+- [ ] Gate specify.passed = true (updated via CLI)

package/dist/templates/base/claude/agents/task-generator.md

@@ -298,29 +298,11 @@ O artefato deve:
 
 **ATENCAO:** Alem de gerar o artefato, voce DEVE manter a governanca do workflow.
 
-### 1. Registrar Artefato em orchestrator-index.json
-
-Apos criar o `tasks.md`, atualize `.orchestrator/orchestrator-index.json`:
-
-```json
-{
-  "activeWorkflow": {
-    "currentPhase": "tasks",
-    "status": "in_progress"
-  },
-  "artifacts": [
-    {
-      "id": "art-XXX",
-      "type": "tasks",
-      "path": ".orchestrator/artifacts/tasks/tasks.md",
-      "status": "draft",
-      "createdAt": "{timestamp}",
-      "workflowId": "{workflowId}",
-      "phase": "tasks"
-    }
-  ]
-}
-```
+### 1. Artifact Registration (automatic via MCP tools)
+
+Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. Sub-agents MUST NOT edit `.orchestrator/orchestrator-index.json` directly.
+
+The CLI will use MCP tools to update workflow state in PostgreSQL after artifact storage.
 
 ### 2. Validar Artefato
 
@@ -344,39 +326,19 @@ Parametros:
   - description: "Complete TASKS phase - [nome da feature]"
 ```
 
-### 4. Atualizar Gate e Preparar para IMPLEMENT
-
-Atualize o gate da fase tasks e prepare para human-in-the-loop:
-
-```json
-{
-  "gates": {
-    "tasks": {
-      "passed": true,
-      "evaluatedAt": "{timestamp}"
-    },
-    "implement": {
-      "passed": false,
-      "pending": true,
-      "requiresApproval": true
-    }
-  },
-  "activeWorkflow": {
-    "status": "awaiting_approval",
-    "nextPhase": "implement"
-  }
-}
-```
+### 4. Return Structured Output for Human Approval
+
+Return structured output to the CLI indicating that tasks phase is complete and human approval is required before IMPLEMENT. The CLI will use MCP tools to update workflow state in PostgreSQL to "awaiting_approval".
 
 ### Checklist de Governanca (OBRIGATORIO)
 
 Antes de considerar a fase TASKS finalizada:
 
 - [ ] tasks.md criado em .orchestrator/artifacts/tasks/
-- [ ] Artefato registrado em orchestrator-index.json
+- [ ] Structured output returned to CLI for state update
 - [ ] Validacao executada via artifact-validator
 - [ ] Status do artefato = "validated"
 - [ ] Checkpoint criado via MCP
-- [ ] Gate tasks.passed = true
-- [ ] Gate implement.requiresApproval = true (prepara human-in-the-loop)
-- [ ] Status do workflow = "awaiting_approval"
+- [ ] Gate tasks.passed = true (updated via CLI)
+- [ ] Gate implement.requiresApproval = true (set via CLI)
+- [ ] Status do workflow = "awaiting_approval" (set via CLI)

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "@orchestrator-claude/cli",
-  "version": "3.0.1",
-  "description": "Orchestrator CLI - Thin Client",
+  "version": "3.1.0",
+  "deprecated": "Use orchestrator MCP server directly. See RFC-014.",
+  "description": "Orchestrator CLI - Thin Client (DEPRECATED)",
   "type": "module",
   "main": "dist/index.js",
   "bin": {

package/templates/base/CLAUDE.md.hbs

@@ -153,12 +153,14 @@ RESEARCH (optional)
 IMPLEMENT
 ```
 
-Each phase produces artifacts in `.orchestrator/artifacts/`:
-- `research/` - Research context documents
-- `specify/` - Specifications (spec.md)
-- `plan/` - Technical plans (plan.md)
-- `tasks/` - Task backlogs (tasks.md)
-- `implement/` - Implementation reports
+Each phase produces artifacts stored in MinIO (object storage) and tracked in PostgreSQL:
+- `research` - Research context documents
+- `specify` - Specifications (spec.md)
+- `plan` - Technical plans (plan.md)
+- `tasks` - Task backlogs (tasks.md)
+- `implement` - Implementation reports
+
+**CRITICAL**: Artifacts are accessed via MCP tools (`artifactStore`, `artifactRetrieve`), NOT via filesystem paths. The `.orchestrator/artifacts/` directory does NOT exist on the filesystem.
 
 ---
 
@@ -302,7 +304,6 @@ When user approves implementation with ANY of these phrases:
    Requirements:
    - Follow TDD (write tests BEFORE implementation)
    - Maintain 80% minimum coverage
-   - Update orchestrator-index.json after EACH task
    - Create checkpoint after every 3-5 tasks
    - Generate implementation-report.md at the end
    ```
@@ -312,7 +313,7 @@ When user approves implementation with ANY of these phrases:
 - Using Edit/Write tools directly for code implementation
 - Skipping Task tool invocation
 - Writing production code without implementer agent
-- Forgetting to update orchestrator-index.json
+- Editing `.orchestrator/orchestrator-index.json` directly (state is in PostgreSQL)
 
 ### Self-Verification Checklist
 
@@ -334,19 +335,24 @@ If ANY answer is NO -> STOP and correct before continuing.
 - **Clean Architecture**: Dependencies point inward
 - **TypeScript Strict**: `strict: true` required
 
-## Project Structure
+## State Management
 
 ```
-.orchestrator/
-├── artifacts/           # Generated artifacts by phase
-├── memory/
-│   └── knowledge-base/
-│       ├── core/        # CONSTITUTION.md (immutable rules)
-│       └── contextual/  # Project context
-├── checkpoints/         # Checkpoint metadata
-└── orchestrator-index.json  # Workflow state
+PostgreSQL (Single Source of Truth):
+├── workflows          # Workflow state, pending actions, phases
+├── artifacts          # Artifact metadata
+├── checkpoints        # Checkpoint metadata
+└── agent_invocations  # Agent invocation history
+
+MinIO (Object Storage):
+└── artifacts/         # Generated artifact content by phase
+
+.orchestrator/ (DEPRECATED - do NOT read or write directly):
+└── orchestrator-index.json  # DEPRECATED: state is in PostgreSQL
 ```
 
+**CRITICAL**: All workflow state is in PostgreSQL. All artifact content is in MinIO. Access everything through MCP tools. NEVER edit `.orchestrator/orchestrator-index.json` directly.
+
 ## Important Notes
 
 1. **Always start with workflow detection** - Don't skip this step

package/templates/base/claude/agents/api-extractor.md

@@ -452,7 +452,7 @@ tags:
 4. MUST identify and document authentication requirements
 5. MUST group endpoints by tags/resources logically
 6. MUST include at least one example per endpoint (request or response)
-7. MUST update orchestrator-index.json after completion
+7. MUST return structured output to CLI for state update (workflow state managed via PostgreSQL)
 8. MUST create checkpoint after MAP phase complete
 
 ### MUST NOT (Forbidden)
@@ -518,29 +518,9 @@ After completing MAP phase (API portion):
 
 2. Validate OpenAPI 3.0 compliance (if swagger-cli available)
 
-3. Update orchestrator-index.json:
-   ```json
-   {
-     "activeWorkflow": {
-       "currentPhase": "map",
-       "status": "in_progress"
-     },
-     "artifacts": [
-       {
-         "id": "art-map-001",
-         "type": "api-spec",
-         "path": ".orchestrator/artifacts/legacy-analysis/{workflowId}/api-spec.yaml",
-         "status": "completed",
-         "createdAt": "{timestamp}",
-         "phase": "map",
-         "format": "openapi-3.0",
-         "validated": true,
-         "endpointCount": 45,
-         "coveragePercent": 92
-       }
-     ]
-   }
-   ```
+3. Return structured output to CLI for state update:
+
+   Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. The CLI will use MCP tools to update workflow state after artifact storage.
 
 4. MUST NOT create checkpoint yet (wait for schema-extractor to complete MAP phase)
 
@@ -652,7 +632,7 @@ Before claiming phase complete, MUST provide evidence:
 - [ ] At least one example per endpoint
 - [ ] No sensitive data in examples
 - [ ] Artifact saved to correct path
-- [ ] orchestrator-index.json updated
+- [ ] Structured output returned to CLI for state update
 
 **FORBIDDEN**: Claiming completion without generating valid OpenAPI 3.0 spec.
 

package/templates/base/claude/agents/business-rule-miner.md

@@ -609,7 +609,7 @@ stateDiagram-v2
 4. MUST categorize rules by domain
 5. MUST generate business-rules.md using template
 6. MUST assign unique IDs to business rules (BR-DOMAIN-###)
-7. MUST update orchestrator-index.json after completion
+7. MUST return structured output to CLI for state update (workflow state managed via PostgreSQL)
 8. MUST create checkpoint after DOCUMENT phase complete
 
 ### MUST NOT (Forbidden)
@@ -665,37 +665,9 @@ After completing DOCUMENT phase:
    - `.orchestrator/artifacts/legacy-analysis/{workflowId}/business-rules.md`
    - `.orchestrator/artifacts/legacy-analysis/{workflowId}/glossary.md`
 
-2. Update orchestrator-index.json:
-   ```json
-   {
-     "activeWorkflow": {
-       "currentPhase": "document",
-       "status": "completed"
-     },
-     "artifacts": [
-       {
-         "id": "art-document-001",
-         "type": "business-rules",
-         "path": ".orchestrator/artifacts/legacy-analysis/{workflowId}/business-rules.md",
-         "status": "completed",
-         "createdAt": "{timestamp}",
-         "phase": "document",
-         "rulesExtracted": 87,
-         "domains": 5,
-         "stateMachines": 4
-       },
-       {
-         "id": "art-document-002",
-         "type": "glossary",
-         "path": ".orchestrator/artifacts/legacy-analysis/{workflowId}/glossary.md",
-         "status": "completed",
-         "createdAt": "{timestamp}",
-         "phase": "document",
-         "termsCount": 25
-       }
-     ]
-   }
-   ```
+2. Return structured output to CLI for state update:
+
+   Artifacts are automatically registered in PostgreSQL when stored via MCP `artifactStore` tool. The CLI will use MCP tools to update workflow state after artifact storage.
 
 3. Create checkpoint (MANDATORY after DOCUMENT phase):
    ```
@@ -720,7 +692,7 @@ Before claiming phase complete, MUST provide evidence:
 - [ ] glossary.md generated (if applicable)
 - [ ] Unique IDs assigned (BR-DOMAIN-###)
 - [ ] Artifacts saved to correct paths
-- [ ] orchestrator-index.json updated
+- [ ] Structured output returned to CLI for state update
 - [ ] Checkpoint created
 
 **FORBIDDEN**: Claiming completion without file:line locations.