fix(secrets-ui): use canonical metadata ink in supported palettes
This commit is contained in:
@@ -0,0 +1,22 @@
|
||||
# Secrets UI 1.0.1 metadata ink correction
|
||||
|
||||
Actual integration of the published UI1.0.0 with the supported ScadaBridge dark
|
||||
palette exposed two producer-owned references to an undefined `--ink-muted` token.
|
||||
Both fell back to literal#626970 despite canonical `--ink-faint` resolving#a8b0bc.
|
||||
Browser measurements against the nearest opaque card background produce2.6576:1;
|
||||
see dark-before.json. The same light fallback had masked this alias mistake in the
|
||||
two-host light acceptance matrix. Parent review records the missed references.
|
||||
|
||||
Publish compatible UI patch1.0.1. Replace only those caption/technical-summary color
|
||||
references with canonical `--ink-faint`. Default light computes the same color;
|
||||
supported host palettes now supply their own canonical ink. No per-consumer alias.
|
||||
Theme stays1.0.1, Abstractions stays0.6.6; no Core/backend repack or release. The
|
||||
published UI1.0.0 artifact and its historical proofs remain immutable.
|
||||
|
||||
Commit clean package inputs before packing with explicit revision metadata. Validate
|
||||
81 source tests, exact UI-only package floor graph, module/source byte parity, actual
|
||||
light/dark computed metadata contrast using supported ScadaCSS, and packaged-host
|
||||
read-only runtime identity/assets. Review exact bytes, publish only that UI artifact,
|
||||
then verify fresh official download and isolated official restore before delivery.
|
||||
Existing66 legacy checks concern unchanged contracts/implementations and are retained
|
||||
as bounded evidence rather than rerun merely for two CSS references/version metadata.
|
||||
Reference in New Issue
Block a user