[Docs] Align public docs with recent product changes

apps/docs/automations.mdx

@@ -94,6 +94,10 @@ Create arbitrary scheduled agent runs with:
 Each automation card summarizes its cadence, workspace target, report destination,
 creator, and most recent run.
 
+Use **View previous runs** on an automation card to open the task list
+filtered to that automation's runs. For a custom automation, the history is
+scoped to that specific automation rather than all custom automations.
+
 When creating an automation through Roomote chat, ask for **suggested tasks** or
 **launchable follow-ups** if qualifying findings should become tasks that
 teammates can start from the report. Asking only for a summary or list of action
@@ -129,6 +133,11 @@ conclusions and actions in its first message; supporting detail can continue in
 thread replies. Explicit instructions in the automation prompt about format,
 length, tone, audience, or detail placement always take precedence.
 
+In Slack, automation reports appear as structured cards. Markdown tables render
+as tables when they fit, and the card can include links to the task, related pull
+requests, and automation settings. Completed runs also show their trigger or
+schedule, model, estimated inference cost, and elapsed time.
+
 Direct-message destinations require the automation owner to link an account for
 the selected communications provider and make the bot reachable there.
 

apps/docs/brain.mdx

@@ -31,8 +31,8 @@ Roomote fills the Brain from what it can already see:
 
 Turning the Brain on also backfills history rather than starting from the
 moment you enabled it. Completed tasks are enqueued immediately, and each
-source drains its own deeper history in the background over the following
-ticks.
+source drains its own deeper history in bounded background passes that resume
+after an interruption.
 
 Private Slack channels and DMs are never read. Adding the Roomote bot to a
 public channel is what designates that channel as a source, so the corpus stays
@@ -78,6 +78,11 @@ Agents get the Brain as an MCP server with read-only tools. They can search it,
 recall relevant pages, browse what exists, and ask for a synthesized answer
 with sources. They cannot write to it directly.
 
+For a substantive topic, agents query the Brain before consulting overlapping
+Slack, GitHub, task-history, meeting, or pull-request sources. They check those
+live sources when Brain coverage is insufficient, freshness could change the
+answer, or you explicitly ask for live verification.
+
 Writes go through Roomote instead. When an agent finishes substantial work it
 records a short memory of what it did, and the platform places that text under
 a slug it controls, after scrubbing credential-shaped strings. An agent can

apps/docs/environments.mdx

@@ -79,11 +79,12 @@ already started with.
 
 ## Edit an environment
 
-When you edit an existing environment, Roomote gives you three views of the
+When you edit an existing environment, Roomote gives you four views of the
 same configuration:
 
 - **Editor** is the visual form for common environment settings.
 - **YAML** is the raw configuration for precise edits and advanced options.
+- **Diff** compares the saved configuration with your editable YAML draft.
 - **Preview** shows the saved structure in a more readable form before you use
   it for new tasks.
 

apps/docs/environments/definition.mdx

@@ -473,10 +473,12 @@ before the environment is used for a task.
 
 ## Validate and iterate
 
-The visual **Editor**, **YAML**, and **Preview** views in the environment editor
-all operate on this same document, so you can switch between hand-written YAML
-and the form freely. Roomote validates the definition on save; fix any reported
-errors before the environment runs a task.
+The visual **Editor**, **YAML**, **Diff**, and **Preview** views in the
+environment editor all operate on this same document, so you can switch between
+hand-written YAML and the form freely. **Diff** keeps the saved configuration
+read-only on the left while you edit the YAML draft on the right. Roomote
+validates the definition on save; fix any reported errors before the environment
+runs a task.
 
 After saving, the surest test is to run a real task. A healthy environment
 finishes setup without manual intervention, exposes the previews or logs a task