0.120.0

Changed — may break callers

• cli-core 0.469.0 and cli-base 0.65.0. cli-core 0.469 accepts only cli-base 0.65, so both pins move together.
  cli-base 0.65 knows the verbs serve and revoke, so their lint baseline entries are gone, and its cli-dev bundle
  finds a server started with a flag before mcp serve. From cli-core 0.468, an MCP server offers a command that only
  fetches into the store through its read tool.
• Mail sync, rules and scoring run from cli-core 0.472.0. The engine moved to @wirecat/cli-core/mail; memo keeps
  its Himalaya and mbox sources, the domain-age lookup and the embedding. The account, ids, sync state and answers are
  the same. mail.source-failed is now declared by cli-core, and mcp serve has the --profiles option of
  cli-core 0.470 only in the shared contract it is checked against, not in memo.
• skill show, skill status and skill install answer --json in the one-thing envelope
  (WC-OUT-4),
  { item, meta }, like every other memo command and cli-core's own skill; they printed the bare object. A caller
  reads the old fields under item, e.g. item.targets of skill status.

Fixed

• memo starts in about half the time: the package runs from a bundle. A command loaded about a thousand module
  files before doing any work; it now loads a few dozen that hold the same code, built by cli-base's
  cli-dev bundle. Warm memo search all --help went from 420 to 186 ms, memo --version from 39 to 18 ms. Output
  is unchanged. A running memo mcp serve loads all of its code soon after it starts, so upgrading memo in place
  does not break it. The package is larger: 3.1 MB to download instead of 0.4 MB.
• memo mcp --json refuses the flag with a JSON validation_error (exit 2), as memo notes --json and
  memo mail --json do; it printed the group's help and nothing in JSON. mcp revoke and mcp server start|stop|status now take --json themselves, so it goes after the command: memo mcp revoke --json, no longer
  memo mcp --json revoke.