prjct-cli 2.1.0 → 2.1.2

package/CHANGELOG.md

@@ -1,12 +1,119 @@
 # Changelog
 
+## [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
+`2.0.0-alpha.12`. The v2 sweep deleted the v1 workflow verbs (`done`,
+`pause`, `resume`, `next`, `reopen`, `dash`, `bug`, `idea`, `linear`,
+`jira`, `tokens`, `velocity`, `plan`) in favour of the `status`/`capture`
+primitives — but left the templates, state machine prompts, the
+installed `CLAUDE.md`, and the context config pointing at ghosts. The
+result was two user-visible regressions (P0 bugs):
+
+### Fixed
+- **P0 — silent-capture data loss.** Typing `prjct done`/`prjct pause`
+  on an active task no longer quietly files a note called "done" into
+  the inbox. Removed verbs now short-circuit with a migration message
+  and exit 1. Matching check added on both the fallback path
+  (`core/index.ts`) and the daemon path (`core/daemon/daemon.ts`).
+  New module: `core/commands/removed-verbs.ts` is the single source of
+  truth for the migration map.
+- **P0 — `prjct ship` degraded prereleases.** `bumpPatch` stripped the
+  prerelease suffix (`2.0.0-alpha.12` → `2.0.1`), corrupting the alpha
+  channel on every ship. Rewritten to follow semver rules:
+  `2.0.0-alpha.12` → `2.0.0-alpha.13`, `0.1.0-beta` → `0.1.0-beta.1`,
+  stable bumps unchanged. Build metadata (`+xyz`) is dropped to match
+  npm/pnpm behavior. Test coverage added in
+  `core/__tests__/services/version-service.test.ts`.
+
+### Changed
+- State machine (`core/workflow/state-machine.ts`) prompts and
+  `formatNextSteps()` now emit executable `prjct …` invocations that
+  map to the v2 CLI. `done`/`pause`/`resume`/`reopen` are surfaced as
+  `prjct status <value>`. Internal `WorkflowCommand` tokens stay for
+  lifecycle validation.
+- `canTransition()` error wording is state-transition-centric instead of
+  advertising non-existent CLI verbs.
+- `core/config/command-context.config.json` bumped to `2.0.0` and pruned
+  to registered v2 verbs only. Removed mappings for
+  `done/dash/next/pause/resume/idea/bug/spec/feature/cleanup/design/now/history/test/work/build/review/refactor/fix`.
+- `GLOBAL_CLAUDE_MD_CONTENT` (`core/infrastructure/command-installer.ts`)
+  rewritten: auto-activate list is the v2 surface; a concise v2
+  lifecycle cheat-sheet replaces the ghost-verb flow.
+- `CommandMethodName` (`core/types/commands.ts`) narrowed to registered
+  method names. `WorkflowCommand` (`core/types/workflow.ts`) no longer
+  includes `next` (never was a real transition).
+
+### Migration (for `prjct` users upgrading from v1.x)
+
+| v1 verb | v2 replacement |
+|---|---|
+| `prjct done` | `prjct status done` |
+| `prjct pause` | `prjct status paused` |
+| `prjct resume` | `prjct status active` |
+| `prjct reopen` | `prjct status active` (on completed task) |
+| `prjct next` | `prjct status` |
+| `prjct dash` | `prjct status` + web dashboard |
+| `prjct bug "…"` | `prjct capture "…" --tags bug` |
+| `prjct idea "…"` | `prjct capture "…" --tags idea` |
+| `prjct linear …` / `prjct jira …` | MCP server (`prjct seed list`) |
+| `prjct tokens` / `prjct velocity` / `prjct plan` | removed |
+
+### Operator note
+
+Upgrading from `1.x` while a long-running daemon is alive may leave a
+stale process bound to the socket. Run `prjct daemon stop` once after
+install, or kill the pid in `~/.prjct-cli/run/daemon.pid`.
+
 ## [2.1.0] - 2026-04-22
 
 ### Features
 
 - current work
 
-
 ## [2.0.0-alpha.12] - 2026-04-21
 
 Summary of the alpha.6 → alpha.12 arc and the dead-code / harness sweep