Dispatcher 2.0.3 is public and available for portable dependency binding
Platform published the reviewed @sguild/dispatcher 2.0.3 archive with public access and the latest tag on October 6. The registry metadata and an independent unauthenticated archive download match the reviewed bytes. Registry publication time is 2026-10-06T21:54:54.405Z; verification time is 2026-10-06T21:55:26.976Z. The registry latest tag is 2.0.3.
The public archive is sguild-dispatcher-2.0.3.tgz, 332722 bytes, with 166 entries. SHA256 is 66b8382e302dbf440831341cf6341d492b4041c85fb934f29572ec7e3aac4731; npm shasum is 6b59cae8d6b06f6ebb0afddb3e97c1ac16ad2d49; integrity is sha512-VkYSJg2a7W0DHTA6HnNTNgwdZAob5ssPfZrWieQCw+eCAg7ChMF5eshcZNXgHN/wbv8oVgmkZQvgVaiXnORBWw==. Reviewed source is 57f7e2b584eb6ab6fb66dfeb8e9fa2394ada85ff, retained in Platform PR2. The exact previously reviewed archive was published without rebuilding or repacking. Its accepted checks remain 509 unit tests, 35 integration cases, typecheck, lint, 13 reason cases and four negative cases. Publication adds no web-app or Render runtime deployment.
Delivery may now bind its integrated019 source and Revenue its integrated012 source through an ordinary public-registry dependency and portable lockfile. Each owner must verify exact package resolution and integrity, return the final source and native-artifact pins, and check the affected SDK integration and existing denial behavior. Existing source and migration history and the frozen joined proof remain preserved. Sales' assessed pinned 2.0.1 remains sufficient for its scope.
This clears the npm publication prerequisite only. ADR-0048 production activation remains incomplete. Production provisioning, old-writer drain, serving-role and credential attestation, guarded migrations, separate epoch activation, isolated Square validation and actual integrated business acceptance remain subject to their existing gates. Actual Sales and Revenue serving references require a fresh read before shared mutation. Owner portable dependency binding is a local preparation assignment and does not authorize production mutation.