Problem
Public verification endpoints and docs can regress silently (host renames, auth changes, empty exports). The published claims should be enforced by CI, not by outside readers.
Scope
- Scheduled workflow (nightly) that runs the one-command verifier (sibling sub-issue) against production, with no repo credentials — an anonymous outsider's view
- On failure: opens or updates a single tracking issue with the failing step and response excerpts; notifies via the existing alerting path (PagerDuty)
- On recovery: closes the tracking issue automatically
- Badge or status line on the docs walkthrough page reflecting the last green run timestamp
Acceptance
A deliberately broken staging config (e.g., auth on the corpus export) turns the job red within one cycle and produces an actionable issue; restoring it goes green and closes it.
Problem
Public verification endpoints and docs can regress silently (host renames, auth changes, empty exports). The published claims should be enforced by CI, not by outside readers.
Scope
Acceptance
A deliberately broken staging config (e.g., auth on the corpus export) turns the job red within one cycle and produces an actionable issue; restoring it goes green and closes it.