chati-dev 2.0.8 → 2.1.0

package/framework/tasks/architect-consolidate.md

@@ -2,7 +2,7 @@
 id: architect-consolidate
 agent: architect
 trigger: architect-security-review
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: false
 outputs: [architecture-final.yaml]

package/framework/tasks/architect-db-design.md

@@ -2,7 +2,7 @@
 id: architect-db-design
 agent: architect
 trigger: architect-api-design
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: false
 outputs: [db-design.yaml]

package/framework/tasks/architect-design.md

@@ -2,7 +2,7 @@
 id: architect-design
 agent: architect
 trigger: detail
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: true
 outputs: [architecture.yaml]

package/framework/tasks/architect-security-review.md

@@ -2,7 +2,7 @@
 id: architect-security-review
 agent: architect
 trigger: architect-db-design
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: false
 outputs: [security-review.yaml]

package/framework/tasks/architect-stack-selection.md

@@ -2,7 +2,7 @@
 id: architect-stack-selection
 agent: architect
 trigger: architect-design
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: false
 outputs: [stack-selection.yaml]

package/framework/tasks/brief-consolidate.md

@@ -2,7 +2,7 @@
 id: brief-consolidate
 agent: brief
 trigger: brief-constraint-identify
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: false
 outputs: [brief.yaml]

package/framework/tasks/brief-constraint-identify.md

@@ -2,7 +2,7 @@
 id: brief-constraint-identify
 agent: brief
 trigger: brief-stakeholder-map
-phase: planning
+phase: discover
 requires_input: true
 parallelizable: false
 outputs: [constraints.yaml]

package/framework/tasks/brief-extract-requirements.md

@@ -2,7 +2,7 @@
 id: brief-extract-requirements
 agent: brief
 trigger: orchestrator
-phase: planning
+phase: discover
 requires_input: true
 parallelizable: false
 outputs: [requirements-raw.yaml]

package/framework/tasks/brief-stakeholder-map.md

@@ -2,7 +2,7 @@
 id: brief-stakeholder-map
 agent: brief
 trigger: brief-validate-completeness
-phase: planning
+phase: discover
 requires_input: true
 parallelizable: false
 outputs: [stakeholder-map.yaml]

package/framework/tasks/brief-validate-completeness.md

@@ -2,7 +2,7 @@
 id: brief-validate-completeness
 agent: brief
 trigger: brief-extract-requirements
-phase: planning
+phase: discover
 requires_input: true
 parallelizable: false
 outputs: [validation-report.yaml]

package/framework/tasks/brownfield-wu-architecture-map.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-architecture-map
 agent: brownfield-wu
 trigger: brownfield-wu-dependency-scan
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: true
 outputs: [architecture-map.yaml]

package/framework/tasks/brownfield-wu-deep-discovery.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-deep-discovery
 agent: brownfield-wu
 trigger: orchestrator
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: false
 outputs: [discovery.yaml]

package/framework/tasks/brownfield-wu-dependency-scan.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-dependency-scan
 agent: brownfield-wu
 trigger: brownfield-wu-deep-discovery
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: true
 outputs: [dependencies.yaml]

package/framework/tasks/brownfield-wu-migration-plan.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-migration-plan
 agent: brownfield-wu
 trigger: brownfield-wu-risk-assess
-phase: planning
+phase: discover
 requires_input: true
 parallelizable: false
 outputs: [migration-plan.yaml]

package/framework/tasks/brownfield-wu-report.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-report
 agent: brownfield-wu
 trigger: brownfield-wu-migration-plan
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: false
 outputs: [wu-report.yaml]

package/framework/tasks/brownfield-wu-risk-assess.md

@@ -2,7 +2,7 @@
 id: brownfield-wu-risk-assess
 agent: brownfield-wu
 trigger: brownfield-wu-architecture-map
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: false
 outputs: [risk-assessment.yaml]

package/framework/tasks/detail-acceptance-criteria.md

@@ -2,7 +2,7 @@
 id: detail-acceptance-criteria
 agent: detail
 trigger: detail-edge-case-analysis
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: false
 outputs: [acceptance-criteria.yaml]

package/framework/tasks/detail-consolidate.md

@@ -2,7 +2,7 @@
 id: detail-consolidate
 agent: detail
 trigger: detail-acceptance-criteria
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: false
 outputs: [prd.yaml]

package/framework/tasks/detail-edge-case-analysis.md

@@ -2,7 +2,7 @@
 id: detail-edge-case-analysis
 agent: detail
 trigger: detail-nfr-extraction
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: true
 outputs: [edge-cases.yaml]

package/framework/tasks/detail-expand-prd.md

@@ -2,7 +2,7 @@
 id: detail-expand-prd
 agent: detail
 trigger: brief
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: false
 outputs: [prd-draft.yaml]

package/framework/tasks/detail-nfr-extraction.md

@@ -2,7 +2,7 @@
 id: detail-nfr-extraction
 agent: detail
 trigger: detail-expand-prd
-phase: planning
+phase: plan
 requires_input: false
 parallelizable: true
 outputs: [nfr.yaml]

package/framework/tasks/greenfield-wu-analyze-empty.md

@@ -2,7 +2,7 @@
 id: greenfield-wu-analyze-empty
 agent: greenfield-wu
 trigger: orchestrator
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: false
 outputs: [wu-analysis.yaml]

package/framework/tasks/greenfield-wu-report.md

@@ -2,7 +2,7 @@
 id: greenfield-wu-report
 agent: greenfield-wu
 trigger: greenfield-wu-tech-stack-assess
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: false
 outputs: [wu-report.yaml]

package/framework/tasks/greenfield-wu-scaffold-detection.md

@@ -2,7 +2,7 @@
 id: greenfield-wu-scaffold-detection
 agent: greenfield-wu
 trigger: greenfield-wu-analyze-empty
-phase: planning
+phase: discover
 requires_input: false
 parallelizable: false
 outputs: [scaffold-report.yaml]

package/framework/tasks/greenfield-wu-tech-stack-assess.md

@@ -2,7 +2,7 @@
 id: greenfield-wu-tech-stack-assess
 agent: greenfield-wu
 trigger: greenfield-wu-scaffold-detection
-phase: planning
+phase: discover
 requires_input: true
 parallelizable: false
 outputs: [tech-stack.yaml]

package/framework/tasks/orchestrator-deviation.md

@@ -54,7 +54,7 @@ Identify which artifacts are impacted:
 ### 4. Assess Impact Scope
 Evaluate the ripple effects:
 - **Localized**: Change affects only current/next agent
-- **Phase-wide**: Change affects current phase (e.g., all of PLANNING)
+- **Phase-wide**: Change affects current phase (e.g., all of DISCOVER or PLAN)
 - **Mode-wide**: Change affects entire mode (e.g., planning → build transition)
 - **Global**: Change affects entire project plan
 
@@ -172,7 +172,7 @@ deviation_plan:
     urgency: "medium"
 
   impact_assessment:
-    scope: "phase-wide"  # Affects multiple PLANNING agents
+    scope: "phase-wide"  # Affects multiple DISCOVER/PLAN agents
     affected_agents:
       - agent: "detail"
         status: "completed"

package/framework/tasks/orchestrator-escalate.md

@@ -191,7 +191,7 @@ escalation_report:
     context:
       previous_agent: "detail"
       session_mode: "planning"
-      pipeline_position: "PLANNING/architect"
+      pipeline_position: "PLAN/architect"
 
   root_cause_analysis:
     primary_cause: "dependency-missing"

package/framework/tasks/orchestrator-handoff.md

@@ -77,7 +77,7 @@ Modify `.chati/session.yaml`:
 
 ### 7. Determine Next Agent
 Based on pipeline position and mode:
-- **PLANNING**: Follow sequence (wu → brief → detail → architect → ux → phases → tasks → qa-planning)
+- **DISCOVER → PLAN**: Follow sequence (wu → brief → detail → architect → ux → phases → tasks → qa-planning)
 - **BUILD**: dev → qa-implementation
 - **DEPLOY**: devops
 - Handle special transitions (e.g., qa-planning → dev requires mode switch)
@@ -171,7 +171,7 @@ handoff_document:
     quality_score: 8.5
     duration_minutes: 45
     mode: "planning"
-    phase: "PLANNING"
+    phase: "DISCOVER"
 
   summary: |
     Completed detailed requirements analysis for HealthCare Portal.
@@ -228,7 +228,7 @@ handoff_document:
 
   session_update:
     agent_status: "completed"
-    pipeline_progress: 37.5  # 3 of 8 PLANNING agents done
+    pipeline_progress: 37.5  # 3 of 8 DISCOVER/PLAN agents done
     mode_transition_check:
       eligible: false
       reason: "QA-Planning not yet complete"

package/framework/tasks/orchestrator-mode-switch.md

@@ -54,7 +54,7 @@ Verify mode-specific requirements are met:
 **For planning → build**:
 - QA-Planning agent completed
 - QA-Planning score >= 95%
-- All PLANNING agents complete or skipped
+- All DISCOVER/PLAN agents complete or skipped
 - No blocking issues
 
 **For build → validate**:
@@ -86,6 +86,17 @@ Assess readiness for transition:
 - Blocker status
 - Return confidence: high (>90%), medium (70-90%), low (<70%)
 
+### 6.5. User Preview Gate (BUILD → DEPLOY only)
+When transitioning from BUILD to DEPLOY, the pipeline returns `nextAction: 'user_preview'` instead of advancing automatically. The orchestrator must:
+1. Execute `orchestrator-preview` task to launch a local dev server
+2. Collect user feedback (approve/adjust/rethink)
+3. Only proceed to DEPLOY after user explicitly approves
+4. Server lifecycle is user-controlled (never killed implicitly)
+
+See `orchestrator-preview.md` for the full preview flow.
+
+This step is skipped for transitions that don't involve BUILD → DEPLOY (e.g., PLAN → BUILD proceeds normally).
+
 ### 7. Execute or Suggest Transition
 Based on autonomous_gate and confidence:
 - **Auto-transition**: confidence high + autonomous enabled → execute
@@ -128,7 +139,7 @@ If user wants to force transition despite low confidence:
 
 ### When Backward Transition is Needed
 If QA-Implementation finds fundamental spec problems:
-1. Identify which PLANNING agent needs to re-run
+1. Identify which DISCOVER/PLAN agent needs to re-run
 2. Mark affected agents as `needs_revalidation`
 3. Set mode to `planning`
 4. Route to earliest affected agent
@@ -182,7 +193,7 @@ mode_transition:
   from_state:
     mode: "planning"
     current_agent: "qa-planning"
-    pipeline_position: "PLANNING/qa-planning"
+    pipeline_position: "PLAN/qa-planning"
 
   to_state:
     mode: "build"
@@ -208,7 +219,7 @@ mode_transition:
     score: 95
     level: "high"
     factors:
-      - "All PLANNING agents completed"
+      - "All DISCOVER/PLAN agents completed"
       - "QA-Planning score excellent (97.5%)"
       - "Only 2 minor open questions"
       - "No blockers"
@@ -251,7 +262,7 @@ mode_transition:
     deviation_protocol: false
 
   user_notification: |
-    ✓ Mode Transition: PLANNING → BUILD
+    ✓ Mode Transition: PLAN → BUILD
 
     QA-Planning completed with score 97.5% (>= 95% required).
     Autonomous transition to BUILD mode approved.

package/framework/tasks/orchestrator-preview.md

@@ -0,0 +1,181 @@
+---
+id: orchestrator-preview
+agent: orchestrator
+trigger: user-preview-action
+phase: build
+requires_input: true
+parallelizable: false
+outputs: [preview-feedback, server-logs]
+handoff_to: null
+autonomous_gate: false
+criteria:
+  - Server started successfully OR graceful fallback for non-visual projects
+  - User provided explicit feedback (approve/adjust/rethink)
+  - Server lifecycle managed by user decision (never killed implicitly)
+  - Adjustment feedback includes server logs context
+---
+
+# Orchestrator Preview Task
+
+## Purpose
+Launch a local preview server after QA-Implementation passes so the user can visually validate the build before deploying. The server stays alive until the user explicitly decides to kill it. Captures server logs for Dev agent context during iterative adjustments.
+
+## Prerequisites
+- QA-Implementation completed with score >= 95%
+- Pipeline state: `phase = 'build'`, `nextAction = 'user_preview'`
+- Project directory with source code ready to run
+
+## Steps
+
+### 1. Detect Project Framework
+Call `detectDevCommand(projectDir)` to identify:
+- Framework (Next.js, Vite, Angular, Django, etc.)
+- Dev command (`npm run dev`, `python manage.py runserver`, etc.)
+- Default port
+
+Also call `detectProjectKind(projectDir)` to determine UX messaging:
+- `frontend` / `fullstack` / `static`: Visual preview (browser)
+- `api`: Endpoint preview (suggest curl/Postman)
+- `cli`: No server needed (show help command)
+- `library`: No server needed (show test results/README)
+
+### 2. Handle Non-Visual Projects
+If project kind is `cli` or `library`, or `detectDevCommand()` returns `null`:
+- Skip server launch
+- Present appropriate message:
+  - CLI: "Run `node bin/cli.js --help` to test your tool"
+  - Library: "Tests passed. Would you like to review the README?"
+  - Unknown: "Proceed to deploy, run tests, or review documentation?"
+- Still collect user decision (approve/adjust/rethink)
+
+### 3. Find Available Port
+Call `findAvailablePort(defaultPort)`:
+- Starts at the framework's default port
+- **NEVER kills existing processes** on occupied ports
+- Scans incrementally (+1, +2, ...) up to 20 attempts
+- Returns first available port
+
+### 4. Launch Preview Server
+Call `launchPreview(projectDir, { command, args, port, framework })`:
+- Spawns the dev server process
+- Captures stdout/stderr into `LogBuffer` (circular, 200 lines)
+- Waits for server health check (HTTP GET, 30s timeout)
+- Opens browser automatically
+
+### 5. Present Preview to User
+Display the running preview with 4 options:
+
+```
+Your app is running at http://localhost:{PORT}
+Opened in your browser.
+
+What do you think?
+1. Deploy (keep local server running)
+2. Deploy (shut down local server)
+3. I need adjustments
+4. Rethink the approach
+```
+
+### 6. Process User Decision
+
+#### Option 1: Deploy + Keep Server
+- Call `confirmPreview(state, 'approve_keep')`
+- Pipeline advances to DEPLOY phase
+- Server stays alive (user can compare local vs production)
+- Route to DevOps agent
+
+#### Option 2: Deploy + Kill Server
+- Kill the preview server process
+- Call `confirmPreview(state, 'approve_kill')`
+- Pipeline advances to DEPLOY phase
+- Route to DevOps agent
+
+#### Option 3: Adjustments
+- Collect feedback: "What needs to change?"
+- Capture server logs via `handle.logs.toContext()`
+- Call `confirmPreview(state, 'adjust')`
+- Route to Dev agent with context:
+  - User feedback (text)
+  - Server logs (last 200 lines)
+  - Filtered errors (stderr + error patterns)
+  - Active URL + port (server ALIVE, hot-reload active)
+- After Dev completes adjustments:
+  - Re-run QA-Implementation (fast, diffs only)
+  - Return to Step 5 (user validates again)
+  - Loop until approval
+
+#### Option 4: Rethink
+- Server stays alive (user can reference it)
+- Call `confirmPreview(state, 'rethink')`
+- Activate deviation protocol
+- Route to appropriate agent for rework
+- When resolved, return to Step 5
+
+### 7. Post-Deploy Cleanup
+After DevOps agent completes deployment successfully:
+- Check if local preview server is still running
+- If running, offer cleanup:
+
+```
+Deploy completed successfully!
+Your local server is still running at http://localhost:{PORT}.
+Would you like to shut it down?
+1. Yes, shut it down
+2. No, keep it running (I want to compare)
+```
+
+## Decision Points
+
+### When Framework Detection Fails
+If `detectDevCommand()` returns `null` but there's a `package.json`:
+1. Check for any script that looks like a server (dev, start, serve)
+2. If found, try running it
+3. If not found, treat as library/CLI project
+
+### When Server Fails to Start
+If health check times out (30s):
+1. Show captured logs (errors from LogBuffer)
+2. Ask user: "Server failed to start. Want to see the error logs?"
+3. Options: Route to Dev for fix, proceed to deploy anyway, rethink
+
+### When Port Range Exhausted
+If no port found in 20 attempts:
+1. Inform user: "Ports {start}-{start+19} are all in use"
+2. Ask user for a preferred port or to free one up
+3. Retry with user-provided port
+
+## Error Handling
+
+### Server Crash During Preview
+- LogBuffer preserves crash output
+- Notify user: "Server stopped unexpectedly"
+- Show last error logs
+- Options: Restart, route to Dev, proceed to deploy
+
+### Browser Failed to Open
+- Show URL for manual access
+- Continue normally (non-blocking)
+
+## Context for Dev Agent (Adjustments)
+
+When routing to Dev agent after user requests adjustments, include:
+
+```yaml
+preview_context:
+  user_feedback: "<text from user>"
+  server_url: "http://localhost:{PORT}"
+  server_alive: true
+  logs:
+    total_lines: 156
+    error_count: 3
+    errors:
+      - "TypeError: Cannot read properties of undefined (reading 'map')"
+      - "Warning: Each child in a list should have a unique key prop"
+      - "Error: ECONNREFUSED 127.0.0.1:5432"
+    recent_output:
+      - "[stdout] GET /api/users 200 12ms"
+      - "[stderr] TypeError: Cannot read properties..."
+      - "[stdout] GET /dashboard 200 45ms"
+  framework: "nextjs"
+  hot_reload: true
+```

package/framework/tasks/orchestrator-resume.md

@@ -50,7 +50,7 @@ Find the most recent agent with `status: completed`:
 
 ### 4. Determine Next Agent
 Based on pipeline position and last completed agent:
-- **PLANNING pipeline**: greenfield-wu → brief → detail → architect → ux → phases → tasks → qa-planning
+- **DISCOVER → PLAN pipeline**: greenfield-wu → brief → detail → architect → ux → phases → tasks → qa-planning
 - **BUILD pipeline**: dev → qa-implementation
 - **DEPLOY pipeline**: devops
 - Handle special cases (skipped, needs_revalidation)
@@ -163,7 +163,7 @@ session_state:
     language: "Portugues"
   current_mode: "planning"
   pipeline_position:
-    phase: "PLANNING"
+    phase: "DISCOVER"
     last_completed_agent: "detail"
     next_agent: "architect"
     completion_percentage: 30

package/framework/tasks/orchestrator-route.md

@@ -58,7 +58,8 @@ Check if the requested action is valid for current position:
 
 ### 5. Select Target Agent
 Based on intent and position, identify the appropriate agent:
-- **PLANNING agents**: greenfield-wu, brownfield-wu, brief, detail, architect, ux, phases, tasks, qa-planning
+- **DISCOVER agents**: greenfield-wu, brownfield-wu, brief, detail
+- **PLAN agents**: architect, ux, phases, tasks, qa-planning
 - **BUILD agents**: dev, qa-implementation
 - **DEPLOY agents**: devops
 - **Orchestrator actions**: status, health, deviation
@@ -151,16 +152,16 @@ routing_decision:
   intent_classification: "pipeline-next"
   target_type: "agent"  # or "orchestrator-action"
   target: "detail"
-  reason: "User completed brief, detail is next in PLANNING pipeline"
+  reason: "User completed brief, detail is next in DISCOVER pipeline"
   mode: "planning"
-  pipeline_position: "PLANNING/detail"
+  pipeline_position: "DISCOVER/detail"
   context_package:
     previous_agent: "brief"
     handoff_file: ".chati/artifacts/handoffs/2026-02-13-brief.md"
     session_excerpt:
       mode: "planning"
       project_type: "greenfield"
-      current_phase: "PLANNING"
+      current_phase: "DISCOVER"
   validation:
     mode_check: "passed"
     prerequisites_check: "passed"

package/framework/tasks/orchestrator-status.md

@@ -46,7 +46,7 @@ For each agent in the pipeline, gather:
 
 ### 3. Calculate Pipeline Progress
 Determine overall completion for each mode:
-- **PLANNING**: 9 agents (greenfield-wu OR brownfield-wu, brief, detail, architect, ux, phases, tasks, qa-planning)
+- **DISCOVER + PLAN**: 9 agents (greenfield-wu OR brownfield-wu, brief, detail, architect, ux, phases, tasks, qa-planning)
 - **BUILD**: 2 agents (dev, qa-implementation)
 - **DEPLOY**: 1 agent (devops)
 - Calculate percentage: completed / total
@@ -160,7 +160,7 @@ status_report:
 
   current_state:
     mode: "planning"
-    phase: "PLANNING"
+    phase: "DISCOVER"
     last_activity: "2026-02-13T02:15:00Z"
     hours_since_activity: 8.25
 
@@ -240,10 +240,10 @@ status_report:
   visual_report: |
     ╔════════════════════════════════════════════════════════════╗
     ║  chati.dev Status - HealthCare Portal                      ║
-    ║  Mode: PLANNING  |  Progress: 25% (3/12 agents)             ║
+    ║  Mode: DISCOVER  |  Progress: 25% (3/12 agents)             ║
     ╚════════════════════════════════════════════════════════════╝
 
-    PLANNING Pipeline (37.5%)
+    DISCOVER / PLAN Pipeline (37.5%)
     ✓ brownfield-wu  ✓ brief  ✓ detail  ◐ architect  ○ ux  ○ phases  ○ tasks  ○ qa-planning
 
     BUILD Pipeline (0%)