enhancement: Triage broodly's 16 open PRs — potential stale epic branches

[don-petry]

Summary

broodly has 16 open PRs, many of which are long-lived epic branches (Epics 0–13). Combined with a failing CI on main, this creates a risk of divergence and merge conflicts.

Open PRs

• Compliance: claude-md-missing-agents-ref #51 — Epic 0: Firebase auth, Cloud Run deploy, CI/CD
• Compliance: missing-pr-quality #48 — Epic 13: Demo readiness
• feat: add AgentShield CI standard and agent-shield.yml workflow template #25–38 — Various epic branches (Epics 2–13)

Recommended Actions

1. Triage each epic PR: is it still active, or should it be closed?
2. Rebase or merge main into long-lived branches to reduce drift
3. Fix the CI failure on main first (see related issue about "Push API Image" failure)
4. Consider adopting a "close stale PRs" automation (e.g., actions/stale)
5. Establish a policy for maximum PR age in standards/ docs

Context

Identified during weekly org CI/Security survey on 2026-04-05.

[don-petry]

Relocated to petry-projects/broodly#73 — repo-specific issues belong in their repo.