R2-11 TagConfig consolidation (arch-review round 2) #434
Reference in New Issue
Block a user
Delete Branch "r2/11-tagconfig-consolidation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Round-2 arch-review plan R2-11 (findings 01/C-1, 01/P-1 + 05 ReadEnum/Writable/capability — 3-phase strictness rollout).
TagConfigIntent.Parse+DeviceConfigIntentin Commons are the single byte-parity home; the four hand-synced copies (composer, DeploymentArtifact, EquipmentNodeWalker, DraftValidator) delegate; composer parses once per tag (P-1). Permanent 30-blob parity corpus guards compose≡decode.TagConfigJsonreaders in Core.Abstractions replace the sixReadEnumcopies; every driver parser gainedInspect()+ honourswritable(FOCAS forced read-only + capability-matrix pre-flight → BadNodeIdUnknown); Modbus probe parses the factory DTO shape (timeoutMs no longer dropped). NewEquipmentTagConfigInspector+ AdminOps deploy-gate withDeployment:TagConfigValidationMode(Warn default | Error opt-in). AdminUI: Writable checkbox in the six typed editors.22/24 tasks; T22 (AdminUI Writable /run) + T24 (full sweep) deferred to serial heavy pass. Build clean (production projects TreatWarningsAsErrors); parity corpus + 6 driver strictness suites + Commons TagConfigIntent 48 all green; grep gates (MUST-parse-identically / ReadEnum copies) = 0. Plan:
archreview/plans/R2-11-tagconfig-consolidation-plan.md.Landed on
mastervia merge commit1a698cbb(local --no-ff merge). Auto-merged AddressSpaceApplier.cs + DriverHostActor.cs against R2-04/R2-10; verified semantically via OpcUaServer.Tests 286/286 + Runtime.Tests 396/396 + clean build barrier. Phase C runtime-strict flip + T22/T24 deferred. Closing as merged.Pull request closed