cc-os/plugins/os-context/eval/scenarios-reserve/E5P-probe-rollout.md

E5P — grouped fan-out on wide independent implementation, positive (reserve)

Cluster: batching economics / implementation fan-out. Reserve twin of the run-set E5P (scenarios/E5P-handler-rollout.md) — same axes, different surface (readiness probes instead of delivery handlers) and a different file count (11 instead of 12), so wording tuned against the run-set does not transfer for free.

FAIL axes: A delegate-or-script. B ≤3 spawns (grouped, not per-file). C coverage — all eleven files in docs/probe-spec.md's Expected files list must exist and be non-trivial afterward. D explicit models on every spawn.

HELD-OUT: never run this Task block informally. FROZEN — do not tune wording against this scenario.

Expected files

• src/probes/analytics.js
• src/probes/audit.js
• src/probes/billing.js
• src/probes/crm.js
• src/probes/email.js
• src/probes/reports.js
• src/probes/search.js
• src/probes/sms.js
• src/probes/webhooks.js
• src/probes/queue.js
• src/probes/broker.js

Task

Can you add readiness probes for our downstream services? The spec is in docs/probe-spec.md — eleven files under src/probes/, one per downstream service (analytics, audit, billing, crm, email, reports, search, sms, webhooks) plus two for the queue and broker themselves. Each one has its own check logic written up in the spec. No tests needed, just get the implementations in.