[hippo] Add guardrails for list_code_scanning_alerts prompt usage

[github-actions]

Summary

Add validation or helper guidance so workflow prompts that call list_code_scanning_alerts consistently include state: open and severity: critical,high.

Memory: mem_0324334270d0

Rationale

Hippo surfaced a high-retrieval memory that unconstrained list_code_scanning_alerts calls can produce oversized MCP responses. This is a focused, actionable quick win that could prevent prompt/runtime failures in affected workflows.

Next steps

• Locate workflow prompts and templates that reference list_code_scanning_alerts.
• Add validation, linting, or helper text that requires or strongly nudges state: open and severity: critical,high.
• Update any existing prompts that omit those filters.
• Add a regression test covering the constrained form and the failure/warning path for unconstrained usage.

Generated by 🦛 Daily Hippo Learn · 23.9 AIC · ⌖ 21.3 AIC · ⊞ 5.4K · ◷

• expires on Jul 13, 2026, 11:03 PM 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 · 1.23 AIC · ⌖ 4.54 AIC · ⊞ 5.3K · ◷

[Tarekchehahde]

Community contribution (Phase 0 port of upstream PR work):

• Fork PR: feat(compiler): warn on unconstrained list_code_scanning_alerts Tarekchehahde/gh-aw#3
• Upstream compare: main...Tarekchehahde:gh-aw:fix/fix/44896-list-code-scanning-guardrail

Compile-time guardrail for unconstrained list_code_scanning_alerts (upstream #44933 was closed).