[deep-report] [quick-win] Justify or reduce `max-effective-tokens: 80M` on `daily-observability-report.md`

[github-actions]

Problem

From Repository Quality audit #35222: daily-observability-report.md sets max-effective-tokens: 80000000 (80M tokens) — twice the next-highest value across all 6 workflows that set this field. It runs daily, with no documented justification for the elevated ceiling.

With the API consumption report (#35204) showing today consumed 118K REST calls (2.6× the 7-day average), per-workflow budget hygiene matters.

Expected Impact

• Either documents the legitimate reason for the 80M cap (so future audits stop flagging it), or reduces it to match peers (saves daily token budget)
• Either way, makes the ceiling auditable

Suggested Approach

1. Check actual token usage from recent runs of daily-observability-report (gh-aw logs MCP tool)
2. If real usage is well below 80M, drop the cap to a value closer to actual (e.g. 2× observed p95)
3. If real usage approaches 80M, add a comment in the workflow frontmatter explaining why

Suggested Agent

Claude or Copilot — needs a quick log query + a single frontmatter edit.

Acceptance Criteria

• Either reduced max-effective-tokens with no degraded report quality over 3 runs, or documented justification in the frontmatter

Estimated Effort

30–60 minutes

Source

• #35222 Repository Quality Improvement Report — 2026-05-27
• #35204 GitHub API Consumption Report — 2026-05-27

Generated by 🔬 DeepReport - Intelligence Gathering Agent · opus47 9.2M · ◷

• expires on May 29, 2026, 4:03 PM UTC

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · haiku45 42.8K · ◷