migration(cdw parallel run): ledger row for GREEN scheduled cycle 482474024241636 (+ carry-forward of Sep 2–11 scheduled rows)

[devin-ai-integration]

Summary

Scheduled ow_tp_cdw_recon cycle 482474024241636 (trigger PERIODIC, 2026-09-12 06:00 UTC) came back GREEN. This PR touches only .migration/08_parallel_run_ledger.md.

Verified against the workspace, not the webhook payload alone:

• r1_fact_commission and r2_mv_agent_commission_summary both TERMINATED/SUCCESS; r3_notify SUCCESS.
• Both recon reports (/Volumes/ow_tp/bronze/landing/cdw/recon/482474024241636/<unit>/<unit>.recon.json) cite tolerances v1 + DEGRADED mode, every check pass (rowcount 3/3, row_diff 0/0/0, cents sums 2,880,000 / 7,000 / 7,000, dropped_join_rows 0), idempotency rerun pass with identical row sets.
• No drift: baseline manifest and feed unchanged, so drift note is none.

Carry-forward (review follow-up). The ten daily ledger PRs #1456, #1480, #1501, #1502, #1503, #1505, #1506, #1536, #1546, #1554 are all still open against the run branch, so the base ledger ends at the Sep 2 drill and the new row alone could not be audited against the consecutive-green requirement. This PR therefore carries one canonical row per scheduled cycle 2026-09-02 → 2026-09-11 (UTC order, PR column = originating PR, drift note flags "keep one copy on merge" so the duplicate is dropped when those PRs land) and records 482474024241636 as the 11th consecutive scheduled green. All eleven PERIODIC runs were re-read from the jobs API and both *.recon.json per run just now: SUCCESS/SUCCESS, PASS/PASS, no missing or red cycle. Sep 11 (509394464811952), whose original PR could not re-read the reports because of a token 403, is now confirmed PASS/PASS; its timestamp is corrected to the run's actual end time 06:01:46Z.

STOP E entry criterion (3 consecutive scheduled greens) was met at 898309753301748 on 2026-09-04. No code, tolerance, or job changes; no cutover action.

make tp-smoke locally stops at the Go leg (go not installed on this VM); the change is markdown-only, so the CI gate is the authority here.

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/fb89680a7f3d4e6f99c6bcb5ec667cab
Open in Devin Desktop: https://partner-workshops.devinenterprise.com/desktop/session/fb89680a7f3d4e6f99c6bcb5ec667cab?variant=devin
Requested by: @DhrovS

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring