Output mangled, bootkey doesn't work

[h33p]

Seems like recent changes broke the CLI. Output of report is completely mangled and the bootkey is not working properly.

patp,p,ship_type,parent_patp,master_ticket,network_keyfile,dominion,owner_address,spawn_proxy_address,management_proxy_address,spawn_transaction,management_proxy_transaction,spawn_proxy_transaction,network_key_transaction,transfer_transaction
1,~bannyt-patfel,<master ticket>,0w2<rest of the bootkey>,0x0000000000000000000000000000000000000000,0xe489d5acef6fe0651c1bb69ca8384e81e9d3ae8e,0x69fcbd4fd1b793153b8b53a4bce82a8c1306e23a7d5695b770f9421df5ebf5d4,0xfb25c0f10a7865381aa39ec9adc6c464e09fde47521894123cfd793034b170ef,,0x739dbafc41351a0081699b224ab5ed07922e2289014593d16b86b9af43cedf54,0x2ad8872a018585872c7fff9a80aa93b847d92847cccd7661cce85aa0254ed898

If we convert this to json:

 {                                            
  "patp": "1",                                                                                                                                                                                                                                
  "p": "~bannyt-patfel",                                                                                                                                                                                                                      
  "ship_type": "~<master ticket>",                                                                                                                                                                                                
  "parent_patp": "<bootkey>",
  "master_ticket": "l2",                                                                                               
  "network_keyfile": "0xdb610347609555539ef469e25b78e9e474ae0ccf",                            
  "dominion": "0x0000000000000000000000000000000000000000",                                        
  "owner_address": "0xe489d5acef6fe0651c1bb69ca8384e81e9d3ae8e",                                   
  "spawn_proxy_address": "0x69fcbd4fd1b793153b8b53a4bce82a8c1306e23a7d5695b770f9421df5ebf5d4",                         
  "management_proxy_address": "0xfb25c0f10a7865381aa39ec9adc6c464e09fde47521894123cfd793034b170ef",                    
  "spawn_transaction": "",                                                                                             
  "management_proxy_transaction": "0x739dbafc41351a0081699b224ab5ed07922e2289014593d16b86b9af43cedf54",
  "spawn_proxy_transaction": "0x2ad8872a018585872c7fff9a80aa93b847d92847cccd7661cce85aa0254ed898",
  "network_key_transaction": null,
  "transfer_transaction": null                                                                                                                                                                                                                
 },

In addition, attempting to use the bootkey, over 2 hours after the ship has booted, I get greeted with this:

~
urbit 1.22
boot: home is /
loom: mapped 2048MB
lite: arvo formula 2a2274c9
lite: core 4bb376f0
lite: final state 4bb376f0
boot: loading pill /
boot: retrieving ~bannyt-patfel's public keys
boot: verifying keys
boot: invalid keys for planet '~bannyt-patfel'
pre-boot error: %life-mismatch

Mind you, here's the query for the pubkeys:

❯ curl -X POST "https://roller.urbit.org/v1/azimuth" -d "{\"params\":{\"ship\":\"~bannyt-patfel\"},\"id\":\"\",\"jsonrpc\":\"2.0\",\"method\":\"getPoint\"}" | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   793    0   713  100    80   1102    123 --:--:-- --:--:-- --:--:--  1227
{
  "id": "",
  "jsonrpc": "2.0",
  "result": {
    "dominion": "l2",
    "ownership": {
      "transferProxy": {
        "address": "0x0000000000000000000000000000000000000000",
        "nonce": 0
      },
      "votingProxy": {
        "address": "0x0000000000000000000000000000000000000000",
        "nonce": 0
      },
      "spawnProxy": {
        "address": "0x0000000000000000000000000000000000000000",
        "nonce": 0
      },
      "managementProxy": {
        "address": "0xe489d5acef6fe0651c1bb69ca8384e81e9d3ae8e",
        "nonce": 0
      },
      "owner": {
        "address": "0xdb610347609555539ef469e25b78e9e474ae0ccf",
        "nonce": 3
      }
    },
    "network": {
      "keys": {
        "life": "1",
        "suite": "1",
        "auth": "0xab275e8905f157e4319b9cdf621bbf46e4874709f55181c5a70dd4973eec944c",
        "crypt": "0xf5edc356b49565d73644e793cc058b912aa0c4ae86b77456d60b8f70d19da161"
      },
      "sponsor": {
        "has": true,
        "who": 26136
      },
      "rift": "0"
    }
  }
}

There has only been one set of network keys attached. They are live on the network, and they don't work.