chati-dev 2.0.9 → 2.1.2

package/framework/agents/{planning → plan}/phases.md

@@ -8,7 +8,7 @@ You are the **Phases Agent**, responsible for breaking the PRD into development
 
 - **Role**: Roadmap & Execution Planning Specialist
 - **Pipeline Position**: 6th (after UX)
-- **Category**: PLANNING
+- **Category**: PLAN
 - **Question Answered**: WHEN will we build it?
 - **Duration**: 20-40 min
 - **Ratio**: 60% Human / 40% AI

package/framework/agents/{planning → plan}/tasks.md

@@ -8,7 +8,7 @@ You are the **Tasks Agent**, responsible for breaking phases into atomic, execut
 
 - **Role**: Work Breakdown & Task Definition Specialist
 - **Pipeline Position**: 7th (after Phases)
-- **Category**: PLANNING
+- **Category**: PLAN
 - **Question Answered**: WHO does WHAT specifically?
 - **Duration**: 30-60 min
 - **Ratio**: 50% Human / 50% AI

package/framework/agents/{planning → plan}/ux.md

@@ -8,7 +8,7 @@ You are the **UX Agent**, responsible for defining HOW the product will look and
 
 - **Role**: User Experience & Design System Specialist
 - **Pipeline Position**: 5th (after Architect in both flows)
-- **Category**: PLANNING
+- **Category**: PLAN
 - **Question Answered**: HOW will it look/feel?
 - **Duration**: 30-60 min
 - **Ratio**: 60% Human / 40% AI

package/framework/agents/quality/qa-implementation.md

@@ -119,18 +119,56 @@ For each completed task:
 Flag unverified criteria for manual review
 ```
 
-### Phase 5: Score & Decide
+### Phase 5: Adversarial Review (Mandatory)
+```
+RULE: Every QA pass MUST identify minimum 3 findings.
+Zero findings = suspiciously clean -> mandatory re-review.
+
+Process:
+1. After Phases 1-4, count total findings across all categories
+2. IF findings < 3:
+   - Log: "Adversarial trigger: only {N} findings detected"
+   - Re-run Phases 2-4 with DEEPER analysis:
+     * Lower severity threshold (include INFO-level observations)
+     * Check for implicit issues (poor naming, missing edge cases, weak error messages)
+     * Look for "things that work but could fail under load/scale"
+   - Findings now include: improvements, suggestions, best-practice deviations
+3. IF findings still < 3 after deep re-review:
+   - Document explicitly WHY the code is genuinely clean
+   - This documentation itself counts as a finding (type: attestation)
+
+Devil's Advocate Pass:
+  After initial review concludes APPROVED:
+  1. Assume the opposite: "This code has a hidden flaw"
+  2. Spend one focused pass actively seeking:
+     - Race conditions, memory leaks, unhandled edge cases
+     - Security assumptions that could be wrong
+     - Performance bottlenecks under 10x load
+     - Integration failures with external services
+  3. Document what you looked for and why it held up (or didn't)
+  4. This analysis is ALWAYS included in the report, even if no new issues found
+
+Findings Classification:
+  - ERROR: Must be fixed before APPROVED
+  - WARNING: Should be fixed, can proceed with documentation
+  - SUGGESTION: Improvement opportunity, does not block
+  - ATTESTATION: Explicit documentation of why something is clean
+```
+
+### Phase 6: Score & Decide
 ```
 Calculate overall quality score:
-  Tests: weight 0.30
-  Coverage: weight 0.20
+  Tests: weight 0.25
+  Coverage: weight 0.15
   Security: weight 0.25
   Code Quality: weight 0.15
   Acceptance Criteria: weight 0.10
+  Adversarial Review: weight 0.10
 
 Result:
-  - All checks pass -> APPROVED -> proceed to DevOps
+  - All checks pass AND adversarial review complete -> APPROVED -> proceed to DevOps
   - Any check fails -> enter silent correction loop
+  - Adversarial review incomplete -> CANNOT approve (re-run Phase 5)
 ```
 
 ---
@@ -233,6 +271,17 @@ Save to: `chati.dev/artifacts/8-Validation/qa-implementation-report.md`
 |------|----------|----------|--------|
 | T1.1 | {criterion} | Yes/No | {OK/FAIL} |
 
+## Adversarial Review
+| # | Type | Category | Description | Severity |
+|---|------|----------|-------------|----------|
+| 1 | {finding/attestation} | {security/performance/quality} | {desc} | {error/warning/suggestion/attestation} |
+
+### Devil's Advocate Analysis
+**Initial conclusion**: {APPROVED/NEEDS CORRECTION}
+**Adversarial hypothesis**: "This code has a hidden flaw in {area}"
+**Investigation**: {what was checked and why}
+**Result**: {held up / new issue found: {desc}}
+
 ## Correction History
 | Loop | Issue | Resolution |
 |------|-------|------------|

package/framework/agents/quality/qa-planning.md

@@ -121,7 +121,44 @@ For each agent that completed PLANNING:
      - Example: Brief said "Brief is well-written" (subjective, not binary)
 ```
 
-### Step 4: Calculate Score & Decide
+### Step 4: Adversarial Review (Mandatory)
+
+```
+RULE: Every planning validation MUST identify minimum 3 findings.
+Zero findings = suspiciously clean -> mandatory re-review.
+
+Process:
+1. After Steps 1-3, count total findings (flags, penalties, observations)
+2. IF findings < 3:
+   - Log: "Adversarial trigger: only {N} findings detected"
+   - Re-analyze with DEEPER scrutiny:
+     * Check for implicit assumptions not documented
+     * Look for missing non-functional requirements (performance, security, a11y)
+     * Verify edge cases are covered in acceptance criteria
+     * Challenge requirement prioritization
+   - Findings now include: suggestions, missing considerations, best-practice gaps
+3. IF findings still < 3 after deep re-review:
+   - Document explicitly WHY the planning is genuinely complete
+   - This documentation itself counts as a finding (type: attestation)
+
+Devil's Advocate Pass:
+  After traceability validation concludes APPROVED:
+  1. Assume the plan has a hidden flaw
+  2. Challenge:
+     - "What requirement is missing that will surface during BUILD?"
+     - "Which acceptance criterion is too vague to test objectively?"
+     - "What stakeholder need was mentioned but not traced to a task?"
+     - "Which architectural decision might not scale?"
+  3. Document the adversarial analysis in the report
+
+Findings Classification:
+  - GAP: Missing traceability link (blocks approval)
+  - WEAK: Subjective or vague criterion (should be fixed)
+  - SUGGESTION: Improvement opportunity (does not block)
+  - ATTESTATION: Explicit justification of completeness
+```
+
+### Step 5: Calculate Score & Decide
 
 ```
 Starting score: 100
@@ -134,10 +171,12 @@ Scoring:
 - Critical gap: -20 points
 - Placeholder: -5 points each
 - Agent defined weak criteria: -10 points
+- Adversarial review incomplete: -15 points
 
 Result:
-- Score >= 95: APPROVED -> GO to BUILD
+- Score >= 95 AND adversarial review complete: APPROVED -> GO to BUILD
 - Score < 95: Enter silent correction loop
+- Adversarial review incomplete: CANNOT approve (re-run Step 4)
 ```
 
 ---
@@ -208,6 +247,18 @@ Save to: `chati.dev/artifacts/7-QA-Planning/qa-planning-report.md`
 |------|------|------|
 | {file} | {placeholder} | {line} |
 
+## Adversarial Review
+| # | Type | Area | Description | Severity |
+|---|------|------|-------------|----------|
+| 1 | {gap/weak/suggestion/attestation} | {traceability/criteria/scope} | {desc} | {blocks/should-fix/info} |
+
+### Devil's Advocate Analysis
+**Initial conclusion**: {APPROVED/NEEDS CORRECTION}
+**Adversarial challenges**:
+1. "What requirement is missing?" → {finding or "None — all Brief problems traced to tasks"}
+2. "Which criterion is too vague?" → {finding or "None — all GWT criteria are binary"}
+3. "What will surface during BUILD?" → {finding or "None — edge cases covered"}
+
 ## Correction History
 | Loop | Agent | Issue | Resolution |
 |------|-------|-------|------------|

package/framework/config.yaml

@@ -1,8 +1,8 @@
 # chati.dev Configuration
-version: "2.0.1"
+version: "2.1.0"
 installed_at: "2026-02-07T10:00:00Z"
-updated_at: "2026-02-13T00:00:00Z"
-installer_version: "2.0.1"
+updated_at: "2026-02-17T00:00:00Z"
+installer_version: "2.1.0"
 project_type: greenfield
 language: en
 ides: [claude-code]

package/framework/constitution.md

@@ -6,7 +6,7 @@ Chati.dev is a planning-first AI-assisted orchestration system that coordinates
 
 ### 4 Core Principles
 
-1. **Planning Before Code**: Never write code without understanding the problem, the users, and the constraints. The PLANNING phase exists because assumptions are the root cause of failed projects.
+1. **Planning Before Code**: Never write code without understanding the problem, the users, and the constraints. The DISCOVER and PLAN phases exist because assumptions are the root cause of failed projects.
 
 2. **Short Iterations**: Deliver value in small, verifiable increments. Every agent validates its own output before passing forward. Every quality gate catches issues early.
 
@@ -242,7 +242,7 @@ The pipeline operates in three execution modes that control agent permissions. M
 
 | Mode | States | Read Scope | Write Scope |
 |------|--------|------------|-------------|
-| **planning** | planning | Entire project (codebase + chati.dev/) | `chati.dev/` and `.chati/` only |
+| **planning** | discover, plan | Entire project (codebase + chati.dev/) | `chati.dev/` and `.chati/` only |
 | **build** | build, validate | Entire project | Entire project |
 | **deploy** | deploy | Entire project | Entire project + infra/CI operations |
 
@@ -390,7 +390,7 @@ The system SHALL support two execution modes that govern the degree of human inv
 
 4. Certain agents are ALWAYS human-in-the-loop regardless of mode:
    - **brief**: Requirements extraction requires human validation
-   - **deviation-handler**: Deviations from the plan always need human approval
+   - **orchestrator (deviation protocol)**: Deviations from the plan always need human approval
 
 5. Safety net triggers SHALL pause autonomous execution when dangerous conditions are detected: consecutive failures, circular approaches, resource limits, or destructive operations.
 
@@ -402,5 +402,5 @@ The system SHALL support two execution modes that govern the degree of human inv
 
 ---
 
-*Chati.dev Constitution v2.0.0 — 17 Articles + Preamble*
+*Chati.dev Constitution v2.1.0 — 17 Articles + Preamble*
 *All agents are bound by this Constitution. Violations are enforced per article.*

package/framework/context/quality.md

@@ -11,7 +11,7 @@
 Scores within 5 points below threshold trigger REVIEW (human confirmation required even in autonomous mode).
 
 ## 5 Pipeline Gates
-1. **Planning Complete** — All PLANNING agents finished
+1. **Planning Complete** — All DISCOVER + PLAN agents finished
 2. **QA Planning** — QA-Planning agent validates plan coherence (95% threshold)
 3. **Implementation** — Dev agent completes all tasks
 4. **QA Implementation** — Tests pass, SAST clean, coverage adequate (95% threshold)

package/framework/context/root.md

@@ -1,7 +1,7 @@
 # Chati.dev System Context
 
 ## Framework
-- **Version**: 2.0.1
+- **Version**: 2.1.0
 - **Agents**: 13 (12 specialized + orchestrator)
 - **Constitution**: 17 Articles + Preamble
 - **Quality**: 5 pipeline gates + 4-tier validation
@@ -15,9 +15,10 @@
 
 ## Pipeline
 ```
-PLANNING: WU -> Brief -> Detail -> Architect -> UX -> Phases -> Tasks -> QA-Planning
-BUILD:   Dev -> QA-Implementation
-DEPLOY:  DevOps
+DISCOVER: WU -> Brief
+PLAN:     Detail -> Architect -> UX -> Phases -> Tasks -> QA-Planning
+BUILD:    Dev -> QA-Implementation
+DEPLOY:   DevOps
 ```
 
 ## How to Use

package/framework/data/entity-registry.yaml

@@ -5,7 +5,7 @@
 metadata:
   version: "1.0.0"
   last_updated: "2026-02-12T00:00:00Z"
-  entity_count: 47
+  entity_count: 50
   checksum_algorithm: sha256
 
 entities:
@@ -19,7 +19,7 @@ entities:
       adaptability: 0.2
 
     greenfield-wu:
-      path: chati.dev/agents/planning/greenfield-wu.md
+      path: chati.dev/agents/discover/greenfield-wu.md
       type: agent
       purpose: "Analyze greenfield project context, constraints, and technology landscape"
       keywords: [greenfield, analysis, context, technology, constraints]
@@ -27,7 +27,7 @@ entities:
       adaptability: 0.5
 
     brownfield-wu:
-      path: chati.dev/agents/planning/brownfield-wu.md
+      path: chati.dev/agents/discover/brownfield-wu.md
       type: agent
       purpose: "Deep discovery of existing codebase — architecture, patterns, debt, dependencies"
       keywords: [brownfield, discovery, codebase, architecture, debt]
@@ -35,7 +35,7 @@ entities:
       adaptability: 0.5
 
     brief:
-      path: chati.dev/agents/planning/brief.md
+      path: chati.dev/agents/discover/brief.md
       type: agent
       purpose: "Extract and structure user requirements through 5 elicitation phases"
       keywords: [requirements, elicitation, brief, functional, non-functional]
@@ -43,7 +43,7 @@ entities:
       adaptability: 0.4
 
     detail:
-      path: chati.dev/agents/planning/detail.md
+      path: chati.dev/agents/plan/detail.md
       type: agent
       purpose: "Transform Brief into formal PRD with complete specifications"
       keywords: [prd, specification, detail, formal, requirements]
@@ -51,7 +51,7 @@ entities:
       adaptability: 0.4
 
     architect:
-      path: chati.dev/agents/planning/architect.md
+      path: chati.dev/agents/plan/architect.md
       type: agent
       purpose: "Design technical architecture, make technology decisions, define system boundaries"
       keywords: [architecture, technology, design, patterns, boundaries]
@@ -59,7 +59,7 @@ entities:
       adaptability: 0.3
 
     ux:
-      path: chati.dev/agents/planning/ux.md
+      path: chati.dev/agents/plan/ux.md
       type: agent
       purpose: "Design user experience, interaction flows, and interface structure"
       keywords: [ux, design, interaction, flows, interface, wireframes]
@@ -67,7 +67,7 @@ entities:
       adaptability: 0.5
 
     phases:
-      path: chati.dev/agents/planning/phases.md
+      path: chati.dev/agents/plan/phases.md
       type: agent
       purpose: "Decompose PRD into development phases with MVP-first strategy"
       keywords: [phases, decomposition, mvp, planning, milestones]
@@ -75,7 +75,7 @@ entities:
       adaptability: 0.4
 
     tasks:
-      path: chati.dev/agents/planning/tasks.md
+      path: chati.dev/agents/plan/tasks.md
       type: agent
       purpose: "Create executable tasks with acceptance criteria from phase definitions"
       keywords: [tasks, acceptance-criteria, executable, given-when-then]
@@ -155,6 +155,14 @@ entities:
       dependencies: []
       adaptability: 0.6
 
+    quick-brief:
+      path: chati.dev/templates/quick-brief-tmpl.yaml
+      type: template
+      purpose: "Condensed brief template for Quick Flow pipeline — single-pass extraction"
+      keywords: [quick, brief, template, fast-track, condensed]
+      dependencies: [brief]
+      adaptability: 0.6
+
   workflows:
     greenfield-fullstack:
       path: chati.dev/workflows/greenfield-fullstack.yaml
@@ -196,6 +204,14 @@ entities:
       dependencies: [orchestrator]
       adaptability: 0.5
 
+    quick-flow:
+      path: chati.dev/workflows/quick-flow.yaml
+      type: workflow
+      purpose: "Fast-track pipeline for simple tasks: bug fixes, small features, config changes. Skips full PLAN phase."
+      keywords: [quick, fast-track, bug-fix, hotfix, simple, condensed]
+      dependencies: [orchestrator, brief, dev, qa-implementation, devops]
+      adaptability: 0.4
+
   schemas:
     session:
       path: chati.dev/schemas/session.schema.json
@@ -333,11 +349,19 @@ entities:
     elicitation:
       path: chati.dev/patterns/elicitation.md
       type: framework
-      purpose: "Elicitation patterns for requirements gathering"
+      purpose: "Elicitation patterns overview and quick reference"
       keywords: [elicitation, requirements, gathering, patterns, interview]
-      dependencies: [brief]
+      dependencies: [brief, elicitation-library]
       adaptability: 0.6
 
+    elicitation-library:
+      path: chati.dev/patterns/elicitation-library.yaml
+      type: intelligence
+      purpose: "Comprehensive catalog of 24 elicitation methods with triggers, steps, agent mapping, and auto-selection rules"
+      keywords: [elicitation, methods, brain-dump, scamper, moscow, five-whys, delphi, pre-mortem, personas, journey-map, stakeholder-map]
+      dependencies: [brief]
+      adaptability: 0.5
+
   i18n:
     en:
       path: chati.dev/i18n/en.yaml

package/framework/domains/agents/brief.yaml

@@ -45,3 +45,17 @@ rules:
   - id: br-05
     text: "MUST validate that success metrics are measurable and specific"
     priority: normal
+
+  - id: br-06
+    text: >
+      MUST select elicitation methods from chati.dev/patterns/elicitation-library.yaml
+      based on project context (type, user level, complexity). Auto-selection rules
+      in the library determine primary and secondary methods.
+    priority: high
+
+  - id: br-07
+    text: >
+      MUST use at least 3 different elicitation methods across the 5 extraction phases.
+      Single-method extraction produces shallow requirements. Recommended: brain-dump +
+      five-whys + playback as minimum set.
+    priority: high

package/framework/domains/agents/qa-implementation.yaml

@@ -41,3 +41,19 @@ rules:
   - id: qai-backward
     text: "If spec/architecture issues found, trigger backward transition to planning mode."
     priority: high
+
+  - id: qai-adversarial
+    text: >
+      ADVERSARIAL REVIEW: Every QA pass MUST identify minimum 3 findings
+      (improvements, warnings, or suggestions). Zero findings is suspiciously
+      clean — trigger mandatory re-review with deeper analysis. This prevents
+      rubber-stamping. Findings can be any severity (low/info counts).
+    priority: critical
+
+  - id: qai-devil-advocate
+    text: >
+      DEVIL'S ADVOCATE: After initial review, assume the opposite conclusion
+      and actively search for evidence to support it. If initial pass says
+      APPROVED, spend one extra pass trying to find reasons to FAIL.
+      Document what you looked for and why it held up (or didn't).
+    priority: high

package/framework/domains/agents/qa-planning.yaml

@@ -42,3 +42,19 @@ rules:
   - id: qap-strategy
     text: "Test strategy must include unit, integration, and E2E test categories."
     priority: normal
+
+  - id: qap-adversarial
+    text: >
+      ADVERSARIAL REVIEW: Every planning validation MUST identify minimum 3
+      findings (gaps, improvements, or suggestions). Zero findings is
+      suspiciously clean — re-analyze with deeper scrutiny across all
+      traceability chains. Findings can be any severity.
+    priority: critical
+
+  - id: qap-devil-advocate
+    text: >
+      DEVIL'S ADVOCATE: After traceability validation, assume the plan has
+      a hidden flaw and actively search for it. Challenge assumptions,
+      question requirement completeness, and look for scope gaps that
+      could surface during BUILD. Document the adversarial analysis.
+    priority: high

package/framework/domains/constitution.yaml

@@ -9,7 +9,7 @@ summary: >
   context brackets, memory governance, registry governance,
   session lock, model governance.
 
-articleCount: 16
+articleCount: 17
 
 rules:
   - id: art-i
@@ -21,7 +21,7 @@ rules:
     priority: critical
 
   - id: art-iii
-    text: "Memory and context must be managed through designated systems (PRISM, RECALL)."
+    text: "Memory and context must be managed through designated systems (PRISM)."
     priority: high
 
   - id: art-iv
@@ -75,3 +75,7 @@ rules:
   - id: art-xvi
     text: "Model governance: respect per-agent model assignments. No downgrade from assigned model."
     priority: high
+
+  - id: art-xvii
+    text: "Execution mode governance: autonomous requires gate >= 90%. Safety net with circuit breaker (3 failures)."
+    priority: critical

package/framework/domains/workflows/brownfield-discovery.yaml

@@ -1,11 +1,9 @@
 # Brownfield Discovery Workflow Domain — PRISM L3
-# Discovery-only pipeline (no implementation)
+# Standalone discovery pipeline (no implementation)
+# Agent: brownfield-wu only (7 phases of analysis)
 
 steps:
   - brownfield-wu
-  - brief
-  - detail
-  - architect
 
 rules:
   - id: disc-deep
@@ -14,3 +12,6 @@ rules:
   - id: disc-readonly
     text: "Discovery workflow does not modify project code."
     priority: high
+  - id: disc-standalone
+    text: "Brownfield discovery is a standalone workflow using only brownfield-wu across 7 analysis phases."
+    priority: normal

package/framework/domains/workflows/quick-flow.yaml

@@ -0,0 +1,23 @@
+# Quick Flow Workflow Domain — PRISM L3
+# Fast-track pipeline for simple tasks (bug fixes, small features, config changes)
+# Skips full PLAN phase — goes from Brief directly to Dev
+
+steps:
+  - brief
+  - dev
+  - qa-implementation
+  - devops
+
+rules:
+  - id: qf-scope
+    text: "Quick Flow is only for low-complexity tasks. Escalate to full pipeline if scope grows."
+    priority: critical
+  - id: qf-quality
+    text: "QA-Implementation validation is mandatory even in Quick Flow. No quality shortcuts."
+    priority: critical
+  - id: qf-brief
+    text: "Brief runs in quick-extraction mode: single-pass, 2 rounds max."
+    priority: high
+  - id: qf-escalation
+    text: "If dev discovers unexpected complexity, pause and offer escalation to full pipeline."
+    priority: high

package/framework/hooks/mode-governance.js

@@ -28,13 +28,25 @@ const MODE_SCOPES = {
   },
 };
 
+// Maps session states to governance modes (Article XI)
+const STATE_TO_GOVERNANCE_MODE = {
+  discover: 'planning',
+  plan: 'planning',
+  planning: 'planning',
+  build: 'build',
+  validate: 'build',
+  deploy: 'deploy',
+  completed: 'deploy',
+};
+
 function getCurrentMode(projectDir) {
   const sessionPath = join(projectDir, '.chati', 'session.yaml');
   if (!existsSync(sessionPath)) return 'planning'; // Default to most restrictive
 
   const raw = readFileSync(sessionPath, 'utf-8');
   const match = raw.match(/^\s*mode:\s*(.+)$/m);
-  return match ? match[1].trim().replace(/^["']|["']$/g, '') : 'planning';
+  const state = match ? match[1].trim().replace(/^["']|["']$/g, '') : 'discover';
+  return STATE_TO_GOVERNANCE_MODE[state] || 'planning';
 }
 
 function isPathAllowed(filePath, projectDir, mode) {
@@ -83,7 +95,7 @@ async function main() {
   }
 }
 
-export { getCurrentMode, isPathAllowed, MODE_SCOPES };
+export { getCurrentMode, isPathAllowed, MODE_SCOPES, STATE_TO_GOVERNANCE_MODE };
 
 // Only run main when executed directly (not imported by tests)
 import { fileURLToPath } from 'url';

package/framework/hooks/model-governance.js

@@ -93,4 +93,8 @@ async function main() {
 
 export { AGENT_MODELS, UPGRADE_CONDITIONS, getCurrentAgent };
 
-main();
+// Only run main when executed directly (not imported by tests)
+import { fileURLToPath } from 'url';
+if (process.argv[1] === fileURLToPath(import.meta.url)) {
+  main();
+}

package/framework/hooks/prism-engine.js

@@ -27,7 +27,7 @@ function readSessionState(projectDir) {
   };
 
   return {
-    mode: extract('mode') || 'planning',
+    mode: extract('mode') || 'discover',
     currentAgent: extract('current_agent') || null,
     workflow: extract('workflow') || null,
     pipelinePosition: extract('pipeline_position') || null,

package/framework/hooks/session-digest.js

@@ -21,7 +21,7 @@ function extractDigest(projectDir) {
 
   return {
     timestamp: new Date().toISOString(),
-    mode: extract('mode') || 'planning',
+    mode: extract('mode') || 'discover',
     currentAgent: extract('current_agent') || 'none',
     pipelinePosition: extract('pipeline_position') || 'unknown',
     workflow: extract('workflow') || 'unknown',
@@ -57,4 +57,8 @@ async function main() {
   }
 }
 
-main();
+// Only run main when executed directly (not imported by tests)
+import { fileURLToPath } from 'url';
+if (process.argv[1] === fileURLToPath(import.meta.url)) {
+  main();
+}

package/framework/hooks/settings.json

@@ -16,6 +16,17 @@
         ]
       }
     ],
+    "PreCompact": [
+      {
+        "matcher": ".*",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node chati.dev/hooks/session-digest.js"
+          }
+        ]
+      }
+    ],
     "PreToolUse": [
       {
         "matcher": "Read",

package/framework/i18n/en.yaml

@@ -16,9 +16,9 @@ installer:
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Will install:"
-  agents_count: "13 agent definitions (PLANNING, BUILD, DEPLOY phases)"
-  workflows_count: "5 workflow blueprints"
-  templates_count: "5 templates (PRD, Brownfield PRD, Architecture, Task, QA Gate)"
+  agents_count: "13 agent definitions (DISCOVER, PLAN, BUILD, DEPLOY phases)"
+  workflows_count: "6 workflow blueprints"
+  templates_count: "6 templates (PRD, Brownfield PRD, Architecture, Task, QA Gate, Quick Brief)"
   constitution: "Constitution (17 Articles + Preamble)"
   session_mgmt: "Session management system"
   quality_gates: "Quality gates (4-tier validation)"

package/framework/i18n/es.yaml

@@ -16,9 +16,9 @@ installer:
   ides_label: "IDEs"
   mcps_label: "MCPs"
   will_install: "Se instalara:"
-  agents_count: "13 definiciones de agentes (fases PLANNING, BUILD, DEPLOY)"
-  workflows_count: "5 blueprints de workflow"
-  templates_count: "5 templates (PRD, PRD Brownfield, Arquitectura, Task, QA Gate)"
+  agents_count: "13 definiciones de agentes (fases DISCOVER, PLAN, BUILD, DEPLOY)"
+  workflows_count: "6 blueprints de workflow"
+  templates_count: "6 templates (PRD, PRD Brownfield, Arquitectura, Task, QA Gate, Quick Brief)"
   constitution: "Constitucion (17 Articulos + Preambulo)"
   session_mgmt: "Sistema de gestion de sesion"
   quality_gates: "Quality gates (validacion en 4 capas)"