docs(batch): record PR #21 QC pass and lead confirmation

docs/batches/bat-025_20260715_portfolio-ledger-alembic-migration/verification.md

@@ -1,6 +1,6 @@
 # BAT-025 Developer Self-Verification
 
-- Status: **verification-reopened — PR #21 provenance remediation and independent re-QC pending**
+- Status: **release-candidate — PR #21 independent QC PASS; lead confirmation recorded**
 - Batch: BAT-025
 - Requirement: REQ-057
 - Date: 2026-07-15
@@ -60,6 +60,6 @@ The delivery was implemented and initially verified on the isolated worktree cha
 - Developer self-verification: **complete** on the original worktree remediation chain, with the PR #21 commit mapping above.
 - Initial independent QC: **FAIL** — documentation provenance and untracked `uv.lock` hygiene only; technical ACs reproduced.
 - Original-worktree independent re-QC: **PASS** (`deleg_6b805aa0`, 2026-07-15), including loopback PostgreSQL and direct Ruff evidence.
-- PR #21 committed-diff QC: **reopened**. The previous PR review correctly required provenance mapping and a DSN-bearing local reproduction. This document supplies the mapping and records the reproduction evidence; a fresh independent PR QC must still issue the final PASS/FAIL.
-- `confirm-batch-verification`: **reopened pending PR #21 independent QC**. This state does not authorize main merge, release, deployment, operational database migration, or service restart.
+- PR #21 committed-diff QC: **PASS** (`deleg_ae0c6f27`, 2026-07-15). It verified the cherry-pick patch-id mapping, PR head `bd51330`, migration semantics, loopback PostgreSQL suite (**3 passed**), fixture-generated UUID catalog cleanup (**0**), direct Ruff checks, clean tested worktree, and PR diff hygiene.
+- `confirm-batch-verification`: **PASS accepted by TREX lead (2026-07-15)**. This approval is limited to merging the verified PR; it does not authorize release, deployment, operational database migration, or service restart.
 - M5 Release: **not started**. Release preparation requires separate scope/approval after merge; production migration requires a separate operational decision and release approval.