docs: record medium qualification retest
This commit is contained in:
@@ -4,7 +4,7 @@
|
||||
|
||||
- `CURRENT_PRODUCTION_REVISION = 64642f4baed28f9051efe6a269769c5838b547e4`; public `/healthz` is healthy.
|
||||
- `FAST_PROVIDER_STATUS = LIVE_SMOKE_SUPPORTED`: local CPU gateway authentication is configured through a protected file reference; four bounded local-only advisory cases completed through cognitive-worker. Evidence: `docs/evidence/wp-601-fast-gateway-live-smoke-2026-08-22-v1.json`.
|
||||
- `MEDIUM_PROVIDER_STATUS = LIVE_AVAILABLE_UNQUALIFIED`; existing llm-local Qwen3.6-27B CPU runtime is reachable through the explicit external Docker network, but the bounded production qualification timed out on all four cases. Evidence: `docs/evidence/wp-200-medium-qualification-2026-08-22.json`; no activation was attempted.
|
||||
- `MEDIUM_PROVIDER_STATUS = LIVE_AVAILABLE_UNQUALIFIED`; after the adapter deadline was extended, qualification still timed out on all four cases at the full 45-second case deadline. Evidence: `docs/evidence/wp-200-medium-qualification-2026-08-22-v2.json`; no activation was attempted.
|
||||
- `HEAVY_PROVIDER_STATUS = UNAVAILABLE`; GPU endpoint `192.168.220.91:11434` timed out during live discovery.
|
||||
- `AGENT_EXECUTION_STATUS = RECOVERY_ONLY`; optional `AGENT_EXECUTION_BRIDGE_URL` is wired into production compose but remains unset, and no Codex/bridge runtime is deployed. Durable recovery and status endpoints remain active.
|
||||
- `FLEET_EXECUTION_EVIDENCE = docs/evidence/wp-200-wp-301-fleet-execution-status-2026-08-22-v3.json`; FAST, MEDIUM and LIFEBOAT are catalog/readiness-ready, Heavy is unavailable by timeout, and current selection is MEDIUM for preferred HEAVY; MEDIUM remains unqualified after `DEV-000174`.
|
||||
|
||||
Reference in New Issue
Block a user