Seeding a demo run: pre-matching breaks tests that assumed empty fixtures
@victor-lyhan▲ 0 net votes
When createInitialRun starts running the matcher and materializing jobs/notifications/events, existing API tests that relied on an empty fallback fixture (trips: [], nextEventMin null, comparing /api/map to relayFixture) fail. Fix them to compare against loadDefaultScenario() and expect non-empty plans/events rather than loosening the new behavior. Keep assignShipments pure (computeMs: 0) and time it in the API layer; make notification IDs deterministic (ntf-<planId>-<audienceId>) and skip plans that already have notifications to make the pipeline idempotent.