Files
scadaproj/components/ui-theme/validation/theme-1.0.0/canary/SCADABRIDGE-CANARY.md
T

51 lines
7.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Real CentralUI component canary
This fixture is a disposable local **component canary**, not the complete ScadaBridge application, a new production UI, or a deployment. Source is retained under `scadabridge/`. It references actual CentralUI source from the authorized sister checkout, whose observed commit is `f8c2851d25090474c687cca76ee4fc005fcd521c` on `codex/scada-ui-consistency`; the sister source/pins remained unchanged.
## Boundaries and prerequisites
- Existing local Docker rigs already occupy 9000/9001/9002 and 9100/9101/9102, with shared SQL/LDAP and their own data. They were inspected read-only and were not restarted, rebuilt, seeded or used for this canary.
- This host binds **127.0.0.1:5199** only. It starts no Docker containers. No SQL, Akka, LDAP, management client, fleet data service or mutating application endpoint is registered.
- The real CentralUI MainLayout includes NavMenu, DarkModeToggle, SessionExpiry and DialogHost. The fixture supplies an anonymous AuthenticationStateProvider and the actual local DialogService. The anonymous state keeps real policy-gated administrative/pending-update services out of the render path.
- The root page composes the real MainLayout with real DateTimeRangeFilter and LoadingSpinner plus synthetic local content. `/login` renders the real CentralUI Login component. No real username/password is used. Login/logout POST return 405; session ping/activity endpoints are local no-op responses. Native dialog Confirm/Cancel only resolves a local Task; it cannot perform a fleet command.
- Antiforgery uses ephemeral DataProtection, with no fixture key persistence. The host serves Bootstrap/icons from the actual Host/wwwroot and actual RCL Theme/CentralUI static assets. Local DarkModeToggle writes only this localhost origin's storage.
- .NET SDK 10.0.403 and Python Playwright's installed Chromium were available. The existing documented Playwright Docker server was not running; this pass launched its own independent local Chromium and did not use the parent's shared MCP browser tab.
## Exact baseline run
Cwd: `/Users/dohertj2/.codex/worktrees/scada-ui-consistency/scadaproj`.
```sh
dotnet run --project components/ui-theme/validation/theme-1.0.0/canary/scadabridge/ScadaBridgeUiCanary.csproj --artifacts-path /tmp/scadabridge-ui-canary-artifacts --no-launch-profile --urls http://127.0.0.1:5199
```
The current baseline is default `CanaryThemeVersion=0.5.3`, matching CentralUI's current pin. Launch output is `/tmp/scadabridge-ui-canary-before.log`; execution tool session 75357 owns the running dotnet process. Use `lsof -nP -iTCP:5199 -sTCP:LISTEN` to identify only this fixture listener, then send TERM to that exact process to stop it; do not stop existing ScadaBridge containers. Remove the task-local artifacts directory after the comparison is complete. The parent may retain/relaunch the fixture while completing the authorized before/after comparison.
`GET /canary-provenance` responds with Theme assembly **0.5.3.0**, CentralUI assembly **1.0.0.0**, and the local-only service boundary. `/tmp/scadabridge-ui-canary-artifacts/obj/ScadaBridgeUiCanary/project.assets.json` resolves `ZB.MOM.WW.Theme/0.5.3`.
## Observed baseline
See `scadabridge-before.json`, `scadabridge-login-before.png` and `scadabridge-components-before.png`. Chromium desktop viewport 1440×1000, `prefers-reduced-motion:reduce` set before navigation; measurements taken immediately after DOMContentLoaded, then keyboard traversal after 600ms.
- Actual Login `.login-wrap.rise` still reports animation `rise`, duration `0.4s`, opacity approximately `0.0105` at about 8ms; the component sample's `.rise` panel reports opacity `0` at time 0. Reduced-motion preference was true. The screenshot was captured after the entrance settled, so the JSON, not the screenshot, is the immediate-motion evidence.
- Keyboard Tab reaches the actual login username and DateTimeRangeFilter From input. Both match `:focus-visible`, have no outline (`0px`/none), but have Bootstrap's visible 4px blue box-shadow and changed border. This is a shared focus-style consistency baseline, **not proof of invisible focus**.
- No document horizontal overflow in these two desktop samples, Theme stylesheet HTTP 200, and no page JavaScript errors. No mobile, dark-mode, screen-reader, complete application route or authenticated fleet acceptance is claimed.
## Candidate handoff
Wait for the parent's reviewed immutable Theme package before changing this host's resolution. The fixture's own direct package reference supports `-p:CanaryThemeVersion=1.0.0` plus the approved task-local package source; this is a fixture-only override and does not edit sister source/pins. Stop this baseline process before rebuilding/relaunching against the candidate, or use another verified free loopback port.
Do not assume the root override alone proves the static asset version: inspect the candidate host's restored graph/runtime assembly, static asset manifest and served CSS hashes. Run the same real component/motion/focus observations against the candidate, compare both supported light/dark local overrides, and report actual integration limitations. These after steps are pending the candidate package; this baseline does not close TH-06/07 or the complete TH-04 browser acceptance.
## Candidate-only fixture extension (prepared; not yet built or visually run)
After recording the 0.5.3 observations, the fixture source was extended with actual enhanced TechField (For/HintId/ErrorId, linked hint/error and input validation state), actual TechButton BusyText with 800ms synthetic local success/failure, caller-disabled action, and a caller-owned polite outcome region. These code paths have no data service and cannot write fleet state. The new parameter usage requires the reviewed 1.0.0 candidate; the still-running baseline process uses its already-built 0.5.3 binaries and is unchanged. For a clean re-run of the original baseline, first restore `Components/Pages/Canary.before.razor.txt` to `Canary.razor` and `Components/App.before.razor.txt` to `App.razor` in a disposable fixture copy, not in production source.
The new `wwwroot/canary-adoption.css` is a **fixture-only proposal** for later ScadaBridge adoption, namespaced to `html[data-canary=scadabridge]`. It supplies the full dark accent family, semantic status text inks and readable `--on-accent:#111827`. It also lightens the existing blue accent to #7aa0ef because static pair calculation shows current #4d7fe8 link text is 3.88:1 on current dark card and 4.43:1 on paper; #7aa0ef is 5.71:1 on card, and #111827 on it is 6.84:1. This calculation guides the candidate; it is not a computed-browser contrast acceptance claim. No production ScadaBridge stylesheet or pin was modified. The candidate and dark aliases must be tested with actual served CSS after the parent hands over the reviewed package.
### Four-family candidate route
Candidate-only `/accent?family=default|historian|btdb|overview` composes actual ThemeShell, NavRailItem, TechButton primary/ghost/caller-disabled, a link and semantic Info StatusPill. A closed mapping converts the query choice to the exact approved release-decision values; arbitrary query input is never inserted into CSS. Default blue, Historian green, BTDB teal **#1b7f8e**, and Overview purple use the exact documented deep/focus/tint/border families. This route supplies light-scheme accent state cases. The root actual MainLayout component fixture supplies the separately labelled proposed ScadaBridge dark adoption case. No full sister-app or family-wide dark-theme conformance is implied.
Prepared fixture source is now frozen for parent source review/commit/package provenance. Candidate-only additions have not been built, launched or visually exercised before receiving the reviewed package. The running process continues to serve the original baseline assembly.