test(recovery): cover stale evidence registry cleanup

[seonghobae]

Summary

• add deterministic regression coverage for stale weak-reference cleanup guards in PostgreSQL backup and packaged-schema evidence registries;
• preserve a replacement registry entry when an older weakref callback fires; and
• restore the two protected-main coverage arcs postgres_backup_evidence.py:65->exit and postgres_schema_evidence.py:49->exit without changing production behavior.

Exact protected base and current head

Protected main remains exact b84f0c94154043a3473939c01bb6471de5a129ae.

Current PR head remains exact 5951b7a4d779903b8924abaef2a387cae50b7f54, exactly two commits ahead / zero behind, and changes only tests/test_postgres_recovery_evidence_registry.py. Production source and canonical documentation are unchanged. Fresh targeted branch inventory finds this as the only recovery-evidence-weakref branch.

Root cause and regression contract

Protected main inherited two unexercised weakref-callback guard branches from merged recovery-evidence work. The regression tests model a registry slot being replaced while the original weak reference is still live, collect the original object, and prove its stale callback cannot delete the replacement. Production behavior is unchanged.

Exact-head validation — actual checkout authority

Do not infer source identity from workflow-run head_sha metadata or a green conclusion alone. Fresh job-log inspection distinguishes actual contributor-head execution from synthetic pull-request merge execution.

True exact-head evidence on unchanged 5951b7a4d779903b8924abaef2a387cae50b7f54:

• CI 32066570209: the quality job explicitly checks out ref: 5951b7a4d779903b8924abaef2a387cae50b7f54, verifies git rev-parse HEAD, runs Python 3.14.7, reaches exact 100% owned production statement/branch coverage (3633 statements / 1006 branches, zero misses/partials), 100% public docstrings, 1334 passed, 5 deselected, lock freshness and distribution build;
• Release Acceptance 32098143650: the reproducible wheel/sdist job explicitly checks out and verifies exact 5951b7a4d779903b8924abaef2a387cae50b7f54, uses Python 3.14.7, builds two clean exact-head source trees, verifies reproducible wheel/sdist identity, and uploads bounded evidence named for the exact source commit.

Non-passing under the repository's exact-head acceptance contract despite green workflow conclusions:

• Security Scan 32066570256: this is organization-required central workflow ContextualWisdomLab/.github required-workflow id 309078942. Its Trivy job default checkout fetched refs/pull/233/merge and actually ran at synthetic merge commit 20581a0a9c51be71baa229cfa1d9e6b050c14c5b, not contributor head 5951b7a...;
• SAST Semgrep 32066570191: this is organization-required central workflow id 309078929. Its Semgrep job likewise default-checks out refs/pull/233/merge and actually ran at synthetic merge commit 20581a0a9c51be71baa229cfa1d9e6b050c14c5b.

Those Security/SAST results are useful merge-preview evidence but not exact-head Security/SAST success. Synthetic evidence does not transfer into the exact-head gate. The owning workflow source is the read-only central .github control plane; do not copy its workflow locally merely to manufacture a passing pg gate.

Fresh inline review-thread inventory is empty.

Current independent-review state

The pg source/test head is unchanged and has no known source finding, but it is not review-clean and must not merge yet.

Fresh formal review inventory remains:

• predecessor head 1ddfc3260cc8e7e981c5c3bdd4ba2206348f4143: CHANGES_REQUESTED — predecessor evidence;
• current head 5951b7a4d779903b8924abaef2a387cae50b7f54, OpenCode run 32069198553: DISMISSED — not approval; and
• current head 5951b7a4d779903b8924abaef2a387cae50b7f54, OpenCode run 32100082025: active CHANGES_REQUESTED because central coverage-evidence failed before proving required test/docstring evidence.

Those current-head review failures remain non-passing until superseded by a qualifying fresh same-head review. They are not reinterpreted or dismissed as approval.

Read-only central control-plane boundary

The review/evidence and organization-required Security/SAST control planes are owned by ContextualWisdomLab/.github, which has its own enabled writer and remains read-only from this repository loop. Mutable central branch, PR, workflow-run, and review state is intentionally not duplicated in this PR body because it can change independently of this unchanged pg head.

Issue #244 is the sole pg-owned mutable control-plane ledger for the current central prerequisites and must be freshly read before any action that depends on them. It tracks both the independent-review/coverage prerequisite and the newly proven exact-source defect in the central required Security/SAST workflows.

Accordingly, there is presently no pg-owned source defect that justifies churn on this unchanged head. Keep the head stable while the dedicated central writer resolves its own lanes. After repaired review/evidence and exact-source Security/SAST controls are actually integrated on protected central ancestry, reacquire fresh same-head evidence if protected scheduling does not materialize it automatically.

Governance boundary

Protected main remains protected. Merge only the unchanged expected head after fresh verification of protected pg main, exact head/base/ancestry, every available live protection/ruleset surface, actual checkout SHA for required workflows, formal reviews and review threads. Every required exact-head/current-base gate must be terminal-success, zero valid findings/threads may remain, and any qualifying non-author current-last-push approval required by then-live governance must exist.

Queued, pending, cancelled, skipped-required, absent, neutral, stale, predecessor, status-only, synthetic, author-only, rate-limited, infrastructure-failed, dismissed, or conclusion-null evidence is non-passing.

Do not copy central materializer/reviewer/scheduler/security workarounds into pg-llm-batch, manufacture a pg head event, self-approve, dismiss substantive review state, weaken gates, or transfer frozen review runs.

Refs #244, #157, #204.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d1cb030e-2080-476a-a556-5a2368121beb

📥 Commits

Reviewing files that changed from the base of the PR and between b84f0c9 and 1ddfc32.

📒 Files selected for processing (1)

• tests/test_postgres_recovery_evidence_registry.py

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

백업 및 스키마 복구 증거 레지스트리에 stale weak-reference callback 회귀 테스트를 추가했다. 각 테스트는 replacement entry 보존을 검증하고 테스트 후 레지스트리를 정리한다.

Changes

PostgreSQL 복구 증거 레지스트리

Layer / File(s)	Summary
Stale callback replacement 보존 검증 tests/test_postgres_recovery_evidence_registry.py	백업 및 스키마 증거 레지스트리에 replacement entry를 설치한다. 기존 증거 객체를 삭제하고 garbage collection을 실행한다. stale callback이 replacement entry를 삭제하지 않는지 검증한 후 레지스트리 항목을 정리한다.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 1ddfc

This is a localized test-only change that adds regression coverage without changing production behavior; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 stale evidence registry cleanup을 검증하는 회귀 테스트 추가라는 주요 변경 사항을 정확하고 간결하게 설명합니다.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/recovery-evidence-weakref-coverage-b84f0c9

---

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

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 1ddfc3260cc8e7e981c5c3bdd4ba2206348f4143.

• Head SHA: 1ddfc3260cc8e7e981c5c3bdd4ba2206348f4143

• Workflow run: 32003415023

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Test: test_postgres_recovery_evidence_registry.py"]
  S1 --> I1["regression suite"]
  I1 --> R1["Review risk: Test: test_postgres_recovery_evidence_registry.py"]
  R1 --> V1["targeted test run"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: 5951b7a4d779903b8924abaef2a387cae50b7f54
• Workflow run: 32100082025
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 5951b7a4d779903b8924abaef2a387cae50b7f54.

• Head SHA: 5951b7a4d779903b8924abaef2a387cae50b7f54

• Workflow run: 32100082025

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Test: test_postgres_recovery_evidence_registry.py"]
  S1 --> I1["regression suite"]
  I1 --> R1["Review risk: Test: test_postgres_recovery_evidence_registry.py"]
  R1 --> V1["targeted test run"]

Loading

[seonghobae]

@opencode-agent Please re-review the unchanged exact head 1ddfc3260cc8e7e981c5c3bdd4ba2206348f4143 against protected base b84f0c94154043a3473939c01bb6471de5a129ae. The prior central coverage-evidence run failed while materializing trusted uv archives before tests/coverage execution (HTTPError); repository-local exact-head CI, Security Scan, SAST Semgrep, and Release Acceptance are terminal-success. This request is review-only: do not update the branch or enable auto-merge.

[seonghobae]

@opencode-agent Please re-evaluate the current exact head 5951b7a4d779903b8924abaef2a387cae50b7f54 against live protected main@b84f0c94154043a3473939c01bb6471de5a129ae. Repository-local exact-head CI, Security Scan, SAST Semgrep, and Release Acceptance are terminal-success; the prior CHANGES_REQUESTED review is anchored to predecessor head 1ddfc3260cc8e7e981c5c3bdd4ba2206348f4143 after central coverage-evidence infrastructure failed before test materialization. Please publish only fresh same-head review evidence; do not transfer predecessor evidence.

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 5951b7a4d779903b8924abaef2a387cae50b7f54.

• Head SHA: 5951b7a4d779903b8924abaef2a387cae50b7f54

• Workflow run: 32069198553

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Test: test_postgres_recovery_evidence_registry.py"]
  S1 --> I1["regression suite"]
  I1 --> R1["Review risk: Test: test_postgres_recovery_evidence_registry.py"]
  R1 --> V1["targeted test run"]

Loading

[seonghobae]

@opencode-agent

[seonghobae]

@cwl-noema-review

[seonghobae]

@opencode-agent review

Please re-evaluate exact current head 5951b7a4d779903b8924abaef2a387cae50b7f54 now that the central trusted-uv download repair from ContextualWisdomLab/.github#1116 is integrated on protected .github/main@092df969f71c7afc56dd9ab2662b016ad40696c8. Do not reuse the prior infrastructure-failed verdict or predecessor evidence; run the current exact-head coverage/review path once under the repaired central control plane.

[seonghobae]

@cwl-noema-review

Please perform a fresh independent review of exact current head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected main@b84f0c94154043a3473939c01bb6471de5a129ae. Repository-local CI, Security Scan, SAST, Release Acceptance, and CodeRabbit status are terminal-success for this unchanged head. Do not transfer predecessor review evidence. Evaluate the actual one-file test-only change and, if your reviewer identity is eligible and the unchanged head is acceptable under live policy, publish the appropriate formal review for this exact last push; otherwise report concrete current-head findings only.

[seonghobae]

@opencode-agent review

Please re-review the unchanged exact head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected pg-llm-batch/main@b84f0c94154043a3473939c01bb6471de5a129ae. Protected central .github/main@e4a853b3f32f263050aee5f29885dfad532578ed now includes merged .github#1216, whose activation contract specifically requires a fresh trusted mention to dispatch review work with trigger_reviews=true. Publish only fresh same-head review evidence; do not update this branch, transfer predecessor evidence, weaken gates, or enable auto-merge.

[seonghobae]

@opencode-agent review

Please re-evaluate the unchanged exact current head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected pg-llm-batch/main@b84f0c94154043a3473939c01bb6471de5a129ae. Since the previous trusted dispatch, protected central .github/main advanced to 5304770ae4d3a5089028e7d7f08af50e4836a2e0 via merged .github#1221, which repaired a real reusable PR-review control-plane source-identity failure caused by nonexistent job.workflow_* context properties. Publish only fresh same-head review/coverage evidence produced under the current protected central control plane. Do not update this branch, reuse predecessor or infrastructure-failed evidence, reinterpret synthetic Security/SAST checkout as exact-head evidence, weaken gates, self-approve, or enable auto-merge.

[seonghobae]

@opencode-agent review

Please re-evaluate the unchanged exact current head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected pg-llm-batch/main@b84f0c94154043a3473939c01bb6471de5a129ae. Since the previous trusted dispatch, protected central .github/main advanced to daf5ad43b48c826a3a119f385a2f80bef893ae49 via merged .github#1235, which repaired the organization-wide agent-mention sweep's transient GitHub installation-token rate-limit handling after a live quiet period. This is a bounded fresh activation attempt under materially changed protected control-plane code. Publish only fresh same-head review/coverage evidence. Do not update this branch, reuse predecessor or infrastructure-failed evidence, reinterpret synthetic Security/SAST checkout as exact-head evidence, weaken gates, self-approve, or enable auto-merge.

[seonghobae]

@opencode-agent Please re-review the unchanged exact contributor head 5951b7a4d779903b8924abaef2a387cae50b7f54 against current protected-central controls. The prior same-head coverage-evidence failure (32100082025) occurred before product tests because trusted uv version verification rejected the installed binary. That control-plane defect was subsequently fixed and integrated by ContextualWisdomLab/.github#1136 (9e9f59f3ac1e96a960c021b131d768c238f4c21a), and current protected .github/main@208803a65235b09154f3cb087c6e5ef612133ed3 retains the corrected exact Linux/x86_64 output contract. Do not transfer predecessor evidence: run fresh coverage/test/docstring evidence and issue a new semantic verdict only for this unchanged pg head.

[seonghobae]

@opencode-agent Please re-review the unchanged exact contributor head 5951b7a4d779903b8924abaef2a387cae50b7f54 against current protected-central controls. Since the previous same-head request, protected ContextualWisdomLab/.github/main advanced from 208803a65235b09154f3cb087c6e5ef612133ed3 to 23a776ed37027d8ab8ab2aefcf81fac586352e2f. That ancestry contains two material control-plane changes after the prior request: ContextualWisdomLab/.github#1230 at 307fcfd80e5a84e2dbd655046ed5fc1cb79f641d, which repaired the OpenCode coverage/review runtime to honor exact Corepack pnpm packageManager specifications, and ContextualWisdomLab/.github#1223 at 387b87dadcac7d4dbd82bc6179304989acc1ed41, which repaired org-queue-sweep rotation/fairness so review dispatch is not fixed-order/starved.

This is one bounded retry after material protected control-plane change. Run fresh same-head coverage/test/docstring evidence and publish a new semantic verdict only for 5951b7a4d779903b8924abaef2a387cae50b7f54. Do not update this pg branch, transfer predecessor or infrastructure-failed evidence, reinterpret synthetic Security/SAST checkout as exact-head evidence, weaken gates, self-approve, or enable auto-merge.

[seonghobae]

@opencode-agent Please perform a fresh review-only pass on the unchanged exact contributor head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected main@b84f0c94154043a3473939c01bb6471de5a129ae. The prior current-head CHANGES_REQUESTED was coverage-evidence/infrastructure-bound; current protected central ancestry contains the uv materialization repair. Re-evaluate current test/docstring/coverage evidence semantically, but do not merge, update/rebase the branch, manufacture approval, or transfer predecessor evidence. Keep Security/SAST exact-source identity separate: existing green required-workflow runs checked out synthetic merge 20581a0a9c51be71baa229cfa1d9e6b050c14c5b and are not exact-head acceptance evidence.

[seonghobae]

@opencode-agent review

Please re-evaluate the unchanged exact contributor head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected pg-llm-batch/main@b84f0c94154043a3473939c01bb6471de5a129ae under the current protected central control plane .github/main@8fd471a31399a914d9cb22a840f4a4c68e010ea6. The active same-head CHANGES_REQUESTED was emitted by central run 32100082025 on old central main 092df969f71c7afc56dd9ab2662b016ad40696c8, and no later same-head formal verdict is currently present. This is a bounded review-only activation: keep the pg head unchanged, generate fresh current-head coverage/test/docstring evidence, and publish a new semantic verdict only from current trusted evidence. Do not treat member-repository green statuses, synthetic Security/SAST merge-preview evidence, dismissed/predecessor reviews, or this activation comment as approval; do not update the branch or enable auto-merge.

[seonghobae]

@opencode-agent Please re-review the unchanged exact contributor head 5951b7a4d779903b8924abaef2a387cae50b7f54 against the now-current protected central control plane.

Since the prior bounded same-head request on 2026-08-23, protected ContextualWisdomLab/.github/main has materially advanced and is now exact d2c554dbbc04854db6215970fabb70cef1ceb690. That protected commit merged .github#1320 and repairs the central Strix/provider contract path, including the fallback-model contract, event repository visibility, NVIDIA-overload fallback, cross-provider API-base isolation for direct OpenAI fallback, and known-console-notice classification. The pg PR head and protected pg base remain unchanged (5951b7a... against b84f0c9...), and inline review threads remain empty.

This is one bounded activation after a material protected-central change. Generate fresh same-head coverage/test/docstring evidence and a new semantic verdict only for 5951b7a4d779903b8924abaef2a387cae50b7f54. Do not mutate the pg branch, transfer predecessor or infrastructure-failed evidence, reinterpret synthetic Security/SAST checkout as exact-head proof, weaken gates, self-approve, or enable auto-merge. The independent exact-source Security/SAST prerequisite tracked by the read-only central .github#1222 remains separate.

[seonghobae]

@opencode-agent review

Please re-evaluate the unchanged exact contributor head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected pg-llm-batch/main@b84f0c94154043a3473939c01bb6471de5a129ae under current protected central control plane .github/main@e3b7ece44ba8e891e4c948e9b5b75773f330cd0e.

Since the prior same-head activation, protected central #1333 materially changed this review path: it removed nonexistent openai/gpt-5.6-luna from the OpenCode review candidate pool, aligned the direct OpenAI slot and contract tests to gpt-5.4, and kept provider/retry terminal handling fail-closed.

This is one bounded review-only activation after that material protected control-plane change. Generate fresh same-head coverage/test/docstring evidence and publish a new semantic verdict only from current trusted evidence. Do not update or rebase the pg branch, transfer predecessor or infrastructure-failed evidence, treat existing synthetic Security/SAST merge-preview execution as exact-head proof, self-approve, weaken gates, or enable auto-merge.

[seonghobae]

@opencode-agent review

Please re-evaluate the unchanged exact contributor head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected pg-llm-batch/main@b84f0c94154043a3473939c01bb6471de5a129ae under current protected central control plane .github/main@33dc57d7984b937e4f5ab915d5eae69a0f42e3a5.

Since the prior same-head activation against central e3b7ece44ba8e891e4c948e9b5b75773f330cd0e, protected central #1331 materially changed this exact review/provider path: it completed the gpt-5.6-luna → gpt-5.4 rename across the OpenCode dispatch chain, refreshed the pinned review-dispatch workflow blobs, and corrected cross-provider direct-OpenAI API-base/credential routing while preserving fail-closed behavior.

This is one bounded review-only activation after that material protected control-plane change. Generate fresh same-head coverage/test/docstring evidence and publish a new semantic verdict only from current trusted evidence. Do not update/rebase the pg branch, transfer predecessor or infrastructure-failed evidence, treat existing synthetic Security/SAST merge-preview execution as exact-head proof, self-approve, weaken gates, or enable auto-merge.

[seonghobae]

@opencode-agent review

Please perform one bounded review-only re-evaluation of the unchanged exact contributor head 5951b7a4d779903b8924abaef2a387cae50b7f54 against protected pg-llm-batch/main@b84f0c94154043a3473939c01bb6471de5a129ae under current protected central control plane .github/main@17052a7ca3c16db90932a4d6036b43165ddee418.

Since the last same-head activation, protected central #1360 materially changed this exact review execution path: central pr-review-autofix now routes through the pinned vendored contextual-orchestrator orchestrator/free pool with provider discovery and ZDR-first routing while preserving fail-closed mutation/review boundaries. Generate fresh same-head coverage/test/docstring evidence and publish a new semantic verdict only from current trusted evidence.

Keep the pg head unchanged. Do not update/rebase the branch, transfer predecessor/infrastructure-failed evidence, reinterpret the existing synthetic Security/SAST merge-preview execution as exact-head proof, self-approve, weaken gates, or enable auto-merge.