36 lines
7.2 KiB
Markdown
36 lines
7.2 KiB
Markdown
# Technical-Light token, recovery and navigation acceptance
|
|
|
|
MX-05/06/08 use shared Theme1.0.1 and delivered Secrets.Ui1.0.1/Abstractions0.6.6; the existing Secrets/Core runtime package remains0.6.2. Exact official nupkg hashes and restored graph are in evidence/mx-final/packages.json. Framework HtmlRenderer/xUnit remain; no bUnit/parser dependency was added to production or tests. No worker/COM/proto/options or production authorization policy changes.
|
|
|
|
## Shared visual ownership
|
|
|
|
Repeated surface/border/hover/semantic text colors now resolve to canonical tokens. Signal fills remain distinct from readable status inks. Bootstrap's important text utilities have explicit host adapters. Theme owns primary normal/hover/active/disabled colors; the measured pointer-focus difference requires one retained token-based local focus rule. Shared keyboard outlines and form focus replace the duplicate local halo; app-specific field/button geometry remains local. Structural native backdrop opacity and menu elevation remain documented local geometry, with menu color derived from ink.
|
|
|
|
Actual paired component measurements use the real Theme buttons and MX host styles. Semantic text contrast is at least5.555:1. Primary normal/hover/active/pointer-focus/keyboard-focus colors match before/after; disabled/busy semantics remain native, busy text is meaningful. Field keyboard focus is2px with no duplicate shadow. Evidence/mx05 contains computed values, source CSS comparison and captured component states. The first immediate-transition probe was corrected to wait for actual state settling. A first busy fixture wait incorrectly awaited the infinite busy spinner; the harness now waits only finite entrances. These are measurement fixes, not product animation workarounds. Local page-owned entrance animations now honor reduced motion with final opaque content.
|
|
|
|
## Recoverable browse failures
|
|
|
|
App-local DashboardDiagnostic renders escaped complete detail through the existing DashboardRedactor boundary. Tree failures expose context-named native disclosure and Retry. Retry shares existing loading callbacks, has a guard before focus await, keeps the affected object's stable toggle focused and announces one recovery. Siblings, watched values and tree state remain. Search/read errors have visible recovery text, and redeploy notification failures retain their existing automatic reconnection. Manual live-read Retry uses the existing read path under a shared single-flight guard; no new automatic retry/poll loop or telemetry was introduced. Existing per-value quality error hover metadata remains outside this tree/global-error task.
|
|
|
|
Four meaningful framework cases cover sensitive detail redaction and long escaped text; existing tree/home/render tests remain. Actual once-failing child fixture verifies full600+character detail, exactly one recovery attempt, retained watched sibling and stable focus at1440/1024/390px and real200% zoom. Initial fixture attempted to fail a leaf whose attributes were already loaded; no child request occurred. That failed harness run is retained, followed by a fixture-only nested child and correct actual failure/recovery proof. A final focused recheck covers the guard refinement. No COM/worker provider runs.
|
|
|
|
## Navigation and real host layout
|
|
|
|
Overview, API keys and Sign out use shared sentence case. Routes, NavRailSection persistence keys, enum text, policy constants and static POST logout/antiforgery are unchanged. Actual MainLayout fixtures cover Admin/Viewer/anonymous visibility, keyboard footer reachability and native narrow navigation. Twelve destination cases verify exactly one active rail item and matching h1/document title for Overview/Browse/API keys at1440/390px for Admin/Viewer; viewers retain read-only key access without create controls. Login remains the shared native POST LoginCard with existing return URL and antiforgery behavior. No login/logout is submitted during browser QA.
|
|
|
|
The fixture now exposes actual production URL aliases for the three destination checks; its standalone native-dialog scenario moved to /native-fixture. Reproduction scripts use that synthetic path. These aliases do not change production routing.
|
|
|
|
## Verification and limits
|
|
|
|
NonWindows solution build:0warnings/0errors. Full gateway: **1460 passed,0failed,6existing platform skips**, after a standard-path restore of the final shared package graph. A prior no-restore full run still read the old standard obj graph while the isolated fixture had the new graph; pre-package-refresh evidence is retained separately and is not the final package proof. Final targeted tests cover subsequent copy/description-only adjustments. Actual MainLayout17-case keyboard/recovery/principal/viewport/reduced-motion matrix has0pageerrors/document overflow; separate12 destination cases pass. Earlier generic-shell17 cases remain history, not proof of the actual rail.
|
|
|
|
Shared Theme assets must be deployed together with their app. Rollback restores the consumer commit/package graph plus matching dialog module and component, never just one side. Previous immutable Theme0.5.0/Secrets0.6.2 artifacts and pre-migration source identify the rollback inputs; no application deployment has occurred. Windows/COM/live LDAP/worker acceptance is not claimed. The shared Abstractions450-character name/tombstone limit requires host inventory before production adoption; legacy-provider default snapshot behavior has the bounded producer compatibility proof. No real secret, historian write, key mutation, database migration or live gateway restart was used for these checks.
|
|
|
|
## Independent identity review corrections
|
|
|
|
The peer review found two concrete identity/lifetime gaps before final commit. Tree Retry now captures node/callback/generation before native focus awaits, invalidates on parameter replacement/disposal, and applies post-await load/error/recovery only to the current captured node. Roots and recursive children have stable object keys. Two actual framework lifecycle regressions defer the native FocusAsync seam, replace parameters or dispose the renderer, then verify no stale callback dispatch; these passed2/2. No initial red is claimed because the production fix existed at the first runnable regression build.
|
|
|
|
Fault summaries/table rows now key their session/source/worker/message identity, excluding the per-snapshot observation timestamp. A real Blazor fixture opens and focuses sessionA's complete diagnostic, then prepends/reorders faults and advances A's timestamp. Before correction, both compact and table modes transferred the open/focused DOM to another session; retained browser JSON records both failures. After correction, both retain A's original focused/open element across that snapshot. This is actual DOM identity evidence, not an HTML snapshot assertion. The final whole gateway suite passes1460/6 after both fixes.
|
|
|
|
The newly introduced diagnostic/supporting-counter disclosures also measure at least44px in an explicitly verified coarse/touch context. Final native recovery/reduced-motion recheck has0pageerrors. Three actual runtime shared DLLs and seven downloaded CSS/font/module assets equal accepted official package bytes (served-assets.json). The fixture uses ephemeral data protection and synthetic principals; no new persistent credential store is required.
|