chore(release): bump to v0.8.5-0

[lavaman131]

Summary

Prepares the 0.8.5-0 prerelease by bumping all workspace package versions and refreshing the lockfile. This prerelease bundles the workflow picker keybinding fixes and UX improvements landed since v0.8.4.

Changes

Release mechanics

• Bumped all workspace package versions to 0.8.5-0 (coding-agent, workflows, subagents, mcp, web-access, intercom)
• Refreshed bun.lock with updated prerelease version references
• Added [0.8.5-0] changelog section to packages/coding-agent/CHANGELOG.md

What's bundled (since v0.8.4)

• feat(workflows): support package resources and direct run options
• feat(workflows): refine stage chat pause and input controls
• feat(workflows): refine run control and discovery diagnostics
• fix(workflows): make picker key handling terminal-safe (fix(workflows): harden TUI input, stage chat interrupts, and executor options #961)
• fix(workflows): harden TUI layout for keybindings and wide text (fix(workflows): harden TUI input, stage chat interrupts, and executor options #961)
• fix(workflows): stabilize attached stage chat pause handling
• refactor(types): tighten model and tool renderer typings
• style(ui): normalize keyboard shortcut hint labels
• chore(coding-agent): update assistant guidance and thinking style
• test(workflows): improve wiring and integration test reliability (fix(workflows): harden TUI input, stage chat interrupts, and executor options #961)

Validation

• Pre-commit/pre-push hooks ran bun run lint and bun run test:unit successfully
• Publishing is triggered by git push origin v0.8.5-0 after this PR merges (npm next tag, prerelease GitHub Release)

[claude]

Review: chore(release): bump to v0.8.5-0

Routine prerelease version bump — straightforward and largely mechanical. The PR is already merged; leaving notes for future release PRs.

What looks good

• Version bumped consistently across all six workspace packages (coding-agent, intercom, mcp, subagents, web-access, workflows). ✓
• bun.lock regenerated to match the new versions. ✓
• New ## [0.8.5-0] - 2026-05-18 section added to packages/coding-agent/CHANGELOG.md in the format the publish workflow expects. ✓
• Matches the procedure documented in CLAUDE.md (bun run scripts/bump-version.ts + bun install, then commit before tagging).

Observations / suggestions

1. Pre-existing version drift between package.json files and bun.lock. Before this PR, every packages/*/package.json was on 0.8.4 while bun.lock already recorded 0.8.4-0 for the same packages. This PR happens to mask the drift by moving both to 0.8.5-0, but it's worth checking whether scripts/bump-version.ts always re-runs bun install (or whether a prior prerelease left the lockfile mid-state). If the lockfile can diverge from the workspace package.json versions silently, that's a subtle release-flow bug worth fixing once.

2. Changelog entry is empty in content. "Prepared the 0.8.5-0 prerelease" describes the act of cutting the release rather than what changed since 0.8.4. For prereleases this is generally fine, but if there are real fixes/features bundled in 0.8.5-0 they should be enumerated under ### Added / ### Fixed / ### Changed so the GitHub Release body (extracted from this section by the publish workflow) is meaningful to consumers. If literally nothing changed, that's worth saying explicitly.

3. Tag flow reminder (not in this PR, but the next step). Per CLAUDE.md, publishing is gated on pushing the v0.8.5-0 git tag, not the branch merge. Worth confirming the tag was pushed and .github/workflows/publish.yml ran with the next npm dist-tag (prerelease behavior) rather than latest.

Code quality / bugs / perf / security / tests

• Code quality: N/A — version strings only.
• Bugs: None in the diff.
• Performance: N/A.
• Security: No dependency additions or surface changes. Provenance is handled by npm publish --provenance in CI (no token), consistent with the repo policy.
• Test coverage: Not applicable to a version bump; PR description confirms bun run lint + bun run test:unit passed via pre-commit/pre-push hooks. ✓

Overall: ✅ safe release-prep PR. The only durable takeaway is to look at whether bump-version.ts should also assert that bun.lock matches the bumped versions before allowing the commit, so the lockfile can't drift between bumps.