48 issues, newest first, like every tracker. They light up in the order they can actually be worked.
Same issues. Same waves. Same speed. Now laid out in issuegraph order, so the next wave is always the next group.
You never had to guess the work order. It just wasn’t written down.
The backlog is 48 issues with real blocked-by, serialize-with and together-with edges. Each wave is the top of the ready set by effective priority, exactly as the spec's reader rules define it. Both rounds play the identical sequence.
The issues lit up in the order they could actually be worked. The list just had no way of showing you that order.
Sorted newest first. You had to guess where each wave would land.
Same issues, same waves, same speed. The next wave was always the next group.
You didn't get better at whacking. The work order was written down, so you could see it coming.