Repository navigation
chore(agents-state): flip tier3-pr-shepherd to merged (self-implementing) - #95
Conversation
…ing) The Tier 3 PR shepherd was shipped end-to-end before this proposal got promoted through the accepted -> implemented -> merged pipeline. Code merged in mctl-agents PR #12 (1.9.0 tag, commit 0780af4), CWFT + CronWorkflow merged in mctl-gitops PR #88, un-suspend in PR #93. The cron has run autonomously every 2h since 2026-05-01 (smoke run on 2026-05-01 flipped 11 other proposals: 9 merged, 2 rejected). Promoting straight to `merged` rather than walking through accepted -> implemented because: - the implementer has no diff to produce (changes already in main) - the shepherd's status filter is {implemented, review-fixing} only (orchestrator/run_shepherd.py:82), so leaving this `proposed` strands the proposal indefinitely.
|
@codex review |
|
@copilot review |
…shepherd .status.yaml Agent-Logs-Url: https://github.com/mctlhq/mctl-gitops/sessions/e1855f34-53fd-4dcb-9343-aebabaddadaf Co-authored-by: mashkovd <1842423+mashkovd@users.noreply.github.com>
Reviewed. The change is correct — single-file YAML flip to terminal One schema inconsistency fixed in d540972: timestamps were unquoted ( One minor note left unfixed: Otherwise the change is safe to merge: data-only, no K8s effect, and |
|
Codex Review: Didn't find any major issues. Can't wait for the next one! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
The Tier 3 PR shepherd was shipped end-to-end before its own proposal walked through the
accepted -> implemented -> mergedpipeline. Flipping the proposal's.status.yamldirectly tomergedto close the loop — meta-irony resolved.What's already in production
mctl-agentsadded toSERVICESorchestrator/run_shepherd.py,agents/_shepherd/shepherd.md,--review-feedbackon the implementer, tests, README → tag1.9.0(merge commit0780af4, 2026-05-01)1.9.0Why not walk it through the normal pipeline
SHEPHERD_INPUT_STATUSES = {"implemented", "review-fixing"}(orchestrator/run_shepherd.py:82) —proposedis invisible to the cronacceptedand triggering the Tier 2 implementer produces no diff (code already inmain); it would either error out or open an empty PR codex would rejectDiff
Single file:
platform-gitops/agents-state/mctl-agents/proposals/tier3-pr-shepherd/.status.yaml→status: proposed→status: mergedpr:,merge_commit:,merged_at:, and anotes:block explaining the out-of-band shipmentTest plan
git diffshows yaml-only changeagents-state/succeeds (data-only, no K8s effect){implemented, review-fixing}