hermes/cto
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record Case Qwen loop evidence

Browse Source
This commit is contained in:
Svrnty 2026-05-31 22:21:47 -04:00
parent 6762403d51
commit 66c0244a9a
3 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.sot/03-PROTOCOLS/CTO-CASE-AGENT-PROTOCOL-BLOCKER.md
View File

@ -204,3 +204,9 @@ Forbidden next actions:
- `CTO-WORK-030` must be resolved before another configured Qwen local run can retest the Case `AGENT_RESULT` protocol path.
- Until `CTO_HARNESS_CASE_LOCAL_BASE_URL` is supplied, the harness blocks before Case starts.
- The agent protocol blocker remains unproven for the isolated Spark endpoint path until Case reaches execution again and returns or fails the required result envelope.
## Case Qwen Loop Entrypoint Evidence - 2026-06-01
- Hermes commit: `6c453ee Add Case Qwen loop entrypoint`.
- The new `harness/evals/case-qwen-loop.sh --json` command is the next standard path for retesting the Case `AGENT_RESULT` protocol after Spark endpoint config is supplied.
- This does not resolve the protocol blocker because Case has not reached execution through the configured isolated Spark endpoint path yet.

8
.sot/03-PROTOCOLS/CTO-CASE-PROVIDER-BUILD-ISSUES.md
View File

@ -167,3 +167,11 @@ Validation Evidence:
- The Hermes harness requires `CTO_HARNESS_CASE_LOCAL_BASE_URL` before local Case provider execution can start.
- Missing endpoint config blocks before `case_process_started` and writes `backend/provider-local-config-unavailable.txt`.
- `CTO-WORK-016` remains blocked until real Case Stage 2 pass evidence exists through the Harness Evidence Interface.
## Case Qwen Loop Entrypoint Evidence - 2026-06-01
- Hermes commit: `6c453ee Add Case Qwen loop entrypoint`.
- New command: `harness/evals/case-qwen-loop.sh --json`.
- The command gives the selected Qwen local path a standard Case harness entrypoint.
- It does not remove the `CTO_HARNESS_CASE_LOCAL_BASE_URL` blocker.
- `CTO-WORK-016` remains blocked until real Case Stage 2 pass evidence exists.

16
.sot/03-PROTOCOLS/CTO-CASE-SPARK-ENDPOINT-CONFIG-ISSUES.md
View File

@ -45,3 +45,19 @@ Current evidence:
- Non-secret readiness check on 2026-06-01 showed `CTO_HARNESS_CASE_LOCAL_BASE_URL=missing`.
- Existing Hermes harness blocks missing local provider config before `case_process_started`.
## Hermes Case Qwen Loop Evidence - 2026-06-01
- Hermes commit: `6c453ee Add Case Qwen loop entrypoint`.
- New command: `harness/evals/case-qwen-loop.sh --json`.
- The command sets fixed non-secret Case/Qwen routing knobs for `qwen-local` / `qwen3.6-35b-a3b`.
- The command requires `CTO_HARNESS_CASE_BIN` and `CTO_HARNESS_CASE_MODEL_ADMISSION_FILE` from the caller.
- The command delegates to `run-case.sh --engine case` so runtime artifacts keep the Harness Evidence Interface shape.
- The command must not print `CTO_HARNESS_CASE_LOCAL_BASE_URL`.
- Focused validator passed: `python3 harness/runner/validate-case-provider-adapter.py --harness-root harness --json`.
- Focused validator artifact: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T022022Z-r1-string-slugify-2694767`.
- Pre-merge aggregate validator passed: `harness/evals/health.sh --json`.
- Pre-merge aggregate validator artifact: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T022036Z-r1-string-slugify-2695716`.
- Post-merge aggregate validator passed: `harness/evals/health.sh --json`.
- Post-merge aggregate validator artifact: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T022100Z-r1-string-slugify-2697229`.
- `CTO-WORK-030` remains blocked until `CTO_HARNESS_CASE_LOCAL_BASE_URL` is supplied at runtime and a real Stage 2 pass report exists.