v0.3.1

What's changed

Fixes MCP clients that were configured by a Navop build released before the
0.1.x argument removal.

• Legacy mcp positional is accepted again. Those builds write
  npx -y @navop/mcp@latest mcp --discovery <path> into client configs. Since
  0.2.0 this package is the bridge and rejects that positional with
  invalid_arguments before any JSON-RPC handshake, so clients that only watch
  "process started" showed the server as connected with an empty tool list. The
  launcher now accepts and ignores a leading mcp; any other unexpected
  argument is still rejected with the usage error.
• Regression test for the legacy argument in test/cli.test.mjs.
• Published as @navop/client@0.3.1, @navop/cli@0.3.1, @navop/mcp@0.3.1.

Existing installations need no config edit: update the package and the old
configuration connects. The corrected argument list (-y,
@navop/mcp@latest, --discovery, <path>) is also what current Navop builds
should generate.