N+1 Query

Sentry Issue: [BACKEND-NG](https://bcps-wps.sentry.io/issues/7615092937/?referrer=github_integration)
| | |
| ------------- | --------------- |
| **Offending Spans** | db - SELECT critical_hours.start_hour, critical...

Start with the linked Sentry issue and its offending database span, then trace the query back to the relevant Python entry point. Identify where the repeated query is issued and determine how to verify that the N+1 behavior is gone; the payload names no source file or test, so the completion check is not yet specified.

Written by the indexing model from the issue text.