docs(archreview): record post-round-2 namespace-flatten fix (PR #438)

2026-07-13 18:29:53 -04:00
parent 50e04707c8
commit 40d130e7c2
1 changed files with 14 additions and 0 deletions
@@ -277,3 +277,17 @@ Brought up the 2-node central cluster (`central-1`+`central-2`, SQL, traefik) fr
 `capper-03`'s `production-count` virtual tag for the PureRemove test). Reset with
 `docker compose -f docker-dev/docker-compose.yml down -v`. The remaining integration-suite sweep + genuinely-external
 gates (R2-06 VPN, R2-08 live LDAP, R2-01 S7 blackhole) still need their infra.
 ---
 ## Post-round-2 loose-end closure (2026-07-13)
 - **Pre-existing red unit test closed** (theme-#4 "CI to all suites" hygiene; predates round 2, not an R2 plan).
  `InterfaceIndependenceTests.AllPublicTypes_LiveInRootNamespace` was red on master because four
  continuous-historization types (`IHistorizationOutbox`, `HistorizationOutboxEntry`, `IHistorianValueWriter` /
  `HistorizationValue`, `HistorizationCommitMode`) had drifted into a `ZB.MOM.WW.OtOpcUa.Core.Abstractions.Historian`
  sub-namespace while the other six files in the same folder use the root namespace — violating decision #59's
  flat-public-surface rule. Fixed by moving all four to the root namespace and dropping/retargeting the redundant
  `using …Core.Abstractions.Historian;` in ~11 consumers (no behavioral change). **Gitea PR #438 → master `50e04707`.**
  Verified: Core.Abstractions `129/129` (was 128/129), Runtime historian+DI `72/72`, Gateway driver unit `102/102`,
  full solution build `0 errors`.