zyycnandClaude Opus 5 237ba96233 feat(core,store): record account probe failures as ops events ...

Connection tests run through a transient execution store, so a failed probe
left no trace at all: nothing in model_requests, nothing in ops_events, and
nothing in the log at info level. The reason a probe failed — upstream status,
provider error code, send state — was only reachable by reproducing it.

Add a ProbeFailure port on ExecutionStore, defaulting to a no-op so existing
implementations are unaffected, and have the execution service report probe
failures to the persistent store while the probe itself keeps using the
transient one. The Postgres store logs a warning and appends an ops event with
no model_request_id.

Such events already fit the surrounding contracts: the ops error list left
joins model_requests, health metrics inner join it so probes stay out of
business failure rates, and retention already targets rows with a null
model_request_id.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-07-26 22:44:25 +08:00

..

src

feat(core,store): record account probe failures as ops events

2026-07-26 22:44:25 +08:00

tests

perf(store): index retention deletes, parallelize dashboard, expose pool budget

2026-07-26 20:28:52 +08:00

Cargo.toml

refactor(gateway): finalize provider-level account architecture

2026-07-25 00:33:12 +08:00