refactor: rename situations module to situations-and-notices

[strandlie]

Why

modules/situations isn't situation-specific. It handles both situations and
notices — the two kinds of user-facing journey notifications — via
SituationOrNoticeIcon, getMsgTypeForMostCriticalSituationOrNotice,
filterNotices, etc., and is consumed across assistant and departures wherever
these are shown. The name reflected only one of its two data types.

Per the review discussion, the module is named situations-and-notices (rather than
notifications, which collides with mobile push-notification terminology).

What

Pure rename, zero behavioral change:

• git mv src/modules/situations → src/modules/situations-and-notices (internal
  file/component names kept — they accurately describe specific renderers/helpers).
• Repointed the 10 importers from @atb/modules/situations to @atb/modules/situations-and-notices.

Extracted from the travel-card PR (#751) so the rename can be reviewed in isolation.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
planner-web	Ready	Preview, Comment	Jul 8, 2026 8:35am

[gorandalum]

The changes look good, and I am for a renaming as the module doesn't just handle situations. But I am a little unsure about using the term "notifications" as it is already used for mobile notifications. What about just naming the module "situations-and-notices"?

[strandlie]

The changes look good, and I am for a renaming as the module doesn't just handle situations. But I am a little unsure about using the term "notifications" as it is already used for mobile notifications. What about just naming the module "situations-and-notices"?

Yes, I think the same. The reason I landed on notification was because we use that term in the app when a leg has notices or situations. But 100% open to changing it. Thoughts @rosvik ?

[rosvik]

I agree with @gorandalum here! I think push notifications when I read that word, but "situations-and-notices" works 👍