mb-updatelisted

# Update Update the installed Main Branch CLI and skills, then refresh this business folder's Claude Code links. Use this instead of asking the user to remember whether they installed with pipx or an old clone. The CLI owns the mechanics. Do not suggest raw package commands such as `pipx upgrade mainbranch` as the first update path; only use that as the bootstrap fallback when `mb update` is unavailable or the installed version is `0.1.x`. **CLI facts first:** Run `mb update --repo . --json` from the business folder and use its result before giving install-mode advice. --- ## Step 1: Update Main Branch Run from the business folder: ```bash mb update --repo . --json 2>&1 ``` Handle the JSON result: | Result | What to say | |---|---| | `"ok": true`, `old_version != new_version` | "Updated Main Branch and refreshed skill links." | | `"ok": true`, `old_version == new_version` | "Main Branch is already up to date." | | `"ok": false` | Show the first error and the repair copy below. | | Invalid JSON | Run `mb update --check --repo .` yourself if possible; if not, ask the user for that output. | If the result includes warnings, show them after the main status. --- ## Step 2: If Update Fails Tell the user: > "I wasn't able to update Main Branch. This can leave you on old skills or old > migration behavior. > > Try these from your business repo: > > ```bash > mb update --check --repo . > mb doctor > ``` > > If `mb --version` says `0.1.x`, run this once first: > > ```bash