Repository navigation
crons: the trinity auto-merge card -- ten-minute sweep, dispatch half live, merge half waiting for the bee - #12169
Conversation
…, dispatch half live, merge half waiting for the reviewer bee (Refs #12145.)
Summary by t27-beesChecked by the t27 compilert27c parse, parse-complete and typecheck on each changed .t27 file at
Read by the modelThis PR adds a cron card ( Worth a look
Read: 1 files, +101 -0, the whole diff. Head |
|
Merged on explicit owner instruction: the owner overrode the |
What
The cron card for the trinity merge autopilot's GitHub Actions job:
specs/crons/trinity-auto-merge.t27, modulecron_trinity_auto_merge, IDgithub-actions/trinity/auto-merge.The job it describes is the workflow
Auto Merge Ready PRsat Trinity-S-AI-DNA/trinity.github/workflows/auto-merge.yml(the trinity half of this pair: Trinity-S-AI-DNA/trinity#1742): every ten minutes it sweeps trinity's open PRs on main -- dispatching the existing "PR work report and blog" workflow for heads that lack theirT27 work reportcommit status, and squash-merging only what a reviewer bee labelledbee-reviewedafter the head push. The merge half is dormant by design until the reviewer bee reaches trinity (the owner's rule of 2026-10-02: the Queen must not merge by herself).Registry honesty
Per the crons law (specs/crons/README.md and #12145), the card lands only together with the workflow: this PR and the trinity workflow PR land as a pair and reference each other. This PR is therefore held with the
no-auto-mergelabel until the trinity workflow PR merges -- remove that label (or merge by hand) once the workflow is on trinity main.The card follows the README schema exactly (KIND
cron, HOSTgithub-actions, REPOtrinity, SERVICE.github/workflows/auto-merge.yml, SCHEDULE*/10 * * * *, RUNS empty with RUNS_NOTEno skill invocation found in source, ON_FAILUREissue, CONTROLgithub-actions-dispatch), carries the four schema tests of its sibling cards, and typechecks (t27c check: 0 errors, 0 warnings; ID unique among the cards).Owner approval (owner-approved-foreign label)
On 2026-10-25, in the agent session driving the T27F live lane (OpenCode, t27/trinity repos), the owner said, verbatim: "сам!! одобряю тебе сделать все owner-approved-foreign" -- approving the owner-approved-foreign label for the pull requests of this lane. This PR itself adds no hand-written foreign code (the card is a .t27 spec); the label covers the lane's pair PR in trinity, which adds the workflow YAML.
The t27 half of #12145 (the cron card). The trinity half is the workflow PR: Trinity-S-AI-DNA/trinity#1742.
Refs #12145.