Accept interaction convergence and record split package rollout
This commit is contained in:
@@ -166,7 +166,7 @@ each project's **code-verified current state**, and the **gaps** between. See
|
||||
| Config + validation (options / startup validation) | Adopted (lib `0.1.0`, on the feed; **all 4 apps**, pushed — the "local only / not yet pushed" caveat was stale) | Shared `ZB.MOM.WW.Configuration` lib | [`components/configuration/`](components/configuration/) | [`ZB.MOM.WW.Configuration/`](ZB.MOM.WW.Configuration/) |
|
||||
| Audit (event model + writer seam) | Adopted (lib `0.1.0`, on the feed; **all 4 apps**, pushed to origin) | Shared `ZB.MOM.WW.Audit` lib | [`components/audit/`](components/audit/) | [`ZB.MOM.WW.Audit/`](ZB.MOM.WW.Audit/) |
|
||||
| Galaxy Repository (object-hierarchy SQL browse + gRPC service) | **Adopted** (feed `0.1.0` + `0.2.0`; consumed at `0.2.0` by HistorianGateway **and mxaccessgw**, whose Server wires `AddZbGalaxyRepository` — verified 2026-07-18; the prior "mxaccessgw adoption is a follow-on" claim was stale) | Shared `ZB.MOM.WW.GalaxyRepository` lib | _(design in histsdk + design doc 2026-06-23)_ | [`ZB.MOM.WW.GalaxyRepository/`](ZB.MOM.WW.GalaxyRepository/) |
|
||||
| Secrets (encrypted store + `${secret:}` resolution) | **2026-11-09: source at `0.6.6`, UNPUBLISHED** — Sqlite 10.0.13, concurrency-safe SQLite init (#25), order-independent SqlServer/Akka registration + contentRootPath (#30/#31), `${secret:}` survives reload (#32), Akka actor starts with the host (#33), CLI value via stdin/prompt (#35), 13 P3 review fixes (#45). Built; family version **`0.6.3`** (published 2026-09-28; apps still pin `0.6.2`). Pins: **all four apps `0.6.2`** (verified against each repo's checked-in pins AND its origin default branch 2026-09-03 — the earlier "OtOpcUa unpushed / mxgw 0.6.0 / ScadaBridge 0.5.1" notes were stale). **Target `0.6.1`+, never `0.6.0`, and use the 4-arg `AddZbSecrets(..., contentRootPath)` overload at every pre-host `${secret:}` expander call site — the pin alone does not close the hole.** `Secrets:SqlitePath` must be absolute and outside the content root (fail-closed, no opt-out; the 2026-08-09 mxgw outage). Production topologies decided (scadaproj#3/#4 closed): OtOpcUa = Akka pair-local (`Replicator.AkkaDotNet`; it never used the gRPC hub); **ScadaBridge retired the gRPC secrets hub for itself (2026-09-28, ScadaBridge `main` @ `23a139a4`, follow-ups `2650f794`) — sites now receive secrets via Deploy Artifacts instead of the hub, central still on ONE shared SQL store (`Secrets:Store:Provider=SqlServer`, `0.5.1` minimum)**; both default-off elsewhere. **`0.6.3` (hub sweep outcome logging + public `ISecretsHubSyncStatus`) is PUBLISHED to the feed (2026-09-28) but pinned by no app** — ScadaBridge, its original motivation, retired the hub for itself; no hub consumer remains (OtOpcUa is Akka pair-local), so nothing can usefully pin it — **`ZB.MOM.WW.Secrets.Replicator.Grpc` is DEPRECATED (scadaproj#8, 2026-11-09):** out of the Secrets solution/pack, `IsPackable=false`, entry points `[Obsolete]`; `0.6.3` is its last published version (feed unlisting left to the owner). Full narrative (`0.1.x`→`0.6.3`, incidents, live gates, container caveat, `NU1102` note): [`ZB.MOM.WW.Secrets/CLAUDE.md`](ZB.MOM.WW.Secrets/CLAUDE.md). | Shared `ZB.MOM.WW.Secrets` lib (5 packages + CLI) | [`components/secrets/`](components/secrets/) | [`ZB.MOM.WW.Secrets/`](ZB.MOM.WW.Secrets/) |
|
||||
| Secrets (encrypted store + `${secret:}` resolution) | **UI1.0.1 and Abstractions0.6.6 published and byte-verified for the UI consistency rollout.** Core/backend source0.6.6 remains unpublished; existing app runtime package0.6.2 pins are preserved. Release evidence, dependency/name-limit caveats and historical deployment constraints: [`ZB.MOM.WW.Secrets/CLAUDE.md`](ZB.MOM.WW.Secrets/CLAUDE.md). | Shared `ZB.MOM.WW.Secrets` lib (5 packages + CLI) | [`components/secrets/`](components/secrets/) | [`ZB.MOM.WW.Secrets/`](ZB.MOM.WW.Secrets/) |
|
||||
| LocalDb (embedded cache + 2-node sync) | **`0.3.8` PUBLISHED 2026-11-13 (scadaproj#57) and pinned by both consumers** (OtOpcUa `47f0b98c`, ScadaBridge `8e32f353`; not deployed) — sync streams end on `ApplicationStopping` and new ones are refused `Unavailable` while stopping, so a graceful stop of the passive node no longer waits out Kestrel's drain (lmxopcua#906; both apps keep their host-side interceptor). Earlier, `0.3.7` (2026-11-12, scadaproj#53): Sqlite 10.0.13; sync endpoint enforces `ApiKey` (#36; set the same key on both nodes); FK-ordered snapshots, PK upserts (no INSERT OR REPLACE), drift check on snapshots (#37–#39); `AUTOINCREMENT` tables refused at `RegisterReplicated`. **#16 fixed in `0.3.7`:** a tombstone is pruned only once past `TombstoneRetention` AND held by the peer (retention restarts at delivery), so a peer offline past retention no longer resurrects deleted rows; optional `TombstoneHardCap` (default off) bounds ledger growth during an outage. **Adopted** by ScadaBridge (Phases 1+2 merged; pins **`0.3.8`**) and OtOpcUa (Phases 1+2 merged; pins **`0.3.8`**; deployed builds still `0.3.4`) — no version skew remains (every release is wire-compatible, so one would be supported). Replication is **default-OFF**; enabled on the docker rigs' site-a pairs and on the **QA pair vq03/vq04** (ScadaBridge site pair + OtOpcUa pair — OtOpcUa's sync only actually CONNECTED after the 2026-09-10 `b8b4c18f` upgrade; the old build answered the sync POST with the login 302); DEV vd03 is single-node. Operational constraints: a pair stops/starts together (no rolling upgrade), the sync `ApiKey` must match on both nodes, and from `0.3.7` the tombstone ledger grows while a peer is down (no more resurrection past `TombstoneRetention`). Full release narrative (`0.1.1`→`0.3.8`) + gates: [`ZB.MOM.WW.LocalDb/CLAUDE.md`](ZB.MOM.WW.LocalDb/CLAUDE.md). | Shared `ZB.MOM.WW.LocalDb` lib | [`docs/plans/2026-07-17-localdb-design.md`](docs/plans/2026-07-17-localdb-design.md) + the two adoption designs ([ScadaBridge](docs/plans/2026-07-19-scadabridge-localdb-design.md), [OtOpcUa](docs/plans/2026-07-20-otopcua-localdb-design.md)) | [`ZB.MOM.WW.LocalDb/`](ZB.MOM.WW.LocalDb/) |
|
||||
|
||||
Each hosted library directory carries its own `CLAUDE.md` with the full version narrative, consumer matrix and
|
||||
|
||||
File diff suppressed because one or more lines are too long
@@ -0,0 +1,34 @@
|
||||
# G2 common interaction acceptance and extraction decision
|
||||
|
||||
Status: interaction recipe verified across ScadaBridge managed overlays, ignitionoee registry native dialogs, and the MX/OEE router native pilots; retain validated app-local adapters for this release. Theme1.0.1 remains the common visual authority. No new package/API is introduced by this decision.
|
||||
|
||||
| Contract | MXAccess pilot | ignitionoee second pilot |
|
||||
|---|---|---|
|
||||
| Native modal lifecycle | `260d58af`, `docs/ui-validation/technical-light-dialogs.md` | `fb192405`, `docs/ui-validation/technical-light-family.md` |
|
||||
| Open/close, inert background, safe initial focus, native Tab/Escape | Actual four-viewport/browser proof; native browser chrome distinguished from document focus | Actual15/22/8 loaded-editor interaction cases |
|
||||
| Single active presentation, generation guards, pending cancel, disposal/import race | Deferred-import/lifecycle browser checks;343 dashboard tests | Same lifecycle contract adapted to17 modal instances/15 callers;1705 UI tests after follow-up |
|
||||
| Busy operation ownership | Caller owns operation and typed fields, JS owns DOM only | `ecf1380d`: disabled body fieldset plus detached submission snapshot before authorization await; three actual busy viewport cases |
|
||||
| Validation/recovery | Existing API-key validation remains visible outside long scroll body | Caller validation/footer remain outside disabled body; safe return focus |
|
||||
|
||||
Native Tab uses the browser's top layer. Browser chrome may receive focus; while the document has focus, focus must remain in the dialog. The MX/OEE router adapters do not add a custom Tab trap. This statement does not apply to the registry or ScadaBridge managed overlay. A rendered busy marker is reinforced by caller single-flight guards; no DOM helper invokes operations or receives secret values.
|
||||
|
||||
## Master-plan comparison: ScadaBridge and registry
|
||||
|
||||
| Responsibility | ScadaBridge managed overlay | ignitionoee registry native dialog |
|
||||
|---|---|---|
|
||||
| Presentation | App-owned `DialogHost.razor`/drawer with named modal roles; actual `dialog.js` activates the presentation | Actual `registry/src/Registry.Host/wwwroot/driverCatalog.js` calls native `showModal` |
|
||||
| Keyboard/background | Synchronous app Tab boundary handling and ancestor-sibling inert locks; typed Escape cancellation | Native top-layer modal **plus existing explicit Tab boundary wrap**; Escape routes to `DismissEditor` |
|
||||
| Initial/return focus | Caller initial selector; connected-trigger focus checked for actual success, then temporary-tabindex heading/main fallback | Caller initial focus; connected-trigger/fallback restoration, without the same verified disabled/unfocusable-target fallback contract |
|
||||
| Lifetime/body state | Per-overlay state, single-active guard, previous inert/body-lock restoration, detached-node observer | App-owned body-overflow restoration and native close lifecycle |
|
||||
| Domain state | Existing typed Confirm=false, Prompt=null/custom cancellation and DialogService resolution | Driver draft, revision guards and registry busy bridge remain local |
|
||||
| Actual acceptance | `87c882ec` plus final `d370dbd3`: native focus/cleanup regressions, full1597 tests, final actual-component integration/preferences | `RegistryWorkflowsTests.Driver_catalog_filters_and_modal_preserve_drafts_focus_and_revision_guards`: actual `:modal`, Name focus, Escape/return, stale revision/draft recovery, safe fixture save/390px bounds; registry11 tests and13 width/zoom cases |
|
||||
|
||||
The registry author independently reviewed this comparison against current source and recorded runtime evidence. Do not describe all four implementations as interchangeable native lifecycle adapters. Shared requirements are naming, safe initial focus, managed background interaction, cancellation, cleanup, honest busy/outcome behavior and preserved domain state; presentation and focus-restoration implementations currently differ.
|
||||
|
||||
## Decision
|
||||
|
||||
The common **behavior recipe** is stable; the tested **public component ownership** differs. MX takes caller-owned title/description IDs, sizing classes and complete child chrome. OEE generates a title ID, owns the initial-focus heading/body/disabled fieldset, and separates its footer. The second pilot exposed an important caller requirement: native modal busy state alone does not freeze editable data or protect post-await writes. Those submissions now use detached snapshots and real authorization checks in their own domain code. Secrets also requires target-specific reveal/mutation isolation rather than a generic editor contract.
|
||||
|
||||
Retain these tested local adapters and the existing Theme recipe. Extracting only the apparently similar markup now would either discard these tested contracts or add options before another caller has established their required combinations. Keep the shared package free of domain state/services. A later extraction must be a separate reviewed change/release with two-host lifecycle and busy-submission tests before caller migration; it is not silently bundled into this visual rollout. Existing local adapters remain covered by their project tests and browser fixtures.
|
||||
|
||||
This closes G2's two-consumer interaction and explicit extraction-decision requirement. It does not close G3, remaining project tasks, or deployment acceptance. Filter/table conventions are also exercised in the completed Overview and ScadaBridge batches; their data/DTO ownership remains local and is not replaced by speculative shared filtering state.
|
||||
@@ -0,0 +1,28 @@
|
||||
# Independent ScadaBridge SB01–03 peer review
|
||||
|
||||
Reviewed 2026-11-13 against the actual sister checkout based on cdd3adf6, with SB01–03 changes pending at review time. Read-only source review plus one narrowly scoped native Chromium focus probe; no sister source/test edits, broad suite rerun, operations endpoints or deployment.
|
||||
|
||||
## Concrete finding
|
||||
|
||||
**P2 — Connected does not guarantee a usable focus restoration target.** `src/ZB.MOM.WW.ScadaBridge.CentralUI/wwwroot/js/dialog.js:33` enters its trigger branch whenever the captured element remains connected and outside inert ancestry. A disabled, hidden or otherwise nonfocusable trigger meets those checks; `.focus()` silently fails, and the heading fallback never executes. Removing the closed overlay then leaves focus on BODY, interrupting keyboard position.
|
||||
|
||||
Reproduced with the unchanged actual script in a disposable Chromium document: focus a native trigger button → activate the overlay → disable the still-connected trigger → remove the overlay → await the script's MutationObserver. Observed `active=BODY`, heading tabindex absent, modal-open=false, inert count0. This is a native lifecycle reproduction, not a claim that a specific live fleet route disables its trigger during dismissal.
|
||||
|
||||
Recommendation: after attempting trigger focus, verify `document.activeElement === trigger`; otherwise use the existing logical heading/main fallback. Filtering disabled/hidden targets is useful, but verifying actual focus also covers programmatically captured nonfocusable headings. Add a focused regression for disabled/hidden connected triggers alongside disconnected-trigger coverage. Retain current typed cancellation, single-active-overlay guard, lock cleanup and deferred temporary-tabindex removal.
|
||||
|
||||
## Reviewed behavior without an additional finding
|
||||
|
||||
- DialogHost uses per-instance IDs for overlay/title/prompt and confirmation description; prompt label targets the actual input. It preserves Confirm=false, Prompt=null and custom typed default cancellation through DialogService.Resolve; disposal unsubscribes before cancelling any pending local result. The original service second-dialog guard remains.
|
||||
- The actual DOM keydown listener owns synchronous Tab prevention; native-event filtering excludes disabled, hidden/inert and negative-tabindex controls. Escape's typed cancellation stays in Blazor. Single-active presentation rejection prevents sibling/descendant modal lifecycle ambiguity. Detached-node observer cleanup restores prior inert/body-lock state. Drawer routes rejection/Escape through its existing OnClose callback and deactivates on disposal.
|
||||
- Sampled OPC UA and Mx Gateway field/error changes preserve the original EntityName exact/suffix matching logic. Conditional invalidity/describedby and rendered error ID use the same helper/key. Newly added text/number/select IDs are per-component-instance scopes. Existing primary/backup checkbox IdPrefix callers remain explicitly distinct in DataConnectionForm. No sampled field was newly assigned an unrelated validation error or bypassed a validator.
|
||||
- MultiSelect toggle name combines the visible field ID and its unique current-summary ID. Its individual checkboxes retain wrapping labels. DataTable's new visible search label targets its instance ID rather than relying on placeholder text.
|
||||
|
||||
## SB03 acceptance boundary
|
||||
|
||||
The batch report correctly leaves SB03 incomplete. Source associations are evidence of intended relationships, not proof of the rendered accessibility tree or control internals. TreeView currently names every checkbox “Select tree item” (`Components/Shared/TreeView.razor:114`); contextual tree names are an already documented pending item. Sampled repeated SchemaBuilder property names/types are also generic; native/editor/group context and Monaco internals require their promised rendered checks. Help descriptions, aggregate errors, repeated editor IDs and transport/notification/instance runtime samples remain under the author's explicit pending verification.
|
||||
|
||||
No new contradictory SB03 completion claim was found in the reviewed report. Do not infer all30+ component runtime acceptance from source-group JSON, regex counts or the passing full suite. This review makes no shared ledger/gate change. Address the concrete focus-target finding before lifecycle acceptance; the remaining known SB03 work stays open.
|
||||
|
||||
## Resolution checkpoint
|
||||
|
||||
The original disabled/hidden connected-trigger finding was corrected in the accepted SB01–02 batch `87c882ec`: current `dialog.js` checks whether trigger focus actually succeeded and otherwise uses the existing heading/main fallback. Focus cleanup/lifecycle regressions and rendered browser proofs were accepted. The originally pending SB03 work subsequently passed scoped composite labels, native editor/Monaco/contextual tree and help/error checks (`915a8a59` plus `102cbb2e`). This historical review's incomplete status describes its original checkpoint, not the final chapter; final chapter acceptance is `d370dbd3`,1597 tests, with explicit representative-runtime/deployment limits in the sister verification report.
|
||||
@@ -84,6 +84,8 @@ Execute [BU-01–BU-10](2026-11-12-scada-ui-consistency/BUnit.md). Seven test pr
|
||||
|
||||
**G2: interaction convergence** occurs after two representative dialog/filter/table implementations meet the shared recipes. Compare ScadaBridge's managed dialog and ignitionoee registry's native dialog before extracting generic behavior. Extract only stable common behavior in a later Theme release; domain editors and state logic remain local. G2 does not block independent repairs or G1's recipe publication.
|
||||
|
||||
**Execution checkpoint:** G2 interaction comparison is accepted in [G2 evidence](../../components/ui-theme/validation/interaction-pilots/G2.md): ScadaBridge managed overlays and registry native dialogs retain distinct tested lifecycle ownership, with MX/OEE router native pilots providing additional busy/disposal proof. Retain local adapters and the shared recipe; any later extraction requires a separate two-host tested release. G3 remains open.
|
||||
|
||||
After G1/required shared UI releases, orders 5–9 can run in parallel with separate repo ownership. The table is a safe serial execution order if only one engineer is available. Do not release each application after a different unresolved token/API contract.
|
||||
|
||||
## Shared APIs and migration rules
|
||||
|
||||
@@ -97,3 +97,9 @@ cross-page contracts remain in progress. G2/G3 and whole100-task objective stay
|
||||
Secrets UI1.0.0/Abstractions0.6.6 delivery passed legacy66 checks and actual two-host44 checks. Subsequent dark composition exposed two obsolete metadata color fallbacks (2.658:1). UI1.0.1 centrally fixes them; independent review,81 source tests, exact official publication and empty package/HTTP cache inference/two-host builds passed. Actual dark6.761/light5.564 contrasts verified. Consumers now target UI1.0.1/Abs0.6.6/Theme1.0.1 with Core/backends preserved. No deployment.
|
||||
|
||||
ScadaBridge03–12 accepted through9dbfe7bc,1591full tests and corrected actual light/dark/zoom/coarse proofs. MX01/03/07 acceptedc9a6c31c; MX04 narrow fault message correction is in progress. OEE02 native pilot plus frozen busy submissions accepted through ecf1380d (1705tests); OEE05 full long-rail acceptance51a546d8 supersedes its earlier representative evidence; OEE08 responsive/touch acceptedcac2e4e5. Native OEE runtime/theme acceptance, remaining projects and G2/G3 stay open.
|
||||
|
||||
## Interaction convergence and ScadaBridge final checkpoint
|
||||
|
||||
G2 accepted with explicit managed/native comparison and retain-local extraction decision in validation/interaction-pilots/G2.md. Registry native Tab handling is recorded distinctly from MX/OEE router behavior; no generic component/package was introduced. TH09 is complete; G3 remains open.
|
||||
|
||||
ScadaBridge final d370dbd3 passes1597 tests, exact delivered shared package/runtime hashes and retained Core/backend pins. Deterministic slowA/fastB filter callback test caught older completion overwriting Last submitted; captured submitted state now updates before awaiting caller. SB00/13–15 complete. Full source route inventory is distinguished from representative actual-component runtime coverage. MX04b06921ce accepted nine actual overview cases; MX05/06/08 final package graph/build/browser acceptance and peer review are underway.
|
||||
|
||||
@@ -444,3 +444,15 @@ explicitly includes browser chrome in the permitted focus scope. Keep native Tab
|
||||
behavior; test outside application controls remain inert. The illustrative snippet
|
||||
above is stricter than that native-browser acceptance condition and must not force
|
||||
an unnecessary custom Tab trap.
|
||||
|
||||
|
||||
MX-04's concrete affected-session route requires the existing shared app component
|
||||
`Dashboard/Components/Shared/FaultList.razor` in its file set. Add encoded links to
|
||||
the existing session route without changing snapshot filtering/policies. For long
|
||||
already-exposed fault messages, use the same named native diagnostic disclosure
|
||||
as the Overview/Browse recipe instead of hover-only title text. No new data fields,
|
||||
queries or logging payloads; retain original message escaping and read boundaries.
|
||||
|
||||
### Execution clarification: MX04–08 composition and diagnostics
|
||||
|
||||
MX04 adds an app-local compact FaultList mode for Overview: messages lead at narrow widths while every existing snapshot field remains visible; detailed tables elsewhere retain their existing mode. MX06 adds app-local DashboardDiagnostic to preserve complete escaped detail through the existing DashboardRedactor boundary, and shares the existing live-read path with manual Retry under a single-flight guard. No new backend request/protocol or polling interval. MX08 also updates ApiKeysPage's visible title/action casing to match its rail entry. Actual MainLayout fixtures validate unchanged URL/section/policy/logout contracts; fixture-only aliases are explicitly separate from production routing.
|
||||
|
||||
@@ -282,12 +282,12 @@
|
||||
"title": "Publish G1 and govern shared extraction (DS-05/06)",
|
||||
"chapter": "Theme.md",
|
||||
"line": 330,
|
||||
"status": "in_progress",
|
||||
"status": "completed",
|
||||
"prerequisiteGates": [
|
||||
"GB"
|
||||
],
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task.",
|
||||
"evidence": "components/ui-theme/validation/theme-1.0.0/ACCEPTANCE.md",
|
||||
"evidence": "Exact Theme1.0.0/1.0.1 official delivery accepted; G2 comparison/extraction decision components/ui-theme/validation/interaction-pilots/G2.md. Validated local adapters retained; G3 remains open.",
|
||||
"remaining": "G1 release/delivery passed; G2 interaction comparison and extraction decision follow representative consumer pilots."
|
||||
},
|
||||
{
|
||||
@@ -464,12 +464,12 @@
|
||||
"title": "Compatibility adoption and baseline captures",
|
||||
"chapter": "ScadaBridge.md",
|
||||
"line": 49,
|
||||
"status": "in_progress",
|
||||
"status": "completed",
|
||||
"prerequisiteGates": [
|
||||
"GB"
|
||||
],
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task.",
|
||||
"evidence": "Theme1.0.1 adoption verified (20885b61); full-route baseline and published Secrets adoption remain pending per ScadaBridge verification record."
|
||||
"evidence": "ScadaBridged370dbd3; official UI1.0.1/Abs0.6.6/Theme1.0.1 hashes, full44page/57route source baseline plus Secrets route,1597tests; explicit representative-runtime limits."
|
||||
},
|
||||
{
|
||||
"id": "SB-01",
|
||||
@@ -620,33 +620,36 @@
|
||||
"title": "Reconcile theme palette ownership safely",
|
||||
"chapter": "ScadaBridge.md",
|
||||
"line": 208,
|
||||
"status": "planned",
|
||||
"status": "completed",
|
||||
"prerequisiteGates": [
|
||||
"GB"
|
||||
],
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task."
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task.",
|
||||
"evidence": "ScadaBridged370dbd3; existing sb-theme/dark ownership retained, eight actual persistence cases."
|
||||
},
|
||||
{
|
||||
"id": "SB-14",
|
||||
"title": "Simplify audit filters and refuse invalid exact ids",
|
||||
"chapter": "ScadaBridge.md",
|
||||
"line": 219,
|
||||
"status": "planned",
|
||||
"status": "completed",
|
||||
"prerequisiteGates": [
|
||||
"GB"
|
||||
],
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task."
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task.",
|
||||
"evidence": "ScadaBridged370dbd3;26 filter regressions including deterministic out-of-order callback red\u2192green; actual hidden-filter/clear/UTC acceptance."
|
||||
},
|
||||
{
|
||||
"id": "SB-15",
|
||||
"title": "Consolidate domain status visuals and final acceptance",
|
||||
"chapter": "ScadaBridge.md",
|
||||
"line": 239,
|
||||
"status": "planned",
|
||||
"status": "completed",
|
||||
"prerequisiteGates": [
|
||||
"GB"
|
||||
],
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task."
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task.",
|
||||
"evidence": "ScadaBridged370dbd3; thin semantic markers, retained full flow outcomes and opaque pending text."
|
||||
},
|
||||
{
|
||||
"id": "OT-01",
|
||||
@@ -843,11 +846,12 @@
|
||||
"title": "Make overview prioritize faults while preserving counters",
|
||||
"chapter": "MxAccessGateway.md",
|
||||
"line": 228,
|
||||
"status": "in_progress",
|
||||
"status": "completed",
|
||||
"prerequisiteGates": [
|
||||
"GB"
|
||||
],
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task."
|
||||
"dependencies": "GB is mandatory before every UI task; additional G1/G2/chapter dependencies remain in the master and named task.",
|
||||
"evidence": "MxAccessGatewayb06921ce; three framework tests, nine actual healthy/mixed/zero browser cases with complete14counter inventory, narrow fault messages, keyboard full diagnostic."
|
||||
},
|
||||
{
|
||||
"id": "MX-05",
|
||||
|
||||
Reference in New Issue
Block a user