[Docs] Sync recent user-facing behavior

apps/docs/automations.mdx

@@ -155,10 +155,10 @@ 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.
+In Slack, automation reports use Slack Markdown with a compact report header and
+action controls. Reports 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/integrations/notion.mdx

@@ -40,9 +40,11 @@ When Memory is enabled, Roomote also backfills the pages shared with this
 integration and keeps their Markdown snapshots current. Notion pages are
 stored under the `notion/` namespace. New and edited pages are picked up on
 regular Memory collector ticks, and a daily full sweep discovers older pages
-that were newly shared without being edited. The same sweep replaces pages
-that are no longer shared with unavailable tombstones, so their former
-content is no longer retained in Memory search results.
+that were newly shared without being edited. After each full sweep, Roomote also
+walks accessible child pages and data sources so content omitted from Notion's
+search index can still enter Memory. The same sweep replaces pages that are no
+longer shared with unavailable tombstones, so their former content is no longer
+retained in Memory search results.
 
 When the integration's capabilities allow listing users, Memory also
 refreshes the workspace user directory once a day to link page authors,

apps/docs/memory.mdx

@@ -194,6 +194,10 @@ Slack, GitHub, task-history, meeting, or pull-request sources. They check those
 live sources when Memory coverage is insufficient, freshness could change the
 answer, or you explicitly ask for live verification.
 
+When recalled context materially shapes an agent's approach, the response
+briefly names the specific useful insight without exposing Memory's internal
+provenance or storage metadata.
+
 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/tasks.mdx

@@ -60,6 +60,9 @@ The task view gives you the working context for a run:
 - previews for running apps
 - task metadata and links back to the surface that started the task
 
+Structured tool details use a readable YAML view. For supported tools, Roomote
+also shows selected inputs after redacting secrets and sanitizing sandbox paths.
+
 If a task started from Slack, Teams, Telegram, Discord, Linear, or source
 control, use the task view when the chat or provider thread does not show enough
 detail to review the work. Presentational widgets remain available in the task