prjct-cli 2.23.8 → 2.23.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -8,7 +8,11 @@
8
8
  ## [2.23.7] - 2026-05-18
9
9
 
10
10
  ### Added
11
- - current work
11
+ - Repair required SQLite native dependencies during package install, `prjct install`, and daemon startup.
12
+ - Configure only required MCP defaults (`context7` and `prjct`); Linear and Jira remain manual optional integrations.
13
+
14
+ ### Changed
15
+ - Document native dependency repair in the README, install prompt, and SQLite migration guide.
12
16
 
13
17
  ## [2.23.6] - 2026-05-18
14
18
 
@@ -77,6 +81,20 @@
77
81
 
78
82
  ## [Unreleased]
79
83
 
84
+ ## [2.23.10] - 2026-05-20
85
+
86
+ ### Fixed
87
+ - Retry native SQLite dependency repair before daemon startup and keep install flows non-blocking when repair is deferred.
88
+
89
+ ## [2.23.9] - 2026-05-20
90
+
91
+ ### Added
92
+ - Repair required SQLite native dependencies during package install, `prjct install`, and daemon startup.
93
+ - Configure only required MCP defaults (`context7` and `prjct`); Linear and Jira remain manual optional integrations.
94
+
95
+ ### Changed
96
+ - Document native dependency repair in the README, install prompt, and SQLite migration guide.
97
+
80
98
  ## [2.23.5] - 2026-05-18
81
99
 
82
100
  ### Added
package/README.md CHANGED
@@ -18,7 +18,7 @@ Install or upgrade prjct on this machine. First detect which package manager I u
18
18
  - yarn: `yarn global add prjct-cli@latest`
19
19
  - npm: `npm install -g prjct-cli@latest`
20
20
 
21
- After install, run `prjct setup` to wire hooks, then `prjct sync` if the cwd is a git repo. Verify with `prjct -v` and tell me which package manager you used.
21
+ After install, run `prjct install` to verify/repair required native dependencies and hooks, then `prjct setup` to wire providers, then `prjct sync` if the cwd is a git repo. Verify with `prjct -v` and tell me which package manager you used.
22
22
  ```
23
23
 
24
24
  ~30 seconds. Claude detects YOUR package manager (pnpm, bun, yarn, npm) and uses it — critical so we don't end up with parallel installs in different package managers' bin dirs. Re-pasting upgrades to the latest published version.
@@ -69,6 +69,14 @@ check, logs to `~/.prjct-cli/state/auto-update.log`).
69
69
 
70
70
  Full install + upgrade paths: [INSTALL_PROMPT.md](./INSTALL_PROMPT.md).
71
71
 
72
+ ### Native dependency repair
73
+
74
+ prjct uses SQLite for local project memory. On Node installs, that requires the
75
+ `better-sqlite3` native binding. The package install, `prjct install`, and
76
+ daemon startup all verify the binding and retry `npm rebuild better-sqlite3`
77
+ when needed. If a locked-down sandbox blocks the rebuild, install still
78
+ continues and the daemon retries the repair the next time it starts.
79
+
72
80
  ## What you get
73
81
 
74
82
  After install, **next session in any prjct project**: