Change merge submission mode to merge_queue_only

[justin808]

Summary by CodeRabbit

• Configuration
  • Updated submission handling so changes are processed through the merge queue instead of being merged directly.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a486d175-162a-4971-aed0-3152676d20e4

📥 Commits

Reviewing files that changed from the base of the PR and between 47a783d and 016029f.

📒 Files selected for processing (1)

• .agents/agent-workflow.yml

---

Walkthrough

The agent workflow now requires merge-queue-only submissions instead of direct submissions.

Changes

Submission Policy

Layer / File(s)	Summary
Require merge queue submissions .agents/agent-workflow.yml	merge_submission.mode changes from direct to merge_queue_only.

Estimated code review effort: 1 (Trivial) | ~2 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch justin808-patch-1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Per docs/seam-design.md / workflows/pr-processing.md, an explicit mode: merge_queue_only policy on a queue-disabled base returns a deterministic configuration error before mutation (pr-merge-submit fails closed). Worth double-checking that GitHub Merge Queue is actually enabled for main on this repo before/after this merges — otherwise the automated merge-submission tooling (pr-merge-submit) will start failing closed on every PR here instead of falling back to direct merge.

[claude]

Review Summary

What it does: One-line config change in .agents/agent-workflow.yml, switching this repo's own merge_submission.mode from direct to merge_queue_only.

Code quality

• Trivial, well-formed YAML change; no syntax issues.
• merge_queue_only is a documented, supported value for this seam (see docs/seam-design.md, docs/adoption.md, workflows/pr-processing.md, skills/pr-batch/SKILL.md), and the same value is already exercised in test/fixtures/consumer-repo/.agents/agent-workflow.yml, so the value itself is known-good and not a typo/unsupported option.

Potential issues / risk (see inline comment)

• Per the seam docs, an explicit mode: merge_queue_only policy on a queue-disabled base fails closed before mutation with a deterministic configuration error — pr-merge-submit will refuse to merge rather than falling back to direct merge. Since this changes the live policy for this repo's own PRs, it's worth confirming GitHub's Merge Queue is actually enabled for main on shakacode/agent-workflows. If it isn't, this change will break automated merge submission for future PRs here.
• The PR description is empty, so there's no stated rationale for the switch (e.g., "we just enabled Merge Queue on main") — a short description would help future readers/auditors understand why this seam value changed.

Security / performance

• No security or performance implications; this is a policy/config value consumed by internal tooling, not user-facing or executable code.

Test coverage

• No test changes accompany this PR, but none seem necessary — the value is a pre-validated enum already covered by existing fixtures/config-validation tests.

Recommendation: Looks safe to have merged as long as Merge Queue is confirmed enabled for main; otherwise, flip back to direct (or merge_queue_or_guarded_direct) to avoid fail-closed merge failures.