Promote v0.41.0 to production

[mrubens]

Promote v0.41.0

Frozen at 23ac667ef993a1c82295e895b3d1df9b2f9e27bb — the commit where 0.41.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.41.0 and triggers the existing GHCR v* image publish (latest channel).
• The release/v0.41.0 branch can be deleted after this PR merges.

Changelog

0.41.0 (2026-08-24)

This release adds a shared task board, expands Fast delegation and preferences, delivers actionable pull-request CI updates and proactive operator alerts, clarifies inference costs, and gives the Brain richer pull-request context.

Highlights

• Coordinate team work from a shared board organized by task lifecycle, ownership, and context.
• Launch multiple independent tasks from one Fast conversation, choose their coding models, and consult focused reasoning subagents.
• Send actionable GitHub check failures back to linked tasks and their originating conversations.
• Warn operators about provider usage limits and deliver configuration issues to admins even without a configured channel.

Minor changes

• Break down, filter, and inspect inference costs by usage source so operators can attribute spend to features such as task routing and title generation.
• Let Fast choose an enabled coding model for each delegated task and consult advisor or judge subagents for focused reasoning without launching another workspace-backed task.
• Let Fast launch multiple independent Roomote tasks from one Slack or Discord turn while keeping each kickoff visible and preventing repeated identical requests from creating duplicate work.
• Notify linked Roomote tasks and their originating conversations when checks fail on a GitHub pull request, consolidating related failures and ignoring results from outdated commits.
• Warn operators before supported inference-provider usage limits are exhausted, and deliver platform configuration issues to linked deployment admins by direct message when no alert or Manager Channel is configured.
• Add a shared task board that groups work into Active, Needs input, Blocked / failed, and Done columns, with ownership, participant, activity, workspace, and pull-request context for coordinating team work.

Patch changes

• Give Brain pull-request pages the PR description and labels from GitHub, GitLab, Gitea, Bitbucket, and Azure DevOps so agents can recall why a change was made, not only its title.
• Enrich Brain pull-request pages with files changed, code areas, line totals, and review outcomes across supported source-control providers so agents can find the changes that affected a part of the codebase.
• Keep Fast conversations moving with clearer delegated replies, Slack task cards that resume after follow-ups, recovery from missing runtime dependencies and transient provider outages, and accurate guidance when a provider blocks a response.
• Show Fast response mode to every user in Personal Settings and apply each saved preference to eligible linked Slack and Discord messages without requiring deployment configuration.
• Trust only explicitly configured Roomote GitHub App slugs for managed pull-request activity, and keep Roomote attribution in pull-request descriptions to one canonical entry.
• Make onboarding easier to follow with clearer account, inference-provider, source-control, and environment guidance throughout the setup flow.
• Make pull-request feedback in Fast conversations reliable by delivering review activity consistently, keeping Slack review actions usable after delegated tasks settle, suppressing duplicate or stale results, and reducing notification pressure on provider quotas.
• Keep Brain task-memory history accurate by recording completed tasks reliably, distinguishing real ingestion gaps from completed backfills, and preventing the history-ingestion banner from returning after completion.
• Finish Slack task cards with the delegated agent's real result after Fast work settles, preserve actionable input requests, and keep terminal error cards stable while delivery retries.
• Give Fast and normal Roomote agents the semantic product release in their core prompt context while omitting channel tags and unavailable versions.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
roomote	🟢 Ready	View Preview	Aug 24, 2026, 6:16 PM

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

[roomote-community]

1 issue outstanding. See task

• packages/sdk/src/server/lib/user-direct-message.ts:355 - Discord is omitted from the best-effort direct-message fan-out, so Discord-only installation requesters are not notified.

_{Reviewed 23ac667}

[roomote-community]

sendUserDirectMessageBestEffort still fans out only to Slack, Teams, and Telegram, despite its contract saying every linked provider. handleInstallationCreated uses that helper, so a requester linked only to Discord will never receive the GitHub-installation approval message. Add Discord to the result type and fan-out (with coverage).