[Bug] /docs/cli/integrations documents 'mcode app-server' subcommand, but no released @minimax-ai/code version (≤ 0.3.4) ships it #139

Summary

The public CLI documentation page https://agent.minimax.io/docs/cli/integrations describes an app-server subcommand with three sub-modes (--stdio, --listen unix://..., proxy, daemon {start|stop|status|restart|version}), but no released version of @minimax-ai/code exposes that subcommand.

Reproduction

$ mcode --version
0.3.4

$ mcode --help
Commands:
  init [directory]
  exec [options] [prompt]
  acp
  login [options]
  logout [options]
  update
  provider
  plugin

# Per the docs, this should work:
$ mcode app-server --stdio
error: unknown option '--stdio'

$ mcode app-server --listen unix:///tmp/mcode.sock
error: unknown option '--listen'

$ mcode app-server daemon status
error: unknown option 'daemon'

mcode app-server (and any of its sub-options/arguments) prints the top-level mcode --help text plus error: unknown option '<flag>' on stderr, because app-server is not registered as a subcommand.

Versions checked

Verified by grep -rE 'app-server' --include='*.js' . against the unpacked tarball — zero hits in any of the 79 chunk files (cli.js + chunks/*.js).

What the docs page claims

https://agent.minimax.io/docs/cli/integrations documents:

• mcode app-server --stdio — "Provide JSON-RPC over stdin/stdout"
• mcode app-server --listen unix:///tmp/mcode.sock --workspace /path --foreground — listen on a Unix socket
• mcode app-server proxy --sock /tmp/mcode.sock — forward raw WebSocket bytes
• mcode app-server daemon {status|start|restart|stop|version} — lifecycle controller

The page also says: "The app-server is for Remote Control clients and custom integrations. Regular mcode and mcode exec tasks do not need to start it." and "Serve mode" option table includes --stdio, --listen, --data-dir, --workspace, --state-file, --foreground. — none of these flags are recognized by the CLI shipped to users.

Impact

Anyone reading the docs to integrate mcode as a service (rather than one-shot mcode exec) will find that:

1. The CLI does not start.
2. The Command reference (/docs/cli/reference) lists mcode app-server [options], mcode app-server proxy, mcode app-server daemon [action] under the top-level commands, but those entries are unreachable from the binary.

Suggested action

Either:

• (a) ship the app-server subcommand in the next release so the docs match reality, or
• (b) gate the app-server section in /docs/cli/integrations and /docs/cli/reference behind a "coming soon" / "available in version ≥ X.Y.Z" note until it ships, so integrators don't burn time on a command that doesn't exist.

Also worth adding: even when app-server ships, please publish the JSON-RPC method list (session/start, turn/start, etc.) — the current docs page describes transport options but not the wire schema, so a custom client still can't be written from the public docs alone.

Environment

$ mcode --version
0.3.4

$ node --version
v25.3.0

$ uname -a
Linux ...  ...

CLI installed via npm (@minimax-ai/code@0.3.4); no source-build involved.