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

Record isolated Pi config gate evidence

Browse Source
This commit is contained in:
Svrnty 2026-05-31 22:09:44 -04:00
parent 5b8f6812ee
commit ebcb2c96f1
3 changed files with 48 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -176,3 +176,25 @@ Forbidden next actions:
- 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.
## Isolated Pi Config Evidence - 2026-06-01
- Hermes commit: `09b5851 Isolate Case Pi provider config`.
- The Hermes CTO Case harness now sets `PI_CODING_AGENT_DIR` under the run artifact directory before invoking Case.
- The harness writes isolated Pi auth state under `backend/case-data/pi-agent/auth.json`.
- Local Case providers now require explicit `CTO_HARNESS_CASE_LOCAL_BASE_URL`.
- Missing local provider config writes `backend/provider-local-config-unavailable.txt`.
- Missing local provider config blocks before `case_process_started`.
- 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/20260601T020732Z-r1-string-slugify-2609546`.
- Aggregate validator passed before merge: `harness/evals/health.sh --json`.
- Aggregate validator artifact before merge: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T020741Z-r1-string-slugify-2611203`.
- Post-merge aggregate validator passed: `harness/evals/health.sh --json`.
- Post-merge aggregate validator artifact: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T020801Z-r1-string-slugify-2613843`.
- Real Qwen local config-gate proof artifact: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T020847Z-r1-string-slugify-2619644`.
- Real Qwen local config-gate status: `blocked`.
- Real Qwen local config-gate failure reason: `provider unavailable`.
- Real Qwen local config-gate Case process started: `false`.
- This removes the ambient `~/.pi/agent` dependency from the harness path.
- This does not prove Case can produce the required `AGENT_RESULT` envelope.
- `CTO-WORK-028` remains blocked until a configured local provider or another admitted provider returns a valid result envelope and produces a Stage 2 artificial fixture diff.

12
.sot/03-PROTOCOLS/CTO-CASE-MODEL-PROVIDER-ADMISSION-ISSUES.md
View File

@ -192,3 +192,15 @@ Acceptance:
- 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`.
## Qwen Local Isolated Pi Config Gate Evidence - 2026-06-01
- Hermes commit: `09b5851 Isolate Case Pi provider config`.
- The admission file remained valid for `qwen-local` / `qwen3.6-35b-a3b`.
- Real Qwen local config-gate proof artifact: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T020847Z-r1-string-slugify-2619644`.
- Report status was `blocked`.
- Case model admission status was `admitted`.
- Case process started was `false`.
- The block reason was missing explicit local provider config, not missing model admission.
- The required unblock variable is `CTO_HARNESS_CASE_LOCAL_BASE_URL`.
- `CTO-WORK-020` remains blocked because no real Case Stage 2 pass report exists.

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

@ -126,6 +126,20 @@ Validation Evidence:
- `CTO-WORK-016` remains blocked because no real Case Stage 2 pass report exists.
- Current downstream blocker remains `CTO-WORK-028`.
## Isolated Pi Config Runtime Evidence - 2026-06-01
- Hermes commit: `09b5851 Isolate Case Pi provider config`.
- The Case harness now sets an isolated `PI_CODING_AGENT_DIR` for the Case process.
- The Case harness no longer relies on ambient `~/.pi/agent` model/auth state for local provider routing.
- Local providers require explicit `CTO_HARNESS_CASE_LOCAL_BASE_URL`.
- Missing local provider config writes `backend/provider-local-config-unavailable.txt`.
- Real Qwen local config-gate proof artifact: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T020847Z-r1-string-slugify-2619644`.
- Report status was `blocked`.
- Failure reason was `provider unavailable`.
- Case process started was `false`.
- `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
Status: validated.