chore: bump version to 0.2.8

[Astro-Han]

Summary

Bump PawWork workspace release metadata from 0.2.7 to 0.2.8.

Why

Prepare the next stable desktop release after the macOS updater config fix in #168 landed on dev.

Related Issue

No issue. This is a release preparation PR.

How To Verify

bun install --frozen-lockfile
bun turbo typecheck
bun test scripts/verify-release.test.ts scripts/release-metadata-contract.test.ts scripts/release-workflow-contract.test.ts electron-builder-app-update.test.ts scripts/write-app-update-config.test.ts

Earlier in this release-prep pass, bun turbo test:ci also completed with Turbo success. The opencode JUnit report emitted a warning after reporting 2030 pass, 0 fail; I did not use that command as the final local gate because it triggered checkout/reset side effects in this checkout.

Screenshots or Recordings

Not applicable. No visible UI changes.

Checklist

• I linked the related issue, or stated why there is no issue
• This PR has type, scope, and priority labels, or I requested maintainer labeling
• I listed the relevant verification steps, including tests when behavior changed
• I manually checked visible UI or copy changes when needed, with screenshots or recordings
• I considered macOS and Windows impact for desktop, packaging, updater, signing, paths, shell, or permissions changes
• I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, or generated/local file changes when relevant
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English

[coderabbitai]

Warning

Rate limit exceeded

@Astro-Han has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 6 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 4 minutes and 6 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c2d2d271-eb81-45c3-81c2-6f896fa48ea5

📥 Commits

Reviewing files that changed from the base of the PR and between c2cb152 and ea895d6.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• packages/app/package.json
• packages/desktop-electron/package.json
• packages/opencode/package.json
• packages/util/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-v0-2-8

---

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

[gemini-code-assist]

Code Review

This pull request bumps the version of several workspace packages, including @opencode-ai/app, @opencode-ai/desktop-electron, opencode, and @opencode-ai/util, from 0.2.7 to 0.2.8. Feedback suggests that other workspace packages such as @opencode-ai/sdk and @opencode-ai/shared should also be updated to maintain version consistency across the release line.