docs(index): record SDK1 terminal server ownership repair

2026-11-10 17:14:53 -05:00
parent 805e3aac67
commit 16418e48a0
2 changed files with 3 additions and 1 deletions
@@ -406,3 +406,5 @@ AddRoute of the dev Mac (`oee-tagdump-mac`, `10.181.206.245.1.1`) on the two tes
 - **2026-11-10 historiangw#131 completed independently on master `230cef4e`.** Consumes actual published Client/Contracts1.0.0 from gateway release commit `ea9f21c8`; the new direct `AllowUntrustedServerCertificate = UseTls && configuredOptOut` mapping preserves verified TLS defaults and ignores stale certificate options for h2c. Three real local gRPC tests prove strict self-signed rejection before RPC, explicit opt-out success, and h2c success. Whole consumer solution Release build0 warnings/errors; Gateway523pass/6existing live skips, Runtime1,002pass/3existing retired-fixture skips, zero failures; Astra source/security approved. Pushed to master, merged into SDK2 candidate and original checkout fast-forwarded; #131 closed with immutable package hashes/test receipt. No deployment/new gateway capabilities; #78 remains separate. ScadaBridge has no direct HistorianGateway dependency.

  - **Final local verification (SDK2 candidate):** 18,489 executed across63 TRX; 18,478 passed,11 known baseline failures (#796/#798),635 existing skipped results. Test exit1/guard0 preserved. A baseline Runtime test race was causally repaired on master `52d1373e` (#805 closed); original browser different-port NAT limitation was independently reproduced on SDK1.5 (#806 open), and corrected direct fixtures pass5+5. Canonical candidate saturation completed384+1cycles/96restarts within1,425.242seconds with zero generated-factory events/newSDKassemblyloads/lostevents in both fixed windows, but original coldRSS rejection/exit1 remains. The original canonical adapter has only partial diagnostic proof and unsupported ownership/process-memory parity; no accepted RSS denominator. Astra source/security review is closed, release HOLD; #799/#800/#801/ScadaBridge#121 remain open. Latest runbook/evidence and draftPR#802 explicitly record these limits. No SDK2 master merge or deployment.
+
+- **2026-11-10 SDK1 terminal server ownership repaired independently on master `efb9197a` (lmxopcua#807 closed).** Investigation for #799 found the old host stopped the application but omitted the SDK server's terminal Dispose. Exact original1.5.378.182 publications show five server-graph weak targets survive normal stop; one separately gated public Dispose releases all five (timers7→2), without rewriting the original failed diagnostic. Master now guarantees terminal server disposal, elects one cleanup owner and makes repeated/concurrent Dispose callers await shared completion; new startup after disposal is rejected. Five causal REDs became five GREENs; owning server suite1,032passed/0failed/1existing skip and whole solution Release0warnings/errors. Astra verified source, raw TRX, hashes and security/same-PKI two-boot checks. Consumer impact is bounded cleanup on in-process host replacement; namespaces, NodeIds, API-key/ACL behavior and certificate identity are unchanged. This does not claim general concurrent async Start/Dispose support. Frozen83ed880e publications and aggregate oracles remain unchanged; no new RSS denominator or #799/G4 acceptance was adopted. SDK2 remains separate on draftPR#802 and under release HOLD; this master repair does not merge or deploy SDK2. Candidate shared-completion/pre-adoption ownership refinements and native import attribution remain under separate review.