Summary
Windows support is planned and should be released soon.
Why
The current CLI/server control path relies on Unix signaling and process handling.
Required adaptation
In Unix paths we currently use (for , , , ) together with .
For Windows support, adapt this control flow to Windows-compatible APIs (e.g. Tokio and/or ) while preserving equivalent stop/reload behavior.
Acceptance criteria
- No Unix-only assumptions in Windows code paths
- // behavior is documented for Windows
- README clearly marks Windows as upcoming until release
Summary
Windows support is planned and should be released soon.
Why
The current CLI/server control path relies on Unix signaling and process handling.
Required adaptation
In Unix paths we currently use (for , , , ) together with .
For Windows support, adapt this control flow to Windows-compatible APIs (e.g. Tokio and/or ) while preserving equivalent stop/reload behavior.
Acceptance criteria