v0.41.2· Prompt Fires

Fixed

• Bare kandown now actually shows the "no project found, create one?" prompt. resolveKandownDir walked up every ancestor directory until it found a .kandown/kandown.json. Combined with the ~/.kandown/ updater cache that also happened to hold vava's personal home board, the ascent silently attached to the home board from any subdirectory under $HOME, so the TUI init confirmation almost never triggered. The walk now stops at the current git repository root and never treats $HOME as a project root unless the walk started there, so a deliberate home board still resolves from ~ but never from below. Bare kandown in a non-git, non-project subdirectory of $HOME now hits the project creation prompt as designed, and Enter creates the project, starts the daemon and opens the board in one step.
• Bare .kandown/ directories without kandown.json are no longer treated as projects. The bare-kandown branch in src/cli/cli.ts now checks for kandown.json (mirroring the TUI gate and the resolver), so a partial init cannot start the daemon or block the prompt.

Added

• Regression tests for the boundary behavior in src/cli/lib/__tests__/resolve-kandown-dir.spec.ts: five specs pinning the home-board-still-works-at-~, git-root-walk-stop, $HOME-skipped-from-below, filesystem-root fallback, and project-at-exact-git-root behaviors.