docs(audit): fix canonical record field count (10 not 8) + drop BCL-only overstatement (review fixes)

components/audit/current-state/scadabridge/CURRENT-STATE.md

@@ -19,7 +19,7 @@ replace* — mostly naming alignment; the enormous transport/storage/CLI/UI stay
 
 `src/ZB.MOM.WW.ScadaBridge.Commons/Entities/Audit/AuditEvent.cs:22` — a `sealed record`,
 append-only, "single source of truth for AuditLog (#23) rows." Far richer than the canonical
-8-field event. Notable fields:
+10-field event. Notable fields:
 
 - Identity / correlation: `EventId` (idempotency key, `:25`), `CorrelationId` (per-op
   lifecycle, `:68`), `ExecutionId` (per-run, `:75`), `ParentExecutionId` (spawner link, `:82`).
@@ -139,7 +139,7 @@ done carelessly. **Priority: LOW. Blast radius: HIGH.**
 - **Confirm the writer contract matches.** `IAuditWriter.WriteAsync(AuditEvent, CancellationToken
   = default)` is already byte-for-byte the canonical signature, and the "never abort the
   user-facing action" wording matches. The only delta is the **record type**: the library's
-  `IAuditWriter` is typed on the *canonical* 8-field `AuditEvent`, while ScadaBridge's is typed on
+  `IAuditWriter` is typed on the *canonical* 10-field `AuditEvent`, while ScadaBridge's is typed on
   its ~25-field record. Resolve by either (a) keeping ScadaBridge's writer on its own rich record
   and adopting only the library's *interface name + outcome enum*, or (b) having the shared seam be
   generic over the event type. **Recommended: (a)** — adopt the canonical `AuditOutcome` enum and