chore(release): bump desktop to 2026.8.1

[Astro-Han]

Summary

Bump the PawWork desktop release version from 2026.7.4 to 2026.8.1 in the package manifest and Bun lockfile. This is the requested August stable release preparation and has no related issue.

Why

The August stable release needs a unique CalVer version before macOS and Windows artifacts can be built, notarized, published, and mirrored from one pinned commit.

Human Review Status

Approved by @Astro-Han

Review Focus

Confirm the diff changes only the desktop package version and its lockfile workspace entry to 2026.8.1.

Risk Notes

The visible UI check is not applicable because this changes no UI or copy. The version is the source for release asset names and updater metadata, so all three final release targets must build the merged commit.

How To Verify

Version contract: RED on 2026.7.4, GREEN on 2026.8.1
Release contract tests: 21 passed, 0 failed (release-metadata-contract + release-workflow-contract)
Release typecheck: passed (tsgo -p tsconfig.release.json)
Frozen install: passed with no lockfile changes
Diff check: no whitespace errors

Checklist

• Type label — task
• Routing labels — desktop
• Priority label — P3
• Human Review Status above is set to Approved by @Astro-Han
• I linked the related issue, or stated in Summary why there is no issue.
• I described the review focus and any meaningful risks.
• I replaced the example block in How To Verify with the real verification steps and the key result for each.
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope.
• (conditional) I manually checked visible UI or copy changes when needed — not applicable, no UI change.
• (conditional) I considered macOS and Windows impact — version is the source for release asset names and updater metadata, so all three final release targets must build the merged commit.
• (conditional) I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant — no such surfaces changed.
• I reviewed the final diff for unrelated changes and suspicious dependency changes.
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English.

Summary by CodeRabbit

• Chores
  • Updated the desktop application release version to 2026.8.1.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 458c7b03-eb25-49a0-9c8a-720f78cfb9a2

📥 Commits

Reviewing files that changed from the base of the PR and between 512ab27 and ede745a.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• packages/desktop-electron/package.json

---

📝 Walkthrough

Walkthrough

The desktop-electron package version changes from 2026.7.4 to 2026.8.1.

Changes

Desktop Electron release

Layer / File(s)	Summary
Update package version packages/desktop-electron/package.json	The package version changes from 2026.7.4 to 2026.8.1.

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

Possibly related PRs

• Astro-Han/pawwork#1520: Updates the desktop-electron package version for a desktop release.
• Astro-Han/pawwork#1527: Updates the desktop-electron package version for a release.
• Astro-Han/pawwork#1536: Performs the preceding desktop package version bump.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the desktop release version bump to 2026.8.1 and uses a concise Conventional Commit format.
Description check	✅ Passed	The description covers the change, rationale, review status, focus, risks, verification, and checklist, but omits the Screenshots or Recordings heading and uses an unsupported routing label.
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 chore/release-2026.8.1

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install failed. For unrecoverable errors, disable the tool in CodeRabbit configuration.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Suggested priority: P2 (includes non-doc, non-test paths outside the low-risk bucket).

P1/P0 are reserved for maintainer confirmation. Please relabel manually if this is a release blocker, security issue, data-loss risk, or updater/runtime failure.