13.0.4 — stdio transport in the Docker image, correct serverInfo

Added

• docker run -i … stdio. The image only ever started the supervisor,
  which serves MCP over Streamable HTTP on :3737 and the dashboard on
  :37737. Every client that runs a local server the ordinary way — piping
  JSON-RPC over stdin/stdout, which is what Docker MCP Toolkit does — got a
  container that never answered. The engine always supported stdio
  (MCP_TRANSPORT defaults to it); nothing in the image reached that path.
  The entrypoint now has a stdio case that execs the server directly.
  Logs already went to stderr, so stdout carries JSON-RPC and nothing else —
  verified frame by frame.

Fixed

• serverInfo was wrong in both fields. The name was still
  claude-total-memory, the package name retired in v7, and no version was
  ever passed to Server(...), so clients rendered version: "". It now
  reports total-agent-memory and the real version.