EvoLink CLI 0.10.0

The CLI now tells you when a newer release exists, auth status no longer reads like an expired login, and plain doctor checks installed skill copies.

• Update notices. setup, doctor and auth login ask the npm registry for the latest release and report update (status, update_available, latest_version, command); setup and login print one progress line when an update exists, and a failed login names it too. Other commands, except the offline auth status, reuse an answer from the last 24 hours and print one stderr line after their own output when a newer release exists, at most once a day per release. stdout, --json envelopes and exit codes are unchanged. A check waits at most 3 seconds and never keeps the process running after that. Turn checks off with EVOLINK_CLI_UPDATE_CHECK=0; NO_UPDATE_NOTIFIER and CI also turn them off.
• auth status. The bare expires_at (the ten-minute access-token expiry) is replaced by access_token_expires_at, access_token_renewal: automatic, logged_in_at, login_check and a note: an elapsed access token renews itself and is not an expired login. Verify a login with evolink balance --json.
• doctor. Without --agent, doctor reports installed skill copies as skills.status with guidance (outdated copies point to evolink skills install; local edits are never replaced). It does not change ok.
• No change to estimates, generation, uploads or the bundled platform core (same core as 0.9.x / MCP 1.7.0).

Validation: 122 unit tests and 94/94 mutations on Node 22 and 24; the packed CLI against the real npm registry (17 scenarios), a logging proxy and network-failure cases on the test cloud; six Linux/macOS/Windows × Node 22/24 CI jobs passed on the merged main commit.

Upgrade with npm install -g @evolinkai/cli@0.10.0, then run evolink skills install.