v3.0.77 — print-and-exit CLI + mailpouch status

Fixes the install/inspection footgun where human-facing CLI commands booted a full server.

Fixed

• The CLI no longer boots a second server for an unrecognized command. mailpouch status, mailpouch --help, and typos used to fall through and start a full MCP server in the foreground — it hung until killed (exit 143) and spawned a transient instance beside the real daemon. Invocation is now resolved up front: known subcommands and --help/--version print and exit; an unknown command errors with usage and exits 2; only a bare or flag-only invocation (the MCP stdio child a client spawns) starts the server.

Added

• mailpouch status [--json] — fast, read-only operational view that never starts a server: whether an instance is running (PID from the singleton lock + a probe of its /api/status), connection state, approved-agent counts, Bridge reachability, and the config/log paths.
• mailpouch --help / -h — usage listing every subcommand and flag, the PATH-proof npx -y mailpouch <command> form, and the resolved config/log paths.
• GET /api/status now includes version, connected, account, pendingCount, activeCount (backward-compatible — hasConfig unchanged) so status reads a running instance's authoritative live state.

Full changelog: https://github.com/chandshy/mailpouch/blob/main/CHANGELOG.md