[deep-report] Add proxy.golang.org to firewall allow-list for Go-tooling reviewer workflows

[github-actions]

Description

The PR Code Quality Reviewer workflow needs Go tooling, but proxy.golang.org is not in its network.allowed list, so go-based commands are blocked mid-run and the run fails at the firewall. The Weekly Workflow Analysis (discussion #43770) attributed a firewall block of proxy.golang.org (3 requests) as the root cause of at least one PR Code Quality Reviewer failure, and this same block was flagged back in April (prior deep-report #24311) — it is a recurring, unfixed gap.

What to do

Add proxy.golang.org (and sum.golang.org if Go module verification is used) to the network.allowed list in the frontmatter of every Go-tooling workflow (start with pr-code-quality-reviewer), or add it to the shared defaults allow-list if Go tooling is broadly used. Recompile the affected lock files.

Expected Impact

Eliminates a recurring firewall-induced failure class in the PR review family (currently a 50-62% success-rate hotspot), reducing false-red runs and wasted action-minutes.

Suggested Agent

Instructions Janitor / a workflow-config agent, or the PR Code Quality Reviewer maintainer.

Estimated Effort

Fast (< 30 min)

Data Source

DeepReport Intelligence Briefing 2026-07-06; source discussion #43770 (Weekly Workflow Analysis).

Generated by 🔬 Deep Report · 204.6 AIC · ⌖ 17.5 AIC · ⊞ 10.2K · ◷

• expires on Jul 8, 2026, 8:03 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 · 3.81 AIC · ⌖ 5.37 AIC · ⊞ 7.2K · ◷