2.5 KiB
G1 accepted — shared Technical-Light 1.0.0
Accepted November 13, 2026, after GB and independent source/artifact/pilot/delivery review. The exact package and static export are published, fresh downloads match their reviewed hashes, and Overview restores the same package from the official feed into an isolated package directory without the candidate source. Release record and machine-readable gate record exact provenance and delivery URLs.
| Verification | Actual result |
|---|---|
| Theme Release build | 0 warnings, 0 errors |
| Theme suite | 105 passed, 0 failed/skipped |
| Overview suite | 197 passed, 0 failed/skipped |
| ScadaBridge suite | 1,551 passed, 0 failed/skipped after a narrow dispatcher-safe test fix |
| Registry browser suite | 11 passed, 0 failed/skipped |
| Exporter / registry importer | 15 / 6 passed |
| Package / static export | Exact clean-source bytes; independent delivery hashes match |
| Fresh feed-only restore | Theme 1.0.0, actual official source metadata and exact hash |
Real browser evidence covers four light accent families, supported ScadaBridge dark adoption, label/hint/error focus, slow local busy success/failure, caller-disabled actions, keyboard focus, reduced motion, mobile navigation and bounded layout. Real browser 200% zoom changes layout width and DPR; no CSS zoom substitute is used. Recorded Overview and ScadaBridge selector contrast checks exceed 4.5:1 for tested active text. Detached prerender-node measurements and an initially cropped zoom capture were corrected in bounded confirmation runs, with raw first observations retained. No product fix is claimed for those measurement corrections.
The ScadaBridge actual-source dark adapter preserves the blue identity, improves active text contrast and keeps original signal colors. Registry consumes canonical static assets with its existing Auth graph unchanged and no private Theme dependency; native layout CSS remains local. Only theme.css loads against that native chassis.
This gate permits the remaining consumer chapters to adopt the same immutable contract. It does not claim full authenticated/fleet route coverage, all native Perspective behavior, application deployment, G2 interaction convergence or G3 family completion. G2 follows two representative dialog/filter/table pilots and a documented extraction decision; as specified in the master plan, it does not block G1's recipe publication. Broader consumer work remains tracked individually in the task ledger.