docs: publish LocalDb 0.1.0 to the feed + reconcile component status against verified state

Publishes the three ZB.MOM.WW.LocalDb packages to the Gitea feed (restore-verified
from a scratch consumer) and adds the build/push.sh the other shared libs already have.

The status prose across CLAUDE.md, README.md and components/*/GAPS.md had drifted from
reality, so it was re-derived from the feed listing and the actual PackageReferences +
registration calls on each consumer's default branch rather than from prior claims.
Five claims were false: Health "not yet adopted" (all four apps wire MapZbHealth),
GalaxyRepository's mxaccessgw adoption "a follow-on" (its Server wires
AddZbGalaxyRepository), Configuration "not yet pushed", Secrets G-8 "not yet
committed", and Theme pinned at 0.2.0 (all four are on 0.3.1). Every doc also said
"three apps" while HistorianGateway is a fourth consumer of seven libs, and all
eight libraries' test counts were stale (re-ran each suite; all green).

Surfaces one previously unrecorded gap: Secrets source is at 0.1.3 with KEK rotation
committed, but the feed tops out at 0.1.2, so no app can consume rotation until it
is published.

Health and observability divergence tables are labelled historical, not re-verified —
the libraries are proven wired, but per-app probe coverage vs spec was not re-walked.

Claude-Session: https://claude.ai/code/session_01BL2Vu1ESDQ9SCN4gVKkdts

components/audit/GAPS.md

@@ -3,6 +3,10 @@
 Divergence of each project from [`spec/SPEC.md`](spec/SPEC.md), and the ordered backlog to
 reach the shared `ZB.MOM.WW.Audit` library. Status legend: ⛔ gap · 🟡 partial · ✅ matches.
 
+> **Current state (verified 2026-07-18):** `ZB.MOM.WW.Audit` `0.1.0` is on the Gitea feed and
+> **all four** apps reference it — **HistorianGateway is a fourth consumer** this file predates.
+> Library suite: **23 tests**, green 2026-07-18.
+>
 > **✅ ADOPTED 2026-06-02 (local-only) — DEEP.** The backlog (#1–#6) was implemented across all three apps on each repo's
 > **`feat/adopt-zb-audit`** branch (stacked on `feat/adopt-zb-auth`) — committed + spec/code-reviewed, then **merged to
 > each repo's local default (main/master) and PUSHED to origin (gitea) on 2026-06-03** (in sync). The user chose **DEEP adopt**:

components/auth/GAPS.md

@@ -3,6 +3,12 @@
 Divergence of each project from [`spec/SPEC.md`](spec/SPEC.md), and the ordered backlog to
 reach the shared `ZB.MOM.WW.Auth` library. Status legend: ⛔ gap · 🟡 partial · ✅ matches.
 
+> **Current state (verified 2026-07-18):** feed carries `0.1.0`–`0.1.4`; consumer pins are
+> OtOpcUa `0.1.1`, ScadaBridge `0.1.3`, MxAccessGateway `0.1.4`, **HistorianGateway `0.1.4`**
+> (a fourth consumer this file predates, taking all four packages). OtOpcUa is three minors
+> behind — it does not get the `0.1.4` API-key-expiry enforcement. Library suite: **215 passing,
+> 1 skipped**, green 2026-07-18.
+>
 > **✅ ADOPTED 2026-06-02 (local-only).** The full backlog (#1–#8) was implemented across all three apps on each repo's
 > **`feat/adopt-zb-auth`** branch — committed + spec/code-reviewed, then **merged to each repo's local default
 > (main/master) and PUSHED to origin (gitea) on 2026-06-03** (in sync; `feat/*` kept locally). Shared

components/configuration/GAPS.md

@@ -1,10 +1,13 @@
 # Configuration validation — gaps & adoption backlog
 
 Divergence of each project from [`spec/SPEC.md`](spec/SPEC.md), and the ordered backlog to adopt
-the shared `ZB.MOM.WW.Configuration` library. The library is **BUILT @ 0.1.0** (42 tests) at
+the shared `ZB.MOM.WW.Configuration` library. The library is **BUILT @ 0.1.0** (42 tests, re-run
+green 2026-07-18) at
 [`../../ZB.MOM.WW.Configuration/`](../../ZB.MOM.WW.Configuration/) and was **ADOPTED across all three
-apps on 2026-06-01** — published to the Gitea feed, then consumed on each repo's local default branch
-(merged, **not yet pushed** to remotes). The adoption items below are now largely closed: MxGateway +
+apps on 2026-06-01** — published to the Gitea feed, then consumed on each repo's local default branch.
+**Re-verified 2026-07-18:** `0.1.0` is on the feed and **all four** apps reference it (HistorianGateway
+too, which this file predates) on their pushed default branches — the earlier "merged, **not yet pushed**
+to remotes" caveat is stale and has been removed. The adoption items below are now largely closed: MxGateway +
 ScadaBridge migrated to `OptionsValidatorBase`/`AddValidatedOptions` behaviour-preservingly (validator
 messages byte-identical), ScadaBridge's `StartupValidator` → `ConfigPreflight`, and OtOpcUa gained
 net-new `Ldap`/`OpcUa` validators (plus a follow-on pass: real `Security:Ldap` binding, `ValidateOnStart`

components/health/GAPS.md

@@ -3,6 +3,20 @@
 Divergence of each project from [`spec/SPEC.md`](spec/SPEC.md), and the ordered backlog to
 reach the shared `ZB.MOM.WW.Health` library. Status legend: ⛔ gap · 🟡 partial · ✅ matches.
 
+> **✅ ADOPTED — verified 2026-07-18.** This file previously carried no adoption banner and the
+> root docs claimed the library was "**not yet adopted**". That was stale. Verified directly:
+> `ZB.MOM.WW.Health` `0.1.0` is on the Gitea feed, and **all four apps reference it and wire
+> `MapZbHealth`** — OtOpcUa (+ `.Akka` + `.EntityFrameworkCore`, uses `AkkaClusterHealthCheck`),
+> MxAccessGateway (core only), ScadaBridge (all three packages; uses `AkkaClusterHealthCheck` +
+> `IActiveNodeGate`), HistorianGateway (core; uses `GrpcDependencyHealthCheck`).
+>
+> **Caveat on the evidence:** this was verified by `PackageReference` + registration-call grep,
+> which proves the library is wired in — *not* that every per-app probe below is registered or
+> that the endpoint tiers match the spec. The divergence tables further down were written
+> pre-adoption and have **not** been re-verified against current code; treat them as historical
+> until someone re-walks them. They also predate HistorianGateway, which is absent from every
+> table below.
+
 ## Divergence vs spec
 
 ### §1 Endpoint tiers

components/observability/GAPS.md

@@ -3,6 +3,19 @@
 Divergence of each project from [`spec/SPEC.md`](spec/SPEC.md), and the ordered backlog to
 reach the shared `ZB.MOM.WW.Telemetry` library. Status legend: ⛔ gap · 🟡 partial · ✅ matches.
 
+> **✅ ADOPTED — verified 2026-07-18.** `ZB.MOM.WW.Telemetry` + `.Serilog` `0.1.0` are on the Gitea
+> feed and **all four apps reference both and call `AddZbTelemetry`** (Resource + standard
+> instrumentation + Prometheus `/metrics`). Logging: OtOpcUa, MxAccessGateway and **HistorianGateway**
+> (a fourth consumer this file predates) use `AddZbSerilog`; ScadaBridge deliberately keeps its own
+> `LoggerConfigurationFactory` for min-level governance and adds only the shared `TraceContextEnricher`
+> — that split is by design, not a gap. Library suite: **34 tests**, green 2026-07-18.
+>
+> **The `⛔ not set` divergence tables below are the pre-adoption 2026-06-01 snapshot** — the §1
+> Resource-attribute gaps they describe are what `AddZbTelemetry` closed. Read them as the
+> historical case for the library, not as current state. Deferred items noted at the time
+> (MxGateway `ms`→`s` + Meter rename, ScadaBridge app instruments + Site-node HTTP/1.1 metrics
+> listener, OTLP wiring) were **not** re-verified in this pass.
+
 ## Divergence vs spec
 
 ### §1 OTel Resource / `service.name` (P1 — nobody has it)

components/secrets/GAPS.md

@@ -5,6 +5,28 @@ The delta between each project's [`current-state`](current-state/) and the
 reference-consumer-proven**; everything here is per-app adoption of an existing lib (not lib
 construction).
 
+## Current state (verified 2026-07-18)
+
+- **Source is at `0.1.3`; the feed is at `0.1.2`.** `ZB.MOM.WW.Secrets/Directory.Build.props`
+  declares `<Version>0.1.3</Version>` and the G-8 KEK-rotation work (`KekRotationService`,
+  `RewrapReport`, `secret rewrap-all`, `docs/operations/kek-rotation.md`) is **committed and
+  pushed** on `main` (`d82d345`). The Gitea feed carries only `0.1.0`–`0.1.2` for all three
+  packages. **→ `0.1.3` is unpublished: no app can consume KEK rotation yet.** (An earlier note
+  claiming G-8 was "not yet committed/pushed" was stale — it is committed; only the *publish*
+  is outstanding.)
+- **All four apps are pinned to `0.1.2`** — OtOpcUa, MxAccessGateway, ScadaBridge take
+  `Secrets` + `.Abstractions` + `.Ui`; HistorianGateway takes `Secrets` + `.Ui`.
+- **G-7 clustered replication is designed + planned, not built** — plan at
+  `docs/plans/2026-07-17-secrets-g7-*` (resolved to build the shared SQL-Server `ISecretStore`;
+  Akka replicator deferred to phase 2). No `ISecretStore` SQL-Server implementation exists yet.
+- Library suite: **97 passing, 1 skipped**, green 2026-07-18.
+
+### Open
+
+- ⬜ Publish `ZB.MOM.WW.Secrets` `0.1.3` (+ `.Abstractions`, `.Ui`) to the Gitea feed.
+- ⬜ Execute the G-7 plan (shared SQL-Server `ISecretStore`).
+- ⬜ Per-app live wonder gates for the G-8 rotation path.
+
 ## Execution status (2026-07-16)
 
 - **mxaccessgw — G-4 + G-5 + G-6 DONE.** Executed via the plan below (8 tasks, subagent-driven,

components/ui-theme/GAPS.md

@@ -3,6 +3,12 @@
 Divergence of each project from [`spec/SPEC.md`](spec/SPEC.md), and the ordered backlog to
 reach adoption of the `ZB.MOM.WW.Theme` shared RCL. Status legend: ⛔ gap · 🟡 partial · ✅ matches.
 
+> **Current state (verified 2026-07-18):** the kit has moved on from the `0.2.0` this banner
+> describes — the Gitea feed carries `0.2.0`, `0.2.1`, `0.3.0`, `0.3.1`, and **all four apps are
+> pinned to `0.3.1`** (HistorianGateway is a fourth consumer this file predates). The `0.3.0`/`0.3.1`
+> nav/aria/login fixes are recorded in `themeissues.md`, not here. Library suite: **48 bUnit tests**,
+> green 2026-07-18. History below is accurate for the original cutover.
+>
 > **✅ ADOPTED 2026-06-03 (local-only).** Backlog #2–#4 implemented across all three apps on each repo's
 > **`feat/adopt-zb-theme`** branch — full canonical cutover (SPEC §7): `<ThemeHead/>`/`<ThemeScripts/>`,
 > thin `MainLayout` → `<ThemeShell>` + `NavRailItem`/`NavRailSection`, per-app `theme.css`/IBM-Plex fonts/