ScheduleWakeup one-shot wakeups silently vanish before firing (WSL2, long session)
Draft upstream report: ScheduleWakeup one-shots vanish before firing
Environment: Claude Code CLI on WSL2 (Ubuntu), long-running interactive
session, Fable 5, dynamic self-paced loop via ScheduleWakeup.
Observed: One-shot wakeups scheduled via ScheduleWakeup appear in
CronList initially, then silently disappear before their due time; the
original never fires. 4 instances in one session (2026-07-23):
- due 18:43Z — absent at 18:41Z; replacement fired normally
- due 19:14Z — absent at 18:58Z (T-15m)
- due 19:58Z (session ~12:58 local) — scheduled 19:31Z, absent at 19:41Z
- (recovery wakeups armed in the same session persisted and fired
normally in 2 of 4 cases — no clear discriminator found)
Pattern notes: recurring cron jobs in the same session never vanished
(dentists/keeper/cogitation stable all day). Only ScheduleWakeup one-shots
affected. Session had heavy interleaved activity (registers, plan-mode
entries/exits, background tasks) — plan-mode transitions are a suspect
window but not confirmed.
Impact: self-paced dynamic loops silently stall; mitigation in use:
a keeper cron cross-checks CronList each pass and re-arms missing wakeups.
Repro: not minimal yet; can provide session timeline on request.