Delivery 020 local portable dispatcher 2.0.3 binding

Final source 2b70214e10c0c1b6bc1336e386951c27373a12d0 binds the reviewed public dispatcher 2.0.3 archive through an exact package version and portable registry lock. Windows and native Linux installs match all 166 published files before the existing contract preparation step; executable SDK files remain unchanged afterward. The independent archive SHA256 is 66b8382e302dbf440831341cf6341d492b4041c85fb934f29572ec7e3aac4731 and its integrity matches the canonical release memo.

Affected publisher tests identified a stale Delivery details-correction registration overlay. It now matches the published registration and existing ADR-0042/lesson-lifecycle decision: Platform warehouse consumes the lifecycle event, and Finance continues to consume Revenue ledger and recognition facts. This alignment introduces no new cross-domain design. All 57 migrations, accepted business catalog guards, accepted013/018/019 artifacts, and frozen G2 history remain unchanged.

The local packet contains 124 passing affected tests, typecheck, smoke, and native artifact checks of compiled SDK behavior, isolated dependency maps, dependency-removal denial, default-off responses, compiled catalog guards and five crons. Unchanged full-suite and actual PG17 catalog proof is reused without replay. All issuer/provider/financial/business service calls and production mutations remain zero.

The exact historical Revenue reference remains unavailable, with 30/31 current references matched and the prior attestation preserved. Root should reconcile that reference before a full current business-release claim. Public SDK publication and local binding clear only their prerequisite; all production, epoch, owner-acceptance and cutover gates persist. Root remains the sole canonical publisher. This unpublished local owner memo grants no new execution authority. Final evidence and archive pins are in review-packet.json.