infra[notask]: add multi-repo coverage to DevOps PR status skill

[Proletter]

🎯 What problem does this PR solve?

• The qv-devops-pr-status dashboard only ever scanned the primary monorepo (tetherto/qvac), even though the SKILL.md prose advertised extraRepos multi-repo coverage that was never implemented in code. The DevOps pod owns work across ~two dozen ops/dev/research repos and had no single view of open PRs across them.
• Supersedes the closed infra[notask]: extend qv-devops-pr-status to scan qvac-*/github-ops/oss-actions repos #2183, which attempted the same feature on a now-stale branch using a qvac-* glob + oss-actions. This PR uses an explicit curated extraRepos list (keeping glob support available for anyone who prefers it).

📝 How does it solve it?

• Adds an optional extraRepos list to .github/teams/<pod>.json (validated in team.mjs, defaults to []). In --mode team, collectPRActivity scans the primary repo (path-filtered by ownedPaths) plus every open PR in each extra repo, where the pod is treated as the sole owner.
• resolveExtraRepos accepts plain owner/name entries and owner/prefix-* globs (resolved per run via gh repo list). Repos the caller cannot read are skipped with a one-line stderr reason instead of aborting the run.
• pr-status.mjs emits a Repos: scope header and renders extra-repo PRs as owner/repo#<num> (the monorepo keeps bare #<num>) across the active sections, the Excluded section, and JSON output.
• --mode review / --mode my are unchanged (primary repo only), so qv-pr-mine and the daily-work-update consumer are unaffected.
• Hardening from review:
  • The Excluded section is capped at 10 PRs per repo with a … +N more in <repo> summary, so a busy sole-owner extra repo can't bury the dashboard (--json still carries the full list).
  • gh repo list glob resolution warns when it hits the 1000-repo cap instead of silently missing repos.
  • extraRepos specs must be exactly owner/name; multi-segment specs (owner/group/name) are now rejected with a warning rather than silently truncated.
  • Team-dashboard re-review dedup is keyed on the repo-qualified prRef, so same-numbered PRs in different repos no longer mask each other.

🧪 How was it tested?

• Ran node .cursor/skills/_lib/pr-skills/pr-status.mjs --pod devops --mode team --authors pod against the live curated list: scanned the monorepo + 19 reachable extra repos; the 7 unreachable qvac-research-* / qvac-model-tools repos were skipped with Could not resolve to a Repository reasons and the run continued.
• Verified the per-repo Excluded cap: tetherto/qvac-workbench (11 excluded PRs) rendered 10 entries + … +1 more in tetherto/qvac-workbench — use --json for the full list.
• Confirmed extra-repo PRs render as owner/repo#<num> and monorepo PRs stay bare #<num>; the Repos: header lists the primary repo + 19 extra.
• Sanity-checked --mode my still scans only the primary repo.
• node --check clean on the edited scripts; no linter errors.

Scope note: the curated extraRepos list has 26 entries; 7 (qvac-research-*, qvac-model-tools) are currently unreachable for the runner's account (private/no-access or renamed) and auto-activate once reachable.

🤖 Regenerated with Cursor (skill: /qv-devops-pr-create)

[github-actions]

Tier-based Approval Status

**PR Tier:** TIER1

**Current Status:** ✅ APPROVED

**Requirements:**
- 1 Team Member approval ✅ (2/1)
- 1 Team Lead OR Management approval ✅ (1/1)



---
*This comment is automatically updated when reviews change.*

[Proletter]

/review