Release v0.5.1

[cmeans-claude-dev]

Summary

Patch release rolling up the post-0.5.0 fixes. Five PRs land in this release:

• fix(state): atomic write for runtime state files #69 — Atomic state-file writes (closes State file writes are not atomic — crash mid-write corrupts state.yaml #36). New core/fs.py::atomic_write_text helper; save_state and _save_global_state route through it. Eliminates torn-write windows on state.yaml / global.yaml.
• fix(setup): atomic write for interactive config file #71 — Atomic write for cli/setup.py interactive config (closes Atomic write for cli/setup.py config persistence (nice-to-have follow-up to #36) #70). Last user-visible non-atomic write site cascaded onto the same helper.
• docs(readme): per-installer and per-OS download-breakdown badges #72 — README per-installer and per-OS download-breakdown badges. Mirrors mcp-clipboard's layout; all 9 new badges link to cmeans/pypi-winnow-downloads (the dogfooded service).
• fix(filestation): probe recycle-bin status per share #73 — Recycle-bin status probed per share (closes recycle_status passed to delete_files is always empty — incorrect recycle-bin messaging #37). Lazy ensure_recycle_status helper; self-correct on observation; clear-on-reauth via new AuthManager.add_on_reauth_callback API. Fixes incorrect "Recycle bin is enabled" messaging on shares with #recycle disabled.
• fix(filestation): per-path serial for multi-path getinfo and delete #77 — Per-path serial for multi-path getinfo and delete (closes v0.5.0 regression: delete_files and get_file_info silently mishandle multi-path arrays #68). Critical: fixes a v0.5.0 silent-no-op regression on delete_files with multi-path arrays — caller would see [+] Deleted N item(s) listing every path, but none were actually deleted on real DSM 7.x. Same root cause on get_file_info (single synthetic record with comma-joined path). Both tools now issue one DSM call per input path.

Files touched (per CLAUDE.md release procedure)

• pyproject.toml: 0.5.0 → 0.5.1
• server.json: synced via scripts/sync-server-json.py (top-level + packages[0].version)
• uv.lock: refreshed via uv lock
• CHANGELOG.md: ## Unreleased renamed to ## 0.5.1 (2026-05-01); fresh empty ## Unreleased added above for the next cycle

QA

Manual tests

1. • python scripts/sync-server-json.py --check — reports "in sync (0.5.1)".
2. • uv run pytest — 550 passed, 96.13% coverage.
3. • uv run ruff check src/ tests/ scripts/ — clean.
4. • uv run ruff format --check src/ tests/ scripts/ — clean.
5. • uv run mypy src/ scripts/ — clean.
6. • CHANGELOG diff is exactly: ## Unreleased → ## 0.5.1 (2026-05-01), plus a fresh empty ## Unreleased heading inserted above. No content was moved or rewritten — every entry under ## 0.5.1 already lived under ## Unreleased on main.
7. • After merge: tag-push triggers publish.yml. The awk extractor on ## <version>( |\() matches ## 0.5.1 (2026-05-01) correctly and the new empty ## Unreleased is harmlessly walked past.

Verification I already ran

Check	Result
python scripts/sync-server-json.py --check	in sync (0.5.1)
uv run pytest	550 passed, 100 deselected, 96.13% coverage
uv run ruff check src/ tests/ scripts/	clean
uv run ruff format --check src/ tests/ scripts/	72 files already formatted
uv run mypy src/ scripts/	clean (30 files, strict-mode)
git diff --stat HEAD~1	4 files: CHANGELOG.md, pyproject.toml, server.json, uv.lock

🤖 Generated with Claude Code

[cmeans]

LGTM

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[cmeans]

QA Round 1 — PASS

Release rollup PR for v0.5.1, bundling #69, #71, #72, #73, #77 — all five already QA-Approved this cycle. Diff is exactly what a clean release PR should be: 6 lines across 4 files, no feature-code changes.

Verification

Check	Result
python scripts/sync-server-json.py --check	server.json in sync with pyproject.toml (0.5.1)
uv run pytest	550 passed, 100 deselected, 96.13% coverage (matches the post-#77 baseline)
uv run ruff check src/ tests/ scripts/	clean
uv run ruff format --check src/ tests/ scripts/	72 files already formatted
uv run mypy src/ scripts/	clean (30 files, strict-mode)
Required CI on d7343e0	13/13 green (vdsm completed SUCCESS)

Diff sanity

Verified the four files contain exactly the version-bump + CHANGELOG-split mechanics, no surprise content:

• pyproject.toml: single line version = "0.5.0" → "0.5.1".
• server.json: top-level version + packages[0].version both 0.5.0 → 0.5.1 (the two distinct version sites that scripts/sync-server-json.py keeps in lockstep).
• uv.lock: single line version = "0.5.0" → "0.5.1" on the mcp-synology package entry.
• CHANGELOG.md: new ## 0.5.1 (2026-05-01) heading inserted between the existing ## Unreleased and the existing ### Fixed content. No prose moved or rewritten — every entry under ## 0.5.1 already lived under ## Unreleased post-#77. Section order on disk is now Unreleased (empty placeholder) → 0.5.1 (2026-05-01) → 0.5.0 (2026-04-10) → … as expected.

publish.yml extractor sanity (manual test #7 — post-merge but pre-verifiable)

Read the awk extractor at .github/workflows/publish.yml:117-120:

$0 ~ "^## "version"( |\\()" {flag=1; next}
flag && /^## / {exit}
flag

For VERSION=0.5.1 against this CHANGELOG:

• ## Unreleased — pattern ^## 0.5.1( |\() doesn't match (no version match), flag=0, walked past.
• ## 0.5.1 (2026-05-01) — pattern matches the literal 0.5.1 (, flag=1, next.
• All ### Fixed / ### Added content under 0.5.1 — flag=1, lines emitted.
• ## 0.5.0 (2026-04-10) — flag=1 and ^## matches, exit.

The empty ## Unreleased placeholder is harmlessly skipped exactly as the PR body claims; the extracted block will be the 0.5.1 entries verbatim.

Notes

• All five rolled-up PRs are already QA-Approved with audit trails on each PR.
• No CHANGELOG drift, no version desync between manifest files, no test regressions, no lint/type drift.
• Manual tests 1–6 verified directly; #7 verified by reading the awk pattern against the new heading shape (post-merge tag-push behavior is then mechanical).

PR-body manual tests 1–7 all checked.

Verdict

Ready for QA Signoff. Final maintainer call.

[cmeans]

Applying Ready for QA Signoff as the final act of round 1. Release rollup PR for v0.5.1 — bundles #69, #71, #72, #73, #77 (all already QA-Approved). All four files (pyproject.toml, server.json, uv.lock, CHANGELOG.md) contain exactly the version-bump + section-split mechanics; no surprise content. scripts/sync-server-json.py --check reports in-sync. publish.yml awk extractor verified by inspection — matches ## 0.5.1 (2026-05-01) and walks past empty ## Unreleased placeholder. 550/550 pass, 96.13% coverage, ruff/mypy clean, 13/13 required CI green. Final maintainer call.