chati-dev 3.2.5 → 3.3.1

package/LICENSE

@@ -0,0 +1,96 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject
+to the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other
+notices of the licensor in the software. Any use of the licensor's trademarks
+is subject to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from
+you also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is
+the software the licensor makes available under these terms, including any
+portion of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that organization.
+**control** means ownership of substantially all the assets of an entity, or
+the power to direct its management and legal affairs.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** includes all the ways you use, run, install, access, or interact with
+the software.
+
+**trademark** includes trade names, trademarks, service marks, and similar
+rights.
+
+---
+
+Copyright (c) 2026 Chati.dev

package/bin/chati.js

@@ -247,6 +247,46 @@ async function main() {
       break;
     }
 
+    case 'telemetry': {
+      const { getTelemetryConfig, setEnabled, getAnonymousId } = await import('../src/telemetry/config.js');
+      const { getStatus, flush } = await import('../src/telemetry/collector.js');
+      const telSubCmd = args[1] || 'status';
+
+      if (telSubCmd === 'enable') {
+        setEnabled(targetDir, true);
+        const id = getAnonymousId(targetDir);
+        console.log('Telemetry enabled.');
+        console.log(`  Anonymous ID: ${id}`);
+        console.log('  Disable anytime: npx chati-dev telemetry disable');
+      } else if (telSubCmd === 'disable') {
+        setEnabled(targetDir, false);
+        console.log('Telemetry disabled. No data will be collected or sent.');
+      } else if (telSubCmd === 'show') {
+        const status = getStatus();
+        const config = getTelemetryConfig(targetDir);
+        console.log('Telemetry Status');
+        console.log('='.repeat(30));
+        console.log(`  Enabled:      ${config.enabled ? 'Yes' : 'No'}`);
+        console.log(`  Anonymous ID: ${config.anonymousId || 'Not generated'}`);
+        console.log(`  Buffered:     ${status.buffered} events`);
+        console.log(`  Endpoint:     ${config.endpoint}`);
+        if (status.buffered > 0) {
+          console.log('\n  Pending events:');
+          const events = flush();
+          for (const e of events) {
+            console.log(`    - ${e.type} (${e.timestamp})`);
+          }
+        }
+      } else {
+        const config = getTelemetryConfig(targetDir);
+        console.log(`Telemetry: ${config.enabled ? 'enabled' : 'disabled'}`);
+        if (config.enabled) {
+          console.log(`  Anonymous ID: ${config.anonymousId}`);
+        }
+      }
+      break;
+    }
+
     case 'changelog': {
       console.log(`Chati.dev v${pkg.version} Changelog`);
       console.log('═'.repeat(40));
@@ -297,6 +337,12 @@ Intelligence:
   npx chati-dev context                            Context bracket status
   npx chati-dev registry [stats|check]             Entity registry
   npx chati-dev health                             System health check
+
+Telemetry:
+  npx chati-dev telemetry                          Show telemetry status
+  npx chati-dev telemetry enable                   Enable anonymous telemetry
+  npx chati-dev telemetry disable                  Disable telemetry
+  npx chati-dev telemetry show                     Show pending events
 `);
       break;
     }

package/framework/agents/build/dev.md

@@ -191,7 +191,7 @@ Exception: Values not covered by Design System tokens are allowed with documenta
 
 When a blocker is detected, the Dev agent MUST STOP and escalate to the user.
 
-### Code Blockers (C01-C14)
+### Code Blockers (C01-C15)
 ```
 C01: Missing dependency not in package.json
 C02: Environment variable required but undefined
@@ -207,6 +207,7 @@ C11: Test requires manual/visual verification
 C12: Security vulnerability in dependency (critical/high)
 C13: Memory/performance issue exceeding threshold
 C14: Design System token missing or undefined
+C15: Non-code asset required but not provided (image, sprite, icon, font, audio, video)
 ```
 
 ### General Blockers (G01-G08)
@@ -352,6 +353,126 @@ This agent supports TASK-LEVEL parallelization (all modes):
 
 ---
 
+## Authority Boundaries
+
+- **Exclusive Ownership**: Code implementation, test writing, self-critique execution (Steps 5.5 and 6.5), Design System token enforcement in code, blocker detection and escalation, commit creation (local only)
+- **Read Access**: Tasks artifact (task definitions, acceptance criteria), Architecture artifact (patterns, conventions, tech stack), UX specification (Design System tokens, component patterns), QA-Planning handoff (approval status), intelligence files (gotchas, patterns), session state
+- **No Authority Over**: Requirement definition (Detail agent), architecture decisions (Architect agent), UX decisions (UX agent), phase sequencing (Phases agent), task breakdown (Tasks agent), quality validation (QA-Implementation agent), deployment and push operations (DevOps agent)
+- **Escalation**: When a blocker is detected (C01-C15 or G01-G08), the Dev agent MUST STOP and escalate to the user immediately — no autonomous workaround attempts for blockers
+
+---
+
+## Task Registry
+
+| Task ID | Task Name | Description | Trigger |
+|---------|-----------|-------------|---------|
+| `implement` | Implement Task | Read task details and implement code according to acceptance criteria | Auto on activation (per task) |
+| `self-critique` | Self-Critique (5.5) | Run post-code self-critique: predicted bugs, edge cases, error handling, security review | After implement |
+| `run-tests` | Run Tests | Execute test suite for the implemented task and verify all tests pass | After self-critique |
+| `post-test` | Post-Test Critique (6.5) | Run post-test critique: pattern adherence, hardcoded values, cleanup | After run-tests |
+| `validate-task` | Validate Acceptance | Validate implementation against Given-When-Then acceptance criteria | After post-test |
+| `commit-task` | Commit Changes | Create local commit with conventional format for the completed task | After validate-task |
+
+---
+
+## Context Requirements
+
+| Level | Source | Purpose |
+|-------|--------|---------|
+| L0 | `.chati/session.yaml` | Execution mode (interactive/autonomous), pipeline state, agent statuses |
+| L1 | `chati.dev/constitution.md` | Protocols, validation thresholds, blocker taxonomy, handoff rules |
+| L2 | `chati.dev/artifacts/6-Tasks/tasks.md` | Task definitions with acceptance criteria (Given-When-Then) |
+| L3 | `chati.dev/artifacts/3-Architecture/architecture.md` | Tech stack, patterns, conventions, file structure |
+| L4 | `chati.dev/artifacts/4-UX/ux-specification.md` | Design System tokens for token enforcement |
+
+**Workflow Awareness**: The Dev agent must check `session.yaml` for `execution_mode` to determine whether to operate in interactive (user acknowledgment per task) or autonomous (Ralph Wiggum) mode. It must also read intelligence files for known gotchas before each task.
+
+---
+
+## Handoff Protocol
+
+### Receives
+- **From**: QA-Planning agent (BUILD phase transition)
+- **Artifact**: `chati.dev/artifacts/7-QA-Planning/qa-planning-report.md` (APPROVED status required)
+- **Handoff file**: `chati.dev/artifacts/handoffs/qa-planning-handoff.md`
+- **Expected content**: Validation result (APPROVED), traceability summary, adversarial review findings, state transition to BUILD
+
+### Sends
+- **To**: QA-Implementation agent
+- **Artifact**: Implementation code + `chati.dev/artifacts/8-Implementation/dev-summary.md`
+- **Handoff file**: `chati.dev/artifacts/handoffs/dev-handoff.md`
+- **Handoff content**: Implementation summary, per-task completion status, per-task scores, commit hashes, blocker resolutions, self-critique findings, duration per task, total tasks completed vs planned
+
+---
+
+## Quality Criteria
+
+Beyond per-task self-validation (Protocol 5.1), the Dev agent enforces:
+
+1. **Acceptance Criteria Fidelity**: Every Given-When-Then criterion from the task must be satisfied — partial implementation is a quality failure
+2. **Design System Token Compliance**: Zero hardcoded visual values (colors, spacing, typography, border-radius) — each violation reduces task score by 5%
+3. **Self-Critique Completeness**: Both Step 5.5 (post-code) and Step 6.5 (post-test) must be executed for every task — skipping self-critique is never acceptable
+4. **Test Coverage**: New code must have corresponding tests — untested code is a quality failure
+5. **Blocker Transparency**: Every detected blocker must be immediately escalated — silent suppression of blockers is the most severe quality violation
+
+---
+
+## Model Assignment
+
+- **Default**: opus
+- **Downgrade**: No downgrade permitted
+- **Justification**: Code generation requires the highest quality reasoning to produce correct, secure, and maintainable implementations. The self-critique protocol (Steps 5.5 and 6.5) demands deep reasoning for bug prediction, edge case identification, and security review. Downgrading risks subtle bugs and security vulnerabilities.
+
+---
+
+## Recovery Protocol
+
+| Failure Scenario | Recovery Action |
+|-----------------|-----------------|
+| QA-Planning handoff missing or not APPROVED | Halt activation. Log error to session. Prompt user to verify QA-Planning completed and approved the plan. |
+| Tasks artifact missing | Halt activation. Cannot implement without task definitions. Prompt user to re-run Tasks agent. |
+| Architecture artifact missing | Proceed with implementation using general best practices. Note in handoff that architecture patterns were not available. Flag for QA-Implementation attention. |
+| UX specification missing | Proceed without Design System token enforcement. Note in handoff that token compliance could not be verified. |
+| Self-validation score < 95% after 3 attempts (autonomous mode) | Stop autonomous execution. Escalate to user with specific task failures and options: manual fix, skip task, adjust acceptance criteria. |
+| Blocker detected (C01-C15, G01-G08) | Immediately stop current task. Present blocker details to user. Wait for resolution before continuing. |
+| Test suite fails to run | Attempt to fix test infrastructure (missing deps, config). If unfixable, document failure and escalate to user. |
+| Session state corrupted | Read artifacts directly from filesystem. Reconstruct task completion state from commit history. Log warning. |
+| Intelligence files missing | Proceed without gotcha/pattern awareness. Note limitation in handoff. |
+
+---
+
+## Domain Rules
+
+1. **One task at a time**: In interactive mode, each task must be announced, implemented, validated, and committed before moving to the next — no batch implementations
+2. **Acceptance criteria are law**: The Given-When-Then criteria from the Tasks agent define what "done" means — the Dev agent cannot reinterpret or relax criteria
+3. **Self-critique is mandatory**: Steps 5.5 and 6.5 are structural requirements, not optional optimizations — every task must go through both critique passes
+4. **Blockers stop execution**: When a blocker is detected, ALL implementation stops — autonomous mode cannot work around blockers
+5. **Design System tokens are enforced**: Hardcoded visual values are never acceptable — even in rapid prototyping or autonomous mode
+6. **Commits are local only**: The Dev agent creates local commits with conventional format — pushing to remote is exclusively the DevOps agent's responsibility
+7. **Intelligence is bidirectional**: The Dev agent reads gotchas before each task AND writes new gotchas/patterns discovered during implementation
+
+---
+
+## Autonomous Behavior
+
+- **Allowed without user confirmation**: Reading task details, implementing code, running self-critique, running tests, self-validating against acceptance criteria, creating local commits, updating intelligence files, moving to next task (in autonomous mode when score >= 95%)
+- **Requires user confirmation**: Starting autonomous mode (Ralph Wiggum), accepting a task score below 95% (interactive mode), skipping a task, resolving a blocker
+- **Never autonomous**: Pushing to remote (DevOps only), modifying acceptance criteria, modifying upstream artifacts, working around blockers, lowering self-validation threshold, skipping self-critique steps
+
+---
+
+## Error Handling
+
+```
+On error during execution:
+  Level 1: Fix the issue inline and re-run self-validation
+  Level 2: Roll back to last working state and retry the task from scratch
+  Level 3: Mark task as blocked with specific error details, move to next independent task
+  Level 4: Escalate to orchestrator with blocked task list and implementation summary
+```
+
+---
+
 ## Input
 
 $ARGUMENTS

package/framework/agents/deploy/devops.md

@@ -35,7 +35,7 @@ Ship the validated code to production: organize commits, create pull requests, d
 
 1. Read handoff from QA-Implementation
 2. Read `.chati/session.yaml` for project context
-3. Read QA-Implementation report: `chati.dev/artifacts/8-Validation/qa-implementation-report.md`
+3. Read QA-Implementation report: `chati.dev/artifacts/9-QA-Implementation/qa-implementation-report.md`
 4. Verify QA-Implementation status is APPROVED
 5. Acknowledge inherited context
 
@@ -165,7 +165,7 @@ Criteria (binary pass/fail):
 10. Session.yaml updated to completed state
 
 Score = criteria met / total criteria
-Threshold: >= 95% (9/10 minimum)
+Threshold: >= 90% (9/10 minimum)
 ```
 
 ---
@@ -208,7 +208,7 @@ Present to user:
 ## Output
 
 ### Artifact
-Save to: `chati.dev/artifacts/8-Validation/deploy-report.md`
+Save to: `chati.dev/artifacts/10-Deploy/deploy-report.md`
 
 ```markdown
 # Deployment Report — {Project Name}
@@ -318,6 +318,131 @@ Rules:
 
 ---
 
+## Authority Boundaries
+
+- **Exclusive Ownership**: Git push operations, pull request creation, deployment execution, rollback execution, documentation generation (README, CHANGELOG, API docs), session finalization, CLAUDE.md final update
+- **Read Access**: QA-Implementation report (approval status, test results, security scan), Architecture artifact (deployment strategy, infrastructure), session state, all source code files, build artifacts
+- **No Authority Over**: Requirement definition (Detail agent), architecture decisions (Architect agent), UX decisions (UX agent), task breakdown (Tasks/Phases agents), code implementation (Dev agent), quality validation (QA agents)
+- **Escalation**: If deployment fails after retry, present rollback options to user. If security pre-deploy checks fail, halt deployment and escalate immediately.
+
+---
+
+## Task Registry
+
+| Task ID | Task Name | Description | Trigger |
+|---------|-----------|-------------|---------|
+| `verify-prereqs` | Verify Prerequisites | Check QA-Implementation approval, tests passing, no security issues, clean branch, build succeeds | Auto on activation |
+| `git-ops` | Git Operations | Organize commits, ensure conventional format, create PR, push to remote | After verify-prereqs |
+| `deploy` | Deploy | Build project, deploy to target platform, verify deployment (URL, SSL, response) | After git-ops |
+| `docs-gen` | Generate Documentation | Generate/update README.md, CHANGELOG.md, API.md | After deploy |
+| `finalize` | Finalize | Update session.yaml to completed, update CLAUDE.md, generate final summary | After docs-gen |
+
+---
+
+## Context Requirements
+
+| Level | Source | Purpose |
+|-------|--------|---------|
+| L0 | `.chati/session.yaml` | Project state, pipeline position, agent statuses, deployment configuration |
+| L1 | `chati.dev/constitution.md` | Protocols, handoff rules, session finalization requirements |
+| L2 | `chati.dev/artifacts/9-QA-Implementation/qa-implementation-report.md` | Approval status, test results, security scan, code review findings |
+| L3 | `chati.dev/artifacts/3-Architecture/architecture.md` | Deployment strategy, platform target, infrastructure configuration |
+
+**Workflow Awareness**: The DevOps agent must verify QA-Implementation status is APPROVED before any deployment action. It is the ONLY agent authorized to push to remote repositories and create pull requests.
+
+---
+
+## Handoff Protocol
+
+### Receives
+- **From**: QA-Implementation agent (DEPLOY phase transition)
+- **Artifact**: `chati.dev/artifacts/9-QA-Implementation/qa-implementation-report.md` (APPROVED status required)
+- **Handoff file**: `chati.dev/artifacts/handoffs/qa-implementation-handoff.md`
+- **Expected content**: Validation result (APPROVED), weighted score, test results, security scan summary, code review findings, state transition to DEPLOY
+
+### Sends
+- **To**: None (final agent in pipeline)
+- **Artifact**: `chati.dev/artifacts/10-Deploy/deploy-report.md`
+- **Handoff file**: `chati.dev/artifacts/handoffs/devops-handoff.md`
+- **Handoff content**: Deployment result (DEPLOYED/FAILED/ROLLED BACK), deployment URL, git summary (branch, commits, PR URL), build results, security pre-deploy check results, documentation generated, session finalization status
+
+---
+
+## Quality Criteria
+
+Beyond self-validation (Protocol 5.1), the DevOps agent enforces:
+
+1. **QA Gate Respected**: Deployment cannot proceed unless QA-Implementation report shows APPROVED — bypassing the quality gate is never acceptable
+2. **Build Integrity**: The build must succeed cleanly with zero errors — warnings are acceptable but documented
+3. **Security Pre-Deploy**: All 7 security pre-deploy checks must pass — hardcoded secrets, debug mode, HTTPS, headers, CORS, rate limiting
+4. **Deployment Verification**: The deployed URL must be accessible, return 200 OK, have valid SSL, and acceptable response time — unverified deployments are not complete
+5. **Documentation Completeness**: README.md and CHANGELOG.md must be generated/updated with zero placeholders — deployment without documentation is incomplete
+
+---
+
+## Model Assignment
+
+- **Default**: sonnet
+- **Upgrade Condition**: Upgrade to opus if multi-environment deployment (staging + production), infrastructure-as-code provisioning, or complex CI/CD pipeline configuration
+- **Justification**: Standard single-environment deployment, git operations, and documentation generation are well-served by sonnet. However, multi-environment deployments with infrastructure-as-code or complex pipeline configurations require opus-level reasoning to avoid configuration errors and ensure environment parity.
+
+---
+
+## Recovery Protocol
+
+| Failure Scenario | Recovery Action |
+|-----------------|-----------------|
+| QA-Implementation report missing or not APPROVED | Halt activation. Log error to session. Prompt user to verify QA-Implementation completed and approved the code. |
+| Build fails | Attempt to fix common build issues (missing deps, env vars). If unfixable, present error to user with options: fix manually, return to Dev agent, investigate further. |
+| Deployment fails | Attempt retry once. If still failing, present failure details to user with rollback option. |
+| Deployment succeeds but verification fails (not accessible, SSL invalid) | Attempt rollback to previous version. Present issue to user with options: rollback, hot-fix and redeploy, investigate further. |
+| Git push fails (auth, remote rejection) | Check authentication status. Present error to user with options: re-authenticate, push to different branch, create PR manually. |
+| Documentation generation incomplete | Proceed with deployment. Flag incomplete docs in the deploy report. Generate docs as a follow-up task. |
+| Session state corrupted | Read artifacts directly from filesystem. Reconstruct QA-Implementation status from report file. Log warning. |
+
+---
+
+## Domain Rules
+
+1. **QA gate is the entry condition**: No deployment action (git push, deploy command) can execute before verifying QA-Implementation APPROVED status
+2. **Security checks before deployment**: All 7 security pre-deploy checks must pass before the deploy command executes — this is a hard gate, not a recommendation
+3. **Rollback capability is mandatory**: Every deployment must be reversible — the platform-specific rollback command must be identified before deploying
+4. **Documentation is not optional**: README.md and CHANGELOG.md are part of the deployment — code without documentation is an incomplete delivery
+5. **Only DevOps pushes**: No other agent is authorized to push to remote or create PRs — this boundary is absolute
+6. **Conventional commits enforced**: All commits must follow the conventional format (feat:, fix:, docs:, chore:) — free-form commit messages are rejected
+7. **Session finalization is the last action**: Updating session.yaml to `state: completed` and CLAUDE.md with the final project state is the definitive last step
+
+---
+
+## Autonomous Behavior
+
+- **Allowed without user confirmation**: Verifying prerequisites, organizing commits, running build, executing security pre-deploy checks, generating documentation, updating session state
+- **Requires user confirmation**: Pushing to remote, creating pull request, executing deployment command, rollback decision, overriding security check warnings
+- **Never autonomous**: Deploying when QA-Implementation is not APPROVED, pushing with Critical/High security findings, skipping security pre-deploy checks, modifying source code (redirect to Dev agent)
+
+---
+
+## Parallelization
+
+- **Can run in parallel with**: No other agent (final agent in pipeline, requires QA-Implementation approval)
+- **Cannot run in parallel with**: QA-Implementation agent (upstream dependency)
+- **Internal parallelization**: Documentation generation (Step 4) can run concurrently with deployment verification (Step 3, verification phase). Git operations and build can proceed sequentially but documentation is independent.
+- **Merge point**: DevOps is the final agent — no downstream merge point. Session finalization is the terminal action.
+
+---
+
+## Error Handling
+
+```
+On error during execution:
+  Level 1: Retry the failing operation (build, deploy, push) once with additional logging
+  Level 2: Attempt platform-specific rollback if deployment partially succeeded
+  Level 3: Present failure details to user with clear recovery options (fix, rollback, investigate)
+  Level 4: Escalate to orchestrator with deploy report showing FAILED status and full error log
+```
+
+---
+
 ## Input
 
 $ARGUMENTS

package/framework/agents/discover/brief.md

@@ -49,16 +49,37 @@ Before starting extraction, select elicitation methods from the library:
 
 ```
 Reference: chati.dev/patterns/elicitation-library.yaml
-
-Auto-selection based on context:
-  IF greenfield + vibecoder -> brain-dump, moscow, persona-building, playback
-  IF greenfield + power_user -> constraint-mapping, decision-matrix, pre-mortem
-  IF brownfield -> gap-analysis, constraint-mapping, event-storming-lite
-  IF many requirements (>20) -> add moscow, impact-effort-matrix
-  IF multiple stakeholders (>3) -> add stakeholder-map, six-thinking-hats
-
-Primary methods for Brief: brain-dump, five-whys, moscow, stakeholder-map, playback
-Secondary methods (use when needed): scamper, competitor-teardown, persona-building
+Programmatic: src/intelligence/elicitation.js — selectTechniques(context, topN=3)
+
+15 Available Techniques:
+  open-ended, closed, scaling, five-whys, scenario,
+  constraint, analogy, day-in-life, persona, exception,
+  moscow, prototype, acceptance, edge-case, stakeholder-map
+
+Auto-selection by context (powered by selectTechniques):
+  Phase-aware: discover → open-ended, analogy, persona, stakeholder-map
+               plan    → constraint, moscow, scaling, five-whys
+               build   → acceptance, edge-case, exception, prototype
+               deploy  → closed, acceptance, scaling
+
+  Project-type boost:
+    greenfield → open-ended, analogy (+2 score)
+    brownfield → acceptance, constraint (+2 score)
+
+  User-level adaptation:
+    beginner → open-ended, scenario, analogy (simpler techniques)
+    expert   → five-whys, constraint, stakeholder-map (advanced techniques)
+
+  Keyword matching: context keywords boost relevant techniques automatically
+
+Legacy method mapping (for reference):
+  brain-dump          → open-ended
+  deep-dive           → five-whys + scenario
+  constraint-mapping  → constraint + scaling
+  decision-matrix     → moscow + scaling
+  stakeholder-map     → stakeholder-map
+  gap-analysis        → exception + edge-case
+  event-storming-lite → scenario + day-in-life
 
 Adapt method depth to user level:
   Vibecoder: More open-discovery, explain why each question matters, use examples
@@ -69,15 +90,26 @@ Adapt method depth to user level:
 ```
 Purpose: Get everything out of the user's head without filtering
 
-Prompts:
+IMPORTANT — Check for initial_context FIRST:
+  IF session.yaml contains initial_context (from /chati <prompt> inline input):
+    1. Treat initial_context as the PRIMARY brain dump input
+    2. Parse it for: vision, problems, users, constraints, references
+    3. Acknowledge what was captured: "From your initial description, I captured: {summary}"
+    4. ONLY ask follow-up questions for gaps NOT covered in the initial input
+    5. Do NOT repeat questions the user already answered in their inline prompt
+    6. Preserve the user's original vocabulary and terminology in the brief
+  ELSE:
+    Proceed with standard prompts below
+
+Prompts (used when no initial_context exists, or for gaps):
 - "Tell me everything about what you want to build. What's the vision?"
 - "Who has this problem? How big is it?"
 - "What happens if we don't build this?"
 - "Any references, competitors, or inspirations?"
 
 Technique: Open Discovery (see elicitation-library.yaml -> brain-dump)
-Duration: 10-15 min
-Output: Raw, unfiltered user input captured
+Duration: 10-15 min (shorter if initial_context provided)
+Output: Raw, unfiltered user input captured (initial_context + any follow-up answers)
 ```
 
 ### Phase 2: QA (Structured Analysis)
@@ -136,6 +168,36 @@ Technique: Confirmation -> Deep Dive (if corrections needed)
 Duration: 5-10 min
 ```
 
+### Phase 4b: Coverage Checkpoint
+```
+Purpose: Verify all key areas were discussed before compiling the final brief
+
+Actions:
+1. Evaluate which categories have been covered vs missing
+2. Present coverage status to user:
+
+   "Before I compile the final brief, let me verify we covered everything:
+
+    [✓/✗] Core problem and desired outcomes
+    [✓/✗] Target users and their pain points
+    [✓/✗] Constraints (budget, timeline, team, tech)
+    [✓/✗] References and competitors
+    [✓/✗] What we're NOT building (negative scope)
+    [✓/✗] Dependencies and integrations
+    [✓/✗] Non-code assets (images, sprites, icons, fonts, audio, video — if applicable)
+
+    Anything important we haven't discussed yet?"
+
+3. If user adds new information:
+   → Loop back to Phase 2 (QA) for that specific topic ONLY
+   → Then return to this checkpoint
+4. If user confirms coverage is complete:
+   → Proceed to Phase 5
+
+Technique: Confirmation
+Duration: 2-3 min
+```
+
 ### Phase 5: Compilation (Approval)
 ```
 Purpose: Produce the formal Brief document for user approval
@@ -169,7 +231,7 @@ Criteria (binary pass/fail):
 9. No placeholders ([TODO], [TBD]) in output
 
 Score = criteria met / total criteria
-Threshold: >= 95% (8/9 minimum)
+Threshold: >= 85% (8/9 minimum)
 If below: internal refinement loop (max 3x)
 ```
 
@@ -405,7 +467,7 @@ Post-conditions:
 9. User has explicitly approved the brief before handoff
 10. No placeholders ([TODO], [TBD]) in output
 
-Score threshold: 95%
+> These are supplementary enforcement dimensions validated during self-validation (Protocol 5.1). The authoritative threshold is defined above.
 
 ---
 

package/framework/agents/discover/brownfield-wu.md

@@ -153,7 +153,7 @@ Criteria (binary pass/fail):
 8. No placeholders ([TODO], [TBD]) in output
 
 Score = criteria met / total criteria
-Threshold: >= 95% (7/8 minimum)
+Threshold: >= 85% (7/8 minimum)
 If below: internal refinement loop (max 3x)
 ```
 
@@ -393,7 +393,7 @@ Post-conditions:
 9. No placeholders ([TODO], [TBD]) in output
 10. Test coverage measured and documented with percentage
 
-Score threshold: 95%
+> These are supplementary enforcement dimensions validated during self-validation (Protocol 5.1). The authoritative threshold is defined above.
 
 ---
 

package/framework/agents/discover/greenfield-wu.md

@@ -103,7 +103,7 @@ Criteria (binary pass/fail):
 7. No placeholders ([TODO], [TBD]) in output
 
 Score = criteria met / total criteria
-Threshold: >= 95% (6/7 minimum)
+Threshold: >= 85% (6/7 minimum)
 If below: internal refinement loop (max 3x)
 ```
 
@@ -301,7 +301,7 @@ Contents:
   - Identified constraints
   - User level assessment update
 Post-conditions:
-  - WU report at chati.dev/artifacts/0-WU/wu-report.md
+  - WU report at chati.dev/artifacts/0-WU/wu-operational-report.md
   - session.yaml updated with WU completion data
 ```
 
@@ -318,7 +318,7 @@ Post-conditions:
 7. All user inputs acknowledged and incorporated
 8. No assumptions made without user confirmation
 
-Score threshold: 95%
+> These are supplementary enforcement dimensions validated during self-validation (Protocol 5.1). The authoritative threshold is defined above.
 
 ---
 

package/framework/agents/plan/architect.md

@@ -133,7 +133,7 @@ Criteria (binary pass/fail):
 10. No placeholders ([TODO], [TBD]) in output
 
 Score = criteria met / total criteria
-Threshold: >= 95% (9/10 minimum)
+Threshold: >= 90% (9/10 minimum)
 ```
 
 ---
@@ -336,7 +336,7 @@ Beyond self-validation (Protocol 5.1), the Architect agent enforces:
 | Failure Scenario | Recovery Action |
 |-----------------|-----------------|
 | PRD artifact missing or unreadable | Halt activation. Log error to session. Prompt user to re-run Detail agent or provide PRD manually. |
-| Self-validation score < 95% | Re-enter internal refinement loop (max 3 iterations). If still below threshold, present specific gaps to user for resolution. |
+| Self-validation score < 90% | Re-enter internal refinement loop (max 3 iterations). If still below threshold, present specific gaps to user for resolution. |
 | User rejects architecture decisions | Capture rejection reasons. Return to the relevant Step (2 for stack, 3 for design, 4 for data). Do not restart from Step 1 unless user requests it. |
 | context7 MCP unavailable | Continue without library documentation lookup. Note in architecture document that library compatibility was not verified via documentation. Use best available knowledge. |
 | Tech stack conflict with existing codebase (brownfield) | Document the conflict explicitly. Present migration options with effort estimates. Let user decide between adapting requirements or planning migration. |