Prepare Tributary 0.6.1 release

[jm2]

Summary

• bump Tributary to 0.6.1 in Cargo metadata and both lockfiles
• publish changelog and AppStream notes for Windows resizing/taskbar handling, Snap Layouts, Rhythmbox Preferences placement, Windows build routing, LF-only sources, and checksum hardening
• advance the documented release checkpoint

Validation

• .\scripts\build-windows.ps1 -Fmt
• .\scripts\build-windows.ps1 -Check
• .\scripts\build-windows.ps1 -Test — 20 library, 1,707 application, and 26 packaging tests passed
• .\scripts\build-windows.ps1 -Clippy — debug all-targets and release passed
• .\scripts\build-windows.ps1 — dependency checks, release build, 477-binary dependency closure, packaged runtime probe, resource validation, and ZIP creation passed
• git diff --check origin/main...HEAD
• tracked EOL audit — zero CRLF or mixed-EOL entries

Summary by CodeRabbit

• New Features

  • Added support for Windows Snap Layouts for easier window arrangement.
  • Improved Windows integration, including resizing and taskbar behavior.
  • Updated Rhythmbox import placement for a more consistent experience.

• Bug Fixes

  • Corrected window behavior and developer-build issues on Windows.
  • Improved release validation and checksum reliability.

• Documentation

  • Updated release notes and project documentation for version 0.6.1.

[claude]

Claude finished @jm2's task in 2m 0s —— View job

---

Claude is reviewing this PR

Todo list

• Gather context (diff, CLAUDE.md, changed files)
• Review CHANGELOG.md changes
• Review Cargo.toml / Cargo.lock / fuzz/Cargo.lock version bumps
• Review data/io.github.tributary.Tributary.metainfo.xml changes
• Review docs/task.md changes
• Post final review

---

Summary

This is a pure release-metadata PR: no source/logic changes, only version bumps, changelog/AppStream notes, and a backlog checkpoint update. Reviewed against correctness, security, performance, testing, and documentation — findings below are minor/informational only, nothing blocking.

Correctness / consistency

• Version bump is applied consistently across Cargo.toml, Cargo.lock, and fuzz/Cargo.lock (all 0.6.0 → 0.6.1) — no drift between lockfiles and manifest.
• CHANGELOG.md's new [0.6.1] entries (Snap Layouts, Rhythmbox placement, LF-only line endings, Windows resizing/taskbar, Windows dev-build routing, checksum hardening) line up with the AppStream <release version="0.6.1"> bullet list in data/io.github.tributary.Tributary.metainfo.xml — same set of user-facing changes, no mismatches.
• data/io.github.tributary.Tributary.metainfo.xml: the new <release> block is correctly inserted above 0.6.0 (AppStream requires reverse-chronological order), and the XML structure is well-formed.
• docs/task.md: date and release-checkpoint text updated coherently; the 14/38 (36.8%) feature numerator is explicitly called out as unchanged by this release, which is a good, deliberate note to prevent confusion about what "0.6.1" actually delivers.
• Left an inline note on CHANGELOG.md:8 — low-confidence observation that adding a new feature (Snap Layouts) under a patch bump is a soft SemVer deviation, though this may just be the project's established 0.x convention (minor = breaking, patch = everything else).
• Minor/non-blocking: the old ## [Unreleased] section is fully replaced rather than leaving an empty ## [Unreleased] placeholder behind. Not wrong, just means the next contributor needs to remember to re-add that heading before their changelog entry.
• Minor/non-blocking: docs/task.md's new release-checkpoint line doesn't link to a release tag or originating PR the way the old 0.6.0 line did ([v0.6.0](...), [#199](...)) — presumably because the v0.6.1 tag/PR don't exist yet at the time this PR was authored, matching the same bootstrap pattern used historically.

Security / Performance

Not applicable — no code paths are touched by this PR.

Testing

No test changes are needed since there's no logic change. The PR description lists a thorough local validation pass (fmt/check/test/clippy/full Windows build, git diff --check, EOL audit), which is appropriate for a release-prep PR of this shape.

Documentation

Changelog, AppStream metainfo, and backlog checkpoint are all updated together and stay mutually consistent — good release hygiene.

Note: I was working from a shallow clone (2 commits of history available), so I could not independently verify that every changelog bullet corresponds to a specific prior merged commit — the content is internally consistent, but full history verification wasn't possible in this environment.

No blocking issues found. This looks safe to merge from a correctness/consistency standpoint.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0a85c358-4bf3-44cc-a357-56909f4c3b7a

📥 Commits

Reviewing files that changed from the base of the PR and between 379f195 and 03e708b.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• fuzz/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• CHANGELOG.md
• Cargo.toml
• data/io.github.tributary.Tributary.metainfo.xml
• docs/task.md

---

📝 Walkthrough

Walkthrough

The project version was updated to 0.6.1. Changelog, application metadata, and release tracking documentation now record the 2026-08-02 release and its included fixes.

Changes

0.6.1 Release

Layer / File(s)	Summary
Version and release records Cargo.toml, CHANGELOG.md, data/io.github.tributary.Tributary.metainfo.xml	The package version changed to 0.6.1. The changelog and application metadata now describe the release fixes and comparison link.
Release tracking update docs/task.md	The audit date and release checkpoint now reference version 0.6.1 dated 2026-08-02.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• jm2/tributary#199: Updates the same release metadata files for version 0.6.0.
• jm2/tributary#202: Implements the Windows, Rhythmbox, MSYS2, and line-ending changes documented by this release.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the pull request's main purpose: preparing the Tributary 0.6.1 release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/prepare-0.6.1

---

_{Comment @coderabbitai help to get the list of available commands.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The PR successfully prepares the project for the v0.6.1 release. The changes are consistent across the manifest, changelog, and metadata files, aligning perfectly with the release requirements. Codacy analysis indicates the PR is up to standards, with no new quality issues, code clones, or increased complexity detected.

Test suggestions

• Verify version string '0.6.1' is consistent across Cargo.toml, CHANGELOG.md, and metainfo.xml
• Confirm release date '2026-08-02' is consistent between CHANGELOG.md, metainfo.xml, and docs/task.md
• Ensure the new release block in metainfo.xml is syntactically valid XML

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[claude]

Minor/low-confidence observation: this changelog states the project "adheres to Semantic Versioning," but the release adds a new user-facing feature (Snap Layouts support) and a UI relocation (Rhythmbox import placement) under a patch bump (0.6.0 → 0.6.1) rather than a minor bump. Under strict SemVer this would normally warrant 0.7.0. That said, for 0.x.y releases many projects use minor-bump-for-breaking / patch-for-everything-else as their working convention, so this may be intentional — flagging in case it isn't.