What the journal asked for: the retro of 3 November 2026 #26

The retro of 3 November 2026 read the 69 journal entries written since the fold of 28 October and ranked eight things to improve, to be fixed one at a time. This issue holds Groove's share. Each child says what the journal saw and when it is done.

In the order of impact:

1. A red main nobody owns
   • #27 A commit that changes a lockfile or names a new path is refused before it lands red
2. Mutants and scripted edits that silently do nothing
   • #28 One script applies a mutant, runs the tests under a limit, and puts the file back
3. Nothing drives the real app, and Playback and the commands have no seam
   • #29 Playback plays into a fake output under cargo test, from prepare through the swap to the mix
   • #30 What a command decides is tested without an AppHandle
   • #31 The clock, following, gear and mix tests share one test device
   • #32 What a page asks the browser for, it asks the backend for
   • #37 A file opened with Groove closed opens the app instead of aborting it
4. Shell habits the brief warns about: held outside this repo, where the sessions start
5. Suite runs that are not verdicts
   • #33 A full run of the suites says up front whether it can finish, and keeps what a red run left
6. Tickets and contracts written by analogy
   • #34 A ticket says which parts of its precedent do not apply, and where its contract is tested
7. Words meaning two things
   • #35 The glossary tells a moment on a clock from a marker's, and a room that has synced from one in touch
   • #36 The window's open document is called a document, whatever kind it is
8. Server hygiene: none of Groove's