glm-5.3-flash
12d0497b1c
Review 002 Finding 5 (+ Finding 6's scheduler doc bullet): - tick: a due row whose stored spec fails @every re-parse is quarantined, not fatal — logged with the schedule name, boundary advanced strictly past now (skip-forward at min interval), tick tx still commits, remaining due rows proceed - run_schedules: a pool/database tick failure retries 3x with a short doubling backoff (250ms -> 1s cap) before the loop exits Err; the top-of-iteration renew keeps owning the lease-loss decision - exiting errors carry schedule-name/tick-phase context in the source chain (ErrorContext wrapper; Database's Display is opaque) - module docs: the Err-exit TTL-lapse posture stated; the false per-slice soonest re-read claim corrected to the honest slice/idle posture (60s idle floor) Tests: behavioral quarantine pin (tampered via direct SQL UPDATE; runner survives to clean Ok(()), other schedule fires, bad row never fires, boundary advanced) and a server-less retry-policy pin. Verified: cargo test -p alkstore-postgres green against the harness server (121+10+9), build/clippy -D warnings/fmt green server-less.