[WIP] Cap Documentation Unbloat at max_turns:30 and require at least 1 safe output

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

---

This section details on the original issue you should resolve

<issue_title>[deep-report] Cap Documentation Unbloat at max_turns:30 and require at least 1 safe output</issue_title>
<issue_description>### Description
The Documentation Unbloat workflow is the most expensive daily workflow in the fleet: 58 turns, $2.46/run, 14.8 min — yet it produces 0 safe outputs (no issues, PRs, or discussions created). The observability kit flags it resource_heavy + partially_reducible (50% of turns are data-gathering that could be moved to deterministic pre-steps). Without a required safe output, the workflow consumes budget without producing any verifiable artifact.

Expected Impact

Two changes: (1) add max_turns: 30 to prevent runaway consumption; (2) add a pre-agent shell step to list candidate docs files (replacing ~29 data-gathering turns); (3) require noop at minimum if no docs need unbloating, enforcing that the agent always signals intent. Estimated savings: ~$1.50/run ($45/month).

Suggested Agent

Any agent with write access to .github/workflows/documentation-unbloat.md and ability to add shell pre-steps.

Estimated Effort

Medium (1–4 hours) — requires prompt redesign to accept pre-gathered file list + max_turns config change.

Data Source

DeepReport Intelligence Briefing — 2026-04-21 (run §24729745351); corroborated by Agent Performance Report #27491, Observability Report #27292.

Generated by DeepReport - Intelligence Gathering Agent · ● 586.9K · ◷

• expires on Apr 23, 2026, 3:15 PM UTC

Comments on the Issue (you are @copilot in this section)