Wake the scheduler on plan and dinner changes (MQ-177-01)

A swap, stored draft, or dinner method/minutes change (edit or grounding)
now calls Scheduler.Wake once committed, so a crock-pot dinner swapped in
for tonight is reminded at start_by minus 15 minutes rather than at the
next hourly pass. Adds a fake-clock test that swaps in a crock-pot
Quest-log dinner at 09:01 and asserts the start reminder at 09:15, once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/ARCHITECTURE.md

@@ -832,9 +832,14 @@ computation the plan API shows) when the dinner is a crock-pot dinner
 whose `start_by` is earlier than that day's `reminder_time`; its run
 calls `EmitStartReminder(period.Date)`, which checks the same again. A
 date whose week has no plan emits neither and logs it. A `DailyAt` fire
-time is looked up from the data on every pass, so a plan change moves it
-within an hour (`maxWait`); a lookup that fails is logged and repeated
-every `ClaimRetry`.
+time is looked up from the data on every pass. A committed change that
+can move a `start_by` calls `Scheduler.Wake` (passed to `plan.NewService`
+and `dinners.NewService` as `wake`): a plan swap or stored draft, and a
+dinner's method or minutes changed by edit or grounding. The next pass
+comes at once, so a crock-pot dinner swapped in for tonight is still
+reminded 15 minutes before its `start_by`, not at the next hourly timer
+(`maxWait`); a lookup that fails is logged and repeated every
+`ClaimRetry`.
 Fake-clock tests of a schedule live in `internal/scheduler`, where
 `SetClock` is visible to tests.