I really don't think there's much point having editing history for book
You'll understand when you've bumped into some of the curious ways the module works, or how working outside the module can impact on previous work done in the book module. The inter-relatedness of the whole package is a double edged sword.
[/quote]I would always output a PDF for review. Partly this is because it is the actual object transmitted to Blurb, and in the past I've picked up some problems [/quote]Yes, doing a careful review of the final project from a PDF is always going to be worth while and something I've banged on about on Blurb's support forums in the past to users getting surprised by their final products.
The issue in LR4 is that the image previews can be quite poor, so you've no idea what the images will look like until they've been rendered. Plus as there's no view at actual size option, assessing how well things work next to each other on the page or how legible text is against a background etc. To see this you're stuck having to render out the whole project, time consuming and inconvenient.
Generally I'll build a number of stacks which represent the sections of the book, rearranging the stacks' order, setting the photos' order within the stack etc.
I'm not convinced using stacks would work for me, I only find them of very limited use. Using the filtering power of the library module seems the way to go.
Use Auto Layout in Book....
Not for me at all. I prefer to start with a blank canvas rather than paint by numbers.