/**
 * `npx freightutils-mcp ping` — single-command diagnostic for a fresh install.
 *
 * Tells the user three things in plain English:
 *   1. Is the FreightUtils backend up?   (GET /api/mcp/health)
 *   2. Does this package's MCP server start and register all tools?
 *      (in-process MCP handshake — Client ↔ Server via InMemoryTransport)
 *   3. Does an end-to-end tool call work through the proxy?
 *      (cbm_calculator with known inputs → backend → assert 0.96 m³)
 *
 * Exit codes:
 *   0 — every check passed
 *   1 — one or more checks failed (specific remediation printed inline)
 *
 * Why InMemoryTransport (not spawn-on-self): the diagnostic should report
 * what THIS process can see. Spawning a second `node dist/bin/cli.js` would
 * test a different process tree (different env, different cwd) and complicate
 * failure attribution. The in-memory pair exercises the same MCP handshake
 * code path Claude Desktop / Cursor / Cline use.
 */
export declare function runPing(): Promise<number>;