chat-cli: reconnect with actual bowl
chat-cli: reconnect with actual bowl

Fixes a bug introduced in 4798b9d.

This, uh, fell into the same old case of using an arm from a |_ without
initializing that core with a sample first. In this case, that resulted
in the bowl in connect being the default bowl here. This is fine for
~zod, since it's the default ship, but gives incorrect behavior for
anyone else.

ngzax/urbit,ngzax/urbit,ngzax/urbit,jfranklin9000/urbit,urbit/urbit,urbit/urbit,jfranklin9000/urbit,urbit/urbit,ngzax/urbit,urbit/urbit,ngzax/urbit,ngzax/urbit,urbit/urbit,jfranklin9000/urbit,jfranklin9000/urbit,ngzax/urbit,jfranklin9000/urbit,jfranklin9000/urbit,urbit/urbit,urbit/urbit,jfranklin9000/urbit