[PHASE 2] Metrics Agent Coverage

[ashleyshaw]

Summary

Add test coverage for the metrics agent so its collection, aggregation, and reporting paths are reliable.

Action

• Action Type: Create
• Target File: scripts/agents/__tests__/metrics.agent.test.js

Proposed Test Content

This phase covers tasks 2.1 to 2.15 from the source README:

• create the test file structure and setup
• cover metric collection and GitHub API response handling
• cover aggregation, report generation, and error handling
• cover edge cases, async timing, and configuration-driven behaviour
• validate the file-level coverage lift and document the slice

Scope & Applicability

• Type: Unit / integration-style coverage for the metrics agent
• Affected Areas: repository metrics collection, aggregation, report generation
• Audience: maintainers, developers, QA

Parent Issue

• Parent Issue: [EPIC] Test Coverage Implementation Programme #932

Acceptance Criteria

• Metrics-agent test file exists and follows repo conventions.
• Core collection, aggregation, and reporting paths are covered.
• Error handling and empty-input edge cases are covered.
• The phase is documented and passes the required test run.
• Change is documented in the project change log.
• PR uses correct branch prefix (test/).

Additional Context

This phase carries the largest single-file coverage lift in the programme.

---

Definition of Ready (DoR)

• Purpose, scope, and audience defined
• Target file and action type specified
• Acceptance criteria listed
• Estimate added (if applicable)

Definition of Done (DoD)

• All acceptance criteria met and verified
• Changelog entry prepared for PR
• Test passes all required scenarios and environments
• Documentation updated (if needed)
• PR uses correct branch prefix (test/)
• Approved by at least one maintainer

[linear-code]

LS-997

LS-1113

[github-actions]

✅ Issue checklists finalised after closure.