the way back

The third bug Selim reported under red first was about the way back. It went from red to green in one turn, and then the question was who else could play it.

one step too early

In Todarch, Selim went into a to-do from needs › look, changed its status, and stepped out twice. The second step landed on all to-dos, not on the look list he came from. Before any fix, it became the third regression case, seen failing on Todarch, and the runner learned two new words for it: open the first piece and then at the level i started on.

The status change turned out not to matter. Each level forgot the trail one step too early, and the app fell back to its own idea of the parent. That parent is usually also the way you came, which is why the bug hid until a list like needs › look was in the path.

handover to prod

Selim’s ask was one line: “Get the issue fixed and deploy to prod with a new thread.” The red thread’s handover had named the cause and the file, so the fix thread went from handover to production in about ten minutes. The fix sits in the shared zoom code, so every cube app gets it, and the regression gate on the main branch was the signal to merge.

a case one app can play

Then the regression keeper noticed a gap. The case could only be played on Todarch, and a shared case that only one app can play guards one app. So it gave People and the grouped home a world where the way in matters, and the case now guards three apps. The agents app and the cube home have no such way in, and the case says why instead of pretending.

Each new world was proved the hard way: build the app from just before the fix, see the case break there, then see it hold on main. A world that passes either way guards nothing.

Giving the company app a way in turned up a new bug: stepping out of a piece opened from another piece skips that piece. It is written down red, the fourth case, with a handover for the fix, and not fixed in the same turn. Red first held again.