Know whether developers can trust the current scan.
This center joins memory health, agent run envelopes, detection coverage, route gaps, diagnostics, and next actions into one operational decision.
Readiness Decision
The short version: whether this scan can support developer work, what blocks trust, and what gate must pass before publish.
Collecting reliability evidence.
The readiness center is waiting on memory, agent, and detection contracts.
Must be resolved before trust claims.
Need review notes before handoff.
Scan Context
Use latest for normal product-health review, or choose a specific saved scan before making report or benchmark claims.
Ship-Readiness Checks
A compact checklist for deciding whether this scan is safe to use as product evidence.
Readiness Command Runbook
Copy-ready gates for backend contracts, frontend regressions, and the final publish check.
scripts/product-health.sh ci-parityscripts/product-health.sh contractsnpm --prefix jedi-frontend run test:unitnpm --prefix jedi-frontend run buildAgent Run Ledger
Per-agent decisions, run envelope status, evidence counts, and queued next actions.
The selected scan has no attached agent decision rows yet.
Detection Route Gaps
Discovered routes that still need detector candidates before the scan can be treated as broadly covered.
The detection coverage ledger did not report untested route pressure for this scan.
Memory Health
Collection posture, governance backlog, and whether learned guidance is safe to rely on.
Memory health is available, but no per-collection posture rows were attached.
Next Developer Actions
Concrete follow-up items produced by the joined reliability endpoint.
The selected scan has no queued developer reliability actions.
Diagnostics And Contract Links
Use diagnostics to decide what blocks trust, then jump to the public reliability contracts when deeper inspection is needed.
No joined reliability diagnostics are attached to this scan context.
The reliability endpoint did not attach public API links for this context.