v1.5.0 — updating and staleness made honest

Two agent-visible reliability chapters: updating the tool without surprises, and knowing exactly what's stale after you do.

• load-lock update: checks npm, classifies where this copy lives before touching anything (bun global / npm global get applied; opencode cache copies and repo checkouts are refused with a pointer to who owns them), then restarts the service explicitly. --check dry run with script-friendly exit codes, --json for structured reports.
• load-lock service restart: composes the hardened stop and honest start; names the failed phase and reason if either side fails.
• Adapter-init drift notice: the OpenCode plugin and MCP server compare their version with the PATH CLI at startup and surface one clear notice naming load-lock update. Notify only — nothing is auto-installed.
• Dashboard staleness surfaces: the TUI panel now tells you when the running session's plugin code is older than the on-disk copy ("restart opencode to pick up vX") and reports "daemon restarted onto vX (was vY)" across daemon restarts via the version handshake.
• Reconnect hardening: a failed initial connect can no longer wedge the dashboard in "connecting" forever, and a pruned install can neither kill the host process nor wedge the daemon auto-spawn — the client falls back to the PATH-installed CLI's daemon entry.
• load-lock --version / version command.

Docs: OPERATIONS.md gains the plugin in-memory staleness section and updated service/restart guidance.

Tests: 181/181 green.