[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 4b1a8b53
• 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.
• Let connected MCP clients read Fast Session history and send follow-ups through the same Roomote task communication interface used for standard tasks.
• 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.

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.

Documentation coverage

• Fast as the default for unpinned requests, direct coding-task selection, Sessions, dashboard search, responsive details, chat continuation, ambient participant handling, reactions, and widget previews: updated Sessions, Communications, and Automations.
• 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 while the release dialog is shown, plus 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, and ingestion freshness: covered by Memory, Discord, Linear, and Notion.
• Fast attachment delegation, Roomote MCP continuation, Merge announcer configuration, and Cost Analytics dimensions: covered by File attachments, Roomote MCP, Automations, and Cost Analytics.
• No new provider or integration was added, so no navigation or provider-icon update is required.

Validation

• pnpm test:release-scripts (16 tests passed after the latest develop amendment)
• mise exec -- pnpm --filter @roomote/docs check (Mintlify validation and broken-link checks passed)
• pnpm check (full lint, type checks, tests, and knip passed across all 27 tasks after resetting the shared test schema)
• node scripts/pre-push-checks.mjs and the push hook (oxlint, residual lint, fast type checks, and knip passed)
• git diff --check
• release integrity checks confirmed 1.0.0, only the root package version changed, every pending changeset was consumed, and .changeset/README.md remains

Impact

Squash-merging this 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 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)

_{Reviewed 5423f01}

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