[daily-report] 2026-05-07 pipeline summary #156

Summary

20 proposals tracked across 8 repos: 13 merged, 4 rejected, 3 implemented (PRs merged on GitHub but shepherd sync pending). The incident-auto-cleanup series (phases 1–4b) shipped in full over the last 24h — phases 1, 3, and docs/mcp-agents-tools are fully merged; phases 2, 4a, 4b have their PRs merged on GitHub but .status.yaml still reads implemented (shepherd will flip them on its next run). The original phase4-metrics proposal was cleanly rejected and split into the 4a+4b approach. 34 PRs merged org-wide in the last 24h — the busiest single day since tracking started, driven by Temporal platform launch, trading-data MCP features, and ArgoCD observability work. Six stale open PRs remain unaddressed: follow-up comment posted on the existing mctl-portal#7 issue, two new stale-pr issues opened for mctl-api dep bumps and the WIP gitops claim-mechanism PR.

Proposal pipeline state

⚠️ Three proposals show implemented but their PRs are already merged on GitHub (phase2/#13 merged 2026-05-06T23:05Z, phase4a/#16 merged 2026-05-07T07:04Z, phase4b/#17 merged 2026-05-07T07:25Z). The shepherd cron will flip these to merged on its next 2h cycle. Not a stuck-proposal condition — transient sync lag.

Pipeline diff (vs yesterday — #122 · 2026-05-05)

• Newly merged (3): mctl-agent/incident-auto-cleanup-phase1, mctl-agent/incident-auto-cleanup-phase3, mctl-docs/mcp-agents-tools
• Newly rejected (1): mctl-agent/incident-auto-cleanup-phase4-metrics — superseded; scope was too large for one $3 implementer run; cleanly split into 4a+4b
• Newly in pipeline (3): incident-auto-cleanup-phase2 (implemented), incident-auto-cleanup-phase4a-metrics-wiring (implemented), incident-auto-cleanup-phase4b-metrics-full (implemented) — all appeared and had their PRs merged within this reporting window
• Still in-progress: none
• Still proposed: none
• Unchanged terminal (13): all pre-existing merged/rejected proposals

Recent merged PRs (24h)

34 PRs merged between 2026-05-06T09:00Z and 2026-05-07T09:00Z:

Notable themes: Temporal platform launch (5 PRs), trading-data MCP/openclaw wiring (6 PRs), ArgoCD observability + ArgoCD-verify-on-merge (3 PRs), incident-auto-cleanup pipeline (4 PRs), CPU limit tuning (2 PRs).

Bot commits (24h)

13 commits by mctl-agents in the last 26h:

fd786c8 2026-05-07 07:22:21 +0000  chore(agents): implement incident-auto-cleanup-phase4b-metrics-full 2026-05-07
454946a 2026-05-07 06:58:43 +0000  chore(agents): implement incident-auto-cleanup-phase4a-metrics-wiring 2026-05-07
48feb84 2026-05-07 06:31:46 +0000  chore(agents): full run 2026-05-07
3f6983a 2026-05-07 00:27:04 +0000  chore(agents): implement incident-auto-cleanup-phase4-metrics 2026-05-07
c012365 2026-05-07 00:00:38 +0000  chore(agents): implement incident-auto-cleanup-phase4-metrics 2026-05-07
34eb354 2026-05-06 23:24:34 +0000  chore(agents): shepherd mcp-agents-tools 2026-05-06
70022f6 2026-05-06 23:15:29 +0000  chore(agents): shepherd mcp-agents-tools 2026-05-06
129de61 2026-05-06 23:05:36 +0000  chore(agents): implement mcp-agents-tools 2026-05-06
6642e4c 2026-05-06 22:39:56 +0000  chore(agents): shepherd run 2026-05-06
48918f0 2026-05-06 22:37:42 +0000  chore(agents): implement incident-auto-cleanup-phase2 2026-05-06
6a8f9a3 2026-05-06 21:40:29 +0000  chore(agents): implement incident-auto-cleanup-phase3 2026-05-06
7dc36e6 2026-05-06 20:31:04 +0000  chore(agents): shepherd run 2026-05-06
2d23b6b 2026-05-06 20:12:21 +0000  chore(agents): implement incident-auto-cleanup-phase1 2026-05-06

Note: incident-auto-cleanup-phase4-metrics appears twice (c012365, 3f6983a) — two consecutive failed implementer runs that exhausted the $3 budget cap, leading to the rejection and 4a/4b split.

Detected problems

No stuck proposals detected (no proposals in in-progress or proposed state). Three proposals show implemented with PRs already merged on GitHub — transient shepherd sync lag, not a stable stuck condition.

Cluster health

Skipped: api.mctl.ai MCP connector not attached yet. See TODO at the bottom of this issue.

Errors during run

• MCP scope restriction (persistent): GitHub MCP connector is scoped to mctlhq/mctl-gitops only. As in all previous runs, this daily-report issue and all stand-alone issues are filed in mctlhq/mctl-gitops instead of the intended mctlhq/mctl-agents. Previous daily-report history was found via search_issues across the org (worked correctly). Fix: add mctlhq/mctl-agents to the MCP connector's allowedRepositories.

TODO

Attach the api.mctl.ai MCP connector to this routine to unlock workflow-run counts (mctl_list_workflows), MinIO PVC % (mctl_get_resource_usage), per-service restart counts (mctl_get_service_status), and ArgoCD app sync state.