docs(changelog): refresh recent product changes

.claude/skills/changelog/watermark

@@ -1 +1 @@
-df6f62db6a285ae76fdeead26f6081f8f79cdb9d
+6544e2c589cf436de4b18b70755177183b10c7d9

docs/public/changelog/2026-05-22.mdx

@@ -49,6 +49,8 @@ This gives Fabro a durable view of agent task state instead of treating todo upd
 <Accordion title="Workflows">
 - `fabro_run_create` now supports `goal_file` and preserves it as a file-backed run goal
 - `fabro_run_create` now accepts the advertised workflow-string shorthand in MCP clients
+- New `fabro_run_get` tool provides read-only run inspection without mutating workflow state
+- `run.checkpoint.skip_git_hooks` can bypass Git hooks during checkpoint commits
 - Pair user and system messages now appear in the stage Thread tab and activity timeline
 </Accordion>
 
@@ -57,11 +59,15 @@ This gives Fabro a durable view of agent task state instead of treating todo upd
 - Fixed Ask Fabro markdown spacing and heading sizes in narrow panels
 - Fixed reasoning deltas leaking into Ask Fabro output
 - Fixed archived run board updates not refreshing active and archived queries consistently
+- Fixed retryable mid-stream LLM failures being treated as terminal agent errors
+- Fixed agent edit operations by reading raw sandbox file contents before applying patches
 </Accordion>
 
 <Accordion title="Improvements">
 - The run stage sidebar can now collapse to an icon rail while preserving status indicators
 - Ask Fabro example prompts now use fuller, action-oriented text
+- Agent context observability now records memory, activated skills, and MCP tools as run events
+- Anthropic agent sessions now support task lookup and task reminders
 - Run board archived columns now stay in a predictable order after archive and unarchive actions
 - OpenAI `apply_patch` handling is now compatible with Codex-style patch grammar
 </Accordion>

docs/public/changelog/2026-05-23.mdx

@@ -1,8 +1,69 @@
 ---
-title: "Legacy sandbox config migration"
+title: "Runs list, Slack notifications, and structured outputs"
 date: "2026-05-23"
 ---
 
-## Legacy sandbox config auto-migration
+<Warning>
+**Run lifecycle status values changed for API and CLI consumers.** The old `queued` state is now split into `pending` and `runnable`, and approval state is represented explicitly.
 
-Fabro now temporarily rewrites confidently migratable pre-v1.0 `[run.sandbox]` config files to the named environment syntax. A backup is written next to the original file before rewriting. Ambiguous or unsupported legacy keys fail with a targeted migration message instead of the generic TOML unknown-field error.
+To migrate:
+1. Update clients that switch on `queued` to handle `pending` and `runnable`.
+2. Use the approval fields on run summaries and projections when deciding whether a run is waiting for human action.
+</Warning>
+
+## Runs are easier to scan, sort, and recover
+
+The runs list now uses a denser table layout with server-side sorting, pagination, and a redesigned toolbar. You can sort by repo, title, workflow, and changes without waiting for the browser to process the full list.
+
+Failed and dead runs can now be retried from the run UI and API instead of being recreated by hand. The same run lifecycle work also separates pending runs from runnable runs, so approvals and blocked start conditions are clearer in the product and the API.
+
+## Batch run actions
+
+The runs list now supports multi-select archive and unarchive, with matching batch lifecycle endpoints for API clients. Workspace preferences remember the runs view choices you make, so list layout and filtering stay consistent across visits.
+
+Run size is now exposed on summaries and projections, which gives the UI and API a shared way to distinguish small, medium, and large runs. The web app uses that signal in the run header and list surfaces where scale matters for triage.
+
+## Agent stages expose more of what is happening
+
+Agent stage pages now include a stage insights sidebar, context-window snapshots, and richer stage projections for todos, subagents, skills, MCP tools, reasoning effort, speed, and model usage. This makes it easier to see why a stage is behaving a certain way without digging through raw events.
+
+Structured output validation is also stricter. Agent and prompt stages with `output_schema` now validate model output in the same context and ask the model to repair invalid responses before the workflow moves on.
+
+## Slack run lifecycle notifications
+
+Workflows can now send run lifecycle updates to Slack through `[run.notifications]`. Teams can keep a channel informed when a run starts, needs attention, finishes, or fails without wiring a separate webhook workflow.
+
+```toml
+[run.notifications]
+slack = true
+```
+
+## More
+
+<Accordion title="API">
+- New `POST /api/v1/runs/archive` and `POST /api/v1/runs/unarchive` endpoints apply lifecycle actions to multiple runs at once
+- Run summaries and projections now expose run size buckets
+- Stage projections now include agent todos, subagents, skills, MCP tools, context-window data, and model usage
+- `output_schema` validation errors now include structured repair context for agent and prompt stages
+</Accordion>
+
+<Accordion title="Workflows">
+- Named environments replace run-scoped sandbox config, with automatic migration for confidently supported legacy `[run.sandbox]` files
+- Legacy sandbox config migration writes a backup next to the original file before rewriting
+- Ambiguous legacy sandbox config now fails with a targeted migration message
+- Interview options now carry metadata through the API, console, Slack blocks, and agent question tools
+</Accordion>
+
+<Accordion title="Fixes">
+- Fixed the Quick Start screen flashing when navigating to `/runs` with archived preferences
+- Fixed implement-plan pull requests advancing before CI checks completed
+- Fixed an event append race covered by a regression test
+</Accordion>
+
+<Accordion title="Improvements">
+- Added a Waterfall view for run events with hover popovers and duration breakdowns
+- Added live timing overlays for in-flight runs
+- Generated run titles now use the lighter `small_default` model role asynchronously
+- Settings pages now show provider and integration logos, including upcoming Teams, Discord, and Jira integrations
+- Stage insights sidebar polish improved visit syntax, spacing, and quiet-state presentation
+</Accordion>

docs/public/changelog/2026-05-24.mdx

@@ -0,0 +1,39 @@
+---
+title: "Batch delete and richer stage details"
+date: "2026-05-24"
+---
+
+## Delete runs in batches
+
+The runs list bulk toolbar now includes Delete for selected runs. API clients can use the matching batch delete endpoint to remove multiple runs in one request and get per-run results back.
+
+```http
+POST /api/v1/runs/delete
+```
+
+## Stage details are closer at hand
+
+Stage status, model, and event details are now available from hover popovers across the run overview graph, stage sidebar, and stage events toolbar. You can inspect stage metadata without leaving the current run view.
+
+Loaded stage events also gained Copy and Download actions. That makes it easier to move event output into an issue, support thread, or local investigation without selecting text from the page.
+
+## More
+
+<Accordion title="API">
+- New `POST /api/v1/runs/delete` endpoint deletes multiple runs and returns per-run results plus a summary
+</Accordion>
+
+<Accordion title="Fixes">
+- Fixed unfinished stages being left open after a run failure
+- Removed a non-functional demo-mode Connect dropdown
+- Suppressed the redundant Starting pill on the runs list
+</Accordion>
+
+<Accordion title="Improvements">
+- Added a run size badge to the run header
+- Unconfigured provider rows now link directly to a prefilled secret form
+- Removed retired OpenAI models from the catalog
+- Improved muted stage status pill contrast
+- Collapsed the stage events search field behind an icon by default
+- Updated the Automations nav icon
+</Accordion>

docs/public/docs.json

@@ -252,6 +252,8 @@
             "group": "May 2026",
             "icon": "clock-rotate-left",
             "pages": [
+              "changelog/2026-05-24",
+              "changelog/2026-05-23",
               "changelog/2026-05-22",
               "changelog/2026-05-21",
               "changelog/2026-05-20",