Promote v0.32.0 to production

[mrubens]

Promote v0.32.0

Frozen at a44f1010956d474ddeeeb60d8370993edb8530d9 — the commit where 0.32.0 was versioned. Commits merged to develop afterward require an explicit candidate refresh or ship in the next release.

• Merge this PR with a merge commit (do not squash or rebase).
• If multiple promote PRs are open, merge them in version order (oldest first).
• Merging publishes a GitHub Release for v0.32.0 and triggers the existing GHCR v* image publish (latest channel).
• The release/v0.32.0 branch can be deleted after this PR merges.

Changelog

0.32.0 (2026-08-03)

This release adds OpenCode Go subscriptions, restores convenient automation test runs, refreshes recommended models, and makes license syncing more resilient.

Highlights

• Let operators connect an OpenCode Go subscription independently from OpenCode Zen and use supported Go models across Roomote task roles.
• Run enabled custom automations on demand and test newly created automations immediately.
• Use current Qwen and DeepSeek recommendations across supported model providers.
• Retry license usage reporting after transient Roomote Cloud failures.

Minor changes

• Let operators connect an OpenCode Go subscription independently from OpenCode Zen and use supported Go models across Roomote task roles.

Patch changes

• Let administrators run enabled custom automations on demand from Automations settings, and offer an immediate test run after an automation is created conversationally.
• Recommend Qwen3.8 Max through supported providers and use OpenCode Zen's supported DeepSeek V4 Flash model identifier.
• Retry license usage reports after transient Roomote Cloud failures and report concurrent license-key changes accurately instead of dropping usage observations or reporting a false success.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
roomote	🟢 Ready	View Preview	Aug 3, 2026, 9:19 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[roomote-community]

1 issue outstanding. See task

• packages/telemetry/src/server/license-cloud.ts:152 treats an HTTP 408 as a permanent rejection. The scheduler then marks that usage observation delivered, so a transient request-timeout response is never retried. Classify 408 as failed alongside 429/5xx so the durable observation is retained for the next job.

_{Reviewed a44f101}