Repository navigation
epic: rollout agy blocking merge gate across mctlhq repositories #11
Description
Overview
Following the successful graduation of Antigravity (agy) reviewer from pilot → blocking merge gate in mctl-agents (PR #140), this issue tracks the staged rollout across all remaining mctlhq repositories.
The reusable workflow mctlhq/.github/.github/workflows/agy-review.yml@main supports blocking: true, which fails the check if the reviewer finds any P1 or P2 severity issues (using an exact machine-readable verdict tag).
Phase 1: Promote Existing Pilot Repositories (blocking: false → true)
These repositories already have .github/workflows/agy-review.yml in pilot mode. Update them to pass blocking: true and add agy-review / review to their branch protection ruleset:
- mctl-agents (PR agy-review: pre-existing classification gaps left out of #139 (quota→decline waves through; a logged-out primary never falls back) #140 merged)
- mctl-api
- mctl-web
- mctl-docs
- mctl-portal
- mctl-telegram
- mctl-design
- mctl-claude-remote
- mctl-pairdesk
- mctl-academy
- pfeifenpatenschaft-backend
- .github — caller added as
agy-pr-review.ymlin ci(agy): review this repository's own pull requests with agy #79 (non-blocking); the standardagy-review.ymlpath is the reusable definition here (ci(agy): mctlhq/.github never reviews its own pull requests with agy #78)
Phase 2: Onboard Remaining Core Repositories
Add .github/workflows/agy-review.yml with blocking: true and configure required status check:
- mctl-gitops
- mctl-agent
- mctl-openclaw
- mctl-trading-data
- mctl-mcp
- mctl-loyalty
- mctl-rule
Workflow Standard Pattern
In .github/workflows/agy-review.yml:
name: Agy PR review
on:
pull_request:
types: [opened, reopened, synchronize, ready_for_review]
permissions: {}
jobs:
agy-review:
uses: mctlhq/.github/.github/workflows/agy-review.yml@75c6d31b97ff15310cd2eec6602198338633d689
permissions:
contents: read
pull-requests: write
with:
blocking: trueAnd configure ruleset via GitHub CLI:
# Add agy-review / review to required_status_checks
Activity
fix(agy-review): name the reviewed commit, and record the latency thi…
mashkovd commentedon Sep 11, 2026
Portfolio hygiene — 2026-09-12
Classification: operational rollout/cleanup, not a strategic platform epic.
This issue should no longer compete in the same portfolio view as Agent Platform, Context Platform, Lifecycle Ownership, Observability or Enterprise MCP.
Cleanup action
Perform one repository-by-repository audit of the actual current state:
Then either:
Do not add new architecture or reviewer-policy design here. Any new cross-repo review lifecycle semantics belong in the current DevLoop/lifecycle-ownership work, not in this historical rollout tracker.
ci(agy): pass no policy text from the caller, and say what @main does…
mashkovd commentedon Oct 15, 2026
Closing this epic as superseded (owner decision, 2026-10-16). Since September 2026 the org policy treats agy as an informational reviewer, not a merge gate: an agy FAIL alone does not block a merge, and each agy P1/P2 on the current head is fixed or refuted during review. The rollout of a blocking agy gate across mctlhq repositories is therefore not planned, which is consistent with the reclassification of this issue as operational cleanup in the comment above from 2026-09-11.
Verified state on the default branches as of 2026-10-16. Fourteen repositories call the reusable
mctlhq/.github/.github/workflows/agy-review.yml; only one passesblocking: true, and no ruleset in the org requiresagy-review / review. Even mctl-agents'mainruleset (id 18455891) requirestests,lintandclaude-review / reviewbut not the agy job.blocking:inputtruefalsefalseagy-pr-review.yml)falsefalse)false)false)false)false)false)false)false)false)false)Child issues closed as not planned with the same rationale, all without activity since 2026-08-08:
No workflow files or rulesets were changed as part of this closure.