docs(batch): confirm BAT-025 verification

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

@@ -2,7 +2,7 @@
 
 - Batch ID: BAT-025
 - Profile: standard
-- Status: confirmed
+- Status: release-candidate
 - Discovery: dcy-012_20260714_manual-ledger-write-api-owner-scoped (REQ-057 follow-on)
 - Included REQ: REQ-057
 - Folder: docs/batches/bat-025_20260715_portfolio-ledger-alembic-migration/
@@ -31,11 +31,11 @@ REQ-056/BAT-024가 사용한 `portfolio_ledger` additive metadata 네 컬럼을
 
 ## DoD
 
-- [ ] confirmed planning/design 문서 local main commit
-- [ ] dev-impl의 migration/code/test/runbook commit
-- [ ] dev-qc 독립 diff review 및 test rerun PASS
-- [ ] lead verification confirmation evidence 기록
-- [ ] M5 Release 미착수
+- [x] confirmed planning/design 문서 local main commit (`600375b`)
+- [x] dev-impl의 migration/code/test/runbook commit (`f6195ff`, remediation `779d6f7`)
+- [x] dev-qc 독립 diff review 및 test rerun PASS (`deleg_6b805aa0`)
+- [x] lead verification confirmation evidence 기록 (2026-07-15)
+- [x] M5 Release 미착수 — 별도 release approval 전 운영 migration/deploy/service activation 금지
 
 ## Gate / Constraints
 

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

@@ -1,6 +1,6 @@
 # BAT-025 Developer Self-Verification
 
-- Status: **draft — initial independent QC failed on provenance/hygiene; re-QC pending**
+- Status: **release-candidate — independent re-QC PASS; lead confirmation recorded**
 - Batch: BAT-025
 - Requirement: REQ-057
 - Date: 2026-07-15
@@ -38,12 +38,12 @@
 - The local container is an isolated test target, not a staging or production database.
 - No production backup/restore, lock-duration measurement under production load, migration run against an operational DB, deploy, or service activation was attempted.
 - The test command uses a transient `httpx2` overlay because this environment's resolved Starlette TestClient requires it while the project declares `httpx`; no dependency source change was made for this batch.
-- The initial independent QC reproduced the technical evidence but returned FAIL because the then-committed document described the remediation as uncommitted and its test run produced an untracked `uv.lock`. This follow-up corrects provenance/hygiene only; independent re-QC must inspect the follow-up committed diff before a QC verdict can change.
+- The initial independent QC reproduced the technical evidence but returned FAIL because the then-committed document described the remediation as uncommitted and its test run produced an untracked `uv.lock`. Follow-up commit `71a0312e1efb54772b94fd7de0d8add5943f05af` corrected provenance/hygiene only; independent re-QC inspected that committed diff and passed it.
 
 ## Gate result
 
 - Developer self-verification: **complete for committed remediation `779d6f7711d700d6f56be22023cb826cc6f2fe28`**.
 - Initial independent QC: **FAIL** — documentation provenance and untracked `uv.lock` hygiene only; technical ACs reproduced.
-- Independent re-QC: **pending**.
-- `confirm-batch-verification`: **not eligible until re-QC PASS**.
-- M5 release / operational migration: **not started and remains blocked**.
+- Independent re-QC: **PASS** (`deleg_6b805aa0`, 2026-07-15). It verified `f6195ff → 779d6f7 → 71a0312` ancestry, committed provenance, clean worktree and absent `uv.lock`; reran the loopback PostgreSQL migration suite (**3 passed in 6.28s**) and direct Ruff 0.15.10 checks on the five relevant migration/runtime/test files (**All checks passed**). The non-declared `.venv/bin/ruff` path was correctly treated as non-contractual.
+- Lead decision: **`confirm-batch-verification` PASS accepted** — batch advances to `release-candidate`.
+- M5 release / operational migration: **not started and remains blocked pending separate release approval**.