Recompile metrics-collector workflow to enable metrics collection

[Copilot]

The metrics-collector workflow lock file had the same timestamp as its source, causing it to be flagged as outdated and potentially blocking metrics collection for the 128 workflows in this repository.

Changes

• Ran make recompile to regenerate workflow lock files
• Updated metrics-collector.lock.yml timestamp to be newer than source (03:36:10 vs 03:31:05)
• Verified workflow compiles with 0 errors/warnings and recent runs succeed

Configuration Validated

The workflow is correctly configured to collect daily metrics:

• Storage: memory/meta-orchestrators branch under metrics/**
• Tools: agentic-workflows (status/logs), GitHub MCP (engagement data), repo-memory
• Schedule: Daily at 14:28 UTC
• Retention: 30 days of daily snapshots

Expected Metrics Structure

{
  "workflows": {
    "workflow-name": {
      "workflow_runs": {"total": 7, "successful": 6, "success_rate": 0.857},
      "safe_outputs": {"issues_created": 5, "prs_created": 2},
      "engagement": {"issue_reactions": 12, "pr_comments": 8}
    }
  },
  "ecosystem": {
    "total_workflows": 120,
    "overall_success_rate": 0.892
  }
}

Metrics will accumulate in latest.json and daily/YYYY-MM-DD.json after next scheduled run. Trend analysis requires ~7 days of data collection.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>P0: Enable Workflow Execution Metrics Collection</issue_title>
<issue_description>## Problem

The workflow health monitoring system lacks execution metrics data, preventing comprehensive health analysis of the 128 workflows in this repository.

Current State

• Metrics Location: /tmp/gh-aw/repo-memory-default/memory/default/metrics/latest.json
• Status: File does not exist
• Impact: Cannot analyze workflow success rates, failure patterns, or mean time between failures (MTBF)

Missing Capabilities

Without metrics data, the health manager cannot:

1. ✗ Calculate workflow success/failure rates
2. ✗ Identify consistently failing workflows
3. ✗ Track performance trends over time
4. ✗ Detect workflow regressions
5. ✗ Analyze error patterns across workflows
6. ✗ Calculate mean time between failures (MTBF)
7. ✗ Generate reliability scores based on execution history

Root Cause

The metrics-collector.md workflow is outdated (source modified after lock file compilation), which may be preventing metrics from being collected and stored properly.

Required Actions

1. Recompile metrics-collector workflow

make recompile  # Or specifically: gh-aw compile .github/workflows/metrics-collector.md

2. Verify metrics collection schedule

Check that metrics-collector.md is scheduled to run daily and has proper permissions to write to shared memory.

3. Wait for metrics accumulation

After fixing compilation, allow at least 7 days for metrics to accumulate for meaningful trend analysis.

4. Verify metrics storage

After first run, verify file exists:

ls -lh /tmp/gh-aw/repo-memory-default/memory/default/metrics/latest.json
cat /tmp/gh-aw/repo-memory-default/memory/default/metrics/latest.json | jq '.timestamp'

Expected Metrics Structure

The metrics file should contain:

• Per-workflow run statistics (total runs, successes, failures)
• Success rates calculated
• Timestamps for tracking trends
• Historical data for 30-day analysis

Dependencies

• Related to: #[P0 recompile issue]
• Blocks: Comprehensive workflow health analysis
• Blocks: Automated failure detection
• Blocks: Performance trend tracking

Priority

P0 - Critical: This is a meta-monitoring capability that enables all other health checks. Without metrics, health monitoring is limited to structural analysis (compilation status, configuration) and cannot detect runtime failures.

Success Criteria

• metrics-collector.md lock file is up-to-date
• Metrics collector runs successfully on schedule
• /tmp/gh-aw/repo-memory-default/memory/default/metrics/latest.json exists and contains valid data
• Historical metrics accumulate in metrics/daily/ directory
• Workflow Health Manager can analyze execution metrics

---

Detected by Workflow Health Manager on 2026-01-04

AI generated by Workflow Health Manager - Meta-Orchestrator

Comments on the Issue (you are @copilot in this section)

• Fixes P0: Enable Workflow Execution Metrics Collection #8824

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.