Fix flow DM in single-view and history pages
Make sure topic history doesn't have a flow-board component, so
flow-initialize can escape its operations.
Also add a sanity check to dm.System's populateBoardTopicsFromJson
roots array so even if we ever fall onto a page with a separate
and different API response the DM at least doesn't explode.