Aha! It turned out to be some temporary flaw in the way iBooks was working with that file.
Simply loading up a different iBook title cleared the way pages were being generated to the screen.
Reloading the failing file no longer showed the flaw.
Interesting to see that iBooks' display engine can go a little funny in the head on its own...