28 KiB
HistorianGateway UI consistency Implementation Plan
For Codex: REQUIRED SUB-SKILL: Use
executeplanto implement this plan task-by-task.
Goal: Make historical queries, manual status freshness and diagnostic-write intent clear and accessible within the shared Technical-Light system.
Architecture: Retain the existing shared shell and green product accent while adopting G1 semantic ink, field associations and state patterns. Keep point-in-time status, read-only Galaxy metadata and administrator diagnostic writes as separate domain responsibilities; no historian protocol or storage mutation is added by theme adoption.
Tech Stack: net10.0 Blazor InteractiveServer, Bootstrap CSS, Theme currently 0.5.0, xUnit 2.9.3, bUnit 2.7.2 after GB, GB-validated AngleSharp dependency graph.
Required testing prerequisite
Complete bUnit standardization and close GB before any task in this chapter, including local fixes and candidate UI pilots. All bUnit snippets below use the post-GB BunitContext / Render / AddAuthorization API; their inherited helpers must be migrated in GB. Preserve framework HtmlRenderer methods and xUnit runner APIs where used. Non-bUnit runtimes retain their existing harnesses, but their UI work also waits for the family gate. Old package pins are discovery baselines, not targets for this chapter.
Execution contract
- Repository:
/Users/dohertj2/Desktop/HistorianGateway. All source/test paths below are relative to that root; use it as cwd unless a step states otherwise. - Planning date: 2026-11-12. This chapter specifies future work; no implementation or test execution is claimed.
- Read the corresponding
/Users/dohertj2/Desktop/scadaproj/impeccable/HistorianGateway.md, the shared design-system report, the master plan and applicableAGENTS.mdbefore execution. - Reuse a suitable checkout; inspect
git status --shortand preserve user edits. No new worktree, commit, push, package publication or deployment is performed by authoring this plan. - Dependency gate: complete shared Theme G1 compatibility audit, assign
THEME_VERSION, and verify its artifact before consumer migration.THEME_VERSIONis a placeholder, never a literal package version to publish. - Shared G1 supplies semantic status ink (
--ok-ink:#236f34,--warn-ink:#855000,--bad-ink:#b42121,--idle-ink:#535d66),--ink-faint:#626970, and independent blue--info-ink; product accent never recolors semantic informational notices. - G1 adds
TechField.For,HintId,ErrorId; callers supply input IDs,aria-describedbyandaria-invalid. G1 addsThemeShell.AccentDeep,AccentTint,AccentBorder,AccentFocuswhile preservingAccent. - Shared accent aliases must resolve in shell scope: G1 uses
--accent-tintdirectly or rebinds inherited aliases at.app-shell. Bootstrap.btn-primary/ghost component variables must follow shell accent for normal/hover/active/disabled states. Compare computed states before deleting any consumer override. - G1 also supplies shared focus/busy/reduced-motion and filter/table/dialog recipes.
TechButton.BusyTextis optional; busy addsaria-busy. Caller-owned status/alert text announces outcomes, never secret values or every polling update. - Pilot native dialogs in two consumers before extracting a common dialog component. Do not build a new component package during a first consumer migration.
- Restore/build first and record actual dependency/runtime failures. Complete GB bUnit/parser standardization first. Preserve xUnit, test SDK and Playwright versions unless a specific demonstrated compatibility fix is recorded in GB; do not perform later incidental framework upgrades. Never treat a skipped native/SQL/COM/live test as a pass.
- Each numbered step is one short action. When a step discovers broader product behavior, stop that task at its boundary and update this written plan before expanding implementation scope.
Verified baseline and package gate
src/ZB.MOM.WW.HistorianGateway.Server/ZB.MOM.WW.HistorianGateway.Server.csproj:30directly pins Theme 0.5.0; Secrets/Secrets.Ui pin 0.6.2. Compare transitive Theme graphs before assigningSECRETS_UI_VERSIONandTHEME_VERSION.- Existing bUnit helpers/fakes live in
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/. The snippets below are additions inside the named existing class, with its current imports, fake andBunitContextbase. - The pre-GB test project pins bUnit 1.40.0 and AngleSharp 1.5.2; BU-08 replaces that baseline with verified bUnit 2.7.2 and its accepted parser graph. Run the post-GB baseline before UI edits; investigate dependency regressions without undoing the standardization.
IDashboardStatusServicenormally catches connectivity-probe failures and returns an Unreachable verdict. HG-02 handles an unexpected page retrieval failure separately; never replace a valid Unreachable snapshot with a generic exception state.- Baseline commands from repo root:
dotnet restore src/ZB.MOM.WW.HistorianGateway.Server/ZB.MOM.WW.HistorianGateway.Server.csproj;dotnet list src/ZB.MOM.WW.HistorianGateway.Server/ZB.MOM.WW.HistorianGateway.Server.csproj package --include-transitive; focused Dashboard tests below. - Preserve green product accent
#2f855a. Set its new deep/tint/border/focus family only to values approved in G1; semantic Info remains blue through--info-ink.
Findings coverage
| Report finding | Planned task | Primary proof |
|---|---|---|
| HG-01 unassociated labels | HG-01 | Every visible console control has associated label |
| HG-02 freshness/stale retrieval | HG-02 | Sequential status fake + manual-refresh header |
| HG-03 hover-only diagnostics | HG-03 | Expandable full safe text on health/member rows |
| HG-04 write intent review | HG-04 | No write before confirm; cancel makes zero calls |
| HG-05 search/toggle names | HG-05 | Named controls, retained lazy rendering and 300 hit cap |
| HG-06 query context/feedback | HG-06 | Submitted request retained independently of edited next request |
| HG-07 landing signposts | HG-07 | Task-oriented links, no duplicate status or new polling |
G1 asset adoption before HG-01
- After G1 compatibility audit resolves
THEME_VERSION, update only the explicit Theme reference in Server.csproj; update Secrets.Ui only if its compatible verified release is required. - Restore and compare the transitive graph; confirm no downgrade/unintended floating reference.
- Build Server, rerun baseline dashboard tests, and check fonts/Theme CSS load in a local browser fixture.
- In
Dashboard/Components/Layout/MainLayout.razor, preserve the existing green Accent and supply matching optional accent family from G1; check focus/selection/hover in the actual shell. - Keep
wwwroot/css/site.cssdomain geometry; remove a local rule only after proving G1 supplies equivalent behavior. Separate semantic ink from status fill swatches. - Record the exact package graph and screenshot comparison in
docs/ui-validation/technical-light-historian.md; commit this isolated adoption asstyle: adopt shared Historian theme contract.
HG-01: Associate all history and diagnostic fields
Files:
- Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/HistorianConsolePage.razor - Modify
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/HistorianConsolePageRenderTests.cs
Step 1 — Establish the failing behavior. Add the following test inside HistorianConsolePageRenderTests. The fake and Viewer authorization idiom already exist. Add a second case for Administrator to cover diagnostic input labels.
[Fact]
public void Query_inputs_have_programmatically_associated_labels()
{
var auth = this.AddAuthorization();
auth.SetAuthorized("viewer");
auth.SetRoles(DashboardRoles.Viewer);
Services.AddSingleton<IDashboardHistorianService>(new FakeDashboardHistorianService());
var cut = Render<HistorianConsolePage>();
foreach (var control in cut.FindAll("input, select"))
{
var id = control.Id;
Assert.False(string.IsNullOrWhiteSpace(id));
Assert.NotEmpty(cut.FindAll($"label[for='{id}']"));
}
}
Step 2 — Run the focused check. From the repository root:
dotnet test tests/ZB.MOM.WW.HistorianGateway.Tests/ZB.MOM.WW.HistorianGateway.Tests.csproj --filter FullyQualifiedName~HistorianConsolePageRenderTests
Expected before: query inputs have no stable IDs with matching labels.
Step 3 — Implement in small edits.
- Assign stable distinct IDs for query-tag/mode/max-values/start/end/retrieval/interval and every value/event write field.
- Apply TechField.For only where the wrapper helps; ensure caller input IDs and describedby/invalid attributes remain explicit.
- Use fieldsets/legends for related date range and write operation; associate hint/error IDs and keep UTC visible in labels.
- Keep current query and server role behavior; do not introduce a second validation model.
Step 4 — Verify the change. Re-run Step 2; expected after: PASS for the named tests or all stated visual checks. Click labels in browser and verify focus moves to the intended field. Tab through both raw/aggregate layouts and Admin write fields; each name stays unambiguous after mode changes.
Step 5 — Commit. Stage only the listed production/test/evidence files, inspect git diff --cached, then git commit -m "fix: associate Historian console form labels". Do not include generated credentials, runtime data or unrelated edits.
HG-02: Show sampled time and recover unexpected refresh failures
Files:
- Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/StatusPage.razor - Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/HealthPage.razor - Modify
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/StatusPageRenderTests.cs - Modify
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/HealthPageRenderTests.cs
Step 1 — Establish the failing behavior. Add a sequence fake inside StatusPageRenderTests. Use BaseStatus() already in that file. First render succeeds, then refresh throws, proving the last snapshot and visible stale state survive independently of the ordinary Unreachable verdict.
private sealed class SucceedsThenFails(DashboardStatus first) : IDashboardStatusService
{
private int calls;
public Task<DashboardStatus> GetStatusAsync(CancellationToken cancellationToken = default)
=> ++calls == 1 ? Task.FromResult(first)
: Task.FromException<DashboardStatus>(new IOException("fixture unavailable"));
}
[Fact]
public void Refresh_failure_retains_the_last_good_snapshot_and_marks_it_stale()
{
Services.AddSingleton<IDashboardStatusService>(new SucceedsThenFails(BaseStatus()));
var cut = Render<StatusPage>();
cut.Find("button").Click();
cut.WaitForAssertion(() => {
Assert.Contains("hist01:32565", cut.Markup);
Assert.NotEmpty(cut.FindAll("[data-stale='true']"));
Assert.Contains("Retry", cut.Markup);
});
}
Step 2 — Run the focused check. From the repository root:
dotnet test tests/ZB.MOM.WW.HistorianGateway.Tests/ZB.MOM.WW.HistorianGateway.Tests.csproj --filter FullyQualifiedName~StatusPageRenderTests
Expected before: an unexpected refresh exception is not handled by the page; no data-stale banner exists.
Step 3 — Implement in small edits.
- Put generated time and “Manual refresh” adjacent to page title/status; use actual GeneratedUtc, not render time.
- Store page-level loading/error state separately from the last successful status/report. Catch expected retrieval exceptions, preserve last-good data, mark it stale and provide Retry.
- On first-load failure render no-data error recovery, never stale empty values. On valid Unreachable report show its actual sampled state.
- Add cancellation/disposal protection to prevent a late result changing disposed component state; prevent duplicate refresh while busy.
- Health has no generated timestamp in HealthReport: record captured time at successful report acquisition using injected TimeProvider, not a fabricated source timestamp.
Step 4 — Verify the change. Re-run Step 2; expected after: PASS for the named tests or all stated visual checks. Check initial failure, slow refresh, successful unreachable report, unexpected refresh failure after success and recovery. Refresh remains manual; no hidden polling is introduced. A real browser verifies one polite outcome announcement and visible retry focus.
Step 5 — Commit. Stage only the listed production/test/evidence files, inspect git diff --cached, then git commit -m "fix: expose Historian snapshot freshness and stale recovery". Do not include generated credentials, runtime data or unrelated edits.
HG-03: Make health and member detail accessible without hover
Files:
- Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/HealthPage.razor - Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/StatusPage.razor - Modify
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/HealthPageRenderTests.cs - Modify
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/StatusPageRenderTests.cs
Step 1 — Establish the failing behavior. Extend existing health/member fixture cases with a long safe description. Assert its full text is present within a named details disclosure, not just a title attribute. Seed a deliberately unsafe credential-like string at the service redaction test boundary and verify it is absent before the UI receives data.
Step 2 — Run the focused check. From the repository root:
dotnet test tests/ZB.MOM.WW.HistorianGateway.Tests/ZB.MOM.WW.HistorianGateway.Tests.csproj --filter FullyQualifiedName~HealthPageRenderTests
dotnet test tests/ZB.MOM.WW.HistorianGateway.Tests/ZB.MOM.WW.HistorianGateway.Tests.csproj --filter FullyQualifiedName~StatusPageRenderTests
Expected before: full messages are only exposed through title text and abbreviated visible spans.
Step 3 — Implement in small edits.
- Replace tooltip-only full-detail access with an inline native details disclosure per relevant row; use concise summary labels including check/member identity.
- Preserve table semantics and short scan rows; full details wrap and are copyable.
- Keep secret removal in service/logging boundaries; UI should never make an unsafe raw exception expandable. Do not broaden returned diagnostic fields.
Step 4 — Verify the change. Re-run Step 2; expected after: PASS for the named tests or all stated visual checks. Tab to a failed health check, open details with Space, read/copy full safe message on touch and keyboard, then close. Confirm a long message only expands its own row and no whole-page horizontal overflow appears.
Step 5 — Commit. Stage only the listed production/test/evidence files, inspect git diff --cached, then git commit -m "fix: expose accessible Historian diagnostic details". Do not include generated credentials, runtime data or unrelated edits.
HG-04: Review diagnostic writes before dispatch
Files:
- Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/HistorianConsolePage.razor - Modify
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/HistorianConsolePageRenderTests.cs
Step 1 — Establish the failing behavior. Replace the old direct-write test expectation with the following Admin test; it uses the existing recording fake. Add cancel and duplicate-submit cases by observing fake call count. These tests intentionally change the UI behavior without changing backend authorization.
[Fact]
public void Historical_insert_waits_for_explicit_confirmation()
{
var auth = this.AddAuthorization();
auth.SetAuthorized("admin");
auth.SetRoles(DashboardRoles.Admin);
var fake = new FakeDashboardHistorianService();
Services.AddSingleton<IDashboardHistorianService>(fake);
var cut = Render<HistorianConsolePage>();
cut.Find("input.console-write-tag").Change("Pump01.PV");
cut.Find("input.console-write-value").Change("99.9");
cut.Find("button.console-write-review").Click();
Assert.Null(fake.LastValueWrite);
Assert.Contains("Pump01.PV", cut.Find("[data-write-review]").TextContent);
cut.Find("button.console-write-confirm").Click();
Assert.Equal("Pump01.PV", fake.LastValueWrite?.Tag);
}
Step 2 — Run the focused check. From the repository root:
dotnet test tests/ZB.MOM.WW.HistorianGateway.Tests/ZB.MOM.WW.HistorianGateway.Tests.csproj --filter FullyQualifiedName~HistorianConsolePageRenderTests
Expected before: the existing Insert action calls the write service immediately, before a review step.
Step 3 — Implement in small edits.
- Keep administrator AuthorizeView and server authorization intact; put diagnostic writes in a clearly labeled disclosure with persisted typed draft.
- Snapshot the proposed value/event request when Review is chosen; show target, operation, tag, value/event and UTC timestamp. Editing the draft invalidates an earlier pending review.
- Require explicit Confirm write to call the existing service. Cancel returns to draft with zero writes; busy disables repeated confirm.
- On failure preserve draft/review context and show safe recovery; success records actual service outcome and clears pending intent so Back/refresh cannot replay it.
- Use in-page review, not a new modal. Do not add API or historian-client operations, and never exercise real writes during visual validation.
Step 4 — Verify the change. Re-run Step 2; expected after: PASS for the named tests or all stated visual checks. In a fake/local fixture verify Viewer cannot see controls, Admin can review, cancellation sends no write, slow confirm sends exactly one request, and an error retains input. Use actual UTC boundary values and non-numeric input validation; never write to a production historian for UI acceptance.
Step 5 — Commit. Stage only the listed production/test/evidence files, inspect git diff --cached, then git commit -m "feat: review Historian diagnostic write intent". Do not include generated credentials, runtime data or unrelated edits.
HG-05: Name Galaxy filtering and expansion controls
Files:
- Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/GalaxyBrowserPage.razor - Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Shared/GalaxyTreeNodeView.razor - Modify
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/GalaxyBrowserPageRenderTests.cs
Step 1 — Establish the failing behavior. Extend existing Galaxy render tests using their current snapshot fixture: assert persistent search label association and a named Expand [object] control with collapsed state. Keep service result-cap and lazy render tests; do not materialize 42k attributes merely to test a label.
Step 2 — Run the focused check. From the repository root:
dotnet test tests/ZB.MOM.WW.HistorianGateway.Tests/ZB.MOM.WW.HistorianGateway.Tests.csproj --filter FullyQualifiedName~GalaxyBrowserPageRenderTests
Expected before: search is placeholder-only and node buttons have generic Toggle names.
Step 3 — Implement in small edits.
- Add visible label and Clear search; derive polite count from the applied search result, including capped-results copy.
- Make node label and chevron one named button with expanded state; keep stable per-node controls ID and child lazy creation.
- Preserve read-only metadata semantics: no Watch, write or subscription buttons are added to this gateway.
- After manual reload preserve current search and expansion keys where objects still exist; avoid full expansion by default.
Step 4 — Verify the change. Re-run Step 2; expected after: PASS for the named tests or all stated visual checks. Keyboard-expand a node, filter to zero, clear and verify contextual state. Load a realistic large fixture and confirm initial rendering is bounded by collapsed roots and the flat search cap remains 300.
Step 5 — Commit. Stage only the listed production/test/evidence files, inspect git diff --cached, then git commit -m "fix: name Historian Galaxy browse controls". Do not include generated credentials, runtime data or unrelated edits.
HG-06: Keep submitted query context separate from editable draft
Files:
- Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/HistorianConsolePage.razor - Modify
tests/ZB.MOM.WW.HistorianGateway.Tests/Dashboard/HistorianConsolePageRenderTests.cs
Step 1 — Establish the failing behavior. Add the following to the existing bUnit class. It protects against silently relabeling old results when a user edits the next query.
[Fact]
public void Editing_the_next_query_does_not_relabel_previous_results()
{
var auth = this.AddAuthorization();
auth.SetAuthorized("viewer");
auth.SetRoles(DashboardRoles.Viewer);
Services.AddSingleton<IDashboardHistorianService>(new FakeDashboardHistorianService());
var cut = Render<HistorianConsolePage>();
cut.Find("input.console-tag").Change("Pump01.PV");
cut.Find("button.console-run").Click();
cut.Find("input.console-tag").Change("Pump02.PV");
var context = cut.Find("[data-submitted-query]").TextContent;
Assert.Contains("Pump01.PV", context);
Assert.DoesNotContain("Pump02.PV", context);
}
Step 2 — Run the focused check. From the repository root:
dotnet test tests/ZB.MOM.WW.HistorianGateway.Tests/ZB.MOM.WW.HistorianGateway.Tests.csproj --filter FullyQualifiedName~HistorianConsolePageRenderTests
Expected before: there is no submitted-query context region; the old result set has only a row count.
Step 3 — Implement in small edits.
- Create an immutable submitted query snapshot at dispatch; render tag/range/mode beside returned rows, never bind this heading to the current draft.
- Name the action Run query and show BusyText/aria-busy according to G1; use one caller-owned outcome status.
- Render unsuccessful result in a distinct safe alert, successful zero samples with range-adjustment guidance, and keep numeric quality plus explained text where mapping is reliable.
- Disable duplicate dispatch while running and guard stale completion with request identity if mode/query can change during work; do not introduce parallel historian calls.
Step 4 — Verify the change. Re-run Step 2; expected after: PASS for the named tests or all stated visual checks. Test success, zero rows, invalid range, failed service, slow query and edit-after-success. Keep full numeric quality/source information and UTC context. Confirm ordinary query submission remains one action; write-review behavior stays separate.
Step 5 — Commit. Stage only the listed production/test/evidence files, inspect git diff --cached, then git commit -m "fix: preserve submitted Historian query context". Do not include generated credentials, runtime data or unrelated edits.
HG-07: Flatten signposts without duplicating status
Files:
- Modify
src/ZB.MOM.WW.HistorianGateway.Server/Dashboard/Components/Pages/Home.razor - Modify
src/ZB.MOM.WW.HistorianGateway.Server/wwwroot/css/site.css - Update
docs/ui-validation/technical-light-historian.md
Step 1 — Establish the failing behavior. Capture the current landing page and the concise task-list proposal. This is low-impact composition/copy: use visual and destination checks rather than a test mirroring the DOM layout.
Step 2 — Run the focused check. From the repository root:
dotnet build src/ZB.MOM.WW.HistorianGateway.Server/ZB.MOM.WW.HistorianGateway.Server.csproj
Expected before: the current equal-size panels repeat rail destinations and dilute the read/query/write distinction.
Step 3 — Implement in small edits.
- Replace equal-size signpost cards with a grouped task list: inspect status/health, browse metadata, query history.
- Keep all existing destinations, route names and Admin navigation gates; do not put a new live metric snapshot or polling on Home.
- Keep compact family typography and spacing; distinguish read-only query entry from administrator-only diagnostic actions.
Step 4 — Verify the change. Re-run Step 2; expected after: PASS for the named tests or all stated visual checks. Check all signposts resolve, each has specific accessible link text, one h1 remains, and no duplicate fetch is introduced. Verify 390px and 200% zoom plus the green shell/blue Info distinction.
Step 5 — Commit. Stage only the listed production/test/evidence files, inspect git diff --cached, then git commit -m "style: simplify Historian landing task navigation". Do not include generated credentials, runtime data or unrelated edits.
Cross-cutting state and viewport matrix
| State | Expected contract | Verification |
|---|---|---|
| First load / slow work | Page identity remains; busy action disabled with meaningful busy text; no false successful zero | Delayed fixture and keyboard |
| Healthy | Text label plus status token, sampled time, real scope | Representative fixture |
| Warning / failed dependency | Plain summary, affected scope and recovery; safe detail disclosure | Fault fixture; no raw secret/connection string |
| Refresh fails after success | Keep last good data visibly marked stale; retry does not clear context | Sequential success/failure fake |
| Empty / no matches | Different from loading/failure; clear-filter or next action | Empty source and filtered-to-zero separately |
| Unavailable / unknown | Show unknown/n/a, never substitute numeric zero or Healthy | Null/missing fixture |
| Permission denied | Route and action gates remain server-enforced; nav reflects existing policy | Viewer/Admin/denied accounts |
| Long content | Full identifiers available in detail/copy context; table scroll local | 200-character path and error |
| Keyboard / modal | Visible focus; enter/space activation; real modal inertness and focus restoration | Browser test, not HtmlRenderer |
| Narrow / zoom / motion | 1440×900, 1024×768, 390×844, 200% zoom; reduced motion keeps status feedback | Batched visual pass and at most one confirmation pass |
No runtime timestamps or status values in a mockup are deployment evidence. Keep status domain mapping app-owned. Test color contrast against actual computed backgrounds; screenshots alone do not establish WCAG compliance.
Release and rollback
- Run focused dashboard tests with
dotnet test tests/ZB.MOM.WW.HistorianGateway.Tests/ZB.MOM.WW.HistorianGateway.Tests.csproj --filter FullyQualifiedName~Dashboard; then run the full project once. Keep all existing role, service redaction and write-gating tests. - Build Server and validate CSS/font/module fetches in an isolated host with fake historian responses. macOS cannot establish Windows AVEVA/COM runtime acceptance; record Windows/native integration tests as outstanding unless actually executed.
- No diagnostic write is required against a real historian for this UI release. Use fakes to verify dispatch payload/count, then separate owner-approved runtime validation if needed.
- Save package graph, shared artifact checksum/version, commit IDs, before/after captures, contrast values and completed keyboard/state matrix to the validation record. Redact tokens and connection details from evidence.
- Deploy only through the existing repository release process as a separate authorized action. Changes have no DB/proto/store-forward schema impact.
- Roll back coherently by reverting consumer UI commits and restoring the former package graph (Theme currently 0.5.0, Secrets.Ui currently 0.6.2). Re-run query, Viewer/Admin gating and native status checks. Do not downgrade stored historian values or delete an outbox as part of UI rollback.
Done: all seven findings are covered; no fake snapshot claims, hidden polling, cross-product status drift, or unintended historical writes were introduced.