prjct-cli 1.23.0 → 1.24.1

package/CHANGELOG.md

@@ -1,5 +1,113 @@
 # Changelog
 
+## [1.24.1] - 2026-02-11
+
+### Bug Fixes
+
+- strip shebangs in build via esbuild plugin (#171)
+
+
+## [1.24.2] - 2026-02-10
+
+### Bug Fixes
+
+- **Strip shebangs in build via esbuild plugin**: Added a `stripShebangPlugin` to the build script that removes shebangs from source files before bundling. This prevents double-shebang SyntaxErrors when source files (e.g. `#!/usr/bin/env bun`) are compiled with a banner that also injects a shebang. The previous fix (v1.24.1) removed shebangs manually from known files; this fix handles it generically for all future source files.
+
+### Test Plan
+
+#### For QA
+1. Add `#!/usr/bin/env bun` to any source `.ts` file used as an entry point
+2. Run `node scripts/build.js`
+3. Verify compiled output has exactly one shebang (`#!/usr/bin/env node`) — not two
+4. Run `node dist/cli/linear.mjs --help` — should work without SyntaxError
+
+#### For Users
+**What changed:** Build-time fix — no user action needed.
+**Breaking changes:** None
+
+## [1.24.0] - 2026-02-11
+
+### Features
+
+- implement daemon mode with IPC socket for near-zero startup (PRJ-302) (#170)
+
+### Bug Fixes
+
+- remove source shebang causing SyntaxError in compiled linear CLI (#169)
+
+## [1.24.1] - 2026-02-10
+
+### Bug Fixes
+
+- **Remove source shebangs from compiled entry points**: `core/daemon/entry.ts` and `core/cli/lint-meta-commentary.ts` had shebangs (`#!/usr/bin/env node`, `#!/usr/bin/env bun`) that caused dual shebangs in compiled `.mjs` output. Node.js only strips the first-line shebang, so the second became a SyntaxError. The build script's `banner` option is the single source of truth for shebang injection.
+
+## [1.24.0] - 2026-02-10
+
+### Features
+
+- **Daemon mode with IPC socket**: Background daemon process keeps CLI modules warm in memory. Commands are routed through a Unix domain socket using NDJSON protocol, achieving 1.6ms IPC roundtrip. Production startup drops from ~1060ms to ~220ms (4.8x speedup).
+- **Thin shim entry point**: Production build now uses a 1.6KB shim (`prjct.mjs`) that tries the daemon first, only loading the full 613KB core bundle (`prjct-core.mjs`) when the daemon is unavailable.
+- **Auto-start daemon**: First CLI invocation automatically spawns the daemon in background for future commands. 30-minute idle auto-shutdown.
+- **Daemon lifecycle commands**: `prjct daemon start|stop|status` for manual control. Supports `--foreground`, `--port=N`, `--no-http` flags.
+
+### Security
+
+- **Removed source maps from production build**: `.map` files previously embedded full `sourcesContent` including credential management code (`keychain.ts`, `project-credentials.ts`). Source maps are now completely removed from `dist/`.
+
+### Implementation Details
+
+Daemon mode with Unix socket IPC for near-zero CLI startup. The daemon pre-loads `PrjctCommands`, `CommandRegistry`, and storage caches once, then reuses them across invocations. The thin shim entry point avoids parsing the heavy core bundle when the daemon handles the command. ESM static imports are hoisted before any code runs, so all imports in `bin/prjct.ts` are now dynamic to enable the fast path.
+
+### Learnings
+
+- ESM hoists static imports — placing code before `import` statements doesn't help; all imports must be dynamic for a true fast path
+- esbuild code splitting creates ~60 chunk files, not suitable for CLI distribution; explicit two-file shim is cleaner
+- `process.stdin.unref()` doesn't exist in Bun — needs try/catch guard
+- Unix domain sockets with NDJSON are ideal for local IPC: secure (file permissions), fast, debuggable
+
+### Test Plan
+
+#### For QA
+1. `prjct daemon start` — verify socket at `~/.prjct-cli/run/daemon.sock`
+2. `prjct daemon status` — shows PID, uptime, commands served
+3. `prjct sync --json --yes` — works via IPC with valid JSON output
+4. `prjct daemon stop` — clean shutdown, socket removed
+5. Run any command without daemon — falls back to direct execution
+6. Verify `dist/` contains NO `.map` files or `sourcesContent`
+
+#### For Users
+**What changed:** CLI commands are now routed through a background daemon for faster execution.
+**How to use:** Automatic — daemon starts on first use, stops after 30min idle. Use `PRJCT_NO_DAEMON=1` to disable.
+**Breaking changes:** None.
+
+## [1.23.1] - 2026-02-10
+
+### Bug Fix
+
+- **Fix dual shebang in compiled linear CLI**: Removed `#!/usr/bin/env bun` from `core/cli/linear.ts` source file. The build script (esbuild) already injects `#!/usr/bin/env node` via banner, so the source shebang was duplicated in `dist/cli/linear.mjs` — causing `SyntaxError: Invalid or unexpected token` on Node.js for all `prjct linear` commands.
+
+### Root Cause
+
+The source file `core/cli/linear.ts` had `#!/usr/bin/env bun` on line 1. esbuild preserved it during compilation, and the build banner injected `#!/usr/bin/env node` — resulting in two shebangs. Node.js only strips line 1's shebang, so line 2 (`#!/usr/bin/env bun`) was parsed as JavaScript and threw a SyntaxError.
+
+### Learnings
+
+- Source files compiled by esbuild should NOT have shebangs — the build script's `banner` option is the single source of truth for shebang injection
+- Only the first line shebang is stripped by Node.js; any subsequent shebang lines cause parse errors
+
+### Test Plan
+
+#### For QA
+1. `head -1 dist/cli/linear.mjs` — single `#!/usr/bin/env node` shebang
+2. `node dist/cli/linear.mjs --help` — no SyntaxError
+3. `prjct linear list` — works end-to-end
+4. `grep -c '#!/' dist/cli/linear.mjs` — returns `1`
+
+#### For Users
+**What changed:** Fixed `prjct linear` commands failing with SyntaxError after v1.23.0.
+**How to use:** Update to v1.23.1 — no action needed.
+**Breaking changes:** None.
+
 ## [1.23.0] - 2026-02-11
 
 ### Features
@@ -11,7 +119,6 @@
 
 - consolidate core modules from 27 to 20 directories (PRJ-292) (#167)
 
-
 ## [1.25.0] - 2026-02-10
 
 ### Infrastructure