include breaks in story representation

There are some issues with the way this is done, but I wanted to mirror what we have on v3.

My biggest concern is that there's an impedance mismatch between read and write (write happens with a list of boolean attributes, read happens with an array that doesn't even really map correctly to those attributes). Again, just trying to avoid rethinking everything while moving to v4 from v3, otherwise I think it would make more sense to just stick to the list of booleans.

Thoughts?