docs: document tool executions in the Operate area

[evantahler]

Adds a Tool Executions page under Operate → Governance, next to Audit Logs, documenting the dashboard surface and read API shipped in ArcadeAI/monorepo#2661 and #2662.

The page covers both jobs the feature exists for: a developer debugging why a tool call failed by reading the exact inputs and outputs, and an operator reviewing what a project ran for compliance and usage. It documents the access split those PRs introduced — the history is readable by anyone holding a role on the project, while the recorded inputs and outputs take project-admin authority, and diagnostics stay readable either way — plus the dashboard filters, the three read endpoints, and the retention window.

Also adds three dashboard screenshots, cross-links the page from the developer-facing tool error handling guide, and adds it to the Governance and Operate card grids.

Verified with pnpm lint, pnpm test (835 pass), pnpm check-meta, Vale (0 errors), and a local dev-server render of the new page and both card grids.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes with no runtime or security logic touched.

Overview
Adds Tool Executions under Operate → Governance: a new guide for the dashboard history and read API (list, count, detail with optional inputs/outputs), including filters, role-based visibility, debugging workflows, and org-level recording/retention.

Governance and Operate overview copy and card grids now mention reviewing tool runs alongside audit logs. The build tool error handling guide links to Tool Executions for post-hoc debugging. Nav metadata and public/llms.txt register the page.

^{Reviewed by Cursor Bugbot for commit d64aa72. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 25, 2026 7:48pm

[josebarrueta]

Reviewed the Retention section against the PLT-2978 stack now in review, and opened #1141 into this branch with the corrections — stacked so nothing here is rewritten.

The headline is that "contact Arcade support" is about to stop being true: setting the retention window and turning recording on or off is becoming self-service (monorepo #3165 for the API, #3243 for the dashboard page). But three smaller things in that paragraph are worth more than the missing capability, because a reader who acts on them is misled:

• "or a project overrides it" — project-level settings are an explicit non-goal of the spec. Nothing customer-reachable sets a project's own window, and the API reports retention_changeable_at_project: false for exactly that reason.
• "turn off execution logging and delete the history" — these are different operations with different effects. Turning recording off stops new runs being written and leaves stored ones to expire on the window; the retention sweep marks on the window alone and never reads whether recording is on. Shortening the window is the control that deletes, and it reaches records already held.
• No bounds — nothing said 0 and 400 are refused with a 422 rather than clamped.

One note for whoever merges: #1141 documents behaviour that hasn't shipped. If this PR lands first, hold that one until the stack merges, or the page promises a dashboard page that isn't there yet.

Everything else here reads correctly against the implementation — the filters, the authority split on inputs and outputs, and the endpoint table all match.