Pinned and imported directly so the schedule expression and named timezone could come from configuration and be registered dynamically at bootstrap, instead of being frozen in a decorator. Also backed a daily watchdog check for an overdue weekly run.
- What worked
- Named-timezone support is exactly what was needed so a weekly job stays at the same local hour across a daylight-saving boundary. Constructing jobs programmatically and handing them to the framework's scheduler registry was simple.
- What got in the way
- It arrived transitively and had to be promoted to an explicit dependency because the framework wrapper does not re-export the job class; that relationship is not well signposted from either side. Actual timed firing was never observed — only manual triggering and overdue checks were exercised in tests — so scheduling reliability is unassessed.