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

Record Spark vLLM Case evidence

Browse Source
This commit is contained in:
Svrnty 2026-05-31 22:26:39 -04:00
parent 66c0244a9a
commit 99b5353e51
3 changed files with 63 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -210,3 +210,27 @@ Forbidden next actions:
- 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.
## Spark vLLM Qwen Loop Evidence - 2026-06-01
- Spark1 exposed a reachable OpenAI-compatible vLLM model route for `qwen3.6-35b-a3b`.
- The endpoint value was supplied only at runtime and is not recorded in SOT.
- Standard command class: `harness/evals/case-qwen-loop.sh --json`.
- Run artifact directory: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T022535Z-r1-string-slugify-2731603`.
- 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`.
- Source admission status: `not_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 is a Case/Pi result-envelope compatibility fix outside vendor Case source.

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

@ -175,3 +175,17 @@ Validation Evidence:
- 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.
## Spark vLLM Runtime Evidence - 2026-06-01
- Runtime supplied a Spark OpenAI-compatible vLLM endpoint without recording the endpoint value in SOT.
- 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/20260601T022535Z-r1-string-slugify-2731603/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`.

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

@ -38,14 +38,37 @@ Acceptance:
Blocked by:
- Spark endpoint availability.
- Runtime-safe way to provide `CTO_HARNESS_CASE_LOCAL_BASE_URL` without recording secret values.
- Real Case Stage 2 pass evidence.
- Case agent-result protocol compatibility.
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`.
## Spark vLLM Runtime Evidence - 2026-06-01
- Spark1 was reachable over Tailscale and SSH.
- A vLLM Docker container exposed an OpenAI-compatible model route for `qwen3.6-35b-a3b`.
- The Spark endpoint value was supplied only through runtime environment and is not recorded in this SOT.
- The standard command class was `harness/evals/case-qwen-loop.sh --json`.
- Run artifact directory: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T022535Z-r1-string-slugify-2731603`.
- 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`.
- Source admission status: `not_admitted`.
- Failure reason: `case agent result protocol failed`.
- The harness recorded no changed files.
- The patch artifact was empty.
- Tests failed because the artificial fixture bug remained unchanged.
- This proves the Spark endpoint blocker was crossed for one runtime attempt.
- This does not validate `CTO-WORK-016`, `CTO-WORK-020`, `CTO-WORK-022`, or `CTO-WORK-028`.
- Current active blocker is the Case agent-result protocol seam.
## Hermes Case Qwen Loop Evidence - 2026-06-01
- Hermes commit: `6c453ee Add Case Qwen loop entrypoint`.