feat: Reporting Agent v2 — multi-repo, session cache, pluggable storage

[Copilot]

Upgrades scripts/agents/reporting.agent.js from v1 to v2.0.0. All v1 exports remain fully backwards-compatible.

---

name: "Feature PR"
about: "New features or enhancements"
title: "feat: {short summary}"
labels: ["status:needs-review", "area:feature"]

Feature Pull Request

This repository enforces changelog, release, and label automation for all PRs and issues.
See the organisation-wide Automation Governance & Release Strategy for contributor rules.

Linked issues

Changelog

Added

• Multi-repository reports — generateMultiRepoReport() aggregates data across multiple repos; parseRepoRef() normalises "owner/repo" strings or { owner, repo } objects (validates exactly one /); buildRepoCacheKey() produces stable cache keys; runAgent({ action: "generate:multi-repo" }) dispatcher entry.
• Session cache — in-process TTL cache (cacheGet/cacheSet/cacheClear/cacheSize) for memoising expensive per-repo computations within a single agent run; exposed via runAgent({ action: "cache:*" }).
• Pluggable storage backend — setStorage/resetStorage/createMemoryStorage replace hard-coded fs calls in saveReport, enabling injection of an in-memory backend in tests.
• AGENT_VERSION constant ("2.0.0") exported and returned by the default runAgent action.
• 50 regression tests covering all new and existing behaviour (scripts/agents/__tests__/reporting.agent.test.js).
• Migration guide at .github/reports/migration/reporting-agent-v2-migration-guide-2026-08-29.md.

Changed

• saveReport now routes writes through the active storage backend instead of calling fs directly.
• runAgent default response now includes version alongside categories and message.
• Removed unused import.meta.url / fileURLToPath import (was blocking Jest transforms).

Fixed

• runAgent cache:get no longer calls cacheGet twice (double expiry-check side-effect).
• parseRepoRef now rejects three-segment strings like "owner/org/repo" explicitly.

Removed

---

Checklist (Global DoD / PR)

• All AC met and demonstrated
• Tests added/updated (unit/E2E as appropriate)
• Accessibility checklist completed (where relevant):
  • Semantic HTML and heading order verified
  • Keyboard navigation and visible focus states verified
  • ARIA used only where needed
  • Contrast and non-colour cues reviewed (WCAG 2.2 AA or higher)
• Docs/readme/changelog updated (if user-facing)
• Security checklist completed (where relevant):
  • Untrusted input validated and sanitised
  • Output escaped for its rendering context
  • Privileged actions enforce nonce and capability checks
  • No secrets/sensitive data introduced; OWASP risks reviewed
• Code/design reviews approved
• CI green; linked issues closed; release notes prepared (if shipping)

---

• Fixes Reporting Agent v2 Phase 4.1: Reporting Agent v2 Integration #2037

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[github-actions]

🔍 Reviewer Summary for PR #2489

CI Status: ❌ pending
Files changed: 5

Recommendations

• CI checks not green

[github-actions]

🔍 Reviewer Summary for PR #2489

CI Status: ❌ pending
Files changed: 5

Recommendations

• CI checks not green

[github-actions]

🚫 This PR description is missing required template content.

Missing required section(s): Linked issues, Global DoD checklist

Please update the PR body using one of the repository PR templates:

• https://github.com/lightspeedwp/.github/blob/develop/.github/pull_request_template.md
• https://github.com/lightspeedwp/.github/tree/develop/.github/PULL_REQUEST_TEMPLATE

Empty placeholders, unchecked checklist boxes, and stub issue references do not count.

[github-actions]

🔍 Reviewer Summary for PR #2489

CI Status: ❌ pending
Files changed: 5

Recommendations

• CI checks not green

[github-actions]

⚠️ Branch Naming Issue

This PR's branch name copilot/reporting-agent-v2-integration doesn't follow the standard pattern.

Standard pattern: {type}/{scope}-{title} (e.g., feat/something, fix/bug-name)

Based on linked issue type: task

Correct template should be: pr_feature.md

No action required — this is informational. Future PRs should use the correct branch name.

See Branching Strategy for more info.