Sequential tier release and tier reordering

[daveearley]

What

• Release tiers in order: new switch on tiered products. A later tier is locked until every earlier tier with a quantity sells out (live reservations count) or passes its sale end date. Locked tiers stay visible, greyed, as "Not yet on sale". The state is derived on every read and re-checked at checkout; nothing is stored beyond the flag.
• Tier reordering: tiers in the product drawer can be dragged into order.
• Widget tidy-up: tiered products no longer show a sold-out badge on the header while the rows are expanded, and rows inherit the product-level reason (sales ended / not started) instead of "Not available".

Notes

• Saving with the switch on requires a quantity on every tier except the last.
• Locked state uses the tier's own stock (sold + reserved vs quantity), not the occurrence- or capacity-capped number, so a full date on a recurring event doesn't unlock the next tier.
• No new queries on the public event endpoint.

Tests

• Unit: domain predicate, filter service, checkout validator, request rule, tier order invariant.
• E2E: locked → unlocked → sold-out flow, header badge expanded vs collapsed, switch validation and persistence, drag reorder.

[railway-app]

🚅 Deployed to the Hi.Events-pr-1350 environment in Hi.Events

Service	Status	Web	Updated
Hi.Events Frontend	✅ Success (View Logs)	Web	Sep 15, 2026 at 4:53 pm UTC
Hi.Events Scheduler	✅ Success (View Logs)		Sep 15, 2026 at 4:50 pm UTC
Hi.Events Queue Worker	✅ Success (View Logs)		Sep 15, 2026 at 4:49 pm UTC
Hi.Events API	✅ Success (View Logs)	Web	Sep 15, 2026 at 4:47 pm UTC

1 service not affected by this PR

• Maildev

[github-actions]

✅ E2E · smoke

✅ Passed	❌ Failed	⚠️ Flaky	⏭️ Skipped	⏱️ Duration
26	0	0	0	1m 2s

View run