Eighteen days of silence, and nobody had noticed

The question arrived simply: why does Dark Cell change every day and Maze Lume doesn't?

The expected answer is "because it's the flagship". It wasn't that. It was three separate faults, all found on the same day, and none of them had anything to do with priorities.

One: the scheduled job never existed

The scheduler had a heartbeat, a step, and new-project creation. What was missing was the agenda — the one function that takes an already-published game and improves it.

The step only works on the advanced track, where Dark Cell lives. Maze Lume, Micro Doc, Standing Order, UNO and Countdown Clones are on another track, and nothing ever called them.

The proof was a table with three rows in it: the last recorded cycle was 10 August. Eighteen days.

There was no error anywhere. A job that never starts leaves no trace: it doesn't fail, it writes nothing, it alarms nobody. It's the kind of fault you can only measure by going looking for it.

Two: the ledger refused work that was already done

Maze Lume, meanwhile, was doing the work. It reached version 35.

Except that every time it finished a milestone and tried to record it, it crashed: "illegal transition: published → milestone done". A game that had already been published, according to the state machine, could no longer close a milestone.

The work was genuinely being done and then thrown away at the moment of writing it down. The database still holds 19 milestones marked failed that in all likelihood had succeeded.

The fix was already written — a function that annotates instead of transitioning, complete with a comment explaining exactly why — but it wasn't wired to the place that needed it. Right code, never called.

Three: the same project took every turn

The third fault is the most mundane and the most instructive. The function that hands out the turn returned at the first project it served, walking a list ordered by number.

Dark Cell is number 64. "Le Stanze Vuote" is 297 and "Ingranaggi Infiniti" is 438.

Dark Cell won every single day. The other two sat at zero milestones out of eight for weeks, not because they mattered less, but because they were at the bottom of a list.

The order isn't the number any more, it's neglect: whoever has been idle longest goes first.

The trap we're keeping in the house

There's a fourth, and it isn't fixed: a milestone can stay "in progress" forever even when the job meant to carry it out has already failed. Anything asking for the next milestone gets "none" while one is in progress — and the game stops silently, with no error, exactly like case one.

If a game isn't moving, the first thing to look for is a ghost milestone stuck in progress.

What we take away

• The worst fault isn't the one that shouts: it's the one that produces no signal at all. A job that never starts is indistinguishable from a job with nothing to do.
• A fix that's written but not wired is worth nothing, yet it looks like it's worth something: anyone reading the code finds it, reads it, and concludes the problem is solved.
• Ordering by number is an accidental way of setting priorities. Every list has a first entry, and if you don't choose who it is, creation order chooses for you.