[daily-report] 2026-05-24 pipeline summary #298

⚠️ Routing note: Intended for mctlhq/mctl-agents; posted here because the GitHub MCP session is restricted to mctlhq/mctl-gitops. Fix: add mctlhq/mctl-agents to the MCP allowed-repositories list. Baseline: mctlhq/mctl-gitops#269 (2026-05-22).

1. Summary

42 proposals tracked across 10 repos — all 42 in terminal state (36 merged, 6 rejected). Pipeline fully clear for the second consecutive day. 6 new proposals appeared and immediately merged within the 24h window (3 mctl-design, 3 mctl-telegram). Standout: mctl-telegram is in an intensive ChatGPT App Store submission sprint — 37 PRs merged in 24h covering MCP annotations, outputSchema, submission readiness, /demo page, and domain verification. 8 bot commits (3 shepherd, 3 implement, 1 reconcile, 1 issue-poll). 4 new stale-pr issues opened (mctl-docs#17, mctl-gitops#217, mctl-agent#20, mctl-web#12 all crossed the 7-day threshold today, as predicted in yesterday's watch list). 7 dedup follow-up comments posted on existing stale-pr issues.

2. Proposal Pipeline State

3. Pipeline Diff (vs #269 — 2026-05-22)

Yesterday: 36 proposals — merged(31), rejected(5) — all terminal
Today: 42 proposals — merged(36), rejected(6) — all terminal

• Newly merged (6): (all appeared as new proposals already in merged state)
  • mctl-design/issue-3 → PR mctl-design#8 merged 2026-05-23T12:46Z
  • mctl-design/issue-4 → PR mctl-design#5 merged 2026-05-22T19:08Z
  • mctl-design/issue-6 → PR mctl-design#7 merged 2026-05-23T00:46Z
  • mctl-telegram/issue-154 → PR mctl-telegram#157 merged 2026-05-23T10:31Z
  • mctl-telegram/issue-158 → PR mctl-telegram#162 merged 2026-05-23T13:57Z
  • mctl-telegram/issue-159 → PR mctl-telegram#163 merged 2026-05-23T12:51Z
• Newly rejected: none
• Newly proposed: none (all new proposals first observed in merged state)
• Still proposed: none
• Still in-progress: none

4. Recent Merged PRs (24h)

PRs merged across the org since 2026-05-23T09:00Z. Source: org:mctlhq is:pr is:merged merged:>=2026-05-23.

45 PRs merged in 24h — mctl-telegram dominates with a ChatGPT App Store submission sprint (versions 0.30.0 → 0.34.1 in a single day).

(45 PRs total — mctl-telegram: 37 (ChatGPT App Store submission sprint, 0.30.0→0.34.1), mctl-gitops: 4, mctl-claude-remote: 3, mctl-agents: 1, mctl-openclaw: 1, mctl-design: 1.)

5. Bot Commits (26h)

git log --author="mctl-agents" --since="26 hours ago" in mctlhq/mctl-gitops

8 bot commits — 3 shepherd, 3 implement, 1 reconcile, 1 issue-poll. The 3 implement runs in ~15 min (09:44–09:57) are consistent with parallel processing of the new mctl-design and mctl-telegram proposals.

6. Detected Problems

New stale-pr issues opened (4)

These PRs crossed the 7-day dormancy threshold today. All were flagged in yesterday's watch list (#269), confirming stable problems.

Existing stale-pr issues — dedup follow-up comments posted (7)

Watch list — PRs approaching 7-day threshold

Stuck proposals

None — all proposals in terminal state.

7. Cluster Health

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

8. Errors During Run

9. TODO

• Fix write scope: Add mctlhq/mctl-agents (read + issue-write) to the GitHub MCP session's allowed-repositories list. Every daily-report run since 2026-05-05 has been misrouted to mctlhq/mctl-gitops.
• Act on watch-list PRs (mctl-api#55–58) — 4 dep-bump PRs will cross the 7-day stale threshold on 2026-05-25.
• Resolve mctl-docs#17 (release 0.1.20 stuck 8 days) — confirm whether release-please auto-merge is configured for mctl-docs or if the PR requires manual merge.
• Resolve mctl-gitops#217 (incident responder CronWorkflow, 8 days) — rebase or close if design has changed.
• Resolve mctl-agent#20 (statefulset-replicas-mismatch skill, 8 days) — merge or close if superseded by newer skill work.
• Resolve mctl-web#12 (redesign v3, 8 days) — confirm whether active or superseded by a different branch.
• 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.