ServerFS v0.13.2

Highlights

• Replaced the normal macOS lifecycle path with a native SMAppService/ServiceManagement companion for the persistent Tunnel and Agent Bridge, while keeping ServerFS and the Bridge themselves in Python.
• Added the bundled Service Manager/launcher contract, private service manifest/log locations, and the serverfs service install/status/start/restart/stop/uninstall/open-settings operator surface with registration and process health reported separately.
• Added controlled v0.13.0/v0.13.1 legacy Bridge and unmanaged-Tunnel hand-over with duplicate prevention, rollback safety, and process-drain ordering so the new Bridge cannot falsely pass health against the retiring legacy socket owner.
• Added macOS native bundle/wheel packaging and acceptance coverage, and aligned container builds so the macOS service-manager assets required by the product wheel are present in the Docker build context.

Upgrade notes

macOS users should use the serverfs service ... lifecycle rather than raw launchctl or hand-installed LaunchAgent files. Existing v0.13.0/v0.13.1 legacy Bridge state is handled by the controlled migration path. No Linux or Windows configuration migration is required.

The persistent macOS services remain per-user services: no root, LaunchDaemon, privileged helper, or pre-login daemon is introduced. Live reboot/re-login recovery and Login Items disable/re-enable validation were explicitly deferred beyond the v0.13.2 closeout and are not release gates for this version.

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.13.2-py3-none-any.whl	ServerFS env	720c8a73f78e42a5e7e0ae0c15f3726b4af4a961cab1ca68138b1ef80c754d77
serverfs_windows_native-0.13.2-cp312-abi3-win_amd64.whl	ServerFS env	cee99d8ad731504bb0300532e68aeac44536338f043856f1c3782a87afd263e8
serverfs_agent_bridge-0.13.2-py3-none-any.whl	Agent Bridge env	df954c9458953584f8dcd330747b17f798ad4a43a3914b207bbe550b5753022e

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.13.2/serverfs_mcp-0.13.2-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.13.2/serverfs_windows_native-0.13.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.13.2/serverfs_agent_bridge-0.13.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.13.2/serverfs_windows_native-0.13.2-cp312-abi3-win_amd64.whl" --sha256 cee99d8ad731504bb0300532e68aeac44536338f043856f1c3782a87afd263e8