evo-client's remote mode now runs over RegionSessionClient (QUIC, session v2): snapshot-fed environment and organism views, the camera following the server's view until the user moves it and then driving the interest, intention records with a simulated state, and reconnects with the next grant of a bundle. The launcher reads 160-byte M10 grants and defaults to the dev route. - quic::resolve_ipv4 shared by the client and evo-session-probe - evo-session-probe grants: owner-only bundles of 1-64 grants - evo-server --m10-max-grant-lifetime (dev only, 60..3600 s) - presets client-network/client-package build QUIC; msquic links the CRT fully static; msquic.dll and msquic/OpenSSL licences in the Windows package - client-remote-session test against a loopback region - ADR-0093/0091/0086 amendments, M10_CLIENT_SESSIONS guide, validation Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.5 KiB
Windows client package (M9.8e)
Decision: ADR-0086. Windows development host
only; requires Visual Studio 2022 C++ tools and prepared SDL, Dear ImGui, Mbed TLS and
msquic sources (cmake -P tools/prepare-sdl3.cmake, prepare-imgui.cmake,
prepare-mbedtls.cmake, prepare-msquic.cmake), plus Strawberry Perl and NASM for
msquic's OpenSSL build (ADR-0090).
Build a package
powershell -NoProfile -ExecutionPolicy Bypass -File tools\client\package-windows.ps1
It refuses uncommitted tracked changes (-AllowDirty packages them with a -dirty
identity), configures client-package with EVO_BUILD_IDENTITY=g<12 hex>, builds,
runs the client/network/quic-session CTest suite, stages the allowlisted files and writes
build/packages/evo-client-windows-x64-<identity>.zip and .zip.sha256. The staged
folder stays next to the ZIP. -Clean deletes build/client-package first; the
build log is build/client-package.log (+ .err).
Package content (exact): evo-client.exe, SDL3.dll, msquic.dll, README.txt,
BUILD-INFO.txt, THIRD-PARTY-NOTICES.txt, SHA256SUMS.txt and LICENSES/
(SDL3, its HIDAPI, yuv2rgb, stb_image and Khronos notices, Apache-2.0, Mbed TLS,
Dear ImGui with fonts and stb notices, msquic, OpenSSL). The tester README template is
tools/client/README-package.txt; the notice index is
tools/client/THIRD-PARTY-NOTICES.txt. No credentials, grant bundles, CA files or
settings are ever packaged; dev CA and grants are issued to testers separately.
Verify a package
powershell -NoProfile -ExecutionPolicy Bypass -File tools\client\verify-windows-package.ps1 -Zip build\packages\<name>.zip [-Interactive]
powershell -NoProfile -ExecutionPolicy Bypass -File tools\client\package-selftest.ps1 -Staged build\packages\<name> -DynamicRuntimeImage build\client-network\evo-client.exe
Verification works without Visual Studio (copy tools/client with the ZIP): digest,
exact content and SHA256SUMS, PE imports of all three images limited to system DLLs plus
SDL3.dll and msquic.dll (no C runtime DLLs),
credential and profile-path scan, then the extracted client runs with only the
Windows system directories on PATH. -Interactive opens a real window for 3 s.
The self-test proves each guard refuses its defect.
Not yet covered
- Gitea Actions publication: needs a Windows runner (none registered).
- A clean Windows VM run and hardware/DPI qualification: M9.8g.
- Code signing: none; Windows SmartScreen may warn on first run.