diff --git a/CHANGELOG.md b/CHANGELOG.md index f854450..9482e48 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,6 +9,30 @@ one of them changed. An entry says which artefact and which version, so `web 0.1 Every version published to a channel appears here. Nothing is written from memory afterwards: a build cannot be published without its entry. +## 2026-08-31 — A scheduling loop, fixed at the shape rather than at the wording `api 0.103.0` + +**If Jarvis got stuck trying to schedule something, this is the fix.** Reported within the hour: +asked to send a message a minute later, it tried four times, each time announcing it would correct +itself and each time sending the same thing. No wake-up was created, and every attempt showed as +"Succeeded" in the transcript. + +Two mistakes of ours, and neither was in the scheduling itself. + +**The tool asked for a choice it then punished.** It took an optional "repeat pattern" and an +optional "single time", and refused unless exactly one was given — a rule the assistant had to +enforce on itself, got wrong, and then could not recover from. It now takes **one** value for when +to wake, and the shape says which kind it is: a timestamp wakes it once, a five-field pattern +repeats. There is no longer a combination to get wrong. The value it kept sending was, as best we +can tell, a fragment of an example in our own field description — so the documentation was feeding +the mistake the tool was refusing. + +**A refused call reported success.** The transcript showed four green rows for four calls that did +nothing, which is the opposite of what a transcript is for. A wake-up that cannot be created now +fails and says so on its row. + +Nothing about existing wake-ups changes and there is no schema change. Take the api image; the +console is unaffected. + ## 2026-08-31 — Jarvis can wake itself up, knows what day it is, and can read the web `api 0.102.0` `web 0.125.0` `browser 0.1.0` **The schema step is uneventful for almost everyone** — unlike `api 0.101.0`. Read the upgrade