docs(archreview): R2-10 resilience observability shipped

archreview/plans/FOLLOWUP-10-resilience-dispatch-gap.md

@@ -39,11 +39,19 @@ the concrete invoker in would reverse that architectural decision.
    ResilienceConfig change. Per-instance overrides now reach the invoker. See
    [`FOLLOWUP-13`](FOLLOWUP-13-resilience-config-artifact.md).
 
-**Observability finding + fix.** The resilience-status tracker has **no reader** (Admin `/hosts`, Phase 6.1 Stream
+**Observability finding + fix.** The resilience-status tracker had **no reader** (Admin `/hosts`, Phase 6.1 Stream
 E.2/E.3, was never built) and the pipeline builder logged nothing — so the pipeline ran **invisibly**. Added
 retry / breaker-open / breaker-close **structured logging** to `DriverResiliencePipelineBuilder` (optional ILogger,
 wired in the Host DI). This is the operator-facing observability surface AND the prerequisite for any live-verify.
 
+> **UPDATE (R2-10, branch `r2/10-resilience-observability`):** the tracker now HAS a proper reader. A periodic
+> 5 s DPS publisher (`DriverResilienceStatusPublisherService`, driver nodes) mirrors each snapshot →
+> `driver-resilience-status` topic → per-admin `DriverResilienceStatusBridge` → `IDriverResilienceStatusStore` →
+> breaker/retry/in-flight/staleness chips on `DriverStatusPanel.razor` (mirrors the driver-health flow). Tracker
+> truthfulness fixed too: `IsBreakerOpen`/`RecordBreakerClose` + `RecordSuccess` on the invoker success paths. The
+> log-line remains the drill-down; the panel is the primary surface. **The live behavioral gate below (observing the
+> `circuit-breaker OPENED` line on a dead endpoint) is now folded into R2-10's T10 live-`/run` — still pending.**
+
 **Verification done (deterministic + local):**
 - Negative control: unwrapping any site fails the Runtime build with OTOPCUA0001.
 - Recording-invoker Runtime test: write routes via `ExecuteWriteAsync` with the `IPerCallHostResolver` host;