Record classified Case protocol evidence
This commit is contained in:
parent
82ffbacd2a
commit
5b8f6812ee
@ -145,3 +145,34 @@ Forbidden next actions:
|
|||||||
- Do not mark Stage 2 validated from this run.
|
- Do not mark Stage 2 validated from this run.
|
||||||
- Do not promote Case to copied repo, sandbox repo, owned repo, or default candidate.
|
- Do not promote Case to copied repo, sandbox repo, owned repo, or default candidate.
|
||||||
- Do not write provider secrets to SOT, argv, task files, backend logs, reports, traces, or commits.
|
- Do not write provider secrets to SOT, argv, task files, backend logs, reports, traces, or commits.
|
||||||
|
|
||||||
|
## Hermes Classifier Evidence - 2026-06-01
|
||||||
|
|
||||||
|
- Hermes commit: `48d487a Classify Case agent protocol failures`.
|
||||||
|
- Hermes commit: `798fb5a Harden Case protocol failure marker`.
|
||||||
|
- `48d487a` adds a CTO Harness `AGENT_RESULT` protocol appendix to the Case task markdown.
|
||||||
|
- `48d487a` adds a fail-closed protocol marker path: `backend/provider-agent-protocol.txt`.
|
||||||
|
- `798fb5a` hardens report-time classification so missing `AGENT_RESULT` evidence is recorded even if backend marker creation is missed.
|
||||||
|
- Focused validator passed: `python3 harness/runner/validate-case-provider-adapter.py --harness-root harness --json`.
|
||||||
|
- Aggregate validator passed: `harness/evals/health.sh --json`.
|
||||||
|
- Post-merge aggregate validator passed: `harness/evals/health.sh --json`.
|
||||||
|
|
||||||
|
## Qwen Local Classified Runtime Evidence - 2026-06-01
|
||||||
|
|
||||||
|
- Run artifact directory: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T020117Z-r1-string-slugify-2566310`.
|
||||||
|
- Report status: `fail`.
|
||||||
|
- Backend: `case`.
|
||||||
|
- Backend exit code: `1`.
|
||||||
|
- Case process started: `true`.
|
||||||
|
- Case model provider: `qwen-local`.
|
||||||
|
- Case model: `qwen3.6-35b-a3b`.
|
||||||
|
- Case model admission status: `admitted`.
|
||||||
|
- Failure reason: `case agent result protocol failed`.
|
||||||
|
- Protocol marker: `backend/provider-agent-protocol.txt`.
|
||||||
|
- Changed files: none.
|
||||||
|
- Patch artifact: `patch.diff`.
|
||||||
|
- Patch digest: `e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855`.
|
||||||
|
- Tests passed: `false`.
|
||||||
|
- Required events passed: `false`.
|
||||||
|
- Result: Stage 2 is still blocked.
|
||||||
|
- Current next route remains a Case/Pi runtime protocol compatibility fix, not another admission record.
|
||||||
|
|||||||
@ -178,3 +178,17 @@ Acceptance:
|
|||||||
- Case retry classified the failure as `agent-protocol-error`.
|
- Case retry classified the failure as `agent-protocol-error`.
|
||||||
- `CTO-WORK-020` remains blocked because no real Case Stage 2 pass report exists.
|
- `CTO-WORK-020` remains blocked because no real Case Stage 2 pass report exists.
|
||||||
- Current downstream blocker remains `CTO-WORK-028`.
|
- Current downstream blocker remains `CTO-WORK-028`.
|
||||||
|
|
||||||
|
## Qwen Local Classified Runtime Evidence - 2026-06-01
|
||||||
|
|
||||||
|
- Run artifact directory: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T020117Z-r1-string-slugify-2566310`.
|
||||||
|
- Report status: `fail`.
|
||||||
|
- Backend: `case`.
|
||||||
|
- Case process started: `true`.
|
||||||
|
- Case model provider: `qwen-local`.
|
||||||
|
- Case model: `qwen3.6-35b-a3b`.
|
||||||
|
- Case model admission status: `admitted`.
|
||||||
|
- Failure reason: `case agent result protocol failed`.
|
||||||
|
- Protocol marker: `backend/provider-agent-protocol.txt`.
|
||||||
|
- `CTO-WORK-020` remains blocked because no real Case Stage 2 pass report exists.
|
||||||
|
- Current downstream blocker remains `CTO-WORK-028`.
|
||||||
|
|||||||
@ -113,6 +113,19 @@ Validation Evidence:
|
|||||||
- `CTO-WORK-016` remains blocked because no real Case Stage 2 pass report exists.
|
- `CTO-WORK-016` remains blocked because no real Case Stage 2 pass report exists.
|
||||||
- Current downstream blocker remains `CTO-WORK-028`.
|
- Current downstream blocker remains `CTO-WORK-028`.
|
||||||
|
|
||||||
|
## Classified Agent Protocol Runtime Evidence - 2026-06-01
|
||||||
|
|
||||||
|
- Real Case Stage 2 run with `/tmp/workos-case/dist/ca` and admitted `qwen-local` / `qwen3.6-35b-a3b` produced report `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T020117Z-r1-string-slugify-2566310/report.json`.
|
||||||
|
- Case process started after admission passed.
|
||||||
|
- Backend exit code was `1`.
|
||||||
|
- Failure reason was `case agent result protocol failed`.
|
||||||
|
- Protocol marker was recorded at `backend/provider-agent-protocol.txt`.
|
||||||
|
- The harness recorded no changed files.
|
||||||
|
- The patch artifact was empty.
|
||||||
|
- Tests failed because the artificial fixture bug remained unchanged.
|
||||||
|
- `CTO-WORK-016` remains blocked because no real Case Stage 2 pass report exists.
|
||||||
|
- Current downstream blocker remains `CTO-WORK-028`.
|
||||||
|
|
||||||
## CTO-WORK-018 - Case Model Provider Admission Gate
|
## CTO-WORK-018 - Case Model Provider Admission Gate
|
||||||
|
|
||||||
Status: validated.
|
Status: validated.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user