0.14.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 overrides are gone, and its cli-dev bundle finds
  a server started with a flag before mcp serve. From cli-core 0.467 every run is recorded by default, successes
  too, and says who asked for it (via); record: false now keeps failures. From cli-core 0.468, an MCP server offers
  a command that only fetches into the store through its read tool.
• The MCP server is wa <profile> mcp serve; wa <profile> mcp alone prints help. Browser logins are
  forgotten with wa <profile> mcp revoke instead of mcp --revoke, and wa mcp serve with no profile serves every
  profile. A bot's server is wa <name> bot mcp serve. An app entry that runs wa personal mcp must change to
  wa personal mcp serve: run wa personal mcp add <app> or wa personal mcp config again. mcp server start,
  the entries mcp config prints and the MCP Registry entry already run the new command (cli-core 0.463.0).
• wa skill show|status|install --json print { item, meta }. The skill's fields moved under item; the
  Windows installer reads them from there (cli-core 0.462.0).
• wa account list says whether each profile is signed in on this computer (signed_in), and search hits of
  every kind name the fields an agent must read as data (untrusted). A caller that checks them against an older,
  strict copy of the schema refuses the new field (cli-core 0.464.0 and 0.466.0).

Added

• wa <profile> mcp server status says what each logged-in browser app last did (cli-core 0.454.0).
• wa upgrade restarts the browser MCP server that wa mcp server start launched on the same port, address and
  limits (mcp_servers, old → new version); one started by hand is left running and named. Agent sessions over
  stdio still on the old version are listed (stale_sessions): restart them from your agent app. This works from the
  next upgrade on (cli-core 0.464.0).

Fixed

• wa 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 wa messages list --help went from 416 to 200 ms, wa --version from 39 to 18 ms. Output is
  unchanged; the WhatsApp engine is still found in its platform package. A running wa serve or wa mcp serve loads
  all of its code soon after it starts, so upgrading wa in place does not break it. The package is larger: 2.7 MB
  to download instead of 0.3 MB.
• wa mcp serve with no profile marks the profiles that are not signed in. It listed every profile, so an app
  could pick one with no linked device and fail. Each profile is now labelled (default — not signed in) in the
  app's menu and in the description, and a call for one that is not signed in answers how to sign it in:
  wa <profile> setup, or from WireCat Desktop.
• The login page of the browser MCP server says each code works for one login. After an app logs in, a new code
  appears in WireCat Desktop and in wa mcp server status (cli-core 0.466.0).