OBSERVED DIAGNOSTIC AND SYNTHETIC TESTS · SEPARATE SCOPES
WAIT_AUTH vs WAIT_RESOURCE: Two Different Recovery Paths
A long-scroll visual companion to the article. It summarizes the article’s evidence boundary and method; it does not extend the underlying result.
At a glance
Evidence in scope
- Auth and resource waits are distinct states
- Synthetic tests do not establish live recovery
- Human auth minutes remain unknown
Evidence boundary: Redacted auth diagnostics, synthetic harness runs, and current account provider state are not one joined event series.
How to use the diagram
Persist a safe checkpoint; route to the correct handler; never store credentials in a public job record; reconcile before resuming.
What this visual explains: A resource wait and an authentication wait have different causes and should not be collapsed into one retry policy.
What it does not establish
No plan-change causality, live accepted-resume result, or human-time measurement.