BT6 Merge Train
Use only after bt6-queue-audit. Apply bt6-maintainer-guardrails.
Authorization preflight
Confirm the current operator explicitly authorized merging in the resolved
repository. Record:
- canonical repository/tracker and expected actor;
- candidate PR numbers and audited head SHAs;
- base branch and permitted merge method;
- whether this is dry-run or live;
- current queue-audit reference and expiration conditions.
Approval to inspect, plan, review, fix, or prepare is not merge authorization.
Never merge
- requested-changes, draft, conflict/dirty, or ambiguous PR state;
- missing/failing required checks;
- head SHA different from the audited SHA;
- policy-disallowed merge method or unexpected base branch;
- unresolved security, privacy, citation, provenance, corpus, schema, data-loss,
compatibility, or research-integrity finding;
- missing profile-required risk-surface verification;
- missing PR-tier core checks, applicable 50% changed-line coverage, or relevant
tests for changed behavior;
- missing, stale, incomplete, or non-merge-ready external-provider assessment;
- a PR whose target repository/tracker/actor cannot be proven.
Candidate ordering
Respect dependencies and gate-critical fixes first. For otherwise independent
work, prefer narrowly scoped docs/config, small verified defects, integrity and
compatibility fixes, then larger features. Recompute ordering after each merge.
Per-PR procedure
- Re-fetch PR metadata, exact head SHA, base, mergeability, reviews, required
checks, linked issues, dependencies, and new human feedback.
- Compare the head with the queue audit and PR-audit evidence.
- Confirm hostile-input and all matched risk-surface checks are current.
- Run any PR-tier
quick or risk-surface validation invalidated by base-branch
movement. Do not require tagged-release full validation for an ordinary
merge candidate.
- For external-provider changes, confirm the provider assessment matches the
exact head and its integration-complete and merge-ready verdicts are
yes.
- Verify the merge method is allowed and dry-run is false.
- Merge exactly one PR through the canonical tracker.
- Verify the resulting canonical-branch commit and post-merge CI.
- Reconcile linked issues by observed state. Comment/close only when separately
authorized; do not assume closing keywords worked.
- Refresh base branch, open queue, reviews, checks, dependencies, and candidate
ordering before considering another PR.
Stop conditions
Stop on any merge conflict, check failure, unexpected commit, issue mismatch,
new feedback, stale audit, changed profile/policy, or ambiguous external state.
Do not skip a failed candidate and continue unless the operator's authorization
explicitly covers that behavior and remaining candidates are independent.
Use templates/bt6-merge-train-report.md. Record every attempted/merged PR,
exact SHA, method, checks, authorization, linked-issue outcome, and stop reason.
1---2namespace: bt6-maintainer3name: bt6-merge-train4platforms: [all]5description: Run an explicitly authorized, conservative BT6 merge train that processes validated pull requests one at a time and reconciles repository, CI, evidence, and issue state after each merge.6triggers:7 - bt6 merge train8 - merge validated BT6 pull requests9 - start a maintainer merge session10 - integrate ready research tool changes11requires:12 - current-queue-audit: ready candidates with exact audited head SHAs13 - explicit-merge-authorization: operator authorizes repository, candidates, and mutation in the current context14 - tracker-write-access: configured canonical tracker actor may merge15ensures:16 - dry-run-default: no merge occurs unless explicitly authorized and dry-run is disabled17 - one-at-a-time: only one PR is merged before all relevant state is refreshed18 - current-gates: head, base, reviews, checks, risk-surface verification, and policy are rechecked immediately before merge19 - reconciliation: canonical branch, CI, linked issues, and queue state are checked after each merge20commandHint:21 argumentHint: "<pr...> [--method squash|merge|rebase] [--dry-run] [--stop-on-conflict]"22 allowedTools: Bash, Read23 model: sonnet24 category: release-management25 modelRole: reasoning26 modelTier: standard27metadata:28 source: https://skillmd.com/skills/elder-plinius/bt6-merge-train29---3031# BT6 Merge Train3233Use only after `bt6-queue-audit`. Apply `bt6-maintainer-guardrails`.3435## Authorization preflight3637Confirm the current operator explicitly authorized merging in the resolved38repository. Record:3940- canonical repository/tracker and expected actor;41- candidate PR numbers and audited head SHAs;42- base branch and permitted merge method;43- whether this is dry-run or live;44- current queue-audit reference and expiration conditions.4546Approval to inspect, plan, review, fix, or prepare is not merge authorization.4748## Never merge4950- requested-changes, draft, conflict/dirty, or ambiguous PR state;51- missing/failing required checks;52- head SHA different from the audited SHA;53- policy-disallowed merge method or unexpected base branch;54- unresolved security, privacy, citation, provenance, corpus, schema, data-loss,55 compatibility, or research-integrity finding;56- missing profile-required risk-surface verification;57- missing PR-tier core checks, applicable 50% changed-line coverage, or relevant58 tests for changed behavior;59- missing, stale, incomplete, or non-merge-ready external-provider assessment;60- a PR whose target repository/tracker/actor cannot be proven.6162## Candidate ordering6364Respect dependencies and gate-critical fixes first. For otherwise independent65work, prefer narrowly scoped docs/config, small verified defects, integrity and66compatibility fixes, then larger features. Recompute ordering after each merge.6768## Per-PR procedure69701. Re-fetch PR metadata, exact head SHA, base, mergeability, reviews, required71 checks, linked issues, dependencies, and new human feedback.722. Compare the head with the queue audit and PR-audit evidence.733. Confirm hostile-input and all matched risk-surface checks are current.744. Run any PR-tier `quick` or risk-surface validation invalidated by base-branch75 movement. Do not require tagged-release `full` validation for an ordinary76 merge candidate.775. For external-provider changes, confirm the provider assessment matches the78 exact head and its integration-complete and merge-ready verdicts are `yes`.796. Verify the merge method is allowed and dry-run is false.807. Merge exactly one PR through the canonical tracker.818. Verify the resulting canonical-branch commit and post-merge CI.829. Reconcile linked issues by observed state. Comment/close only when separately83 authorized; do not assume closing keywords worked.8410. Refresh base branch, open queue, reviews, checks, dependencies, and candidate85 ordering before considering another PR.8687## Stop conditions8889Stop on any merge conflict, check failure, unexpected commit, issue mismatch,90new feedback, stale audit, changed profile/policy, or ambiguous external state.91Do not skip a failed candidate and continue unless the operator's authorization92explicitly covers that behavior and remaining candidates are independent.9394Use `templates/bt6-merge-train-report.md`. Record every attempted/merged PR,95exact SHA, method, checks, authorization, linked-issue outcome, and stop reason.