Mark CTO Case task adapter route validated

WORKBOARD.yaml

@@ -8,53 +8,53 @@ items:
     title: CTO Case Candidate Backend PRD
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-CANDIDATE-BACKEND-PRD.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-003
     title: Planning Validator Coverage
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-CANDIDATE-BACKEND-ISSUES.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-004
     title: Harness Evidence Interface Contract
     status: validated
     source: sot/03-PROTOCOLS/CTO-HARNESS-EVIDENCE-INTERFACE-CONTRACT.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-005
     title: Case Source Admission Record
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-SOURCE-ADMISSION-RECORD.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-006
     title: Case Adapter Contract And Eligibility Decision
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-ADAPTER-CONTRACT.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-007
     title: Case Failure Fixture Matrix
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-FAILURE-FIXTURE-MATRIX.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-008
     title: Staged Proof Gate Records
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-STAGED-PROOF-GATES.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-009
     title: Stage 1 Gated Case Engine PRD
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-STAGE1-GATED-ENGINE-PRD.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-010
     title: Stage 1 Harness Implementation Route
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-STAGE1-GATED-ENGINE-ISSUES.md
-    owner: ""
+    owner: jp
 
   - id: CTO-WORK-011
     title: Stage 2 Artificial Fixture PRD
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-STAGE2-ARTIFICIAL-FIXTURE-PRD.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-012
     title: Stage 2 Harness Artificial Fixture Route
     status: blocked
@@ -64,9 +64,9 @@ items:
     title: Case Provider Admission PRD
     status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-PROVIDER-ADMISSION-PRD.md
-    owner: ""
+    owner: jp
   - id: CTO-WORK-014
     title: Hermes Case CLI Task Adapter Route
-    status: candidate
+    status: validated
     source: sot/03-PROTOCOLS/CTO-CASE-PROVIDER-ADMISSION-ISSUES.md
     owner: jp

sot/03-PROTOCOLS/CTO-CASE-PROVIDER-ADMISSION-ISSUES.md

@@ -30,7 +30,7 @@ Acceptance:
 
 ## CTO-WORK-014 - Hermes Case CLI Task Adapter Route
 
-Status: candidate.
+Status: validated.
 
 Implement the smallest Hermes CTO harness change that converts the Stage 2 artificial fixture contract into a Case task file and invokes the admitted Case provider with the correct command shape.
 
@@ -43,3 +43,11 @@ Acceptance:
 - The Stage 2 pass report is produced only by real Case execution.
 - Provider-unavailable fail-closed behavior remains tested.
 - No Target Repository path is inspected or copied.
+
+## Validation Evidence - 2026-05-31
+
+- Hermes commit: `5d04515 Add Stage 2 Case task adapter contract`.
+- Adapter writes Case task state for the copied artificial fixture and invokes `ca run --task <task-file> --mode unattended`.
+- `validate-case-provider-adapter.py` passed with a local test double for command shape and task contract.
+- `harness/evals/health.sh --json` passed after merge and includes `case_provider_adapter.passed: true`.
+- `validate-case-stage2.py` remains blocked without an admitted real Case provider; this is expected and preserves fail-closed behavior.

tools/validate_cto_child.py

@@ -486,7 +486,7 @@ def main() -> int:
             "CTO-WORK-011": "validated",
             "CTO-WORK-012": "blocked",
             "CTO-WORK-013": "validated",
-            "CTO-WORK-014": "candidate",
+            "CTO-WORK-014": "validated",
         }
         for issue_id, expected in expected_statuses.items():
             checked.append(f"workboard_status:{issue_id}:{expected}")