feat(sandbox): restack exact patch quarantine after nanoid

[seonghobae]

Purpose

Clean protected-main successor for closed stale PR #65 after #76 integrated. This PR starts from current protected main c85d710804139c0697d7ef8fa47d02b1389e6d84 and carries the unique credential-free exact-source patch-quarantine implementation, tests, doctoring, and one current-baseline ## Unreleased changelog entry without replaying #65's stale pre-#76 package/audit state.

Current exact source boundary

• head branch: feat/quarantined-patch-validation-on-main;
• exact current head: fe3074a188739705f89ff67b46712ac9d228081d;
• independently re-resolved protected main: c85d710804139c0697d7ef8fa47d02b1389e6d84;
• changed-file set: 27 paths, matching feat(sandbox): add quarantined patch validation #65's product/docs/test path set plus a current-baseline CHANGELOG.md entry;
• fresh changed-file enumeration contains no package, lockfile, workflow, or nanoid files.

PR #65 is already closed unmerged; its checks/reviews are historical and do not transfer.

Preserved product boundary

• exact repository/base/head/patch-SHA-256/profile binding;
• allowlisted validation profiles with no caller-provided shell command;
• strict UTF-8, path, mode, hunk, file-count and governance-surface validation;
• exact Git HEAD/clean-worktree plus exact-tree/object identity verification;
• descriptor-safe/no-follow/size-bounded reads and source object-store/alternate isolation;
• bounded exact-commit archive materialization and extracted-file Git object rehashing;
• no-network/read-only/non-root container execution without Docker socket or reviewer/model/GitHub write/release/deployment credentials;
• trusted-host result validation and bounded retained evidence;
• beginner-readable public docs, realistic hostile-input regressions and reviewer coverage/docstring gates.

Fresh exact-head technical evidence

For unchanged exact head fe3074a188739705f89ff67b46712ac9d228081d:

• application ci run 31375580944: terminal success;
• reviewer-ci run 31375580959: terminal success;
• central Security Scan run 31375580983: terminal success under its own scanner/revision semantics;
• formal GitHub review submissions: 0;
• inline review threads: 0;
• GitHub reports the PR mergeable.

These runs are fresh post-#76 technical evidence. They do not create live ruleset evidence or qualifying independent approval.

Current acceptance sequence

1. Preserve the proven bounded 27-path implementation set without package/lock/workflow drift.
2. Keep this exact head stable while current review/governance evidence is evaluated.
3. Merge only when live chore(governance): protect main and enforce release checks #27/chore(operations): provision and activate hourly maintainer App #29 ruleset/reviewer requirements are actually satisfied; no check/status/model evidence substitutes for formal approval when required.
4. After protected integration, run exact-source patch-quarantine operational acceptance on main.
5. Restack only feat(sandbox): build and verify patch-validator image #67's unique validator-image work onto the protected successor lineage rather than retaining the stale feat(sandbox): add quarantined patch validation #65 feature-base stack.

No repair/self-modifying workflow, force push, audit waiver, synthetic approval, version bump, release or license decision is introduced.

Related: #9, #27, #29, #65, #66, #67

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 32 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: 77ba42b0-09c6-44a8-bd28-fa2cfd7887e9

📥 Commits

Reviewing files that changed from the base of the PR and between c85d710 and fe3074a.

📒 Files selected for processing (27)

• CHANGELOG.md
• 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_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_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.}