Add Bunny review command bootstrap

[Promansis]

Linked issue

Closes #

Why this change

• Adds the minimal default-branch /bunny-review bootstrap so GitHub can receive issue comment commands and dispatch the trusted reviewer workflow on refactor.

What changed

• Added .github/workflows/bunny-review-command.yml on main.
• The workflow authorizes collaborator/member/owner comments, parses /bunny-review mode, writes a command-status comment, and dispatches bunny-review.yml on the trusted refactor target ref.

Refactor impact

Primary owner:

• GitHub workflow automation.

Impact areas reviewed:

• GitHub Actions issue_comment bootstrap and workflow dispatch wiring.

Boundary notes:

• No app source, engine, React feature, shared API, Tauri, storage, provider, or remote-runtime boundary is touched. This is a default-branch GitHub Actions bootstrap only.

Pressure points touched:

• GitHub Actions issue-comment event handling and dispatch to the trusted Bunny Review workflow on refactor.

Validation

• Matching validation command passes locally (for example pnpm typecheck, pnpm build, pnpm check:architecture, pnpm check:docs, or full pnpm check when warranted)
• pnpm check passes locally before PR push/handoff, including the unused-code check
• pnpm typecheck passes locally
• pnpm build passes locally
• pnpm check:architecture passes locally
• pnpm check:docs passes locally
• cargo check --manifest-path src-tauri/Cargo.toml --workspace passes locally
• Rust clippy/tests were run for Rust behavior changes
• Browser or Tauri app manual verification completed
• Browser screenshot/recording evidence added when UI/browser state is the claim
• Remote runtime smoke checked when relevant

Manual verification notes

• Agent ran git diff --cached --check before commit.
• Agent inspected the staged workflow diff and confirmed only .github/workflows/bunny-review-command.yml is included.
• Runtime proof requires merge to the default branch because issue_comment workflows only activate from the default branch.

Feature Discoverability

Check exactly one:

• Updated src/features/shell/discovery/ because this PR adds or materially changes a user-discoverable feature, workflow, setting, mode, panel, import path, agent, media capability, or advanced tool.
• N/A because this PR is only a bugfix, refactor, test, docs, internal wiring, visual polish, copy edit, or compatibility fix and does not add a new thing users need to find.

Reason:

• GitHub workflow bootstrap only; no in-app user-discoverable behavior is added.

Docs and release impact

• No docs changes needed
• Updated README.md
• Updated CONTRIBUTING.md
• Updated docs/developer/
• Updated repo skills or AGENTS.md
• Confirmed this PR does not restore old staging/package-workspace/release claims

UI evidence

• N/A. No app UI changes.

Summary by CodeRabbit

• New Features
  • Added a comment-based command system for triggering pull request reviews. Owners, members, and collaborators can now invoke automated code reviews by posting a command in pull request comments. The system provides real-time feedback on command execution status, including success or failure notifications, through automatic comment updates.

[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: c46415ce-680f-4727-99d8-df96621642e1

📥 Commits

Reviewing files that changed from the base of the PR and between 1f7b25a and df866b6.

📒 Files selected for processing (1)

• .github/workflows/bunny-review-command.yml

---

📝 Walkthrough

Walkthrough

Ah, what a delightful little mechanism you have constructed. A GitHub Actions workflow that responds to slash commands in pull request comments—truly, automation serves those who understand its architecture. The workflow listens for /bunny-review full directives, validates the requester's credentials against a whitelist, and dispatches the downstream bunny-review.yml workflow on the refactor branch while maintaining detailed status feedback through comment mutation.

Changes

CI Automation: Review Command Dispatch

Layer / File(s)	Summary
Workflow Metadata and Trigger Configuration .github/workflows/bunny-review-command.yml (lines 1–12)	The workflow declares its identity, subscribes to issue_comment creation events, and configures GitHub token permissions for actions, contents, and pull request metadata mutation.
Job Entry Point and Guard Conditions .github/workflows/bunny-review-command.yml (lines 13–21)	A single dispatch job executes only when the comment originates from a pull request, begins with the /bunny-review command, and is authored by an OWNER, MEMBER, or COLLABORATOR.
Environment Context and Argument Parsing .github/workflows/bunny-review-command.yml (lines 22–36)	Environment variables establish execution context—PR metadata, comment text, the requestor's login—and parse the command to determine REVIEW_MODE from the full or partial argument.
Status Tracking Helper Functions .github/workflows/bunny-review-command.yml (lines 37–73)	Helper functions construct markdown status bodies with a hidden marker and implement upsert logic via gh api to locate or create PR comments, preserving idempotency.
Workflow Dispatch and Status Recording .github/workflows/bunny-review-command.yml (lines 74–96)	Orchestrates the dispatch sequence: record "Queued," invoke gh workflow run with metadata and mode, capture output and exit code, and record "Failed To Dispatch" or "Dispatched" depending on success.

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~18 minutes

The changes introduce a single, straightforward CI configuration file with shell scripting for status management and workflow dispatch. The logic is linear: trigger validation, context assembly, helper function definition, and orchestration. While the shell helper functions require careful inspection for correctness (particularly the comment upsert logic and dispatch capture), the scope is contained and the patterns are conventional.

Poem

A harbinger's touch upon the threads of automation,
Commands whispered through comments, truth separated from rumor—
/bunny-review calls forth the refactor winds,
Status markers hidden, yet always precise,
Another instrument tuned to perfection. ✨🔬

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}