[deep-report] Grant LintMonster update_issue permission for scheduled (non-issue-triggered) runs

[github-actions]

Description

LintMonster's 2026-08-03 daily run found 670 largefunc findings and tried to refresh the authoritative function-length tracker (#49251), but the attempt failed with: update_issue requires an issue context ... use create_discussion or create_issue instead. The workflow's safe-output config doesn't currently permit update_issue when the run isn't triggered by an issue event (it's a schedule-triggered run), so it can only publish a discussion report instead of keeping the tracker current.

Expected Impact

Lets LintMonster keep the authoritative function-length backlog issue (#49251) up to date automatically instead of only posting disconnected daily discussions, reducing manual maintainer effort to reconcile the two.

Suggested Agent

Existing maintainer / LintMonster workflow owner (safe-output config change)

Estimated Effort

Quick (< 1 hour) — likely a lockfile/frontmatter permission addition (update-issue safe-output with an explicit target issue number) plus recompile.

Data Source

DeepReport Intelligence Briefing 2026-08-03, cross-referencing LintMonster discussion #49888.

Generated by 🔬 Deep Report · agent · 112.8 AIC · ⌖ 36.4 AIC · ⊞ 5.7K · ◷

• expires on Aug 5, 2026, 7:43 AM UTC-08:00

[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 · gpt54 · 3.44 AIC · ⌖ 9.33 AIC · ⊞ 9.1K · ◷