Release Roomote 0.41.0

[roomote-roomote]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote or in the web UI.

What changed

Prepared the Roomote 0.41.0 release from 0.40.2 with the repository-owned pnpm run version flow. The release consumes all 16 pending and locally authored release notes, bumps only the root product version, adds the final in-app changelog summary and highlights, and fills the public-documentation gaps found during the release audit.

The branch was regenerated from the latest develop and now includes the shared task board, expanded Fast delegation, linked Slack and Discord Fast response defaults, reliable Slack task-card completion, and semantic release context for agents. Integration lifecycle telemetry and Fast advisor/judge routing coverage are internal-only changes with no user-facing release note or documentation requirement.

Minor changes

• 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.
• 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.

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.

Documentation coverage

• Tasks: updated with the shared board lifecycle columns, starter and participant context, recent activity, workspace and pull-request context, the bounded Done shelf, and shareable URL state; the page already covered Fast input replies.
• Personal Settings, Slack, and Discord: current on develop for saved Fast response defaults, eligible linked-message sources, explicit Slack !fast, and excluded surfaces.
• Environment variables: current on develop after removal of the obsolete Fast response deployment gate.
• Brain: updated with pull-request descriptions, labels, changed files and areas, line totals, reviews, and progressive enrichment behavior.
• Inference overview: updated with Fast delegated-model selection, multiple independent task launches per turn, and advisor/judge consultation boundaries; provider usage-limit warnings were already documented.
• GitHub: updated with linked-task check-failure notifications; configured app trust and Fast review actions were already documented.
• Cost Analytics: updated with Source grouping, filtering, examples, and drilldown behavior.
• Automations: updated with default-enabled Platform Issue Alerts, destination precedence, admin-DM fallback, and retry behavior.
• The Brain guide already covers task-memory ingestion and repair states.
• Slack task-card completion and agent release context are visible reliability/context improvements with no new setup or workflow documentation requirement.
• The remaining Fast reliability, GitHub attribution, and onboarding changes are visible fixes or in-flow guidance and need no additional public setup documentation.
• Integration lifecycle telemetry and Fast advisor/judge routing coverage are internal-only and need no public documentation.

Why this change was made

The merged work since v0.40.2 includes backward-compatible capabilities, so the highest pending changeset level produces the default minor semver result 0.41.0. Regenerating one audited release diff keeps the product version, changelog, consumed changesets, and public guidance synchronized.

Impact

Reviewing and squash-merging this PR into develop cuts Roomote 0.41.0 and automatically opens the frozen Promote v0.41.0 to production PR against main. This PR does not publish, deploy, tag, promote, or merge the release itself.

Validation

• pnpm test:release-scripts (16 tests)
• mise exec -- pnpm --filter @roomote/docs check (Mintlify validation and broken-link checks)
• pnpm format:check
• pnpm lint:fast
• pnpm check-types:fast
• pnpm knip
• pnpm lint:pre-push
• pre-push hook during branch push

[roomote-community]

No new code issues found. See task

• Release notes and public documentation cover the shared task-board feature shipping with 0.41.0.
• Task-board docs describe only context the cards actually render.
• Personal Settings accurately scopes Fast response mode to linked Slack and Discord messages.
• Personal Settings accurately reflects the saved Fast-response default without a deployment gate (apps/docs/personal-settings.mdx:67).
• Agent prompts resolve and display only a semantic product release version.

_{Reviewed a56c0fd}

[roomote-roomote]

All prior review feedback remains resolved on the regenerated release head cefe19cd. The branch now targets the default 0.41.0, includes the latest develop change and matching public documentation, passes the full release validation suite, and keeps both review threads resolved.