ClaraWideProvider dispatch safety QA
v0.12.33 · PROVIDER DISPATCH SAFETY

Prove the failure behavior before Clara is allowed to send anything for real.

A sealed provider intent now feeds a separate dispatch state machine. QA can deterministically exercise accepted delivery, redirect escape, throttling, 5xx outages, timeout/network faults, permanent rejection and retry exhaustion without exposing credentials or making an external provider request.

SCHEMA + ATTACK PATHS

Automated dispatch checks

Confirms schema v32, terminal-state guards, manual redirect blocking, bounded Retry-After/backoff, timeout classification, dead-letter exhaustion, immutable attempt/event evidence and live-network lockout.

NOT RUNSchema check has not run yet.
NOT RUNSelf-test has not run yet.
VISIBLE FAILURE FLOW

One intent → one bounded transport lifecycle

Each scenario creates isolated QA evidence. Security blocks are labeled clearly; successful failure-handling appears as a green pass.

READYStart with a QA Dispatch Admin session.
QA policyLoad dispatch state to inspect the active bounded retry / timeout policy.
DISPATCH JOBS

Transport state

No QA dispatch jobs loaded yet.

Immutable attempts

No dispatch attempts loaded yet.

IMMUTABLE EVIDENCE

Dispatch history

No dispatch events loaded yet.

PRODUCTION GATE — DO NOT FAKE

Real provider-dispatch evidence

These remain open until a real provider, secret-store credential and provider-specific adapter are intentionally connected and exercised. This QA page cannot enable production traffic.

Recent dispatch QA runs

No QA runs recorded yet.

Evidence tools

Clearing browser evidence does not rewrite server-owned dispatch jobs, attempts, or events.