docs(plans): close residual #8 (R6 merged); register rows 43-46 (import-session leak, dead rate limiter, outbox DbContext sharing, CLI audit-config query)

docs/plans/2026-08-15-arch-review-remediation-execution-log.md

@@ -158,8 +158,19 @@ Deliberately not fixed in this program — each has a stated reason, not an over
    design: `docs/plans/2026-08-15-target-scale-load-test-design.md`; harness:
    `tests/ZB.MOM.WW.ScadaBridge.LoadHarness/`. Residual: WP-4's `[xc-3]`/`[xc-4]`/`[xc-5]`/`[xc-8]`
    are central-cluster/browser concerns outside this harness and remain open scope.
-8. **Playwright 14 pre-existing env failures.** Present on `main` too, rig-state related, not
-   introduced by this branch.
+8. ~~**Playwright 14 pre-existing env failures.**~~ **RESOLVED 2026-08-15 (`014038fb`, R6).**
+   All 14 triaged to root cause: every one was **selector drift** from two merged Central UI
+   refactors (`9e243493` density sweep moved `.btn-sm` off buttons onto `btn-group-sm` groups and
+   re-cast SiteForm node sections as cards; `a506b19d` moved TemplateEdit modals to the global
+   DialogService host) — no stale rig data, no timing bug, no app defect among the 14. Suite now
+   **0 failed / 172 passed / 1 honestly-skipped** (SmtpEdit test self-skips: SMTP config rows
+   cannot be created or deleted from the management surface, UI-only). Runtime halved (10m → 4.5m
+   — each failure had been burning a 30 s locator timeout). All 49 `.btn-sm` selectors audited
+   individually rather than swept; the 35 still-correct ones left alone with comments. One stray
+   test area deleted from the rig via CLI. Three genuine app bugs found live during triage —
+   recorded as register rows 43–45 (import-session slot leak, dead unlock rate limiter, shared
+   DbContext in outbox dispatch), plus a CLI query oddity as row 46 — found, not fixed, per the
+   program's scope rules.
 9. ~~**`site_events` retention purge still oplog-visible.**~~ **RESOLVED 2026-08-15 (documented
    by design, `9d2834e3`, R7).** The CDC capture of retention/cap deletes is correct and unchanged
    — there is deliberately no purge-exemption path. The operator-facing gap is closed three ways: