[Docs] Sync public guides with recent shipped behavior

apps/docs/automations.mdx

@@ -94,6 +94,9 @@ webhooks for each active repository's current default branch, uses the
 deployment helper model to write a brief commit summary, and includes the pusher
 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.
+Other announcements link to the provider's compare view.
 
 ## Custom automations
 

apps/docs/fast-sessions.mdx

@@ -33,9 +33,11 @@ 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, search, pins, recent
-Sessions, and unread indicators. **Ready** is not a terminal state: you can
-reply or start another execution in the same Session later.
+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.
 
 The transcript renders prompts, replies, and tool activity in real time with a
 generated title that updates as the Session evolves.

apps/docs/memory.mdx

@@ -25,6 +25,8 @@ Roomote fills Memory from what it can already see:
   can read
 - **GitHub issues** in connected repositories
 - **Notion pages** explicitly shared with the deployment's Notion integration
+  including readable database property values such as status, dates, people,
+  labels, relations, and formula or rollup results
 - **meeting notes** from Granola, when that integration is connected
 - **employee directory and reporting structure** from Rippling, when that
   integration is connected; HRIS reporting and membership fields remain
@@ -79,7 +81,9 @@ references in page snapshots in those cases, but it does not guess a match from
 the display name. The workspace user directory is refreshed once a day; people
 removed from the workspace (or hidden when the integration loses its
 user-listing capability) have their Notion identity cards marked deleted on
-the next refresh.
+the next refresh. Notion may truncate long multi-value database properties;
+Memory marks those partial values and links back to the source page for the
+complete list.
 
 ## Turning it on
 

apps/docs/models.mdx

@@ -28,11 +28,13 @@ Some hosting deployments provision **Roomote inference** with a limited,
 spend-capped credit grant during setup. It is separate from your own provider
 connections: in particular, you can add an OpenRouter key in **Settings >
 Models** even when Roomote inference is active. If the hosting deployment does
-not offer it, the option is not shown. Trial token usage and estimated model
-cost appear in task details and [Cost Analytics](/cost-analytics), while the
-remaining credit line reflects the hosted grant's authoritative limit. Its key
-is stored with your other provider credentials, so deleting the Roomote
-inference provider in **Settings > Models** disables it permanently.
+not offer it, the option is not shown. The Roomote Cloud trial includes $5 of
+inference, enough to complete several tasks before you connect your own
+provider. Trial token usage and estimated model cost appear in task details and
+[Cost Analytics](/cost-analytics), while the remaining credit line reflects the
+hosted grant's authoritative limit. Its key is stored with your other provider
+credentials, so deleting the Roomote inference provider in **Settings > Models**
+disables it permanently.
 
 For example, a deployment might use:
 

apps/docs/self-hosting.mdx

@@ -187,9 +187,9 @@ After you upgrade, Roomote can surface the new release in the web app:
 
 The final setup step offers a small set of preselected starter tasks. Keep the
 ones you want, clear any you do not want to run yet, then select **Go**. If you
-start one task, Roomote opens it directly; if you start several, Roomote opens
-the task list. You can also clear every selection and finish setup without
-starting a task.
+keep any selected, Roomote completes setup and opens one **Set up Roomote**
+Session that launches the starter tasks and keeps their progress together. You
+can also clear every selection and finish setup without starting a Session.
 
 After setup, run a small task that uses the first environment if you did not
 start one from the starter list. A healthy deployment should let you: