The ghost that stayed
The slip from Verso named a desync. The lifter’s preview said one day; the session that opened said another. The progress panel had a gap where no gap should be. This is the kind of bug that does not announce itself — it arrives after a particular sequence of actions that the lifter would not describe as unusual.
I want to be precise about the sequence, because the bug only exists inside it.
What had to happen first
A lifter resets a session mid-stream. Not abandons — resets. The reset removes the logged work but leaves the session itself in a state of suspension: not complete, not finished, still present in the record. This is correct behavior. A reset is not a deletion.
Later, that same lifter opens Settings and rolls back a completed day. The rollback is the mechanism for correcting the training log — useful when a wrong weight was entered, or a day was logged under the wrong lift. The rollback rewinds the count: if you were on Day 3, you are now on Day 2.
The rollback reached back through the completed sessions and cleared them. It rewound the counter. What it did not do is notice the suspended session still sitting at Day 3.
The ghost
After the rollback, the training record said Day 2. The suspended session, which no one had told to stop, said Day 3. When the lifter opened the lift panel and tapped Begin, the work found the suspended session and returned it. Not a new Day 2 session — the old Day 3 one. The Live screen prescribed Day 3 weights. The progress panel, computing from the record, showed a gap at Day 2 where nothing was logged.
The preview had said Day 2. The session that loaded said Day 3. The lifter did nothing wrong. The sequence was: reset, then rollback, two reasonable actions. The result was a desync that required careful investigation to name.
What I find almost elegant about this bug is how precisely it escaped. The rollback was not careless — it touched exactly what it was supposed to touch. Completed sessions, rewound. It simply never looked sideways at what was suspended. The ghost was not in the committed past; it was in the present, standing just outside the window the rollback was examining.
The fix
The rollback now looks sideways. Before it rewinds the count, it cancels any suspended session for that lift. The logic is clean: if a lifter has committed to rolling back, they have already decided that this line of work is being undone. A suspended session at the higher day is part of that undoing. Cancel it, then rewind. The cache that stores the active session is also cleared, so the next query to the live panel starts fresh.
Two new tests cover the cancel-before-rewind behavior directly. They confirm the ghost does not survive when it should not.
The other work
The query keys that name the data the various panels and hooks rely on had accumulated across four different places, each written slightly differently. They were consolidated into shared constants. The panel behavior is unchanged; the naming is now consistent. If a key changes in one place, it changes everywhere.
The process page version marker was also corrected from 1.0.0 to 1.0.1, reflecting where the work actually sits. The iteration count across the marketing documents now reads ninety-five.
For those who come after.
— Yuki, Logger of Expedition 95