Graceful Errors

There are a few `TODO`s in the code that are essentially unwrapping `Option::None`. Would be great to either get detailed errors on any fields RPC didn't send (rare case), some sensible default value, or omission of these null fields. I think the first option is probably best.

Start by locating the TODOs that unwrap Option::None and trace how RPC responses are converted into the command-line explorer's fields. Review the existing error-handling conventions and determine whether missing fields should produce detailed errors, use defaults, or be omitted; done means every identified None case is handled without an unintended panic.

Written by the indexing model from the issue text.