feat(sandbox): restack patch quarantine on current protected main

[seonghobae]

Purpose

Create a clean current-main successor for stale/diverged Draft #268 without force-pushing, rebasing, or mutating the predecessor branch. This Draft transplants only the exact patch-quarantine source, operator documentation, and focused reviewer regressions onto the current protected main.

Exact construction identity

• protected main at construction and immediately before PR creation: e60eff4c71dc4997b9990a79daa5069d6f5e2037
• source predecessor: Draft feat(sandbox): restack exact patch quarantine on latest main #268 unchanged head 4a08323e78f09a9ca59d479c9d6fa1ee31cc5957
• successor head: 7f61c5f6139e728652be11d5b1c1c15cdc6f1cc2
• successor tree: e59acedde19cf0b4a2fc731cc6aa0f70b9994a4c
• ancestry: one commit directly on current protected main
• scope: exactly 28 paths: two patch-quarantine documents, reviewer/noema_reviewer/__init__.py, reviewer/noema_reviewer/patch_validation.py, and 24 focused reviewer regression suites
• every transplanted blob is byte-identical to the corresponding feat(sandbox): restack exact patch quarantine on latest main #268 live-head blob; every other byte is inherited from protected main
• no workflow, package, lockfile, changelog, release, deployment, KPI, governance, license, or unrelated protected-main byte is replayed

Evidence boundary

No CI, review, scanner, model, release, deployment, or predecessor evidence transfers from #93, #262, or #268. This exact successor head must obtain fresh terminal-success application ci, reviewer-ci, protected-base-eligible central Security Scan, and every other applicable live gate. Pending, queued, skipped, absent, neutral, failed, cancelled, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.

Before Ready or merge, independently re-resolve live base/head and ancestry, verify workflow checkout SHAs, re-read the live Noema ruleset and exact central .github Security Scan authority, require exact 100% owned production statement/branch/function/line coverage plus reviewer coverage/docstring gates, and require zero valid unresolved findings. Independent non-author approval is required only if live policy genuinely requires it.

This Draft does not publish a release, deploy production, choose an outbound license, prove a KPI window, or claim commercial/acquisition readiness. Keep #262 and #268 as historical predecessors until this successor is independently verified and safely integrated.

Related: #9, #66, #67, #262, #268

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 73 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cd181230-fd05-47b8-9a8b-d0c97b0e4bea

📥 Commits

Reviewing files that changed from the base of the PR and between e60eff4 and 7f61c5f.

📒 Files selected for processing (28)

• docs/doctoring/quarantined-patch-validation.md
• docs/quarantined-patch-validation.md
• reviewer/noema_reviewer/__init__.py
• reviewer/noema_reviewer/patch_validation.py
• reviewer/tests/test_patch_validation.py
• reviewer/tests/test_patch_validation_archive_boundaries.py
• reviewer/tests/test_patch_validation_blob_identity_edges.py
• reviewer/tests/test_patch_validation_canonical_paths.py
• reviewer/tests/test_patch_validation_coverage_edges.py
• reviewer/tests/test_patch_validation_exact_tree_and_output.py
• reviewer/tests/test_patch_validation_exact_tree_archive_binding.py
• reviewer/tests/test_patch_validation_exact_tree_canonical_metadata.py
• reviewer/tests/test_patch_validation_git_control_descriptor_edge.py
• reviewer/tests/test_patch_validation_git_control_isolation.py
• reviewer/tests/test_patch_validation_git_metadata_mask.py
• reviewer/tests/test_patch_validation_git_output.py
• reviewer/tests/test_patch_validation_hardening.py
• reviewer/tests/test_patch_validation_mode_boundaries.py
• reviewer/tests/test_patch_validation_object_alternates_boundary.py
• reviewer/tests/test_patch_validation_path_consistency.py
• reviewer/tests/test_patch_validation_prearchive_and_result_channel.py
• reviewer/tests/test_patch_validation_primary_space_paths.py
• reviewer/tests/test_patch_validation_provenance_and_hunk_edges.py
• reviewer/tests/test_patch_validation_security_boundaries.py
• reviewer/tests/test_patch_validation_source_integrity.py
• reviewer/tests/test_patch_validation_streaming_edges.py
• reviewer/tests/test_patch_validation_streaming_final_edges.py
• reviewer/tests/test_patch_validation_streaming_git_output.py

---

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