6 Commits

Author	SHA1	Message	Date
Joseph Doherty	b8208b3312	test+docs(v3-batch4-wp5): 2-node dual-namespace harness tests + address-space docs ... Tests: - OpcUaServer.IntegrationTests/DualNamespaceAddressSpaceTests.cs (NEW, over-the-wire, offline-safe): both namespace URIs registered + distinct; Raw + UNS subtrees browse and read; UNS variable Organizes-references its raw node; single-source fan-out parity (identical value/quality/timestamp on both NodeIds); HistoryRead via either NodeId -> GoodNoData under the shared tagname; WriteOperate gate symmetric across both NodeIds. - Host.IntegrationTests/EquipmentNamespaceMaterializationTests.cs (extended): full deploy -> persisted-artifact -> ParseComposition round-trip carrying both realms, sealing across the redundant 2-node cluster (redundancy non-interference). In-memory harness, offline. Docs (dual-namespace reality): - CLAUDE.md: new "v3 OPC UA Address Space (Batch 4)" section + Batch-4 testing paragraph. - docs/Uns.md: address-space projection (two namespaces, Organizes edge, effective-name leaf). - docs/Historian.md: dual-registration (both NodeIds -> one tagname); updated CLI examples. - docs/ScriptedAlarms.md + docs/AlarmTracking.md: multi-notifier fan-out, ConditionId=RawPath. - docs/ScriptEditor.md: dual-namespace clarification (script tag-path semantics unchanged). Claude-Session: https://claude.ai/code/session_01LVneM3eh1UtJxEisFXgmox	2026-07-16 13:11:34 -04:00
Joseph Doherty	f4f3e17e3e	feat(v3-batch4-wp1): composer/planner emit both Raw + UNS subtrees ... Un-darken the address-space composition for the v3 dual namespace. Composer (AddressSpaceComposer): - Raw subtree: RawContainerNode (Folder/Driver/Device/TagGroup as Object/Folder nodes, keyed s=<RawPath>, parent-before-child) + RawTagPlan (raw tag Variables keyed (realm=Raw, s=<RawPath>) carrying DataType / writable / historize+historian tagname / array shape). Native-alarm intent attaches at the RAW tag (ConditionId = RawPath) with the list of referencing equipment UNS paths (one alarm at the raw tag, not one per equipment). - UNS subtree: UnsReferenceVariable per UnsTagReference, keyed (realm=Uns, s=<Area>/<Line>/<Equipment>/<EffectiveName>), carrying its backing RawPath (Organizes UNS->Raw target + fan-out) and inheriting DataType/AccessLevel from the backing raw tag. Effective name = DisplayNameOverride else backing raw Tag.Name. - All RawPaths flow through one shared RawTopology (RawPathResolver + memoised container paths), byte-parity with EquipmentReferenceMap. - Every new node carries an AddressSpaceRealm (so WP3's applier picks the namespace at the call site). Additive/defaulted model changes only — the un-migrated AddressSpaceApplier still compiles. Planner (AddressSpacePlanner.Compute) + AddressSpacePlan: - Per-realm diff sets: RawContainers + RawTags keyed by RawPath (NodeId) so a rename = remove+add; UnsReferenceVariables keyed by the stable UnsTagReferenceId so a backing-tag rename re-points (BackingRawPath moves, NodeId stable) and a display-name-override edit is UNS-only. - PINNED: raw-tag rename = remove+add in Raw AND re-point in UNS. Classifier folds the new sets in (adds->PureAdd, removes->PureRemove, changed->Rebuild safe default). Tests: AddressSpaceComposerDualNamespaceTests (7), AddressSpacePlannerDualNamespaceTests (8, incl. the rename pin), AddressSpaceChangeClassifierDualNamespaceTests (8); reactivated EquipmentNamespaceMaterializationTests' Batch-4-pending case, re-authored to drive the composer over the seeded config (the artifact-decode seam is WP3). Claude-Session: https://claude.ai/code/session_01LVneM3eh1UtJxEisFXgmox	2026-07-16 09:30:12 -04:00
Joseph Doherty	2c7fc65bae	test(v3): migrate OpcUaServer.Tests + Host.IntegrationTests to v3 dark address space ... Migrate the server composer/applier + 2-node harness tests off the retired Namespace/NamespaceKind + equipment→driver/device binding schema onto the v3 greenfield shape (raw-only Tag; DriverInstance-RawFolderId; equipment via UnsLine). OpcUaServer.Tests (134 build errors -> green, 335 pass / 4 skip): - LIVE (migrated, passing): VirtualTag-historize + ScriptedAlarm composition, composer purity/hierarchy, applier MaterialiseHierarchy + MaterialiseEquipmentTags idempotency (hand-fed applier, not dark). - SKIP dark-until-Batch-4: {{equip}} token expansion, applier equipment-namespace E2E (equipment-tag variable materialization). - RETIRE-with-comment / skip: alias-tag (Tag.EquipmentId binding gone) + device-host equipment binding (architecturally removed). - Add local DarkAddressSpaceReasons Skip-reason constants (mirrors Runtime.Tests). Host.IntegrationTests (green, in-memory): drop deleted-Namespace seeds from MultiClusterScoping + DriverReconnect; reshape EquipmentNamespaceMaterialization to assert the DARK contract (folder nodes decode, EquipmentTags empty despite a seeded v3 raw tag) with the full raw-tag->EquipmentTag materialization kept as a Batch-4-pending Skip. Tests-only; no src/ changes.	2026-07-15 21:41:04 -04:00
Joseph Doherty	859d63178a	fix(harness): make deploy E2E tests pass against real SQL (seed cluster FKs) ... Integration-sweep follow-up #6 (SQL leg). The sweep flagged 7 heavy 2-node deploy/failover/reconnect E2E tests as 'time out under amd64-emulated SQL' and suggested raising deadlines. That diagnosis was WRONG: run against real (native-amd64) SQL on the Docker host, they still hang — even at 4x deadline. Root cause is that these tests had never actually run against real SQL, only the EF in-memory provider, which does NOT enforce foreign keys. Two distinct defects, both hidden by in-memory: 1. Missing FK-parent seed (5 tests). The deploy records a NodeDeploymentState row per node, FK'd to ClusterNode (FK_NodeDeploymentState_ClusterNode_NodeId). The tests never seeded ServerCluster + ClusterNode, so on SQL each node-state INSERT throws and the deploy never seals (waits the full deadline regardless of size). Added TwoNodeClusterHarness.SeedDefaultClusterAsync (seeds a ServerCluster + a ClusterNode per node; Warm/NodeCount=2 to satisfy the SQL CHECK constraint CK_ServerCluster_RedundancyMode_NodeCount AND the ClusterEnabledNodeCountMismatch validator). Called it in DeployHappyPath x2 / Failover / FleetDiagnostics / EquipmentNamespace; fixed DriverReconnect to seed node B + NodeCount=2. 2. Stale EquipmentId (EquipmentNamespace test; pre-existing on BOTH providers). Seeded EquipmentId='eq-1', but the later-added EquipmentIdNotDerived validator requires EquipmentId == DeriveEquipmentId(EquipmentUuid) ('EQ-'+first 12 hex). Fixed the seed to a canonical id + matching UUID. Only surfaced once the FK fix let the deploy reach equipment validation. Also added OTOPCUA_HARNESS_SQL_HOST / OTOPCUA_HARNESS_LDAP_HOST overrides so the harness fixtures can run on the native-amd64 Docker host (avoids arm64 mssql emulation entirely). Verified: the 5 SQL-backed classes go 11/11 green vs native SQL; in-memory default unregressed (12/12). RoslynVirtualTagEvaluatorTests racing test is a pre-existing flaky race (not SQL-backed; passes in isolation) — left as-is.	2026-07-15 06:43:15 -04:00
Joseph Doherty	40e8a23e7c	refactor(opcuaserver): rename Phase7* address-space pipeline to AddressSpace* ... The OPC UA address-space build pipeline was named after a v2-roadmap milestone number rather than its domain. Rename the family to describe what it does (build/diff/apply the OPC UA address space): Phase7Composer -> AddressSpaceComposer Phase7CompositionResult -> AddressSpaceComposition Phase7Planner -> AddressSpacePlanner Phase7Plan -> AddressSpacePlan Phase7Applier -> AddressSpaceApplier Phase7ApplyOutcome -> AddressSpaceApplyOutcome The 9 Phase7*Tests suites follow suit; Phase7ScriptingEntitiesTests -> ScriptingEntitiesTests (it tests the scripting migration, not the pipeline). Log-message prefixes move to the new class names. Pure mechanical rename, no behavioral change. EF migration classes/IDs (AddPhase7ScriptingTables, ExtendComputeGenerationDiffWithPhase7) are immutable and left untouched, as are historical design docs. Build clean; OpcUaServer 261/261, Runtime 272/272, ScriptingEntities 12/12 green.	2026-06-18 19:16:28 -04:00
Joseph Doherty	a5d857d5b2	test(opcua): E2E deploy of an Equipment namespace through the real ConfigComposer ... Seed a 1-area/1-line/1-equipment/1-tag Equipment namespace, StartDeployment via the in-process 2-node harness, and assert the persisted artifact decodes (ParseComposition) to the equipment signal (FullName from TagConfig) + friendly UNS folder names. Covers the ConfigComposer -> ArtifactBlob -> ParseComposition.EquipmentTags seam the unit tests only approximated with hand-built JSON. (OPC UA browse is covered against a real SDK node manager in Phase7ApplierHierarchyTests; the cluster harness binds the no-op sink.)	2026-06-06 15:22:25 -04:00