Files
scadaproj/ZB.MOM.WW.Secrets/docs/ui-consistency-validation.md
T
2026-11-13 17:56:57 -05:00

4.4 KiB
Raw Blame History

Secrets UI consistency validation

Release preparation

UI-only project version 1.0.0; required Abstractions 0.6.6; exact shared Theme 1.0.1. Shared Directory.Build.props and Core/backend source versions remain 0.6.6 without a backend release. The package pair is not published until its clean-source artifact/dependency review is accepted.

Source acceptance

  • Target/draft/pending operation isolation: f07bd3c,34 baseline → 50 UI tests.
  • Field labels/error associations, accessible confirmation lifecycle and committed/read recovery: 510d15d, 69 tests and actual keyboard/focus proofs in per-page/global host modes.
  • Name-only metadata filtering, native secondary details, contextual actions, keyed rows and generation-bound audited reveal: 46556db, 81 tests; 93 final rendered checks across both actual integration modes, 1440/390px/native200% browser zoom; zero page errors.
  • The exact Theme 1.0.1 nupkg hash is 995b117b0245577598c91404ed7957c071ebe3413696c8be48b419c9deb1bd5d. Selected UI text contrasts measured 5.144:1–16.877:1. CSS/fonts and source DOM module bytes were checked in both hosts. Runtime evidence is under components/ui-theme/validation/secrets-ui from the monorepo root; see its SEC01, SEC02-04 and SEC05-06 reports and retained TRX/browser artifacts.

Preserved security and state contracts

Metadata listing/filtering never reads values. Each public handler checks its own policy. Reveal requires a successful audit before plaintext enters current rendered state; status, labels, URLs, interop arguments and audit payloads exclude values. Hide, row removal, navigation, target changes and disposal clear disclosure. There is no timer-based auto-hide policy. Mutation audit failure after commit does not turn a successful write into failure or skip captured cache eviction. Retry after list failure reads only; it never repeats a committed credential change.

Dependency compatibility gate

Before publication, exercise actual published Core 0.6.2/0.6.3 and matching supported SQL-Server/Akka replicator binaries with Abstractions 0.6.6, rather than recompiling the old implementation from current source. Include an old-compiled key provider to prove the added default interface method, real envelope encryption/rewrap/tamper checks, disposable SQLite persistence/tombstones and offline replication contract/message paths. Record exact graphs/audits and all actual package hashes. Live SQL/cluster deployment is outside this local binary smoke proof.

The new 450-character normalized name limit is a behavior boundary, not a schema migration. Compatibility proof is bounded to valid names. Existing longer names/tombstones require a host inventory decision before adopting Abstractions 0.6.6. The default snapshot implementation copies the legacy key/id API; a rotating provider must supply an atomic snapshot if it needs that guarantee.

Artifact and host gate

Freeze a clean committed library source revision and pass it explicitly as both SourceRevisionId and RepositoryCommit when packing. Pack exactly UI 1.0.0 and Abstractions 0.6.6; inspect their nuspec IDs/versions/floors and hash them. Keep unpublished candidates out of shared NuGet caches; isolated restores must verify package bytes/source rather than assembly version alone. A stale unpublished Theme 1.0.1 candidate was caught during source validation and replaced by exact official bytes.

Use isolated local candidate feeds plus mapped official feeds for a fresh restore, then run both packaged synthetic hosts: the exact OtOpcUa per-page wrapper with its Bootstrap and the global interactive host with ScadaBridge Bootstrap. Verify one route, live controls, DOM assets, role boundaries, fail-closed reveal, committed outcomes and keyboard/focus behavior. Check version collisions again immediately before any exact package publication. Publication requires final artifact/dependency review; there is no wildcard push step.

Rollout and rollback

Hosts adopt UI 1.0.0, Abstractions 0.6.6 and Theme 1.0.1 together through reviewed pins; keep their current Core/store/replicator version unless separately upgrading it. Preserve the previous host and immutable package artifacts. Roll back UI/assets together without replaying mutations, removing tombstones or changing keys/storage formats. Preserve target isolation when feasible. No application deployment or production-secret operation is part of this validation.