prjct-cli 2.50.0 → 2.51.0

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "prjct-cli",
3
- "version": "2.50.0",
3
+ "version": "2.51.0",
4
4
  "description": "Context layer for AI agents. Project context for Claude Code, Gemini CLI, and more.",
5
5
  "main": "dist/bin/prjct.mjs",
6
6
  "bin": {
@@ -94,7 +94,6 @@
94
94
  "bin/prjct",
95
95
  "dist/",
96
96
  "templates/",
97
- "scripts/ensure-bun.sh",
98
97
  "scripts/install.sh",
99
98
  "LICENSE",
100
99
  "README.md",
@@ -101,6 +101,7 @@ On every turn ask: "what is the user trying to accomplish?" and match to a verb
101
101
  | "what did we accomplish?" | `prjct retro 7d --md` | 1 |
102
102
  | pause / resume the working context | `prjct context-save` / `prjct context-restore --md` | 1 |
103
103
  | reduce over-engineering — "make it leaner" / YAGNI review / cut complexity | `prjct lean review` (or `audit` / `debt`) | 1 |
104
+ | enforce test-first / "use TDD" / run the tests before shipping | `prjct tdd` (off\|assist\|strict; `check` runs the test command) | 1 |
104
105
  | sync this project across machines / "share with my other machine" / "is cloud on?" | `prjct cloud link` (then `status` / `sync` / `pull` / `pause`) | 2 |
105
106
 
106
107
  Disambiguators: the "why" separates a `decision` from an `inbox` dump — if you can't state it in one line, capture as inbox. A bare "fix X" is `task`, never `spec`. `audit-spec` requires an existing spec. For `ship`, if the active task has a `linked_spec_id`, ship surfaces the spec's acceptance_criteria as a PR checklist — STOP on any unmet criterion (override: `prjct ship --no-spec-gate`).
@@ -1,44 +0,0 @@
1
- #!/bin/sh
2
- # Auto-install Bun if not present (best-effort, never fails)
3
- #
4
- # Used by:
5
- # - scripts/postinstall.js (npm install)
6
- # - bin/prjct (first CLI invocation)
7
- #
8
- # NEVER exits with error — graceful fallback to Node.js
9
-
10
- # Already installed? Done.
11
- if command -v bun >/dev/null 2>&1; then
12
- exit 0
13
- fi
14
-
15
- # Also check ~/.bun/bin (may not be in PATH yet)
16
- if [ -x "${BUN_INSTALL:-$HOME/.bun}/bin/bun" ]; then
17
- exit 0
18
- fi
19
-
20
- # Only attempt on supported platforms
21
- case "$(uname -s)" in
22
- Darwin|Linux) ;;
23
- *)
24
- echo " Bun auto-install not supported on $(uname -s). Using Node.js."
25
- exit 0
26
- ;;
27
- esac
28
-
29
- echo " Installing Bun for optimal performance..."
30
-
31
- # Official Bun installer (non-interactive)
32
- if curl -fsSL https://bun.sh/install | bash >/dev/null 2>&1; then
33
- # Source the new PATH
34
- export BUN_INSTALL="${BUN_INSTALL:-$HOME/.bun}"
35
- export PATH="$BUN_INSTALL/bin:$PATH"
36
-
37
- if command -v bun >/dev/null 2>&1; then
38
- echo " ✓ Bun $(bun --version) installed"
39
- exit 0
40
- fi
41
- fi
42
-
43
- echo " Bun auto-install skipped. Using Node.js (still works fine)."
44
- exit 0