docs(changelog): backfill product updates from 2026-10-08 to 2026-10-19

en/ai-sre/artifacts.mdx

@@ -7,10 +7,10 @@ sidebarTitle: Artifacts
 
 ## Overview
 
-An artifact is a file AI SRE produces in a session and publishes to the artifact gallery. There are two ways to publish, and they accept different types:
+An artifact is a file AI SRE produces in a session and publishes to the artifact gallery. There are two ways to publish:
 
-- **The agent publishes**: HTML / Markdown documents only (`.html` `.htm` `.md` `.markdown`). Each one is a self-contained report or page. The most common example is the operational insight report that `/insight` generates in a session. The agent doesn't publish other types.
-- **You publish**: select the "Publish to artifact gallery" button next to a file in the session (see [Creating an artifact](#creating-an-artifact) below). This accepts a wider set of types:
+- **The agent publishes**: the agent publishes its output from the session as an artifact, in any of the types in the table below. The most common example is the operational insight report that `/insight` generates in a session.
+- **You publish**: select the "Publish to artifact gallery" button next to a file in the session (see [Creating an artifact](#creating-an-artifact) below).
 
    <Accordion title="View publishable file types">
 
@@ -19,6 +19,7 @@ An artifact is a file AI SRE produces in a session and publishes to the artifact
    | Web pages & documents | `.html` `.htm` `.md` `.markdown` `.txt` `.log` |
    | Data & config | `.csv` `.tsv` `.json` `.yaml` `.yml` `.xml` `.toml` `.ini` |
    | Images | `.png` `.jpg` `.jpeg` `.gif` `.svg` `.webp` |
+   | Video & audio | `.mp4` `.webm` `.mov` `.mp3` `.m4a` `.wav` |
    | PDF | `.pdf` |
    | Source code | `.py` `.go` `.js` `.mjs` `.ts` `.jsx` `.tsx` `.java` `.c` `.h` `.cpp` `.cs` `.rb` `.rs` `.php` `.sh` `.sql` `.kt` `.swift` `.scala` `.css` `.vue` `.svelte` `.proto` `.tf` `.hcl`, and more |
    | Archives | `.zip` `.tar` `.gz` `.tgz` |
@@ -31,6 +32,18 @@ A published artifact initially inherits its source session's scope: artifacts fr
 
 Entry point: **AI SRE → Artifacts** in the left navigation.
 
+### Content forms and how they display
+
+| Form | What you see |
+|---|---|
+| Multi-file page | One HTML page can bundle its styles, scripts, and images and is shown as-is on the artifact detail page. A single publish allows up to 255 files (including the entry page) and 64 MiB in total. A page, text, data, or code file can be up to 16 MiB each; images, video, audio, PDF, and archives up to 15 MiB each |
+| Canvas | Several pages laid out on one canvas that you can pan and zoom (2%–400%); select a board to view it full window. Suited to reviewing several interface designs side by side |
+| Slides | Each page is a fixed 1920×1080. Turn pages with the arrow keys or Space, and select **Present** for full screen |
+| Table | `.csv` / `.tsv` files display as a table with a fixed header row. Up to 1000 rows and 200 columns are shown, within 20000 cells in total, so a wide table shows fewer rows |
+| Video & audio | `.mp4` `.webm` `.mov` and `.mp3` `.m4a` `.wav` play in the browser's built-in player |
+
+A publish that exceeds the file-count or size limits is rejected with the reason; trim the files and publish again.
+
 <Note>
 You can't upload files to the artifact gallery directly. The agent produces and publishes every artifact in a session, and **New artifact** also opens a session for this. The gallery is for browsing, searching, and managing published artifacts.
 </Note>

en/ai-sre/automations.mdx

@@ -264,7 +264,7 @@ The preset template **War room initial analysis** (template key `war_room_initia
 
 ## Run history
 
-Every rule keeps its run history. Click a rule row to open its detail page: the left column shows **Configuration** and the right column shows **Run History**. The **Run now** button at the top of the right column triggers a run directly. That button does not appear when **War room created** is the rule's only trigger — those runs happen in the IM group, so the rule has no console run.
+Every rule keeps its run history. Click a rule row to open its detail page: the left column shows **Configuration** and the right column shows **Run History**. The **Run manually** button at the top of the right column triggers a run directly. That button does not appear when **War room created** is the rule's only trigger — those runs happen in the IM group, so the rule has no console run.
 
 Run history is shown as a table with these columns:
 
@@ -308,9 +308,9 @@ When a run's status is `failed`, `blocked`, `abandoned` or `skipped`, the **Name
 |---|---|
 | AI SRE is not enabled, or this period's credits or balance are used up; the run did not execute | Enable or top up on the AI SRE tab of **Payment → Plan** |
 | The On-call subscription has expired or its plan does not include AI SRE; AI SRE is paused | Renew or upgrade on the On-call tab of **Payment → Plan** |
-| The run did not finish in time and was abandoned | Click **Run now** on the rule detail page to retry |
-| The run was interrupted | Click **Run now** on the rule detail page to retry |
-| The run ended without a final reply | Click **Run now** on the rule detail page to retry |
+| The run did not finish in time and was abandoned | Click **Run manually** on the rule detail page to retry |
+| The run was interrupted | Click **Run manually** on the rule detail page to retry |
+| The run ended without a final reply | Click **Run manually** on the rule detail page to retry |
 | Joined another analysis | Click the row to open the analysis that took over the incident |
 
 Other reasons show the text recorded by the system.
@@ -328,7 +328,7 @@ Each rule offers a set of actions in the **Actions** column:
 | Action | Notes |
 |---|---|
 | Enable / Disable | An inline switch. When disabled, the rule is kept but no longer triggers; disabling does not delete existing run history. |
-| Run now | Starts one real run manually from the rule row. The action performs preflight checks first. For a rule at the **Web** execution place it creates a hidden session and opens it; for an **IM** rule it opens a new session in the bound IM chat, and the console only shows **Manual run submitted. Check the run history for progress.** Manual runs are limited to one per rule per minute. When **War room created** is the rule's only trigger, neither the list nor the detail page offers this action — such a rule produces no console run, and calling the run-now API returns an error. |
+| Run manually | Starts one real run manually from the rule row. The action performs preflight checks first. For a rule at the **Web** execution place it creates a hidden session and opens it; for an **IM** rule it opens a new session in the bound IM chat, and the console only shows **Manual run submitted. Check the run history for progress.** Manual runs are limited to one per rule per minute. When **War room created** is the rule's only trigger, neither the list nor the detail page offers this action — such a rule produces no console run, and calling the run-now API returns an error. |
 
 Clicking anywhere on the rule row opens its detail page, where you can edit the configuration, delete the rule, and view its run history (see "Run History" above).