codex-workflows 0.6.8 → 0.6.9

package/.codex/agents/scope-discoverer.toml

@@ -162,76 +162,7 @@ Note: These signals are informational only during steps 1-6. Keep all discovered
 ### Essential Output
 
 ```json
-{
-  "targetPath": "/path/to/project",
-  "referenceArchitecture": "layered|mvc|clean|hexagonal|none",
-  "existingPrd": "path or null",
-  "saturationReached": true,
-  "discoveredUnits": [
-    {
-      "id": "UNIT-001",
-      "name": "Unit Name",
-      "description": "Brief description",
-      "confidence": "high|medium|low",
-      "triangulationStrength": "strong|moderate|weak",
-      "sourceCount": 3,
-      "entryPoints": ["/path1", "/path2"],
-      "relatedFiles": ["src/feature/*"],
-      "dependencies": ["UNIT-002"],
-      "valueProfile": {
-        "targetPersona": "Who this feature serves (e.g., 'end user', 'admin', 'developer')",
-        "userGoal": "What the user is trying to accomplish with this feature",
-        "valueCategory": "High-level capability this belongs to (e.g., 'Authentication', 'Content Management', 'Reporting')",
-        "groupingKey": {
-          "targetPersona": "end-user",
-          "userGoal": "sign-in",
-          "valueCategory": "authentication"
-        }
-      },
-      "technicalProfile": {
-        "primaryModules": ["src/auth/service.ts", "src/auth/controller.ts"],
-        "publicInterfaces": ["AuthService.login()", "AuthController.handleLogin()"],
-        "dataFlowSummary": "Request → Controller → Service → Repository → DB",
-        "infrastructureDeps": ["database", "redis-cache"]
-      },
-      "unitInventory": {
-        "routes": ["POST /login -> AuthController.handleLogin (src/auth/controller.ts:24)"],
-        "testFiles": ["src/auth/service.test.ts"],
-        "publicExports": ["AuthService (src/auth/service.ts:10)"]
-      }
-    }
-  ],
-  "relationships": [
-    {
-      "from": "UNIT-001",
-      "to": "UNIT-002",
-      "type": "depends_on|extends|shares_data"
-    }
-  ],
-  "uncertainAreas": [
-    {
-      "area": "Area name",
-      "reason": "Why uncertain",
-      "suggestedAction": "What to do"
-    }
-  ],
-  "prdUnits": [
-    {
-      "id": "PRD-001",
-      "name": "PRD unit name (user-value level)",
-      "description": "What this capability delivers to the user",
-      "groupingKey": {
-        "targetPersona": "end-user",
-        "userGoal": "sign-in",
-        "valueCategory": "authentication"
-      },
-      "sourceUnits": ["UNIT-001", "UNIT-003"],
-      "combinedRelatedFiles": ["src/feature-a/*", "src/feature-b/*"],
-      "combinedEntryPoints": ["/path1", "/path2", "/path3"]
-    }
-  ],
-  "limitations": ["What could not be discovered and why"]
-}
+{"targetPath":"/path/to/project","referenceArchitecture":"layered|mvc|clean|hexagonal|none","existingPrd":"path or null","saturationReached":true,"discoveredUnits":[{"id":"UNIT-001","name":"Unit Name","description":"Brief description","confidence":"high|medium|low","triangulationStrength":"strong|moderate|weak","sourceCount":3,"entryPoints":["/path1","/path2"],"relatedFiles":["src/feature/*"],"dependencies":["UNIT-002"],"valueProfile":{"targetPersona":"Who this feature serves (e.g., 'end user', 'admin', 'developer')","userGoal":"What the user is trying to accomplish with this feature","valueCategory":"High-level capability this belongs to (e.g., 'Authentication', 'Content Management', 'Reporting')","groupingKey":{"targetPersona":"end-user","userGoal":"sign-in","valueCategory":"authentication"}},"technicalProfile":{"primaryModules":["src/auth/service.ts","src/auth/controller.ts"],"publicInterfaces":["AuthService.login()","AuthController.handleLogin()"],"dataFlowSummary":"Request → Controller → Service → Repository → DB","infrastructureDeps":["database","redis-cache"]},"unitInventory":{"routes":["POST /login -> AuthController.handleLogin (src/auth/controller.ts:24)"],"testFiles":["src/auth/service.test.ts"],"publicExports":["AuthService (src/auth/service.ts:10)"]}}],"relationships":[{"from":"UNIT-001","to":"UNIT-002","type":"depends_on|extends|shares_data"}],"uncertainAreas":[{"area":"Area name","reason":"Why uncertain","suggestedAction":"What to do"}],"prdUnits":[{"id":"PRD-001","name":"PRD unit name (user-value level)","description":"What this capability delivers to the user","groupingKey":{"targetPersona":"end-user","userGoal":"sign-in","valueCategory":"authentication"},"sourceUnits":["UNIT-001","UNIT-003"],"combinedRelatedFiles":["src/feature-a/*","src/feature-b/*"],"combinedEntryPoints":["/path1","/path2","/path3"]}],"limitations":["What could not be discovered and why"]}
 ```
 
 ## Completion Criteria

package/.codex/agents/security-reviewer.toml

@@ -107,25 +107,7 @@ Return the JSON result as the final response. See Output Format for the schema.
 ## Output Format
 
 ```json
-{
-  "status": "approved|approved_with_notes|needs_revision|blocked",
-  "summary": "[1-2 sentence summary]",
-  "filesReviewed": 5,
-  "findings": [
-    {
-      "category": "confirmed_risk|defense_gap|hardening|policy",
-      "confidence": "high|medium|low",
-      "location": "[file:line]",
-      "description": "[specific issue found]",
-      "rationale": "[category-specific, see Category-Specific Rationale]",
-      "suggestion": "[specific fix]"
-    }
-  ],
-  "notes": "[summary of hardening/policy findings for completion report, present when status is approved_with_notes]",
-  "requiredFixes": [
-    "[specific fix 1 — only confirmed_risk and qualifying defense_gap items]"
-  ]
-}
+{"status":"approved|approved_with_notes|needs_revision|blocked","summary":"[1-2 sentence summary]","filesReviewed":5,"findings":[{"category":"confirmed_risk|defense_gap|hardening|policy","confidence":"high|medium|low","location":"[file:line]","description":"[specific issue found]","rationale":"[category-specific, see Category-Specific Rationale]","suggestion":"[specific fix]"}],"notes":"[summary of hardening/policy findings for completion report, present when status is approved_with_notes]","requiredFixes":["[specific fix 1 — only confirmed_risk and qualifying defense_gap items]"]}
 ```
 
 ## Status Determination

package/.codex/agents/solver.toml

@@ -92,6 +92,10 @@ Generate at least 3 solutions from the following perspectives:
 | mitigation | Measures to reduce impact | Temporary measure while waiting for root fix |
 | fundamental | Comprehensive fix including recurrence prevention | When similar problems have occurred repeatedly |
 
+**Adjacent Case Coverage**:
+- When the investigated incident is a bug or regression, or when a confirmed failure point affects a state transition, persisted state, or external boundary, evaluate cases sharing the same path, contract, persisted state, or external boundary for the same class of defect.
+- Include adjacent cases in the solution scope when they share the defect class. Record why any are excluded in `uncertaintyHandling.residualRisks`.
+
 **Generated Solution Verification**:
 - Check if project rules have applicable guidelines
 - For areas without guidelines, research current best practices via web search to verify solutions align with standard approaches
@@ -126,60 +130,7 @@ Return the JSON result as the final response. See Output Format for the schema.
 ## Output Format
 
 ```json
-{
-  "inputSummary": {
-    "identifiedFailurePoints": [
-      {"failurePointId": "FP1", "description": "Failure point description", "status": "confirmed|probable|possible"}
-    ],
-    "failurePointRelationships": [
-      {"from": "FP1", "to": "FP2", "relationship": "independent|upstream_of|downstream_of|amplifies|same_boundary"}
-    ],
-    "coverageAssessment": "sufficient|partial|insufficient"
-  },
-  "solutions": [
-    {
-      "id": "S1",
-      "name": "Solution name",
-      "type": "direct|workaround|mitigation|fundamental",
-      "description": "Detailed solution description",
-      "implementation": {
-        "approach": "Implementation approach description",
-        "affectedFiles": ["Files requiring changes"],
-        "dependencies": ["Affected dependencies"]
-      },
-      "tradeoffs": {
-        "cost": {"level": "low|medium|high", "details": "Details"},
-        "risk": {"level": "low|medium|high", "details": "Details"},
-        "scope": {"level": "low|medium|high", "details": "Details"},
-        "maintainability": {"level": "low|medium|high", "details": "Details"},
-        "certainty": {"level": "low|medium|high", "details": "Details"}
-      },
-      "pros": ["Advantages"],
-      "cons": ["Disadvantages"]
-    }
-  ],
-  "recommendation": {
-    "selectedSolutionId": "S1",
-    "rationale": "Detailed selection rationale",
-    "alternativeIfRejected": "Alternative solution ID if recommendation rejected",
-    "conditions": "Conditions under which this recommendation is appropriate"
-  },
-  "implementationPlan": {
-    "steps": [
-      {
-        "order": 1,
-        "action": "Specific action",
-        "verification": "How to verify this step",
-        "rollback": "Rollback procedure if problems occur"
-      }
-    ],
-    "criticalPoints": ["Points requiring special attention"]
-  },
-  "uncertaintyHandling": {
-    "residualRisks": ["Risks that may remain after resolution"],
-    "monitoringPlan": "Monitoring plan after resolution"
-  }
-}
+{"inputSummary":{"identifiedFailurePoints":[{"failurePointId":"FP1","description":"Failure point description","status":"confirmed|probable|possible"}],"failurePointRelationships":[{"from":"FP1","to":"FP2","relationship":"independent|upstream_of|downstream_of|amplifies|same_boundary"}],"coverageAssessment":"sufficient|partial|insufficient"},"solutions":[{"id":"S1","name":"Solution name","type":"direct|workaround|mitigation|fundamental","description":"Detailed solution description","implementation":{"approach":"Implementation approach description","affectedFiles":["Files requiring changes"],"dependencies":["Affected dependencies"]},"tradeoffs":{"cost":{"level":"low|medium|high","details":"Details"},"risk":{"level":"low|medium|high","details":"Details"},"scope":{"level":"low|medium|high","details":"Details"},"maintainability":{"level":"low|medium|high","details":"Details"},"certainty":{"level":"low|medium|high","details":"Details"}},"pros":["Advantages"],"cons":["Disadvantages"]}],"recommendation":{"selectedSolutionId":"S1","rationale":"Detailed selection rationale","alternativeIfRejected":"Alternative solution ID if recommendation rejected","conditions":"Conditions under which this recommendation is appropriate"},"implementationPlan":{"steps":[{"order":1,"action":"Specific action","verification":"How to verify this step","rollback":"Rollback procedure if problems occur"}],"criticalPoints":["Points requiring special attention"]},"uncertaintyHandling":{"residualRisks":["Risks that may remain after resolution"],"monitoringPlan":"Monitoring plan after resolution"}}
 ```
 
 ## Completion Criteria

package/.codex/agents/task-decomposer.toml

@@ -121,6 +121,7 @@ Decompose tasks based on implementation strategy patterns determined in implemen
    - Task overview
    - Target files
    - Investigation Targets
+   - Change Category when the task is a bug fix, regression, state-change, or boundary-change
    - Investigation Notes
    - Concrete implementation steps
    - Operation Verification Methods
@@ -164,6 +165,18 @@ Decompose tasks based on implementation strategy patterns determined in implemen
 9. **Propagate Proof Obligations**
    When the work plan or referenced test skeletons include Primary failure mode or Proof obligation annotations, copy the applicable obligations into each generated task that implements or verifies the claim. If no skeleton exists, derive the primary failure mode from the acceptance criterion and Verification Strategy. Each obligation must state the AC ID or claim identifier, claim, failure mode, boundary to exercise, state assertion expectation, permitted mock boundary rationale, and residual uncertainty if any.
 
+10. **Classify Change Category for Adjacent Case Sweep**
+   When a task corrects observed behavior or changes a path, contract, persisted state, or external boundary, classify it so executors and reviewers can run a scoped adjacent-case sweep from a concrete field instead of re-inferring intent.
+
+   - `bug-fix`: corrects observed incorrect behavior
+   - `regression`: restores behavior a prior change broke
+   - `state-change`: changes how state is written, transitioned, or persisted
+   - `boundary-change`: changes a published or consumed contract at an external, cross-package, or persisted boundary
+
+   A task can match more than one category. Populate the task's `Change Category` field with every matched value, comma-separated.
+
+   For every matched category, extend Investigation Targets with files sharing the same path, contract, persisted state, or external boundary as the change, including the owner module on both sides of an affected boundary. Union targets across all matched categories. Omit `Change Category` only when the task neither corrects observed behavior nor changes a path, contract, persisted state, or external boundary. Additive, config-only, and scaffolding work is not exempt when it changes one of those dimensions.
+
 ## Verification Strategy Propagation
 
 Verification Strategy defines what correctness means at design time. L1/L2/L3 (from implementation-approach) define task-level verification depth at execution time. Use both.
@@ -250,6 +263,10 @@ When the work plan includes a `Connection Map` section:
 3. For tasks on one side of a boundary, include an Operation Verification Method that observes the expected signal from the other side.
 4. Propagate only boundary rows explicitly mapped in the work plan.
 
+## Change Category Classification
+
+This is distinct from per-AC boundary-path proof. Proof obligations prove the boundary path within an acceptance criterion; Change Category drives a sweep of cases outside the task's explicit ACs that share its path, contract, persisted state, or external boundary. Use Step 10 as the single procedural source for classification and Investigation Target extension.
+
 ## Task File Template
 
 See task template in documentation-criteria skill for details.
@@ -349,6 +366,7 @@ Please execute decomposed tasks according to the order.
 - [ ] Impact scope and boundaries definition for each task
 - [ ] Appropriate granularity (1-5 files/task)
 - [ ] Investigation Targets specified for every task
+- [ ] Change Category set for bug-fix, regression, state-change, or boundary-change tasks, with adjacent path/boundary owners added to Investigation Targets
 - [ ] Quality Assurance Mechanisms propagated to relevant tasks when present in the plan header
 - [ ] ADR Bindings rows propagated to relevant tasks when present in the work plan
   - [ ] ADR source includes section hint

package/.codex/agents/task-executor-frontend.toml

@@ -156,6 +156,15 @@ When the task file, Dependencies, or Investigation Targets reference `docs/proje
 3. **Cross-check against Investigation Notes**: Ensure planned implementation is consistent with the observations recorded in the task file
 4. **Execute determination**: Determine continue/escalation per "Mandatory Judgment Criteria" above
 
+#### Adjacent Case Sweep (Required when the task file has a `Change Category` field set to one or more of `bug-fix`, `regression`, `state-change`, `boundary-change`)
+
+Run this check after Pre-implementation Verification and before the Binding Decision Check. Treat the task file's field value as authoritative for whether the sweep applies.
+
+1. From Investigation Targets, identify cases sharing the same path, contract, persisted state, or external boundary as the change, including related fallback rendering, stale state, retries, and external calls.
+2. Check each adjacent case for the same class of defect this task corrects.
+3. Fold adjacent residuals within Target Files into this task's behavior coverage and implementation.
+4. Record residuals outside Target Files in Investigation Notes so downstream review can detect them.
+
 #### Binding Decision Check (Required when the task file has a Binding Decisions section)
 
 Run this check after Pre-implementation Verification and before behavior-first implementation when the task file contains a Binding Decisions section with one or more rows.
@@ -223,29 +232,7 @@ Return one of the following as the final response (see Structured Response Speci
 Report in the following JSON format upon task completion (**without executing quality checks or commits**, delegating to quality assurance process):
 
 ```json
-{
-  "status": "completed",
-  "taskName": "[Exact name of executed task]",
-  "changeSummary": "[Specific summary of React component implementation/changes]",
-  "filesModified": ["src/components/Button/Button.tsx", "src/components/Button/index.ts"],
-  "testsAdded": ["src/components/Button/Button.test.tsx"],
-  "requiresTestReview": false,
-  "newTestsPassed": true,
-  "progressUpdated": {
-    "taskFile": "5/8 items completed",
-    "workPlan": "Relevant sections updated",
-    "designDoc": "Progress section updated or N/A"
-  },
-  "runnableCheck": {
-    "level": "L1: Unit test (React Testing Library) / L2: Integration test / L3: E2E test",
-    "executed": true,
-    "command": "test -- Button.test.tsx",
-    "result": "passed / failed / skipped",
-    "reason": "Test execution reason/verification content"
-  },
-  "readyForQualityCheck": true,
-  "nextActions": "Overall quality verification by quality assurance process"
-}
+{"status":"completed","taskName":"[Exact name of executed task]","changeSummary":"[Specific summary of React component implementation/changes]","filesModified":["src/components/Button/Button.tsx","src/components/Button/index.ts"],"testsAdded":["src/components/Button/Button.test.tsx"],"requiresTestReview":false,"newTestsPassed":true,"progressUpdated":{"taskFile":"5/8 items completed","workPlan":"Relevant sections updated","designDoc":"Progress section updated or N/A"},"runnableCheck":{"level":"L1: Unit test (React Testing Library) / L2: Integration test / L3: E2E test","executed":true,"command":"test -- Button.test.tsx","result":"passed / failed / skipped","reason":"Test execution reason/verification content"},"readyForQualityCheck":true,"nextActions":"Overall quality verification by quality assurance process"}
 ```
 
 ### 2. Escalation Response
@@ -258,139 +245,35 @@ For task/AC/UI Spec/reference core-mechanism sources, set `details.design_doc_ex
 For core-mechanism violations, put the substitute in `details.actual_situation`, the behavior change in `details.why_cannot_implement`, and the unblock condition in `recommendation`.
 
 ```json
-{
-  "status": "escalation_needed",
-  "reason": "Design Doc deviation",
-  "taskName": "[Task name being executed]",
-  "details": {
-    "design_doc_expectation": "[Exact quote from relevant Design Doc section]",
-    "actual_situation": "[Details of situation actually encountered]",
-    "why_cannot_implement": "[Technical reason why cannot implement per Design Doc]",
-    "attempted_approaches": ["List of solution methods considered for trial"]
-  },
-  "escalation_type": "design_compliance_violation",
-  "user_decision_required": true,
-  "suggested_options": [
-    "Modify Design Doc to match reality",
-    "Implement missing components first",
-    "Reconsider requirements and change implementation approach"
-  ],
-  "recommendation": "[Specific proposal for most appropriate solution direction]"
-}
+{"status":"escalation_needed","reason":"Design Doc deviation","taskName":"[Task name being executed]","details":{"design_doc_expectation":"[Exact quote from relevant Design Doc section]","actual_situation":"[Details of situation actually encountered]","why_cannot_implement":"[Technical reason why cannot implement per Design Doc]","attempted_approaches":["List of solution methods considered for trial"]},"escalation_type":"design_compliance_violation","user_decision_required":true,"suggested_options":["Modify Design Doc to match reality","Implement missing components first","Reconsider requirements and change implementation approach"],"recommendation":"[Specific proposal for most appropriate solution direction]"}
 ```
 
 #### 2-2. Similar Component Discovery Escalation
 When discovering similar components/hooks during existing code investigation, escalate in following JSON format:
 
 ```json
-{
-  "status": "escalation_needed",
-  "reason": "Similar component/hook discovered",
-  "taskName": "[Task name being executed]",
-  "similar_components": [
-    {
-      "file_path": "src/components/ExistingButton/ExistingButton.tsx",
-      "component_name": "ExistingButton",
-      "similarity_reason": "Same UI pattern, same Props structure",
-      "code_snippet": "[Excerpt of relevant component code]",
-      "technical_debt_assessment": "high/medium/low/unknown"
-    }
-  ],
-  "search_details": {
-    "keywords_used": ["component keywords", "feature keywords"],
-    "files_searched": 15,
-    "matches_found": 3
-  },
-  "escalation_type": "similar_component_found",
-  "user_decision_required": true,
-  "suggested_options": [
-    "Extend and use existing component",
-    "Refactor existing component then use",
-    "New implementation as technical debt (create ADR)",
-    "New implementation (clarify differentiation from existing)"
-  ],
-  "recommendation": "[Recommended approach based on existing component analysis]"
-}
+{"status":"escalation_needed","reason":"Similar component/hook discovered","taskName":"[Task name being executed]","similar_components":[{"file_path":"src/components/ExistingButton/ExistingButton.tsx","component_name":"ExistingButton","similarity_reason":"Same UI pattern, same Props structure","code_snippet":"[Excerpt of relevant component code]","technical_debt_assessment":"high/medium/low/unknown"}],"search_details":{"keywords_used":["component keywords","feature keywords"],"files_searched":15,"matches_found":3},"escalation_type":"similar_component_found","user_decision_required":true,"suggested_options":["Extend and use existing component","Refactor existing component then use","New implementation as technical debt (create ADR)","New implementation (clarify differentiation from existing)"],"recommendation":"[Recommended approach based on existing component analysis]"}
 ```
 
 #### 2-3. Investigation Target Not Found Escalation
 When an Investigation Target file does not exist or the path is stale, escalate in following JSON format:
 
 ```json
-{
-  "status": "escalation_needed",
-  "reason": "Investigation target not found",
-  "taskName": "[Task name being executed]",
-  "escalation_type": "investigation_target_not_found",
-  "missingTargets": [
-    {
-      "path": "[path specified in task file]",
-      "searchHint": "[section/function hint if provided, or null]",
-      "searchAttempts": ["Checked path directly", "Searched nearby files with similar names", "Reviewed task dependencies for renamed or moved files"]
-    }
-  ],
-  "user_decision_required": true,
-  "suggested_options": [
-    "Provide the correct file path",
-    "Remove this Investigation Target and proceed",
-    "Update the task file with current paths"
-  ],
-  "recommendation": "[Recommended next step based on what was found]"
-}
+{"status":"escalation_needed","reason":"Investigation target not found","taskName":"[Task name being executed]","escalation_type":"investigation_target_not_found","missingTargets":[{"path":"[path specified in task file]","searchHint":"[section/function hint if provided, or null]","searchAttempts":["Checked path directly","Searched nearby files with similar names","Reviewed task dependencies for renamed or moved files"]}],"user_decision_required":true,"suggested_options":["Provide the correct file path","Remove this Investigation Target and proceed","Update the task file with current paths"],"recommendation":"[Recommended next step based on what was found]"}
 ```
 
 #### 2-4. Dependency Version Uncertain Escalation
 When repository-wide verification is insufficient to determine the appropriate dependency version, escalate in following JSON format:
 
 ```json
-{
-  "status": "escalation_needed",
-  "reason": "Dependency version uncertain",
-  "taskName": "[Task name being executed]",
-  "escalation_type": "dependency_version_uncertain",
-  "dependency": {
-    "name": "[dependency name]",
-    "versionsFound": ["list of versions found in repository"],
-    "filesChecked": ["file paths where the dependency usage was found"],
-    "ambiguityReason": "[why repository state alone is insufficient]"
-  },
-  "user_decision_required": true,
-  "suggested_options": [
-    "Use the majority version already in the repository",
-    "Use a different version with explicit rationale",
-    "Research the latest stable version and decide after review"
-  ]
-}
+{"status":"escalation_needed","reason":"Dependency version uncertain","taskName":"[Task name being executed]","escalation_type":"dependency_version_uncertain","dependency":{"name":"[dependency name]","versionsFound":["list of versions found in repository"],"filesChecked":["file paths where the dependency usage was found"],"ambiguityReason":"[why repository state alone is insufficient]"},"user_decision_required":true,"suggested_options":["Use the majority version already in the repository","Use a different version with explicit rationale","Research the latest stable version and decide after review"]}
 ```
 
 #### 2-5. Binding Decision Violation Escalation
 When one or more Compliance Checks in the task's Binding Decisions section evaluate to `N` during pre-implementation, or to `N` or `Unknown` during completion, escalate in following JSON format:
 
 ```json
-{
-  "status": "escalation_needed",
-  "reason": "Binding decision violation",
-  "taskName": "[Task name being executed]",
-  "escalation_type": "binding_decision_violation",
-  "phase": "pre_implementation | completion_gate",
-  "implementationApproach": "[1-2 sentence summary of the planned or final implementation approach]",
-  "failures": [
-    {
-      "source": "[ADR file path with section hint, copied from Source column]",
-      "axis": "[Axis value copied from the Axis column]",
-      "decision": "[Decision text copied from Decision column]",
-      "complianceCheck": "[Compliance Check predicate copied from Compliance Check column]",
-      "evaluation": "N | Unknown",
-      "rationale": "[One line explaining why the implementation does not satisfy the check, or why it cannot be evaluated]"
-    }
-  ],
-  "user_decision_required": true,
-  "suggested_options": [
-    "Adjust the implementation plan to satisfy the binding decision",
-    "Update the ADR, then update the work plan ADR Bindings and task Binding Decisions",
-    "Provide additional context that resolves the Unknown evaluation"
-  ]
-}
+{"status":"escalation_needed","reason":"Binding decision violation","taskName":"[Task name being executed]","escalation_type":"binding_decision_violation","phase":"pre_implementation | completion_gate","implementationApproach":"[1-2 sentence summary of the planned or final implementation approach]","failures":[{"source":"[ADR file path with section hint, copied from Source column]","axis":"[Axis value copied from the Axis column]","decision":"[Decision text copied from Decision column]","complianceCheck":"[Compliance Check predicate copied from Compliance Check column]","evaluation":"N | Unknown","rationale":"[One line explaining why the implementation does not satisfy the check, or why it cannot be evaluated]"}],"user_decision_required":true,"suggested_options":["Adjust the implementation plan to satisfy the binding decision","Update the ADR, then update the work plan ADR Bindings and task Binding Decisions","Provide additional context that resolves the Unknown evaluation"]}
 ```
 
 #### 2-6. Test Environment Not Ready Escalation
@@ -398,16 +281,7 @@ When one or more Compliance Checks in the task's Binding Decisions section evalu
 Triggered when the Test Environment Check finds the project-configured test toolchain unavailable or unrunnable.
 
 ```json
-{
-  "status": "escalation_needed",
-  "reason": "Test environment not ready",
-  "taskName": "[Task name]",
-  "escalation_type": "test_environment_not_ready",
-  "missingComponent": "test runner | RTL setup | browser runtime | fixtures | mock server | setup file | other",
-  "description": "[why the missing component blocks tests]",
-  "user_decision_required": true,
-  "suggested_options": ["Install or configure the missing component, then re-run the task", "Reassign the task once the environment is ready"]
-}
+{"status":"escalation_needed","reason":"Test environment not ready","taskName":"[Task name]","escalation_type":"test_environment_not_ready","missingComponent":"test runner | RTL setup | browser runtime | fixtures | mock server | setup file | other","description":"[why the missing component blocks tests]","user_decision_required":true,"suggested_options":["Install or configure the missing component, then re-run the task","Reassign the task once the environment is ready"]}
 ```
 
 ## Scope Boundary (delegate to orchestrator)