Files
scadaproj/components/ui-theme/validation/cross-project-final/REFRESH.md
T
2026-11-14 01:25:46 -05:00

24 lines
4.2 KiB
Markdown

# Source-only final package refresh
`refresh-package-status.py` repeats the accepted source inventory without editing any project, package declaration, existing snapshot, index or G3 ledger. It uses Python standard library and fixed read-only Git commands. It never restores/builds/tests/downloads packages, reads environment variables, opens private SQL state, or reads unrelated untracked file contents.
Run only after the coordinator declares the OT source freeze:
```text
python3 components/ui-theme/validation/cross-project-final/refresh-package-status.py --ot-source-frozen --output components/ui-theme/validation/cross-project-final/package-status-final.json
```
The output must be a **new** path; the script refuses to overwrite either the historical accepted `package-status.json` or any existing output. An existing candidate should be retained and a clearly named new output requested for any necessary repeat. Exit 0 means no declared-pin mismatch; exit 1 retains the JSON with mismatch details. Missing/ambiguous declarations fail explicitly. `g3Complete` always remains false: root owns G3 acceptance and the ledger.
The accepted snapshot supplies repository roots, seven expected active bUnit projects, two excluded historical parser probes, expected production Core/backend declarations and producer/static asset provenance. The refresh independently rediscovers tracked active bUnit project references, checks exact bUnit2.7.2/AngleSharp1.5.2, and checks actual application/test shared-package declarations against Theme1.0.1, Secrets.Ui1.0.1 and Abstractions0.6.6. Newly added application references are checked too; removed required references fail.
Tracked validation/fixture project graphs under docs/components/validation/artifacts are listed as exclusions from application package adoption, since frozen historical compatibility fixtures can deliberately declare older packages or imported candidate authorities. Active bUnit discovery still scans tracked projects and only excludes the two explicitly accepted historical probes. This prevents evidence projects from silently becoming newly claimed production consumers.
Core/replicator **production declarations** are compared with the accepted planning-baseline inventory; application/test references are separately version-checked against the accepted Core/replicator versions. A source-only preflight found ScadaBridge SiteRuntime.Tests has a test reference to the retained centrally pinned Core0.6.2. This does not change a production pin or justify a claim that all test/transitive graphs are identical. BTDB's accepted test Pkcs security prerequisite remains separately documented; this check does not broaden or erase that caveat.
The script also checks producer source Version declarations, registry static manifest/payload SHA256 values against the exact accepted Theme export, registry manifest/source revision parity, and native Perspective release mapping. It records each repository branch/HEAD/status and rejects a HEAD change during the read. No runtime/resolved graph, vulnerability status, package-feed availability, clean-all-repositories or test result is inferred.
A preparation-only execution on 2026-11-14 produced zero source-declaration mismatches with seven active bUnit projects. It wrote a disposable `/tmp/scada-package-refresh-preflight3.json`; this was **not** the final source-freeze snapshot. The first preparation probe exposed archived fixture central-import authorities, which are now explicitly classified/listed separately. The second exposed a test-only Core reference, which is version-checked while the unchanged boundary remains production-only. Neither probe edited source or package pins. The final provenance-check additions were then rechecked before handoff.
For the final README/status narrative, main managed-WT and OT implementation fixtures/evidence are **task-owned deliverables** that their owners will commit. Do not repeat the historical snapshot's overbroad “unrelated” adjective for those paths. The known unrelated OEE `docs/recipes/evidence` files remain preserved; only Git path metadata is read. BT peer review and HG shutdown evidence now have their own reviewed commits; obtain their final metadata in the freeze refresh rather than copying old HEAD/status values.