[Akiyo974]

Follow notifications are grouped per UTC day, so two follows a minute apart land in separate groups when midnight falls between them. #924 pinned the clock for one test that relied on them being grouped, but three more do the same:

• NotificationControllerTest: "says whether the user follows each new follower back"
• NotificationControllerTest: "gives the lane of every actor so each notification takes their color"
• Api\NotificationControllerTest: "says which group a notification leads, how many events it has, and whether the user follows the actor"

Each creates one follow a minute or two before another and expects a single group, so a CI run in the first couple of minutes after 00:00 UTC fails. Like #924, they now start at noon with $this->travelTo(today()->setTime(12, 0)). Nothing changes outside the tests.

To find them, I ran the whole suite with the clock frozen at 00:00:30, 00:01:30 and 12:00 UTC. These three were the only ones that failed only just after midnight. Before the change, 3 failed at 00:00:30 and 1 at 00:01:30. After it, all three pass at every time, and so do the other notification tests (105 in all), Pint and Rector.

[Copilot]

🟢 Approval recommended

The three narrowly scoped test changes prevent unintended day-boundary splits without changing assertions or production code.

No open issues 🎉

What changed in this PR

This PR extends the clock-pinning approach from #924 to three notification controller tests, preventing midnight failures caused by UTC-day follower grouping.

Changes:

• Pins two web controller tests and one API controller test to noon.
• Keeps assertions and production behavior unchanged.

File	Description
tests/​Feature/​Controllers/​NotificationControllerTest.php	Pins the follow-back and actor-lane tests to noon.
tests/​Feature/​Controllers/​Api/​NotificationControllerTest.php	Pins the notification group metadata test to noon.

_{Review effort: Balanced}