docs(plans): bookkeeping sync — reconcile stale trackers with merged code

A verified audit of all ~90 plan documents (2026-08-01) found ~30 .tasks.json
trackers and several plan headers still reporting 'pending'/'draft' for work
fully merged to main. Sync them so future audits don't re-litigate closed work:

- Flip ~380 stale task statuses to completed across March/May/June/July
  trackers (audit-log series, milestones M5-M10, playwright waves, stillpending,
  LocalDb, ClusterClient->gRPC DoD rows, and more), each verified against
  code/git evidence before flipping.
- Annotate obsolete-not-done rows: ClusterClient CLI transport (never built,
  HTTP shipped), TreeView Areas/Instances pages (replaced by Topology),
  template-tree drag-drop (dropped for M9 menu reorder), otopcua item C
  (premise superseded by #17).
- Flip stale headers: aggregated-live-alarm + kpi-rollups 'Draft not executed'
  -> Delivered 2026-07-10; otopcua cutover-scope SCOPING -> DECIDED;
  scadabridge-rename -> Implemented; LocalDb phase1/2 status strings ->
  merged 28ca04d7.
- Fix doc drift: T9/T10 'deferred' -> shipped as SMS (Teams dropped); waitfor
  sandbox follow-up shipped; followups #52/#53/#54/#162/#207 resolved; purge
  TODO closed by PendingDeploymentPurgeActor; live-gate pre-existing failures
  #28/#29/#31 fixed; auto-down boot-alone residual superseded by self-first
  seeds; supersession banners on keep-oldest SBR + ClusterClient-era designs;
  requirements-traceability 'Pending' clarified as frozen plan-generation
  status.

Deliberately left pending (genuinely open, tracked in the pending-work list):
opcua-tag-browser task 19 (live smoke), ipsen tasks 7-8 (vd03 verification),
selfform task 7 (vd03 overlay, user-held), live-gate observation 1
(external-system delete orphan bug), otopcua item A + maxDepth calibration.

docs/plans/2026-05-23-inbound-api-full-response-audit-design.md

@@ -132,17 +132,17 @@ same "options validation" path used for other AuditLog settings.
 
 ## Acceptance Criteria
 
-- [ ] `AuditLog:InboundMaxBytes` option exists on the AuditLog options class,
+- [x] `AuditLog:InboundMaxBytes` option exists on the AuditLog options class,
       with the documented default and bounds, validated at startup.
-- [ ] Inbound request middleware writes `RequestSummary` and `ResponseSummary`
+- [x] Inbound request middleware writes `RequestSummary` and `ResponseSummary`
       using the inbound ceiling instead of the 8 KB / 64 KB defaults.
-- [ ] Other channels' rows (e.g. an `ApiOutbound.ApiCall` over the limit) still
+- [x] Other channels' rows (e.g. an `ApiOutbound.ApiCall` over the limit) still
       truncate at 8 KB (64 KB on error rows) — regression-tested.
-- [ ] `PayloadTruncated = 1` on an inbound row iff request body or response
+- [x] `PayloadTruncated = 1` on an inbound row iff request body or response
       body exceeded `InboundMaxBytes`.
-- [ ] Header redaction list and per-target body redactors still apply to
+- [x] Header redaction list and per-target body redactors still apply to
       inbound rows.
-- [ ] Redactor failure on an inbound row still produces `<redacted: redactor
+- [x] Redactor failure on an inbound row still produces `<redacted: redactor
       error>` and increments `AuditRedactionFailure`.
-- [ ] `Component-AuditLog.md` and `Component-InboundAPI.md` updated as
+- [x] `Component-AuditLog.md` and `Component-InboundAPI.md` updated as
       described in **Doc Edits**.