Dispatcher freshness release plan after domain inventories

Why

All five recipient domains replied on 2026-05-20-platform-dispatcher-registry-refresh-needs. The response window is complete. No domain asked for a dispatcher public API change before the freshness publish.

The release still has two pre-publish registry decisions to make explicit so the package cut does not preserve drift.

Release Position

Platform will publish a freshness release of @sguild/dispatcher from the current canonical coordination registry and payload schema tree after the two corrections below validate.

For Delivery hold events, the canonical spelling is delivery.lesson-hold.created and delivery.lesson-hold.cancelled. Platform will not add package-level aliases for the underscored delivery.lesson_hold.* names. Delivery should rename its local constants and vendored registry slice before adopting the refreshed package. Until Delivery adopts the refreshed package, its repo-local registry mirror can continue to protect the current runtime, but the package should not make the drift durable.

For Coaching lesson events, Platform will add Coaching to the consumer list for lesson.cancelled and lesson.delivered before the package publish. Coaching reports live handlers for both. This is an additive consumer mapping correction and does not require a payload schema change.

Revenue's order.created, order.updated, delivery.lesson-hold.created, and delivery.lesson-hold.cancelled needs are already aligned with the canonical registry shape, assuming the freshness package bundles the current tree. Growth and Sales need the same current-tree bundle, especially post-2026-05-02 lead and role events.

Publish Checklist

Before publishing, Platform will:

1. Update the canonical registry consumer mappings for Coaching on lesson.cancelled and lesson.delivered.
2. Verify the canonical registry contains delivery.lesson-hold.created and delivery.lesson-hold.cancelled, not the underscored variants.
3. Mirror the canonical registry and payload schema tree into the dispatcher package bundle.
4. Run the coordination event-type validator and dispatcher package tests.
5. Publish the refreshed package and bump domain consumers from stale @sguild/dispatcher@2.0.0.

References

• Root ask: 2026-05-20-platform-dispatcher-registry-refresh-needs
• Growth reply: 2026-05-20-growth-dispatcher-freshness-inventory
• Sales reply: 2026-05-20-sales-dispatcher-freshness-inventory
• Delivery reply: 2026-05-20-delivery-dispatcher-refresh-needs
• Revenue reply: 2026-05-20-revenue-dispatcher-registry-refresh-needs
• Coaching reply: 2026-05-20-coaching-dispatcher-freshness-inventory