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
This commit is contained in:
@@ -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,
|
||||
|
||||
Reference in New Issue
Block a user