Sync the self-hosting stack

2026-08-31 22:42:54 +02:00
parent b43cddc776
commit 04c7d7f4fa
1 changed files with 25 additions and 0 deletions
@@ -9,6 +9,31 @@ 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 wake-up no longer arrives under your name `api 0.104.0` `web 0.126.0`
 **When a scheduled wake-up fired, the transcript showed it as a message you had sent.** Your avatar,
 your name, and twenty lines of preamble written for the model — for something you never typed, at
 whatever hour the clock came round. Reported within an hour of the feature shipping, and it was the
 whole of what a transcript is for: knowing who said what.
 A wake-up is now its own kind of row. It sits in the middle of the thread rather than on either
 side, under a header saying which wake-up fired and when it was due, with one thing in the body:
 the instruction Jarvis left itself. The scaffolding that turn actually ran on is folded away behind
 **Show the note sent to Jarvis** — still there when a wake-up behaves oddly and you want to see
 exactly what it was told, and out of the way the rest of the time. Wake-ups never merge into the
 message above them either, so the header cannot be lost to grouping.
 The same is true on a share link. A guest sees the same card; what reaches them is the title, the
 time and the instruction, and not the internal id of the wake-up.
 Underneath, the row is still recorded as coming from the person who owns the wake-up, because that
 is whose access the turn runs with and it is how a wake-up interrupted by a restart is picked up
 again. What changed is that the console no longer reads that as authorship.
 **Nothing to do on the way in.** The schema gains one nullable column and the migration is
 uneventful. Notes already in your transcripts keep rendering the old way — the structure is written
 when a wake-up fires, so they have none; anything that fires from now on gets the card.
 ## 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: