prjct-cli 2.46.1 → 2.49.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.46.1",
3
+ "version": "2.49.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": {
@@ -71,7 +71,7 @@
71
71
  "@types/bun": "latest",
72
72
  "@types/chokidar": "2.1.7",
73
73
  "@types/node": "^22",
74
- "esbuild": "0.25.0",
74
+ "esbuild": "0.28.1",
75
75
  "knip": "6.3.1",
76
76
  "lefthook": "2.1.0",
77
77
  "typescript": "5.9.3"
@@ -88,6 +88,7 @@ On every turn ask: "what is the user trying to accomplish?" and match to a verb
88
88
  | "what did we accomplish?" | `prjct retro 7d --md` | 1 |
89
89
  | pause / resume the working context | `prjct context-save` / `prjct context-restore --md` | 1 |
90
90
  | reduce over-engineering — "make it leaner" / YAGNI review / cut complexity | `prjct lean review` (or `audit` / `debt`) | 1 |
91
+ | sync this project across machines / "share with my other machine" / "is cloud on?" | `prjct cloud link` (then `status` / `sync` / `pull` / `pause`) | 2 |
91
92
 
92
93
  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`).
93
94