[TomSoulage]

• Every day at 10:00 (Paris time), the new planner Lambda reads the matches of the day through the Treize Mondial adapter and creates one EventBridge Scheduler one-time schedule per match. Each schedule invokes fetch-results with the match key and deletes itself once it has run.
• A match is checked about 2 hours after kick-off, at 17:00 when the page gives no kick-off time, and never between 23:00 and 08:00, so no notification is sent at night.
• Least privilege: planner may only create schedules in its own schedule group and pass Scheduler a role that can only invoke fetch-results. Both Scheduler roles are limited to this account.

For the reviewer:

• A score that is not published yet when its match is checked is not looked up again. Rescheduling with growing delays and the retry limit (P3) follow in the next pull request.
• Once merged, the pipeline runs end to end, so real Telegram messages go out every match day.
• Deferred to DLQ and alarms #7: the DLQ and alarms must also cover the planner and the Scheduler targets. Until then, their failures only appear in the logs.

Part of #6