Record Case provider timeout evidence
This commit is contained in:
@@ -47,3 +47,34 @@ Acceptance:
|
||||
Blocked by:
|
||||
|
||||
- Missing local `bun` executable, unless a prebuilt admitted `dist/ca` is supplied.
|
||||
|
||||
## Provider Build Evidence - 2026-05-31
|
||||
|
||||
- Reversible Bun bootstrap succeeded under `/tmp/cto-bun`; no global Bun install was required.
|
||||
- `/tmp/workos-case` source pin remained `7959ac917cdeb0983b4aaa20bb9f42021747fed8`.
|
||||
- `bun run build:binary` produced `/tmp/workos-case/dist/ca`.
|
||||
- Built binary digest: `9811f870af2f85616e359d42ba70566c9af08ca20d8660456929a56ec761513f`.
|
||||
- `/tmp/workos-case/dist/ca --help` identified the executable as Case `ca`.
|
||||
- `/tmp/workos-case` remains discovery/build evidence only because build modified `src/generated/package-assets.ts`.
|
||||
- Real Stage 2 run with `CTO_HARNESS_CASE_BIN=/tmp/workos-case/dist/ca` hung and was terminated. It created artifact directory `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260531T233721Z-r1-string-slugify-1814067` without `report.json`.
|
||||
- `CTO-WORK-016` remains blocked because no real Case Stage 2 pass report exists.
|
||||
|
||||
## CTO-WORK-017 - Case Provider Timeout Fail-Closed Route
|
||||
|
||||
Status: validated.
|
||||
|
||||
Harden the Hermes CTO Case adapter so a hung real Case provider fails closed with normal evidence instead of leaving an orphan artifact directory without `report.json`.
|
||||
|
||||
Acceptance:
|
||||
|
||||
- Case provider execution is bounded by `CTO_HARNESS_CASE_TIMEOUT_SECONDS`.
|
||||
- Timeout writes `backend/provider-timeout.txt`.
|
||||
- Timeout still emits `report.json` through the Harness Evidence Interface.
|
||||
- `validate-case-provider-adapter.py` checks a sleeping provider path.
|
||||
- `harness/evals/health.sh --json` passes after merge and includes `provider_timeout_fail_closed`.
|
||||
- This does not mark real Case Stage 2 as passed.
|
||||
|
||||
Validation Evidence:
|
||||
|
||||
- Hermes commit: `d23c492 Fail closed on Case provider timeout`.
|
||||
- Post-merge `harness/evals/health.sh --json` passed.
|
||||
|
||||
@@ -71,3 +71,14 @@ Create a governed provider build and admission route that can produce or accept
|
||||
## Success Definition
|
||||
|
||||
Stage 2 moves from provider-unavailable blocked status to a real Case pass report while preserving the same harness evidence shape, allowed-write control, artifact digests, no-target-inspection proof, and fail-closed behavior.
|
||||
|
||||
## Current Provider Evidence Addendum - 2026-05-31
|
||||
|
||||
- Built binary digest observed: `9811f870af2f85616e359d42ba70566c9af08ca20d8660456929a56ec761513f`.
|
||||
- Hung real-provider artifact directory: `20260531T233721Z-r1-string-slugify-1814067`.
|
||||
- `CTO-WORK-016` remains blocked because no real Case Stage 2 pass report exists.
|
||||
- `CTO-WORK-017 - Case Provider Timeout Fail-Closed Route` records the harness hardening response.
|
||||
- Timeout control: `CTO_HARNESS_CASE_TIMEOUT_SECONDS`.
|
||||
- Timeout marker: `backend/provider-timeout.txt`.
|
||||
- Timeout validator check: `provider_timeout_fail_closed`.
|
||||
- Hermes evidence commit: `d23c492 Fail closed on Case provider timeout`.
|
||||
|
||||
Reference in New Issue
Block a user