0.33.4 — Daemon Update Recovery

Fixed: Default kandown Launch Reusing Stale Daemons — running kandown now validates the already-running project daemon version before reusing it. If the daemon is missing a version or is running a different CLI version than the current command, Kandown safely stops it and starts a fresh daemon from the active CLI so the browser opens the current web app instead of stale in-memory code.
Fixed: Web UI Auto-Update Not Taking Effect Immediately — successful /api/update/apply calls now schedule a detached daemon restart after the HTTP success response is sent. This makes one-click Web UI updates actually switch the local server process to the newly installed package instead of requiring a manual daemon stop/start.
Fixed: Auto-Updater False Success Across Multiple Node Prefixes — global package update attempts now verify the resolved kandown --version after each package-manager install command. If npm, pnpm, yarn, or bun updates a different global prefix than the executable on PATH, the updater keeps trying fallbacks and no longer reports success while the active command remains stale.
Changed: Daemon Health Metadata — daemon status checks now read and propagate the remote daemon version from /api/daemon, keeping CLI-side restart decisions aligned with the process that is actually serving the project.
Changed: Update Route Messaging — the update API success message now explicitly says the daemon is restarting, making the expected short reconnect window clearer for the Web UI.