Document master-only Bore production deploy policy

[vimian]

Add a repo-level agent rule that production Bore deployments must always come from master, and that changes must be committed, pushed, and merged into master before production deploys.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: b282bf74-1c41-4e24-8732-768bbe18c0f1

📥 Commits

Reviewing files that changed from the base of the PR and between c212c04 and 687be7c.

📒 Files selected for processing (1)

• AGENTS.md

---

📝 Walkthrough

Walkthrough

Documentation update to AGENTS.md adding two production governance rules for the Bore server, requiring exclusive use of the master branch and a standard commit→push→PR/merge workflow before any production deployment.

Changes

Cohort / File(s)	Summary
Documentation AGENTS.md	Added production governance rules specifying that Bore production must always run master branch and require standard commit→push→PR/merge workflow before deployment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Documentation hops along,
Rules for Bore, steady and strong,
Master branch stays true,
Governance through and through,
The merge dance won't go wrong! 📋✨

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

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