[Chore] Release Roomote 1.0.0

CHANGELOG.md

@@ -2,6 +2,63 @@
 
 This file tracks product releases for Roomote (single monorepo version). Automated release entries are prepended by `pnpm run version`.
 
+## 1.0.0 (2026-08-30)
+
+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.
+
+### Highlights
+
+- Start unpinned requests in Fast by default, while choosing an environment or repository still starts coding work immediately.
+- Enable Memory by default for new hosted deployments and recall public Discord discussions, visible Linear issues, and richer Notion database properties.
+- Follow conversations, delegated executions, artifacts, reviews, and costs in a searchable Session workspace across desktop and mobile.
+- Continue Fast across supported chat providers, delegate parallel work with attachments, preview generated HTML safely, and announce default-branch changes.
+
+### 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.
+
 ## 0.45.1 (2026-08-29)
 
 This patch restores complete Notion database discovery across Memory and the built-in Notion MCP.

apps/docs/automations.mdx

@@ -96,6 +96,9 @@ and commit authors. Feature-branch pushes and branch deletions are ignored.
 GitHub, GitLab, Azure DevOps, Bitbucket, and Gitea are supported.
 For GitHub merge commits that Roomote can match to a pull request, the summary
 uses that pull request's context and **View changes** opens the pull request.
+When the pull request body contains a suitable image, the Slack announcement
+can also show one representative screenshot after Roomote validates its URL and
+image type. Announcements continue without an image when validation fails.
 Other announcements link to the provider's compare view.
 
 ## Custom automations
@@ -142,11 +145,9 @@ when repository or workspace execution is required.
 Fast runs deliver to every custom-automation report destination: Slack,
 Discord, Microsoft Teams, or Telegram, as either a channel/chat or a direct
 message to the automation owner. Each run keeps a distinct Fast session, and
-the report links back to that session in the web app. Slack, Discord, and
-Microsoft Teams replies continue the Fast session directly in chat. Teams only
-resumes after verifying the active tenant installation, conversation, and
-linked user. Telegram can deliver the same reports and continue them from the
-web app, but inbound Telegram replies still use its normal task-routing flow.
+the report links back to that session in the web app. Replies on all four
+providers continue the Fast session directly in chat. Roomote verifies the
+active provider installation, conversation, and linked user before resuming.
 Runs with no report destination remain stored Fast sessions and do not post to
 chat.
 

apps/docs/communications.mdx

@@ -58,13 +58,18 @@ also needs an environment that can run the suggestion's target repository.
 Configured **Call Roomote via emoji** automations are separate from these
 suggestion reactions.
 
+When the suggestion is not pinned to an execution target, Fast-capable chat
+surfaces start it in Fast so Roomote can answer or delegate as needed. A pinned
+environment, repository-only surface, or provider without Fast support starts
+the coding task directly.
+
 ## React to Roomote replies
 
 When you react to a Roomote reply in an active Fast conversation, Roomote can
-use that reaction as context. The linked user who owns the Fast conversation
-must add the reaction. Roomote posts a text reply when the reaction warrants a
-response and otherwise stays silent; it does not react to the reaction event
-itself.
+use that reaction as context, including as an answer to a question it asked.
+The linked user who owns the Fast conversation must add the reaction. Roomote
+posts a text reply when the reaction warrants a response and otherwise stays
+silent; it does not react to the reaction event itself.
 
 | Provider | Fast reply reactions | Provider limits |
 | --- | --- | --- |

apps/docs/fast-sessions.mdx

@@ -20,6 +20,11 @@ when the request needs a repository workspace. Selecting an environment or
 repository starts the execution directly, but Roomote still creates the
 owning Session and opens it with that execution selected.
 
+Fast is the default for **Auto** and other unpinned requests across the web
+dashboard and supported chat providers. Choose an environment or repository
+explicitly when the request should skip conversation-first routing and start a
+coding task immediately.
+
 Select **New Session** in the navigation to open the same launcher from any
 dashboard page.
 
@@ -33,19 +38,41 @@ Execution cards show their status, workspace, pull requests, artifacts, latest
 error, and cost. Select a card to open the lightweight details panel, or choose
 **Open full workspace** for terminal, logs, diff, and preview tools.
 
-The Sessions page supports list and board views, filters, pins, recent Sessions,
-and unread indicators. Search matches Session and task titles, repositories,
-and conversation text. Queries of at least three characters include transcript
-matches and show a highlighted excerpt. **Ready** is not a terminal state: you
-can reply or start another execution in the same Session later.
+When delegated tasks keep working after the conversation becomes idle, the
+timeline shows the live task count. Select that activity to open the **Tasks**
+panel. The **Artifacts** panel combines the latest uploaded outputs from every
+task in the Session, labels which task produced each item, and opens previews
+without leaving the Session. Individual task details continue to show their own
+artifacts.
+
+**Session info** shows the total inference cost for the conversation and its
+attached tasks. Open the cost breakdown to separate direct Session orchestration
+from each task's usage.
+
+The Sessions page supports list and board views, pins, recent Sessions, and
+unread indicators. Common scope, status, and time filters stay visible; turn on
+advanced filters for user, environment, pull request, model, and source. Active
+advanced filters remain visible until you clear them, and Roomote remembers the
+selected list or board view. Search matches Session and task titles,
+repositories, and conversation text. Queries of at least three characters
+include transcript matches and show a highlighted excerpt. **Ready** is not a
+terminal state: you can reply or start another execution in the same Session
+later.
+
+Session rows show who or which automation started the work, its source and
+cost, and links to accumulated active pull requests. In the Session workspace,
+those pull requests remain available across delegated tasks. Selecting the live
+task count opens the only running task directly or shows the task list when
+several are active. A Session link with a selected task opens that task's full
+workspace while keeping the Session conversation alongside it on desktop.
 
 The transcript renders prompts, replies, and tool activity in real time with a
 generated title that updates as the Session evolves.
 
 Fast sessions can also render presentational widgets such as status cards,
 tables, and plans directly in the transcript. Widget HTML is sanitized and
-sandboxed in the web view; chat surfaces receive only the widget's text
-fallback.
+sandboxed in the web view. Chat surfaces receive a concise text preview and a
+link to open the rendered widget when both are available.
 
 ## Reply to a session
 
@@ -55,12 +82,20 @@ that live on another surface, Roomote posts the answer back into the originating
 thread with a quoted copy of your web message, so the conversation stays in one
 place for everyone following it there.
 
+For substantive requests, Fast sends a brief acknowledgement before it starts
+model-invoked work. An eligible Slack message may receive an acknowledgement
+reaction instead. Immediate answers and clarifying questions remain single
+responses, and delegated tasks keep their existing kickoff message rather than
+posting a duplicate acknowledgement.
+
 Fast replies across Slack, Discord, Microsoft Teams, and Telegram link back to
-the Session view. Slack and Discord can also resume Fast directly from chat.
-Microsoft Teams replies continue the same Session after Roomote verifies the
-tenant, installation, conversation, and linked user. Telegram currently uses
-the Session view for Fast follow-ups because its inbound webhook route does not
-yet carry Fast Session identity.
+the Session view and can resume the same Session directly from chat. Roomote
+verifies the provider installation, conversation, and linked user before it
+accepts the follow-up.
+
+In shared Slack and Discord conversations, Fast can stay silent when linked
+participants are talking to each other. A direct reply to Roomote, a mention,
+an explicit Fast command, or a direct message still requires a response.
 
 ## Execution access