Files
scadaproj/components/ui-theme/validation/cross-project-final/README.md
T
2026-11-14 02:36:01 -05:00

51 lines
6.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Cross-project package declaration and status support
This is a **read-only G3 support snapshot**, not G3 acceptance. OT implementation, composed browser checks and its combined consumer gate were still open when captured. The package-status.json timestamp, branch, HEAD and status entries describe the observed checkouts; later reviewed commits naturally supersede those HEADs.
No restore, package download, test run, environment-variable enumeration or private fixture-state read was performed. The audit read tracked csproj/props XML, nearest Directory.Packages.props authorities, Git branch/HEAD/status metadata, planning-baseline package declarations, and local registry/native Theme manifests. No sister source, existing evidence, staged file or unrelated untracked file was modified.
## Result
**Zero package declaration mismatches.** The accepted GB inventory's seven active bUnit projects all declare bUnit **2.7.2** and direct/central AngleSharp **1.5.2**: Theme, Secrets.Ui, Overview, ScadaBridge CentralUI, OT AdminUI, HistorianGateway and BTDB Manager tests. Tracked discovery matches all seven and finds no additional active consumer. The two archived GB reproduction probes are explicitly excluded; the historical 1.5.0 parser probe remains a historical artifact, not an application pin.
AngleSharp.Css 1.0.0-beta.157 and AngleSharp.Diffing 1.1.1 are the accepted GB-resolved transitive versions. This audit does not invent direct source pins for them or claim a fresh resolved/runtime graph. Existing exact package, runtime binary and vulnerability evidence remains in the GB and individual chapter acceptance records.
| Consumer | Source-declared shared target | Secrets Core/backend boundary |
| --- | --- | --- |
| Overview | Theme 1.0.1 | No Secrets.Ui requirement |
| MxAccessGateway | Theme 1.0.1, Secrets.Ui 1.0.1, Abstractions 0.6.6 | Core package 0.6.2 retained |
| HistorianGateway | Same exact three versions | Core package 0.6.2 retained |
| ScadaBridge | Same exact central versions | Core and SqlServer replicator 0.6.2 retained |
| OtOpcUa | Same exact central versions | Core and AkkaDotNet replicator 0.6.2 retained |
| BTDB Manager | Theme 1.0.1 | Core 0.6.2 retained; it does not consume Secrets.Ui, so no UI/Abstractions migration is imposed |
| ignitionoee router | Same exact central three versions | Core 0.6.2 retained |
| ignitionoee registry | Canonical static Theme 1.0.1 export | No private Theme/Secrets NuGet adoption required |
| Native Perspective | Theme 1.0.1 token mapping recorded in native style resources | No Blazor package/runtime adoption |
Producer source versions are Theme 1.0.1, Secrets.Ui 1.0.1 and Secrets.Abstractions 0.6.6. Secrets.Ui's project-level override does not imply publishing Core/backends. Their package declarations were compared against each repository's recorded planning baseline, including the pre-existing ScadaBridge planning head rather than its older review head; all relevant Core/replicator pins are unchanged. This is a bounded declared-pin comparison, not a claim that every transitive production dependency is unchanged. In particular, BTDB's separately accepted Pkcs security prerequisite remains documented in its GB/chapter evidence.
The registry manifest's six payload hashes match actual local files. Registry and Perspective records identify the accepted Theme 1.0.1 source package SHA `995b117b0245577598c91404ed7957c071ebe3413696c8be48b419c9deb1bd5d`; the static export SHA is `ad52323416e5096e30e4b7624004274689bc2b72e1437f9e9e5d7db9f9e656e0`. Registry package-free/static ownership and native Perspective style ownership remain distinct from the router's Blazor references.
## Repository status boundary
All seven checkout branches were `codex/scada-ui-consistency`, with HEAD stable during each repository read. The JSON records full hashes and exact status paths.
- MxAccessGateway, ScadaBridge and BTDB were clean.
- The managed scadaproj checkout had 25 unrelated untracked evidence/fixture paths.
- OtOpcUa had active implementation/evidence changes, as expected before OT completion.
- HistorianGateway had one modified evidence log, `docs/ui-validation/evidence/raw-draft-canary.log`, and no modified source/package declaration. It was left untouched for owner classification.
- ignitionoee had 2,621 unrelated untracked files, all under `docs/recipes/evidence`; they were inventoried by Git metadata and preserved without reading their contents, staging or deleting them.
These statuses are explicitly not a clean-all-repositories or ready-to-release assertion. Full G3 must reconcile the coordinator's final task ledger, source/artifact acceptance, outstanding runtime limitations and later repository status. Only this README and package-status.json belong to the support commit.
## Common rollout note: preactivation focus capture
The coordinator accepted a bounded adapter observation from OtOpcUa's `docs/ui-consistency/evidence/ot13-dialog-focus-recovery/preactivation-investigation.json`. Four controlled native sequences show that activation captures the focus present at activation time: an external invoker restores correctly, while a synthetic sequence that focuses an internal Save before activation has no retained external-invoker identity and can finish on a heading/body depending on DOM-removal order. This is capture-semantics evidence, not a composed Blazor/ordinary-user timing reproduction. The original scratch observation lacked retained context to certify that cause. No shared-source or package change was made from this investigation; final initialized-modal matrices retain the frozen accepted adapter hash. This note does not turn the G3 support snapshot into G3 acceptance.
## Final coordinator decision
[G3.md](G3.md) records the completed 100-task candidate acceptance on November 14. This README’s original snapshot narrative remains historical. [package-status-final.json](package-status-final.json) is the later source-only refresh: seven active bUnit 2.7.2 projects, zero declared-pin mismatches and exact registry/native export provenance. Task-owned main/OT fixture evidence was subsequently committed; HG shutdown evidence and BT peer notes are committed. Only OEE’s pre-existing unrelated evidence remains untracked.
The helper’s `g3Complete=false` deliberately does not override the coordinator’s accepted G3 decision; source-only tools do not authorize release. [coordinator-verification.json](coordinator-verification.json) captures independent raw-result/source/cleanup checks and later repository metadata, including the documentation-only OT acceptance marker. Retained source/graph records do not claim production deployment, new external integrations, or a simultaneous fresh all-repository suite rerun.