Stabilize Swift 6.3 telemetry ordering tests

[maxches99]

Summary

• What changed: Replaced unstructured per-event telemetry recording tasks in WebSocket tests with a synchronous lock-protected recorder; updated v2.0 DFR and traceability.
• Why: Swift 6.3 exposed nondeterministic recorder scheduling that could invert reconnect_resumed_online and reconnect_success despite ordered production emission.

DFR

• DFR link: NOVA_NETWORK_V2_DFR.md
• Requirement IDs implemented: NFR-4

Traceability

Requirement ID	Code/tests reference
NFR-4	Tests/NovaNetworkClientTests/WebSocketClientTests.swift
Test matrix link/path	docs/TRACEABILITY_PACK_v2.0.md

Test Mapping

Test ID	Type (unit/integration/ui)	Covers requirement IDs	Result
T-GATE-3	unit/integration	NFR-4	50/50 repeated Swift 6.3 runs passed
E2E-v2	e2e	NFR-5, NFR-7	31/31 passed

Analytics Verification

• New/updated analytics requirements are implemented (AR-*) — no production analytics contract change
• Event triggers validated
• Payload schema/properties validated
• Negative path verified (no false success events)
• Evidence: Full 271-test suite and ordered reconnect telemetry assertion.

QA Sign-off

• QA owner: Automated release gates
• Sign-off date: 2026-07-14
• Evidence links (logs/reports/screenshots): PR CI and local verification matrix

Coverage

• Unit test coverage (%): 92.60%
• Coverage is above 90%
• E2E suite executed with RUN_E2E_TESTS=1 swift test --filter E2ECoverageTests
• E2E tests use real public APIs only (no mocks/stubs/fake transports)

Release Notes ("What's New")

• Added or updated — no new user-facing behavior; existing v2.0 notes remain current
• File/path: docs/WHATS_NEW_v2.0.md
• User-facing impact summary: More reliable Swift 6.3 release validation; no SDK API or runtime behavior change.

Rollout

• Feature flag: N/A
• Initial rollout percentage: 100%
• Target segments: CI/test infrastructure
• Monitoring/alerts: Swift 6.2 and Swift 6.3 CI jobs
• Rollback plan: Revert the test-only commit if it causes test infrastructure regression.

Checklist

• Product compliance checked against DFR
• Engineering quality reviewed (architecture/readability/testability/performance)
• No undocumented behavior changes