[jonahgabriel]

OMN-16933 — remove CodeRabbit entirely

Operator ruling (2026-08-29, verbatim): "remove completely."

CodeRabbit is removed entirely, not demoted to advisory. This supersedes the
2026-08-28 usefulness audit (omni_home/docs/tracking/2026-08-28-coderabbit-usefulness-audit.md),
which recommended keeping the reviewer and dropping only the gate.

What this PR does

• deletes .github/workflows/cr-thread-gate.yml
• deletes .github/workflows/cr-thread-gate-caller.yml
• drops the stale CodeRabbit mention from auto-merge.yml's OMN-7786 header comment

Sequencing

Required-context references are removed before workflow files so no in-flight
PR strands on a check that can no longer be produced. This repo carried no
CodeRabbit context in dev branch protection and none in
EXPECTED_EXTERNAL_CONTEXTS, so there is nothing to strand here.

Verified before this PR: gh api repos/OmniNode-ai/<repo>/branches/dev/protection/required_status_checks --jq .contexts returned no CodeRabbit entry.

Not in scope

Downstream dead code (node_coderabbit_triage, coderabbit_triage skills,
pr_review_bot thread-resolution duties) is tracked in OMN-16934.

Ref: OMN-16933

Evidence-Ticket: OMN-16933
Evidence-Source: OCC#7557

Summary by CodeRabbit

• Chores
  • Updated automated merge workflow messaging to refer generally to completed reviews.
  • Removed automated pull request thread-gating workflows and their associated validation checks.

[onexbot-occ-writer]

OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 429d6dfb-f3cb-4393-bf4a-7a17af9e674e

📥 Commits

Reviewing files that changed from the base of the PR and between 1c84840 and f0dc3ab.

📒 Files selected for processing (3)

• .github/workflows/auto-merge.yml
• .github/workflows/cr-thread-gate-caller.yml
• .github/workflows/cr-thread-gate.yml

💤 Files with no reviewable changes (2)

• .github/workflows/cr-thread-gate-caller.yml
• .github/workflows/cr-thread-gate.yml

Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

---

📝 Walkthrough

Walkthrough

The PR updates the auto-merge workflow comment to use general review-completion wording. It also deletes the pull request thread-gate caller and reusable gate workflows.

Changes

Review workflow cleanup

Layer / File(s)	Summary
Auto-merge and thread-gate workflow cleanup .github/workflows/auto-merge.yml, .github/workflows/cr-thread-gate-caller.yml, .github/workflows/cr-thread-gate.yml	The auto-merge comment now refers to review completion generally. The thread-gate workflows and their triggers, inputs, secrets, and validation job are removed.

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

Merge Risk: ⚪ Minimal · up to f0dc3

This change removes obsolete CodeRabbit workflow automation without introducing a current-head merge-blocking risk; it is merge-ready after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: removal of the CodeRabbit thread-gate workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-16933-omnimemory-remove-coderabbit

---

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