Here's a bonus thought about what I showed in the last comment, and maybe @mccanne would have some input here.

The app's guidance "...or fuse results to view as a table" is arguably incorrect since with a sequence of primitive values like this fuse can't turn it into a table, and by applying fuse each value will instead just take on a union type. The way the branch is working now, clicking that fuse link just gives the unlabeled sequence of values.

If the app had picked up on the presence of any primitive values in the query output, perhaps it could have changed the guidance to more accurately reflect that it's impossible to make into a table and say as much, and perhaps drop the fuse link in that case?