prjct-cli 1.46.2 → 1.46.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prjct-cli",
-  "version": "1.46.2",
+  "version": "1.46.5",
   "description": "Context layer for AI agents. Project context for Claude Code, Gemini CLI, and more.",
   "main": "dist/bin/prjct.mjs",
   "bin": {
@@ -81,8 +81,8 @@
   "homepage": "https://prjct.app",
   "packageManager": "bun@1.2.23",
   "engines": {
-    "node": ">=18.0.0",
-    "bun": ">=1.0.0"
+    "bun": ">=1.0.0",
+    "node": ">=18.0.0"
   },
   "files": [
     "assets/",
@@ -90,6 +90,7 @@
     "dist/",
     "templates/",
     "scripts/postinstall.js",
+    "scripts/ensure-bun.sh",
     "scripts/install.sh",
     "LICENSE",
     "README.md",

package/scripts/ensure-bun.sh

@@ -0,0 +1,44 @@
+#!/bin/sh
+# Auto-install Bun if not present (best-effort, never fails)
+#
+# Used by:
+#   - scripts/postinstall.js (npm install)
+#   - bin/prjct (first CLI invocation)
+#
+# NEVER exits with error — graceful fallback to Node.js
+
+# Already installed? Done.
+if command -v bun >/dev/null 2>&1; then
+  exit 0
+fi
+
+# Also check ~/.bun/bin (may not be in PATH yet)
+if [ -x "${BUN_INSTALL:-$HOME/.bun}/bin/bun" ]; then
+  exit 0
+fi
+
+# Only attempt on supported platforms
+case "$(uname -s)" in
+  Darwin|Linux) ;;
+  *)
+    echo "  Bun auto-install not supported on $(uname -s). Using Node.js."
+    exit 0
+    ;;
+esac
+
+echo "  Installing Bun for optimal performance..."
+
+# Official Bun installer (non-interactive)
+if curl -fsSL https://bun.sh/install | bash >/dev/null 2>&1; then
+  # Source the new PATH
+  export BUN_INSTALL="${BUN_INSTALL:-$HOME/.bun}"
+  export PATH="$BUN_INSTALL/bin:$PATH"
+
+  if command -v bun >/dev/null 2>&1; then
+    echo "  ✓ Bun $(bun --version) installed"
+    exit 0
+  fi
+fi
+
+echo "  Bun auto-install skipped. Using Node.js (still works fine)."
+exit 0

package/scripts/postinstall.js

@@ -32,3 +32,14 @@ ${CYAN}${BOLD}   prjct${RESET} ${DIM}v${VERSION}${RESET}
 
    ${DIM}Supports: Claude Code, Gemini CLI, or both${RESET}
 `)
+
+// Auto-install Bun for optimal performance (best-effort)
+try {
+  const { execSync } = require('node:child_process')
+  const ensureBun = path.join(__dirname, 'ensure-bun.sh')
+  if (fs.existsSync(ensureBun)) {
+    execSync(`sh "${ensureBun}"`, { stdio: 'inherit', timeout: 30000 })
+  }
+} catch (_err) {
+  console.log(`   ${DIM}Bun not installed — using Node.js (slower)${RESET}`)
+}

package/templates/commands/done.md

@@ -14,10 +14,23 @@ If CLI output is JSON with `options`, present the options to the user and execut
 - Review files changed: `git diff --name-only HEAD`
 - Ensure work is complete and tested
 
-## Step 3: Handoff context
+## Step 3: Pattern compliance check
+
+If a Pattern Commitment table was created during the "Pattern commitment" step of the task workflow, review each committed pattern against the actual changes:
+
+| Pattern | Status | Evidence |
+|---------|--------|----------|
+| (name) | FOLLOWED | `path/file.ts:line` — used correct abstraction |
+| (name) | VIOLATED | reason — e.g., needed `use client` for interactivity |
+
+Report any VIOLATED pattern with a clear reason. The user decides whether to accept the violation.
+
+If no commitment table exists (e.g., project not synced, or patterns were empty), skip this step.
+
+## Step 4: Handoff context
 Summarize what was done and what the next subtask needs to know.
 
-## Step 4: Follow CLI next steps → Ship
+## Step 5: Follow CLI next steps → Ship
 After completing, you MUST ask:
 ASK: "Subtask done. Ready to ship or continue to next subtask?"
 - Ship now → execute `p. ship` workflow (load and follow `~/.claude/commands/p/ship.md`)

package/templates/commands/task.md

@@ -19,24 +19,41 @@ If CLI output is JSON with `options`, present the options to the user and execut
 - If the task is ambiguous, ASK the user to clarify
 - Explore beyond suggested files if needed
 
-## Step 4: Plan the approach
+## Step 4: Pattern commitment (MANDATORY — do not skip)
+
+Before writing ANY code, complete this checklist:
+
+1. Read **Locked Decisions (NON-NEGOTIABLE)** from the Context Contract output. These are hard constraints — do not deviate.
+2. Read **Pattern Briefing** — each pattern lists a VIOLATION line showing what NOT to do.
+3. Read **Task Patterns (MUST follow)** — for each one, state HOW you will apply it to this specific task.
+
+Output a commitment table:
+
+| Pattern | Implementation plan for this task |
+|---------|----------------------------------|
+| (name from Task Patterns) | (concrete: which files, which types, which components) |
+
+If no patterns were provided in the CLI output (e.g., project not yet synced), skip this step.
+If the user corrects a commitment, update the table before proceeding.
+
+## Step 5: Plan the approach
 - For non-trivial changes, propose 2-3 approaches
 - Consider existing patterns in the codebase
 - If CLI output mentions domain agents, read them for project patterns
 - Summarize anti-patterns from the CLI output before editing any file
 
-## Step 5: Execute
+## Step 6: Execute
 - Create feature branch if on main: `git checkout -b {type}/{slug}`
 - Work through subtasks in order
 - When done with a subtask: `prjct done --md`
 - Every git commit MUST include footer: `Generated with [p/](https://www.prjct.app/)`
 - If a change may violate a high-severity anti-pattern, ask for confirmation and propose a safer alternative first
 
-## Step 6: Ship (MANDATORY)
+## Step 7: Ship (MANDATORY)
 When all work is complete, you MUST execute the ship workflow:
 ASK: "Work complete. Ready to ship?" Ship now / Continue working / Pause
 - If Ship now: execute `p. ship` workflow (load and follow `~/.claude/commands/p/ship.md`)
-- If Continue working: stay in Step 5
+- If Continue working: stay in Step 6
 - If Pause: execute `p. pause`
 
 NEVER end a task without asking about shipping. This is non-negotiable.