prjct-cli 2.1.1 → 2.2.1

package/CHANGELOG.md

@@ -1,5 +1,141 @@
 # Changelog
 
+## [2.2.1] - 2026-04-22
+
+Follow-up to 2.2.0: the vault was generated at the right location but
+Obsidian refused to open it via `obsidian://open?vault=<slug>` because
+the folder wasn't registered in Obsidian's global vault list. Users had
+to manually "Open folder as vault" the first time.
+
+### Added
+- `core/services/obsidian-vault.ts`: `ensureObsidianVault(vaultPath)`
+  does two things, idempotently:
+  1. Bootstraps a minimal `.obsidian/app.json` inside the vault so
+     Obsidian treats the folder as already-initialized (and skips its
+     trust prompt).
+  2. Registers the vault path in Obsidian's config file
+     (`~/Library/Application Support/obsidian/obsidian.json` on macOS,
+     `$XDG_CONFIG_HOME/obsidian/obsidian.json` on Linux,
+     `%APPDATA%\obsidian\obsidian.json` on Windows). The vault then
+     shows up in the Vault Switcher after a restart.
+  Best-effort — quietly skips registration when Obsidian isn't
+  installed (no config directory). Bootstrap still runs so the vault
+  is valid the moment the user does run Obsidian.
+- `wiki-generator.ts` calls `ensureObsidianVault(wikiRoot)` at the end
+  of every regen. `.catch(() => undefined)` guard: never fail a regen
+  because Obsidian glue misbehaved.
+- Tests in `core/__tests__/services/obsidian-vault.test.ts` cover
+  bootstrap, URL-encoding of vault names, registration append (keeps
+  prior vaults), idempotency, and the no-Obsidian-installed path.
+
+### Operator note
+
+First-time upgraders from <2.2.1: Obsidian caches its vault list in
+memory. Close Obsidian fully (⌘Q on macOS, File > Exit on Windows/
+Linux) and relaunch — the newly-registered vault will appear in the
+switcher.
+
+## [2.2.0] - 2026-04-22
+
+Obsidian vault location moved out of the repo. Each project now has its
+own visible vault at `~/Documents/prjct/<slug>/` instead of the hidden
+`<repo>/.prjct/wiki/` path. Two reasons:
+
+1. The `.prjct/` prefix is a dotfile — Finder/Explorer hide it by
+   default, so users who opened Obsidian looking for their vault often
+   couldn't find it. The new path lives under `~/Documents/prjct/`,
+   visible without toggling hidden files.
+2. Privacy-by-default. The old path lived inside the repo and got
+   committed on any `git add -A` unless the user remembered to
+   `.gitignore` it — leaking private decisions, learnings, and gotchas
+   on push.
+
+### Changed (BREAKING — path, not API)
+- Default vault path: `~/Documents/prjct/<slug>/` where `<slug>` is
+  derived from the project directory name (basename, lowercased,
+  slugified). Callers that hard-coded `.prjct/wiki/` will no longer find
+  the vault there.
+- `core/infrastructure/path-manager.ts` exposes a new `getWikiPath()`
+  resolver as the single source of truth. Both `wiki-generator.ts` and
+  `wiki-ingest.ts` route through it.
+
+### Added
+- `vaultPath` field in `.prjct/prjct.config.json` (optional string) —
+  overrides the default. Accepts absolute paths, `~/...`, or
+  project-relative paths (e.g. `"./docs/wiki"` to keep the vault
+  in-repo). Use `"vaultPath": ".prjct/wiki"` to keep pre-2.2.0 behaviour
+  verbatim.
+- Auto-migration: the first `prjct remember`/`ship`/`context wiki sync`
+  after upgrade detects a legacy `.prjct/wiki/` folder and moves its
+  contents to the new location. Cross-filesystem moves (EXDEV) fall
+  back to copy + delete. Idempotent.
+- `.gitignore` gets a `.prjct/wiki/` entry appended when a git repo is
+  detected during migration, so the legacy folder doesn't show up in
+  `git status` if a tracked copy was ever committed.
+- Tests:
+  - `core/__tests__/infrastructure/path-manager-wiki.test.ts` covers the
+    resolver (defaults, overrides, slug collisions, project-relative
+    rollback).
+  - `core/__tests__/services/wiki-migration.test.ts` covers the move
+    (no-op cases, conflict detection, gitignore dedup).
+
+### Migration notes
+
+- **Nothing breaks for users who accept the default.** The first
+  wiki-touching command after upgrading moves your existing
+  `.prjct/wiki/` to `~/Documents/prjct/<repo-name>/` with a one-line
+  stderr notice, then continues. Second invocation is silent.
+- **To keep the old path**, add `"vaultPath": ".prjct/wiki"` to
+  `.prjct/prjct.config.json`. The migration respects the override and
+  leaves the legacy folder alone.
+- **Conflict handling**: if you somehow already have content at both
+  the legacy path and the new default, the migration refuses to
+  overwrite and prints a warning. Merge manually or pick a side via
+  `vaultPath`.
+
+## [2.1.2] - 2026-04-22
+
+Upgrade-safety pass for clients coming from 1.x or 2.1.0. The 2.1.1
+release fixed the CLI surface but left two upgrade hazards that clients
+could hit in the wild.
+
+### Fixed
+- **Zombie daemon after global upgrade.** pnpm's content-addressable
+  store leaves the previous-version files untouched on disk when a new
+  version is installed globally, so the long-lived daemon kept serving
+  requests from the old build. The thin shim's mtime-based stale check
+  never fired. Daemon now reads its own `package.json` at startup,
+  periodically probes the globally-installed `prjct` binary
+  (pnpm/npm/volta/asdf paths covered), and shuts itself down on
+  version mismatch — the next request spawns a fresh daemon.
+  (`core/daemon/daemon.ts`)
+- **Orphan `workflow_rules` after v1 → v2.** v1 users could attach hooks
+  to command verbs that v2 narrowed `HookCommand` to `[task, done,
+  ship, sync]`. Rules keyed on `pause/resume/reopen/next/dash/bug/idea/
+  linear/jira/tokens/velocity/plan` survived the upgrade as dead rows
+  that `prjct workflow list` still surfaced. SQLite migration v15
+  disables them idempotently (enabled=0, not deleted — visible with
+  `--include-disabled` for rename/re-enable). Only the orphans —
+  `done/ship/task/sync` hooks are preserved.
+  (`core/storage/database.ts`, migration v15)
+
+### Added
+- Upgrade-path test coverage in
+  `core/__tests__/storage/upgrade-v1-to-v2.test.ts`: seeds a v1-shaped
+  DB, asserts orphan rules are disabled, valid hooks survive, and the
+  legacy task-status values (`in_progress`/`done`/etc.) still coerce
+  correctly through the state machine.
+
+### Migration notes
+
+- Upgrading from 1.x: no action required. On first `prjct <cmd>` after
+  install, any stale daemon detects the version drift and exits; the
+  next invocation starts a clean daemon and runs migration v15 the
+  first time each project's DB is touched.
+- Orphan rules show as `disabled` in `prjct workflow list
+  --include-disabled`. Rename their `command` to a v2 `HookCommand`
+  value (`task`/`done`/`ship`/`sync`) and re-enable if still relevant.
+
 ## [2.1.1] - 2026-04-22
 
 Closes the v2 migration gap shipped (incompletely) in `2.1.0` and