Add managed console client and interop scenarios
.NET port / test (macos-latest) (push) Canceled after 0s
.NET port / test (ubuntu-24.04) (push) Canceled after 0s
.NET port / test (windows-latest) (push) Canceled after 0s
.NET port / cpp-conformance (push) Canceled after 0s

This commit is contained in:
2026-09-16 16:55:17 +02:00
parent 82ad4c2811
commit 48c754aed9
9 changed files with 277 additions and 7 deletions
+4 -3
View File
@@ -817,11 +817,12 @@ the required ten-minute Windows/macOS listen test is still a manual release gate
conversation through the C# server**, and a C# `vccli` interoperates with a C++ `vccli` on
the same server. This is the full M0M3 criterion re-proven end to end.
**Checkpoint (2026-09-16):** `VoiceCat.Core` implements TOFU-gated TLS, concurrent correlated
**Complete (2026-09-16):** `VoiceCat.Core` implements TOFU-gated TLS, concurrent correlated
requests, snapshots/events, reconnects, encrypted UDP binding and send/receive stream
lifecycle. Two managed clients exchange text and decoded PCM through the managed server.
The remaining Phase 6 item is the managed console client and its explicit C++ CLI
interoperability scenario.
`VoiceCat.Cli` supports interactive channel text and deterministic headless text/voice runs.
Process tests prove two managed CLIs converse with decoded voice in both configured channels,
and a managed CLI exchanges text and bidirectional voice with the existing C++ CLI.
---