Responses become strings when passed along. Encode them as a json string so that we can use the object as needed anywhere we rescue it.
Appropriately deal with file size. We have a magic number here that needs to be tracked down and identified as well as tested on non OSX machines.
Deal with possible error paths through the comment process.

* User submits form but we get an error from regulations.gov - first we reload the form to ensure we have an up to date from and that the agency hasn’t added a required field since we last cached it. Then we attempt to save that form. If it’s invalid we show the user the invalid form per usual with validation errors. However if it passes our validation it will be submitted again. If that second submission is also an error (unexpected form config, unplanned outage since the first submission, etc) we simply rescue that and show the user whatever message came back as there is nothing more we can do at that point.
* Other path is that we simply can’t communicate with regulations.gov. So we let the user know and provide a link to their site where the user can go to see what is happening.