Repository navigation
ServerFS v0.23.2
ServerFS v0.23.2 — Native Windows Deterministic Repo Ops
ServerFS v0.23.2 is a maintenance release that extends independently gated Deterministic Repo Ops to validated native Windows 11 x64 deployments, alongside the Linux Host Bridge support introduced in v0.23.0 and validated native Apple Silicon macOS support added in v0.23.1.
Repo Ops keeps the same narrow public contract: four MCP tools (inspect_repo, run_repo_action, commit_repo_changes, push_repo), operator-owned fixed/integrity-pinned actions, explicit repository mutations, and no generic shell or caller-controlled executable/argv/environment/remote/ref/force surface. Repo Ops does not select a model, create an Agent task/provider session, or fall back to Agent delegation.
Windows-native containment
v0.23.2 closes the Windows-specific execution gaps required to make that existing contract native rather than merely portable:
- Workdir/repository validation rejects NTFS reparse points and junctions before Repo Ops execution.
- Repo Ops child processes are created suspended, assigned to the Bridge-owned Job Object, and only then resumed.
- Timeout, cancellation and output-overflow cleanup converges the descendant process tree before the shared writer lease is released.
- If descendant cleanup cannot be proven, the operation fails closed and keeps the writer lease until an external Bridge generation restart, rather than exposing a potentially concurrent writer.
- Hardened Git-for-Windows execution stays non-interactive with a narrow environment, disables hooks/signing/askpass/SSH overrides, and uses the native
NULsink where needed.
The Windows lifecycle remains current-user and non-elevated through Task Scheduler 2.0; this release does not introduce SCM/LocalSystem services, administrator requirements, a generic command executor, or a second repository policy model.
Windows acceptance
The release candidate passed the Windows CI-equivalent product gates and a live public-MCP acceptance on the managed 0.23.2 runtime:
- Windows Agent root gate excluding local D9: 364 passed, 76 skipped.
- Agent Bridge full suite: 666 passed, 103 skipped.
- Root Repo Ops focused tests: 20 passed, 6 skipped.
- Windows Bridge Repo Ops focused tests: 38 passed, 2 skipped.
- Agent Skills suite: 28 passed, 2 skipped.
- Three-wheel
v0.23.2METADATA version gate: 3/3 PASS. - Documentation site: 39 pages built successfully.
- Final Agent Plugin validation: 21 members / 7 runtime Skills, CRC valid.
For the live acceptance, a disposable workdir used Agent mode disabled and Repo Ops enabled, a disposable local Git worktree, and a local file:// bare upstream. The installed 0.23.2 stdio MCP Server exposed 27 tools through the managed 0.23.2 Bridge. Agent submission was correctly rejected with AGENT_DISABLED, while the public MCP path successfully completed create → inspect → explicit-file commit → exact-current-upstream push → final clean status. The returned/pushed commit was 7054388f69c1e1fd52df4f3485dd2b3df017ad93; Repo Ops created no Agent task.
The original machine-local configuration was restored byte-for-byte after acceptance and the production 0.23.2 managed lifecycle was restarted successfully. Detailed redacted evidence is in v0.23.2 Windows Repo Ops acceptance.
Platform boundary
The current Repo Ops support matrix is:
- Linux Host Bridge — released in v0.23.0.
- Native Apple Silicon macOS — validated in v0.23.1 within the existing Apple Silicon arm64 / macOS 27 / local APFS contract.
- Native Windows 11 x64 — validated in v0.23.2 within the existing current-user / local NTFS native contract.
Linux Compose configuration remains Linux-specific; native Windows/macOS policy continues to use serverfs.toml. Repo Ops remains independently gated from Agent delegation on all supported platforms.
Post-publication verification note
The immutable v0.23.2 tag remains at cd94dcacf7c6e4a6b6da0b36a4e8fa66cd1f0bae. Its tag-triggered Container run 40562374324 and macOS Native run 40562374370 exposed two root Ruff E501 violations in tests/test_agent_skills.py (lines 331 and 333 in the tagged source). This was a test-source lint-only publication-gate defect, not a Windows Repo Ops runtime, wheel, Agent Bridge, or D9 failure.
The tag-triggered Windows wheel release run 40562374466 succeeded, including all three wheel builds, METADATA version gates, Agent Plugin packaging, clean two-interpreter acceptance, clean-runner D9 lifecycle tests, GitHub Release creation, and all four release asset uploads.
The lint-only issue was corrected on main by commit db0ba63ab35ad618f5f51babeafdd9800cfd14e6 without moving or rewriting the release tag. Follow-up macOS Native run 40564870980 and Container run 40564870990 both completed successfully; the latter includes successful root tests, Agent Bridge tests, MCP conformance, and container publish/manifest verification. The publication exception is intentionally retained as evidence rather than hidden by retagging.
Windows installation assets (Python >= 3.12; no Rust/MSVC/Docker required)
The three release wheels install into two isolated environments, matching the
frozen ServerFS/Agent-Bridge process boundary (the supervisor selects the Bridge
interpreter through SERVERFS_BRIDGE_PYTHON; the packages never share one dependency
graph):
| file | installs into | sha256 |
|---|---|---|
| serverfs_mcp-0.23.2-py3-none-any.whl | ServerFS env | adcf5d3bfe6a5f8a8abbb146a68ac553d2176fc5ff4253e652e048cdfb2e35ce |
| serverfs_windows_native-0.23.2-cp312-abi3-win_amd64.whl | ServerFS env | b4982936b14959d5a29b6766682dcd848da9a981b753bb1373067bfc4c5e8e36 |
| serverfs_agent_bridge-0.23.2-py3-none-any.whl | Agent Bridge env | 770d2d53360ceb8d03bfc3c9821f1cb533de32dcc8405de09b3d9adc550e4ac7 |
ServerFS environment (product + native kernel):
uv venv --python 3.12 .venv-serverfs
uv pip install --python .venv-serverfs/Scripts/python.exe https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.2/serverfs_mcp-0.23.2-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.2/serverfs_windows_native-0.23.2-cp312-abi3-win_amd64.whl
Agent Bridge environment (Bridge + provider SDKs; it must NOT contain the product):
uv venv --python 3.12 .venv-bridge
uv pip install --python .venv-bridge/Scripts/python.exe https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.2/serverfs_agent_bridge-0.23.2-py3-none-any.whl
Point the ServerFS supervisor at the Bridge interpreter (set this in the environment
that starts serverfs supervisor; it is not a provider setting and does not belong in
[agent] config):
$env:SERVERFS_BRIDGE_PYTHON = "<path>\.venv-bridge\Scripts\python.exe"
Verified native-wheel storage alternative:
serverfs bootstrap native-wheel --url "https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.2/serverfs_windows_native-0.23.2-cp312-abi3-win_amd64.whl" --sha256 b4982936b14959d5a29b6766682dcd848da9a981b753bb1373067bfc4c5e8e36