0.7.0

Changed — may break callers

• The skeleton runs on cli-core 0.449.0 and cli-base 0.62.0, the only cli-base line cli-core 0.449 accepts; a CLI
  that pins cli-base moves both pins together. The commands and their help do not change, apart from the mcp
  additions below.

Added

• clidev <profile> mcp --http serves the profile to ChatGPT and Claude in the browser, on 127.0.0.1 behind the
  owner's tunnel, with a one-time login code; --revoke ends every login, and is refused under CLIDEV_READ_ONLY.
  mcp server start|stop|status runs it in the background (from cli-core 0.445.0): status shows the port, the
  connector address, the current login code and the apps logged in, and the background server writes no login code to
  its log. A second mcp --http for the same profile is refused. mcp --permission key=level makes a permission
  stricter for one server, over stdio too. A CLI made from an older template takes this with upgrade, or mounts
  mcpServerCommand on its own mcp and passes lockFile: httpLockFile(tokenFile) to serveOverHttp.

Fixed

• new writes the speech model advice into docs/dev/DESIGN.md only for --category messenger. A calendar or
  notes CLI got "If this CLI defines a messenger, set its speechModels…" and a warning that no speech model hears a
  language, though only a messenger transcribes voice messages.
• The cron step new prints points to the list of taken monthly minutes in cli-base's CI page (WC-CI-9), so
  nobody has to read monthly.yml in every repository to find a free one. The examples now use gcal-cli and
  gcal: cal is the system calendar program on macOS and many Linux systems.
• Every command spends less time getting ready (cli-base 0.62.0, cli-core 0.449.0). The check of shared commands now
  describes each command once, not again for every group above it. It was about 60% of each command's setup; in tg a
  warm run(["--version"]) went from 49 to 29 ms. It catches the same changes as before.
• bin/release no longer reports a release that passed as failed. gh run watch also stops with an error when
  one of its own requests to GitHub fails, while the run goes on; 0.6.1 was published, tagged and green, and the
  script said it failed. It now waits for the run to finish, reads its result, and checks npm before it says anything.
  It names bin/release --local only when npm refused the publish because it does not trust the workflow yet.