v4.6.3

Fixed

• CRITICAL: the server never started when launched via npx kie-mcp or a global bin (regression in 4.4.2's #41, affected 4.4.2–4.6.2). npx/global installs invoke through a bin symlink (.bin/kie-mcp → ../kie-mcp/server.mjs), so process.argv[1] was the symlink path while import.meta.url resolved to the realpath. The main-module guard's plain === compare failed, so the module loaded (no error, no output) but never connected its stdio transport — the MCP silently appeared "down". isEntrypoint() now resolves symlinks on both sides (realpathSync) before comparing, so node server.mjs, npx kie-mcp, and global-bin invocations all start correctly. Direct-import (tests) still short-circuits, unchanged. Regression-tested with a real symlink.