[Chore] Release Roomote 1.0.0

[roomote-roomote]

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

Release

• Previous product version: 0.45.1
• Next product version: 1.0.0
• Release base: refreshed through origin/develop commit a2db9429
• Incoming commits audited in this refresh: 3
• Bump: major, selected from the committed major changeset because Fast becomes the default for unpinned requests and Memory is enabled by default for new hosted deployments
• Reproducibility: the major input and every later release-note input are preserved in branch history before the repository version and amendment commands consume them

What changed

Roomote 1.0 makes Fast the default entry point for conversations, enables Memory by default on new hosted deployments, and completes the Session-centered automation, analytics, and artifact experience.

Major changes

• Make Fast the default entry point for unpinned Roomote requests across the web dashboard and supported chat providers, and enable Memory by default for new hosted deployments. Select an environment or repository when work should start directly in a coding task; existing deployments keep their current Memory setting.

Minor changes

• Start and continue linked Fast conversations directly from Microsoft Teams and Telegram, matching the existing Slack and Discord experience.
• React to Roomote Fast replies across Slack, Discord, Microsoft Teams, and Telegram to provide context for a follow-up or let the conversation stay quiet.
• Announce default-branch pushes across supported source-control providers with concise, pull-request-aware summaries, direct change links, and durable Slack, Discord, Microsoft Teams, or Telegram destinations.
• Open Analytics on Costs by default and break out Session orchestration and Memory synthesis so teams can understand where inference spend comes from.
• Let Fast launch multiple independent coding tasks from one turn, forward image and supported file context into delegated work, and show nested startup progress without losing retries or results.
• Let Fast inspect GitHub Actions runs, jobs, and logs to explain CI failures while keeping the diagnostic path read-only.
• Open generated HTML artifacts as safely sandboxed previews with a source-code toggle, while keeping presentational widgets available in web transcripts and linked chat previews.
• Add public Discord discussions and visible Linear issues to Memory, preserve richer Linear planning metadata, and render readable Notion database properties for more complete recall.
• Let administrators enable Memory without a dedicated synthesis-provider key, enable it by default for new hosted deployments, and surface newly ingested pages within minutes instead of waiting for a later maintenance pass.
• Finish setup in one Roomote Session that launches and tracks selected starter tasks, with clearer guidance about the value and limits of hosted trial inference.
• Make Sessions the primary workspace for Roomote work, with dashboard launch and search, recent-session navigation, delegated execution details, artifacts, reviews, costs, stable titles, and responsive mobile layouts in one continuous conversation.
• Browse current and previous Roomote releases directly in the update dialog, with the latest release expanded and newer remotely detected updates kept visible even when their notes are not yet available in the running image.
• Open current and previous Roomote release notes directly from About Roomote in the existing in-app release-history dialog.
• Follow delegated work more clearly in Sessions with live nested-task activity, a conversation-wide artifact gallery, cleaner task details and navigation, and modernized search, filter, board, and list controls.
• Include one safely validated, representative pull-request screenshot in Slack Merge Announcer reports when the pull request provides a suitable image.
• Show richer task context throughout Sessions with accumulated pull requests, actor and source details, clearer status indicators, direct access to a sole running task, and full task workspaces for Session deep links.
• Make Roomote MCP Session-first so ordinary start, search, summary, message, and follow-up operations use Sessions by default while explicit task IDs continue to target individual coding tasks.
• Have Fast acknowledge substantive human requests before starting model-invoked work, using a brief reply or eligible Slack reaction without duplicating immediate answers, clarifications, or delegated-task kickoffs.

Patch changes

• Keep Fast sessions quiet through short transient provider recoveries: retries stay silent unless the wait grows past 30 seconds, all retryable provider errors share a six-retry budget with bounded jittered backoff, and warm-session progress refreshes the recovery budget the way completed coding-task turns do.
• Queue delegated-task updates durably for their Fast parent so busy conversations process child progress and completion in order instead of rejecting or killing the parent event after 30 seconds.
• Keep pull-request review follow-through reliable by showing actionable feedback in Fast and standard web tasks, clearing resolved Roomote findings, preserving the correct destination branch and attribution, and avoiding duplicate review requests.
• Disable anonymous usage reporting in the bundled Infinity service so self-hosted local Memory embeddings stay quiet by default.
• Keep Fast Sessions stable through cold starts and refreshes by preserving conversation context, model and reasoning choices, generated titles, pull-request status, and recovery state without duplicate or stale transcript notices.
• Keep Slack Fast thread titles synchronized with generated and manually edited Session titles instead of leaving conversations labeled Thread.
• Show platform issue alerts sent directly to Slack deployment admins with the same actionable automation card used for configured alert destinations.
• Keep expanded tool-call details readable in Task and Fast transcripts by wrapping long YAML values within the transcript instead of clipping or overflowing them.
• Keep Session context accurate by including attached task inference spend in total costs, opening inline task links in their owning Session, and hiding running or artifact states when they no longer apply.
• Keep Slack-backed Sessions and automations reliable by deferring silent custom-automation delivery, suppressing no-op placeholders, validating Fast titles without retry loops, restoring clear Configure actions, and using the correct Merge Announcer icon.
• Restore required runtime dependencies in standalone deployment images while continuing to bundle in-app release history.
• Show the shared progress spinner while tool calls are active, then restore each tool or integration icon when the call settles.
• Let Fast mode discover, load, and explicitly invoke environment-scoped Settings skills while preserving built-in skill precedence and bounded access.
• Complete large Notion historical discovery scans in the fast continuation loop instead of spreading database-row traversal across weeks of scheduled passes.
• Keep tasks moving when visual proof takes too long by applying one five-minute deadline across capture, retries, and recovery before returning a graceful proof blocker.
• Include authorized Settings skills in Fast mode's unscoped skill inventory.
• Keep running nested-task activity visible when a Session is loaded directly or reconnects, while still hiding it during genuine new parent responses.
• Restore authorized deployment MCP tools in Fast advisor and judge consultations while keeping Fast-native orchestration and custom automation tools confined to the parent Session.

Why this change was made

The default Fast and Memory behavior changes are intentionally semver-major, and the release branch must include every commit present at the final develop cut. This refresh audits and folds all changes through a2db9429 into the existing 1.0.0 candidate without losing the generated release artifacts or prior documentation work.

Documentation coverage

• Fast as the default for unpinned requests, pre-work acknowledgements, direct coding-task selection, Sessions, dashboard search, responsive details, chat continuation, ambient participant handling, reactions, and widget previews: updated Sessions, Communications, and Automations.
• Session live nested-task activity across direct loads and reconnects, conversation-wide artifact gallery, accumulated pull requests, task context and deep links, filter/view controls, and complete task-inclusive cost totals: updated Sessions.
• Memory default-on behavior for new hosted deployments and preservation for existing deployments: covered by Memory.
• HTML artifact preview and source inspection: updated Review a task.
• Persistent Fast model and reasoning selection: updated Models and inference.
• Read-only GitHub Actions diagnostics and actionable review controls in web transcripts: updated GitHub.
• Current and previous release browsing from About Roomote and the update dialog, including newer targets whose notes are not bundled yet: updated Self-hosting.
• Self-hosted local embedding privacy: updated Memory.
• Memory enablement, Discord and Linear sources, richer Notion properties, continuous historical Notion discovery, and ingestion freshness: covered by Memory, Discord, Linear, and Notion.
• Session-first Roomote MCP actions and explicit task targeting: updated Roomote MCP.
• Fast discovery, unscoped inventory, and explicit invocation of authorized environment-scoped Settings skills: updated Skills.
• Merge Announcer configuration and representative Slack screenshots: updated Automations.
• Fast attachment delegation and Cost Analytics dimensions: covered by File attachments and Cost Analytics.
• No new provider or integration was added, so no navigation or provider-icon update is required.

Validation

• pnpm test:release-scripts passed all 16 tests after the latest amendment.
• mise exec -- pnpm --filter @roomote/docs check passed Mintlify validation and broken-link checks.
• pnpm check passed the full lint, type-check, test, and Knip gate across all 27 tasks after clearing four stale task_messages rows in the dedicated test database so the repository schema push could add its new unique constraint. No repository or development data was changed.
• node scripts/pre-push-checks.mjs and the push hook passed oxlint, residual lint, fast type checks, and Knip.
• git diff --check passed.
• Release integrity checks confirmed 1.0.0, only the root package version changed, every pending changeset was consumed, .changeset/README.md remains, origin/develop is an ancestor of the final branch, and the original 1.0.0 version commit remains 6227c5b5.

Impact

Squash-merging this draft PR into develop cuts Roomote 1.0.0. The Release workflow will freeze release/v1.0.0 at that merge and automatically open the separate Promote v1.0.0 to production PR against main.

This PR does not merge, promote, tag, publish, deploy, create a GitHub Release, or write to the CI-owned release/v* namespace.

[roomote-community]

No new code issues found. See task

• package.json:3 — The release advances to 0.46.0 even though every consumed changeset is patch; the standard release script would create 0.45.2. Resolved by the committed major changeset and regenerated 1.0.0 release artifacts. (review comment)
• apps/docs/self-hosting.mdx:160 — The docs claim everyone can browse release history, but the dialog is only reachable while a "What's new" or update notice is active. Resolved by scoping browsing to when the release dialog is shown. (review comment)
• apps/docs/self-hosting.mdx:160 — The documented Release history action is labeled See all Roomote releases in the About dialog. Resolved by documenting the exact visible label. (review comment)

_{Reviewed a00787e}

[roomote-roomote]

Refreshed draft release PR #1887 through origin/develop commit 4b1a8b53; final branch head is 5423f017. The 1.0.0 major rationale is preserved, three newly uncovered release stories were added through committed changesets and pnpm run version -- --amend, and the release-history docs now match the dialog's actual availability. Release tests, docs validation, the full repository check, pre-push checks, and push hooks pass; both review threads are resolved and the PR remains draft.