docs: decouple Collector delivery from production Gate

[proerror77]

Change

Make the repository-wide delivery rule explicit: ordinary development, review, CI, merge, artifact publication, and releases that do not cross a protected runtime boundary must not wait for a production Gate. Development and control-plane verification defaults to a focused check of no more than 15 minutes; the full Gate runs once at the actual collector/runtime transition.

The existing Polymarket 3600-second Gate implementation and fail-closed cutover policy are unchanged.

Issue relationship

Closes #865

Validation

• git diff --check

Runtime impact and rollback

None. This changes repository delivery instructions only. Revert commit 5d11b3e9 to roll back the rule.

Summary by CodeRabbit

• Documentation
  • Clarified when production Gates apply, focusing on runtime transitions.
  • Documented that development, review, CI, merge, publication, and non-boundary release activities use targeted verification instead.
  • Added guidance to run the full Gate check immediately before crossing a protected runtime boundary.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4689f7a7-f1df-469a-8eaa-b7d1bc2f9dce

📥 Commits

Reviewing files that changed from the base of the PR and between 8f0fe52 and 5d11b3e.

📒 Files selected for processing (1)

• AGENTS.md

---

📝 Walkthrough

Walkthrough

AGENTS.md now defines production Gate scope. Failed Gates block only protected runtime or collector transitions. Development and control-plane work uses targeted checks, followed by a full Gate immediately before the protected boundary.

Changes

Production Gate scope

Layer / File(s)	Summary
Document Gate boundaries AGENTS.md	Guidance limits failed production Gates to protected cutovers and requires targeted checks for development and control-plane work before the final full Gate.

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

Merge Risk: ⚪ Minimal · up to 5d11b

This documentation-only change does not alter production behavior, and no actionable merge-blocking risk remains after normal validation checks.

Possibly related issues

• Polymarket Rust production cutover: bounded preflight, 900-second Gate, and CI lanes #499 — The issue also addresses bounded preflight checks and production Gate timing.

Possibly related PRs

• proerror77/monday#79 — Both changes update AGENTS.md guidance for workflow validation scope.
• proerror77/monday#389 — The PR addresses production shadow Gate behavior at the runtime boundary.
• proerror77/monday#422 — The PR addresses preflight and Gate timing before a protected runtime transition.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the documented separation of Collector delivery from the production Gate.
Description check	✅ Passed	The description includes the change, issue relationship, validation, and runtime impact or rollback sections with relevant details.
Linked Issues check	✅ Passed	The documentation change addresses all coding-related requirements in issue #865 and preserves the existing Gate policy and scripts.
Out of Scope Changes check	✅ Passed	The only change is scoped to repository delivery guidance and does not introduce runtime, deployment, or Gate implementation changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/collector-fast-delivery-865

---

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.}