Mission Run Overview
Mission Run: Operator Config & Install Ergonomics
One .kitty.env for all operator knobs, portable committed provenance, and an opt-in rc channel — so install and SaaS opt-in stop requiring manual env exports.
Operators, the dev team, and early adopters hit friction opting into SaaS sync (hand-exported env vars), non-portable absolute paths committed into charter governance files, and no smooth way to catfood rc builds. This mission introduces a single kernel env-expansion seam, a two-tier .kitty.env operator config file, token-based portable provenance, and a default-off unstable release channel — honored by migration/upgrade/doctor and documented with a new Team Kitty (SaaS) architecture section.