Boot without a client env; compact CLI around connect

[SoryAK]

Summary

• Boot uses family + model dials only. A leftover pairing (or the Copilot default) no longer merges environments/ overlays, so operators cannot generate the wrong configs by booting with a sticky env.
• The boot card shows env not set; BOOTED next is mba connect <id>. Connect still stages the card and mints a token (it does not rewrite flags on the running server).
• TTY polish on the same paint kit: status/clients grouped by slot, compact lists and boot card, sparse env folders at pull (no cartesian environments/).

Test plan

• mba s boot <id> — card has env not set, no GGUF path, then waiting health… and BOOTED … next mba connect <id>
• Model already paired to Cursor (or Copilot overlay folders exist) — boot flags still match family+model only
• mba connect <id> --harness cursor after boot stages the card; chat needs the token
• mba status / mba clients group sessions by harness + envelope (card vs pair)
• mba s boot --json / POST /servers/resolve — env.harness is none, envAttached is false (no renamed fields)
• Restart after mba models set still prints next mba s logs
• Rebuild @mba-ai/core and restart mba.service before live checks

Made with Cursor