Description
The console derives AuthOK from cumulative API 401/403 counters. Once any endpoint has failed, the Auth badge says failing for the rest of the process even after access recovers; before any requests it says ok. The request total is also labelled last scrape although the value is cumulative. The source has no current-auth observation to support either live verdict.
Acceptance Criteria
- #1 Initial render and polling updates describe observed lifetime auth-error history without claiming current auth success or failure
- #2 API request count and duration labels state their process-lifetime scope and the underlying counters are preserved
Definition of Done
- #1 just check
- #2 just gen (if any generated artifact changed) and the diff committed
Implementation Plan
Add a failing rendered-output regression for no recorded errors and historical errors; change the card labels and both server/client badge text to historical wording, preserving the JSON fields and counts. Document AuthOK as compatibility history semantics. Verify rendered HTML and integrated tests; no new live-health inference.
Implementation Notes
Both rendered history cases failed before wording repair and passed afterward. Server and polling update use none recorded/errors recorded; counters and AuthOK JSON compatibility preserved. Rendered HTML verified; no browser layout exercise or live-auth claim.
Final Summary
Landed in d2549a5dd314f40bdfaf6ad56f056dcde4821e0a. Targeted evidence recorded above; full just check passed (exit 0), terminal: Your code is affected by 0 vulnerabilities. No generated artifacts changed, so just gen not applicable. Source-only CodeRabbit completed review_completed across 13 files, findings=1; one pass. The sole minor finding concerned the intentionally reversed backup test-server branch and was retained with the regression rationale recorded on OPN-0086. No critical or major findings.