[dpazj]

Summary

Refreshes the Sparkplug TCK conformance results for the 0.6.0 release candidate, rerun against the merged release docs (master at #73).

• edge suite: 6 of 7 tests pass. MultipleBrokerTest now runs with the second broker available (inver on port 1884) and records TIMEOUT with 27 passed, 2 failed:
  • operational-behavior-primary-application-state-with-multiple-servers-walk
  • operational-behavior-edge-node-birth-sequence-wait
    The previously not-executed single-server assertion now passes; both failures follow from the missing broker failover.
• host suite: 6 of 6 pass, including SendCommandTest (36 passed, 1 not executed) and MultipleBrokerTest (7 passed, 1 not executed).
• tck/CONFORMANCE.md: updated the results table, documented the two failing edge assertions and the timeout, and explained that the single-server assertion now passes because the second broker is provided (--second-broker); added a note for the TIMEOUT result meaning.
• CHANGELOG.md: known-limitation wording now says edge:MultipleBrokerTest fails its failover assertions.

Phase 2 verification

• cargo update: no package changes
• cargo fmt --all --check: pass
• cargo clippy --workspace --all-targets -- -D warnings: pass
• cargo test --workspace: pass (0 failures)
• RUSTDOCFLAGS=-Dwarnings cargo doc --lib --no-deps --all-features: pass
• cargo +1.85.0 test --workspace: pass
• cargo package --list for all 7 publishable crates: pass

TCK runs

./target/debug/tck-runner --suite edge --docker-image srad-tck \
    --node-cmd ./target/debug/examples/tck-node --timeout 120

./target/debug/tck-runner --suite host --docker-image srad-tck \
    --node-cmd ./target/debug/examples/tck-host \
    --host-app-id foo --client-id client --console-reply PASS --timeout 120

Results and per-test logs: tck/results/1793820997 (edge) and tck/results/1793821208 (host).

Remaining known gap

edge:MultipleBrokerTest still times out because srad-eon has no broker failover. This is documented as a known limitation and does not block 0.6.0.