9.1 KiB
Limited pre-G1 registry static-export pilot
Recorded 2026-11-13. This is the TH-08 limited candidate import/host pilot, not completion of the broader OEE-03 redesign, native Perspective mapping, package publication or deployment.
Source boundary and current-graph correction
Checkout: /Users/dohertj2/Desktop/ignitionoee, branch codex/scada-ui-consistency, baseline ae770588a86361e24492431a7e2a1ef5521dce7c. Existing untracked docs/recipes/evidence/pending-items-2026-11-03/ was preserved untouched. No commit was made by this task.
The plan's public-only premise is stale for this actual checkout. registry/src/Registry.Host/Registry.Host.csproj references the router Security project, registry/NuGet.Config maps the existing ZB.MOM.WW.Auth* packages to Gitea, and the README's shared-host section documents that integration. A lower README paragraph still says public-only; it was deliberately not edited during this bounded pilot. No authentication, source mapping, project/package reference or package version was changed.
Fresh before/after restored Host library graphs are identical: zero additions/removals and no Theme NuGet package. Existing shared Auth packages remain 0.3.0. See graph comparison, before graph and after graph. The static delivery remains independent of any private Theme dependency.
Exact imported artifact
- Zip:
ZB.MOM.WW.Theme/artifacts/technical-light-web-assets.1.0.0.zipin the managed scadaproj worktree. - Zip SHA256:
6c9c1ee721c51a74a6efe39f596c5ea6d609b851b39f967d71b3f8b426a5cdca. - Theme source revision:
3d61456d6150145a525a3a646721f865f5680c1b; source tag: explicituntaggedmarker. - Original nupkg SHA256:
834d2aad4e61cebff3fb48bbf608d412547d4aa39bdda142d0c7caf24c9e10d0.
Independently verified the provided export checksum, version/source package/revision, complete payload set and each payload hash, and compared the manifest's sourcePackageSha256 with the actual exact nupkg bytes. Verified input retains the manifest; imported hashes independently verifies installed bytes.
Imported the two CSS files, three Plex fonts, tokens.json and manifest.json without changing their bytes under registry/src/Registry.Host/wwwroot/shared-theme/. Provenance is also recorded in docs/design/technical-light/registry-asset-import.json in ignitionoee.
Implementation scope
- Added an independent Python stdlib importer at
deploy/scripts/import-technical-light-assets.py, with--artifact,--destination,--expected-version,--check. - It validates the exact path allowlist/unique entries, schema/version/provenance/hash fields and every payload hash before writing. Dry run is non-mutating. Import stages then atomically installs a new directory; a matching destination is idempotent, and a different existing destination is refused/preserved for review rather than overwritten.
- App loads only
shared-theme/css/theme.cssbefore app/domain styles. layout.css is imported and served but not loaded: the native.shell/.rail-disclosure/.side-railmarkup is not ThemeShell and does not have the RCL's Bootstrap layout contract. - Removed only the three duplicate local Plex
@font-facedeclarations, so browser font requests come from the canonical export. Existing old font files are retained, unused, for bounded rollback. - Kept registry domain selectors, native dialog markup/behavior, floorplan geometry, controls, local palette/chassis overrides and all operation semantics. Existing local
--hover/--activealiases now reference canonical--hover-bg/--active-bg. Broader duplicate-rule/domain-token migration waits for the full consumer chapter. - Added actual HTTP hash, browser font-source and semantic-token checks to existing RegistryShellTests. Screenshot output is optional through
REGISTRY_THEME_EVIDENCE, not a hardcoded developer path.
Actual red → green checks
Cwd for these commands: /Users/dohertj2/Desktop/ignitionoee.
-
Fresh
dotnet restore registry/ZB.MOM.MachineRegistry.slnx, graph capture, thendotnet build registry/ZB.MOM.MachineRegistry.slnx --no-restore: passed, zero warnings/errors. Existing RegistryShellTests baseline passed (1 test). -
Python importer tests first failed with FileNotFoundError for the not-yet-written importer. After implementation:
PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tests -p test_technical_light_asset_import.py -v6 tests passed, including non-mutating check, exact-byte/idempotent import, corruption/version/provenance rejection, traversal/unexpected/duplicate archive rejection and preservation of a nonmatching destination. Red, green.
-
Added asset checks to the existing live-host shell test before import. It failed specifically because
/shared-theme/manifest.jsonwas absent, not because of missing infrastructure. Red log, TRX. -
Executed importer
--check, then intentional import from the exact verified zip. Recorded dry run and actual import. -
After App stylesheet wiring and local font-declaration removal, ran the focused shell test with optional screenshot evidence:
REGISTRY_THEME_EVIDENCE=<managed evidence directory>/registry-pilot \ dotnet test registry/tests/Registry.BrowserTests/Registry.BrowserTests.csproj \ --filter FullyQualifiedName~RegistryShellTests \ --logger 'trx;LogFileName=green-assets.trx' --results-directory <managed evidence directory>/registry-pilot -
Ran the complete existing browser suite against the imported styles:
dotnet test registry/tests/Registry.BrowserTests/Registry.BrowserTests.csproj --no-build \ --logger 'trx;LogFileName=all-browser.trx' --results-directory <managed evidence directory>/registry-pilot11 passed, zero failed/skipped. Log, TRX, test identities.
The actual managed evidence directory is /Users/dohertj2/.codex/worktrees/scada-ui-consistency/scadaproj/components/ui-theme/validation/theme-1.0.0. Full paths are shortened above only for readability; captured logs contain the exact executed commands' outputs.
Observed browser acceptance
Existing Playwright 1.58.0 harness and pinned installed Chromium were used without upgrades. Each test starts an ephemeral loopback host and synthetic demo database, then kills the server and deletes fixture data in its existing finally block. No deployed registry, live database or Ignition resource was touched.
- Manifest and all six payloads return successful HTTP responses and hash to the installed manifest values, including layout.css even though it is not loaded.
- Browser body uses IBM Plex Sans; its regular font request comes from
/shared-theme/fonts/ibm-plex-sans-400.woff2, with no requests to the old/fonts/declaration path. - Browser computed canonical
--ink-faintis#626970. - Desktop rail sits beside content; mobile closed/open navigation preserves visible content/current location; no document overflow on exercised 1280×900 and 390×844 screens.
- Full existing browser suite preserves inventory, machine filtering/details, identity lineage, driver editor draft/focus/revision guards, narrow queues, floorplan marker/zoom interactions, import/retry drafts and synthetic automatic-admin attribution.
Desktop capture and mobile capture were visually inspected in one bounded pass. They show the disposable synthetic inventory and empty floorplan state. This does not claim a full new-route visual audit, actual 200% zoom pass, native Perspective acceptance or comprehensive WCAG conformance.
Impeccable detector returned no findings over the changed App.razor and existing app.css after its bounded modifications; captured host result and CSS result. Diff whitespace checks passed. No code/CSS polishing cycle followed the successful screenshots.
Remaining boundaries and rollback
Exact candidate static delivery and host integration are verified for this limited pilot. The parent owns G1/publication decisions. OEE-03 broad palette-duplicate cleanup, other consumer tasks, local warning-opacity refinements, Perspective mappings and full route/device/zoom acceptance remain future work.
For rollback of this uncommitted slice, restore only the App.razor/app.css edits, undo the corresponding test additions, and remove only the new importer/tests/provenance/shared-theme directory after preserving any subsequent changes. No database/schema/auth change is involved. Do not touch the unrelated existing evidence directory or production registry data.