v0.2.5

What's Changed

• Launch staging: release fix, governance, badges, docs standard by @frumza in #3

Full Changelog: v0.2.4...v0.2.5

v0.2.3

Incremental QMD refresh, atomic freshness checkpoints, runtime ownership safeguards, dedicated XDG paths, cross-platform locking, reference systemd deployment, and release integrity checks.

Homestead Memory v0.2.2

Windows runtime and durability hotfix.

• Replaces Windows os.kill(pid, 0) liveness checks with Win32 process queries.
• Verifies qmd process ownership before termination on Windows.
• Uses Windows-safe process creation and termination.
• Fixes Windows vault-lock deletion races under concurrent writers.
• Makes successful hsm qmd stop return exit code 0.
• Adds a real pinned qmd 2.1 MCP lifecycle job on Ubuntu.

Verification: 238 tests, Python 3.10/3.12 across Windows/macOS/Linux, plus real qmd 2.1 start/status/stop CI.

Homestead Memory v0.2.1

Isolates Homestead from the user's global qmd state and makes retrieval degradation explicit. Adds a dedicated qmd 2.1 runtime, persistent loopback MCP retrieval, fast/balanced/quality profiles, bounded MCP -> dedicated CLI -> direct-scan fallback, runtime lifecycle commands, and structured latency/index metadata. The published LongMemEval result is unchanged.