task: metrics-agent - Verify control-plane integrations #2127

Task Summary

Verify that Metrics Agent data flows through the control-plane integrations for Meta Agent, Reporting Agent and GitHub issue management. Integration adapters and documentation were associated with merged PR #2131, but the remaining production and end-to-end acceptance criteria require evidence before this issue can be treated as complete.

Linked Stories/Tasks

• Related PR: #2131 — merged integration work; lists this issue as related, not closed.
• Related phase task: Task 3.1: Production Deployment — Metrics Workflow #2126 — production deployment prerequisite.
• Linked Linear issue: task: metrics-agent - Verify control-plane integrations #2127
• Phase 3 project: .github/projects/active/metrics-agent-phase-3-production-2026-08-26/
• Task plan: .github/projects/active/metrics-agent-phase-3-production-2026-08-26/TASK_3.2_INTEGRATION_PLAN.md

Milestones & Timeline

• Existing GitHub milestone: v1.1.
• The task plan's August implementation dates have passed. Confirm the current target during triage rather than carrying them forward as a new commitment.

Acceptance Criteria

• Demonstrate that at least two downstream agents can consume current metrics, including Meta Agent context and Reporting Agent input.
• Demonstrate that reports are generated and published automatically from real metrics data; link example output and the triggering workflow.
• Demonstrate that metrics insights can produce actionable GitHub issues with valid labels, links and appropriate ownership; link an example or controlled test result.
• Run and record an end-to-end test from metrics collection through agent consumption, report output and issue-management output.
• Verify handling of missing or invalid metrics and relevant API or workflow failures.
• Update integration documentation to match the verified behaviour and record applicable CI results.

Steps / Checklist

• Identify the merged integration PR (#2131).
• Compare the merged adapters and documentation with the current Task 3.2 plan.
• Verify Meta Agent consumption of metrics in the intended environment.
• Verify automatic Reporting Agent generation and publication.
• Verify anomaly-to-issue creation and its label and ownership behaviour.
• Link test output, sample reports, example issues and applicable CI results.
• Reconcile the project README's “complete” claim with the verified result before changing this issue's status.

Dependencies

• Metrics collection and output from Task 3.1 (Task 3.1: Production Deployment — Metrics Workflow #2126).
• Access to the current Meta Agent, Reporting Agent and GitHub issue-management workflows.
• Representative metrics data and a safe way to test issue creation without generating unwanted live issues.

Additional Context

The Phase 3 README marks Task 3.2 complete, but the Task 3.2 plan still leaves downstream consumption, automatic reports, anomaly issues and the end-to-end flow unchecked. This issue was reopened on 23 September as planned work not yet started. Treat those as conflicting status records until validation evidence resolves them.

Do not infer production operation or full acceptance solely from merged adapters, test counts or documentation claims.

Definition of Ready (DoR)

• Outcome and acceptance criteria are described.
• Related PR, phase task and project resources are identified.
• Current integration surfaces, test environment and target date are confirmed.

Definition of Done (DoD)

• All acceptance criteria have linked evidence.
• Applicable tests and CI results are recorded, with failures resolved or tracked.
• Integration documentation reflects verified behaviour.
• The issue and project status are reconciled after review.

Verification review — 24 September 2026

#2131 merged the integration adapters and tests. This establishes delivery of code, not production acceptance. The 15 September collection summary claims success, but the accompanying report says “No Data Available”. The workflow archive manifest lists collection and reporting workflows as archived. Evidence is still required for current metrics consumed by both agents, a populated automatically published report, a safely controlled anomaly-to-issue result, and the complete flow and failure cases. The PR’s Testing job and overall gate failed; link applicable passing CI and coverage results before checking those criteria.