Files
lmxopcua/docs/ui-consistency/evidence/ot13-uns-callers

OT13 UNS caller isolation and confirmed-write recovery

Frozen production scope: GlobalUns.razor; GlobalRaw.razor has only the idempotent Dispose guard described below. Tests: UnsCallerPresentationTests.cs and two additional TreeRecovery lifetime cases. No wrapper/service/entity/schema/query-policy changes. Shared Theme1.0.1 and focus helper071148e9 remain adopted.

Target and lifetime contracts

Area/Line/Import callbacks carry the render-local parent generation, and their additive Target changes only when the parent presentation changes. Late area/line edit reads cannot open over a new import or after disposal. The old inline deletion shell now uses ModalFrame, safe Cancel focus, contextual title/description, captured node/generation and busy-close guard. Prerequisite entity reads recheck currentness before dispatching a delete; already-dispatched deletes continue once but cannot put errors/close on replacementB. Cluster/Enterprise/Area/Line/Equipment branches retain their existing service method, scope and row-version semantics.

Every structure read has a version. Only the latest live request can install roots/errors/acquisition time or release its loading state. An explicit Retry rejects duplicate current reads, but an older superseded initial request cannot block recovery after a newer postcommit failure. Successful acquisition is recorded in UTC; failed reads preserve the last good roots and timestamp. Loaded-name filtering and structural expansion remain local and do not search or fetch unloaded tags.

Confirmed write is separate from its later read

Actual successful Area update followed by a structure-read failure previously entered PageErrorBoundary; an actual successful Delete followed by a failed read rethrew IOException. Both discarded the usable view instead of offering read-only recovery. The parent now records the confirmed result, closes only its origin and says that refresh failed while keeping the last loaded structure/time. Retry reads structure only and cannot replay the write. Missing-entity recovery says target unavailable; import acknowledgement says import processed rather than inventing inserted counts. Initial read unavailability remains distinct from confirmed empty data. Full escaped diagnostic text is outside the short polite outcome region. A superseded postcommit refresh is explicitly marked for read-only recovery. Current mutation and current editor-load failures retain their existing handling; this local read recovery changes no backend operation.

Actual evidence

  • caller-valid-red.log:6 behavioral failures for late editor read, stale callback/reload close, pre-dispatch/current-target deletion, already-dispatchedA error, out-of-order structures and disposal. first-caller-fixture-red.log contains an earlier reflection harness that omitted the event's normal render; its selector failures/false-positive disposal case were corrected before valid reds. activation-stub-fixture-error.log records2 failures caused by an unconfigured bUnit activation bool; the valid native adapter result is explicitly configured in the final fixture.
  • confirmed-write-read-failure-red.log:2 actual composed producer-success/read-failure reds. An earlier attempt was blocked by an unrelated mid-edit Hosts file, retained separately; it is not counted as a behavioral red.
  • initial-read-recovery-owner-red.log:2 failures show the visible recovery button could not issue its read while the superseded initial query remained pending. Final cases also release that old initial query while recovery is pending and assert no false empty state/new loading reset.
  • repeat-disposal-red.log:2 failures from calling the page-owned CTS Dispose twice. Both tree pages now return immediately on repeated disposal; first disposal still cancels only view-owned reads. This is a one-line lifecycle correction in GlobalRaw and GlobalUns, with no render or query change.
  • tests.log/tests.trx:44 passed,0 failed/skipped (9 caller +2 composed postcommit +2 read-ownership +7 tree recovery +24 standalone UNS modal cases). Exact classes are in test-classes.json. All discovery uses the explicit private SQL runner. Command: python3 infra/tools/ui-consistency/with_private_sql.py --state <private-state-path> -- dotnet test tests/Server/ZB.MOM.WW.OtOpcUa.AdminUI.Tests/ZB.MOM.WW.OtOpcUa.AdminUI.Tests.csproj -c Release --no-restore --filter "FullyQualifiedName~UnsPostCommitRecoveryTests|FullyQualifiedName~UnsRecoveryReadOwnershipTests|FullyQualifiedName~UnsCallerPresentationTests|FullyQualifiedName~TreeRecoveryTests|FullyQualifiedName~UnsModalAccessibilityTests" --logger "trx;LogFileName=uns-callers.trx" --results-directory /tmp/ot13-uns-final-results.
  • fixture-build.log:zero warnings/errors. Synthetic per-circuit state models only prefixed local IDs, fabricated result metadata and cloned in-memory structure. No real database/fleet writes. The fixture's supported update changes only its memory display model.
  • matrix.json/native.log:FIRST16/16 actual composed scenes: current blocked delete, Area save, Line save, confirmed Area save/failed structure read/read-only recovery ×1440/390 and real200%720/195DPR2. Includes safe Cancel focus,8 actual invalid-name corrections/error associations, unclipped action bounds, full escaped failure, only1 fake mutation per scene, last-good time/data through failure, read-only recovery focus and fresh memory model, no body overflow/page errors. Each verifies served focus helper SHA7f63bd6c5181d0b70edc2e87e086fab4dfba96adabd7a19737f9b3b4f18296d5. Zoom captures use a tall fixture viewport for framing; actual heights are recorded, not represented as a short-phone-height certification.
  • The final two idempotent-disposal guards were added after the16-scene UI matrix and are covered by the final44-test result. Rendered/first-disposal behavior is identical; final whole-app acceptance will build the exact combined revision.

Remaining gate / scope

This is a composed synthetic consumer check, not corporate/fleet integration or a deployment. Equipment, ScriptEdit, inline Host/Driver operations and final route/field inventory remain independently owned OT13 slices. Whole combined suite/package graph/runtime/visual acceptance remains OT14. Per user instruction, VoiceOver speech-output testing is excluded; automated accessibility-tree, keyboard and browser checks remain in scope and no speech-output claim is made. Roll back these scoped source changes for regression; preserve published artifacts/data and accepted shared focus fixes.