It's that bug I mentioned in the PR, about the ToC flipping. We decided to handle that with the revamp of the ToC in the ALEX-50 ticket.

I've now added the scenario:

Scenario 3: Multiple 30041s

GIVEN I have a 30040 index, containing at least five 30041 content events

BUT containing no nested 30040 events

WHEN I select that index card from the landing page

THEN the reading view opens with the content in the correct order

AND the ToC lists the content in the correct order

AND clicking on a section, causes the viewer to focus on that section