mb-startlisted

# Start Single entry point for Main Branch. Detect business state, intent, save/sync posture, and the smallest useful next route. ## Router and language contract This skill routes; it is not the worker for coordinated output. Use [references/router-and-language.md](references/router-and-language.md) as the business router before presenting a menu. Business language comes first. Say saved checkpoint, unsaved local work, catch up, sync, reconcile, shared repo, workspace, and provider readiness. Keep raw git terms, checkpoint ids, branch names, `origin`, `ahead`, `behind`, `rebase`, and `commit` out of the first response unless the user asks for technical detail or the exact command must be shown. When summarizing repo state, count `pushes/` records and flag `campaigns/` only as legacy compatibility. Use `core/vocabulary.md` display words in conversation while preserving actual paths in commands. **CLI facts first:** Once the business repo path is known, run `mb status --json --peek` before asking setup or routing questions. Treat JSON as source of truth for update severity, readiness, drift, onboarding, integrations, GitHub, team, bets, dirty git, since-last-check, `content_strategy`, `money_path`, `validation.file_contracts`, and `ranked_actions`. Use GitHub activity `author_display` / `author_known` when naming people. Parse the full JSON once; do not slice status output with `head` or `sed` in the normal path. **Shared source:** The portable daily start/status workflo