prjct-cli 0.35.2 → 0.35.4

package/templates/commands/test.md

@@ -1,279 +1,50 @@
 ---
-allowed-tools: [Bash, Read, Write, Edit]
-description: 'Run tests and advance workflow phase'
-timestamp-rule: 'GetTimestamp() for ALL timestamps'
-architecture: 'Write-Through (JSON -> MD -> Events)'
-storage-layer: true
-source-of-truth: 'storage/state.json'
+allowed-tools: [Bash, Read, Write]
 ---
 
-# /p:test
-
-Run tests to advance from implement phase to test phase in the workflow.
-
-## Usage
+# p. test
 
+```bash
+prjct context test
 ```
-/p:test [all|unit|e2e|failed|fix]
-        [--blocking]           # Exit with error if tests fail
-```
-
-## Context Variables
-- `{projectId}`: From `.prjct/prjct.config.json`
-- `{globalPath}`: `~/.prjct-cli/projects/{projectId}`
-- `{configPath}`: `~/.prjct-cli/config.json`
-- `{statePath}`: `{globalPath}/storage/state.json`
-- `{memoryPath}`: `{globalPath}/memory/events.jsonl`
-- `{syncPath}`: `{globalPath}/sync/pending.json`
-
-## Step 1: Read Project Config
-
-READ: `.prjct/prjct.config.json`
-EXTRACT: `projectId`
-
-IF file not found:
-  OUTPUT: "No prjct project. Run /p:init first."
-  STOP
-
-## Step 1.5: Validate Workflow Phase
-
-READ: `{globalPath}/storage/state.json`
-
-IF currentTask is null:
-  OUTPUT: "No active task. Use p. task to start one."
-  STOP
-
-IF currentTask.workflow exists:
-  IF currentTask.workflow.phase != "implement":
-    OUTPUT:
-    ```
-    Cannot run tests. Current phase: {currentTask.workflow.phase}
-
-    Required phase: implement
-
-    Workflow: analyze → branch → implement → test → review → merge → ship → verify
-    ```
-    STOP
-
-## Step 2: Parse Arguments
-
-SET defaults:
-- {testMode} = "all"
-- {blocking} = false
-
-PARSE args:
-- IF arg is "all|unit|e2e|failed|fix": {testMode} = arg
-- IF arg contains "--blocking": {blocking} = true
-
-## Step 3: Detect Testing Strategy
-
-### Check for Native Test Runner
-
-READ: `package.json`
-IF has "scripts.test":
-  Detect package manager (package.json "packageManager" or lockfiles):
-  - pnpm-lock.yaml → pnpm
-  - yarn.lock → yarn
-  - bun.lock/bun.lockb → bun
-  - else → npm
-
-  {runner} = "{packageManager}"
-  {runnerCmd} = "{packageManager} test"
-  → Go to Step 4 (Native Testing)
-
-IF file exists: `pytest.ini` OR `pyproject.toml` with pytest:
-  {runner} = "pytest"
-  {runnerCmd} = "pytest"
-  → Go to Step 4
-
-IF file exists: `Cargo.toml`:
-  {runner} = "cargo"
-  {runnerCmd} = "cargo test"
-  → Go to Step 4
-
-IF file exists: `go.mod`:
-  {runner} = "go"
-  {runnerCmd} = "go test ./..."
-  → Go to Step 4
-
-IF file exists: `*.sln` OR `*.csproj`:
-  {runner} = "dotnet"
-  {runnerCmd} = "dotnet test"
-  → Go to Step 4
-
-IF no runner found:
-  OUTPUT: "No test runner detected."
-  OUTPUT: ""
-  OUTPUT: "Options:"
-  OUTPUT: "• Add 'test' script to package.json"
-  OUTPUT: "• Add pytest.ini for Python projects"
-  OUTPUT: "• Add Cargo.toml for Rust projects"
-  OUTPUT: "• Add go.mod for Go projects"
-  OUTPUT: "• Add a .sln/.csproj for .NET projects"
-  STOP
-
-## Step 4: Native Test Runner
-
-OUTPUT: "🧪 Running tests with {runner}..."
-
-BASH: `{runnerCmd} 2>&1`
-CAPTURE output as {testOutput}
-
-### Parse Results
 
-IF {testOutput} contains "passed" AND NOT contains "failed":
-  {testStatus} = "passed"
-  {passed} = extract number of passed tests
-  {failed} = 0
-ELSE IF {testOutput} contains "failed" OR contains "FAIL":
-  {testStatus} = "failed"
-  {passed} = extract passed count
-  {failed} = extract failed count
-ELSE:
-  {testStatus} = "unknown"
+Detect test runner from project files:
+- package.json with scripts.test → npm/pnpm/yarn/bun test
+- pytest.ini/pyproject.toml → pytest
+- Cargo.toml → cargo test
+- go.mod → go test ./...
+- *.sln/*.csproj → dotnet test
 
-### Handle Fix Mode
-IF {testMode} == "fix" AND {testStatus} == "failed":
-  OUTPUT: "🔧 Attempting auto-fix..."
-
-  IF {runner} == "npm" OR {runner} == "pnpm" OR {runner} == "yarn" OR {runner} == "bun":
-    # Reason: only JS test runners commonly support snapshot update flags.
-    BASH: `{runnerCmd} -- -u 2>&1`  # Update snapshots (best effort)
-
-  OUTPUT: "Snapshots updated. Re-running tests..."
-  BASH: `{runnerCmd} 2>&1`
-  CAPTURE and re-parse results
-
-→ Go to Step 5 (Results)
-
-## Step 5: Results & Response
-
-### Log to Memory
-
-SET: {now} = GetTimestamp()
-
-APPEND to `{memoryPath}`:
-```json
-{"ts":"{now}","type":"test_run","tool":"{runner}","passed":{passed},"failed":{failed},"mode":"{testMode}"}
-```
-
-### Check Blocking Mode
-
-IF {blocking} AND {failed} > 0:
-  OUTPUT: "❌ {failed} tests failed. Blocking."
-  OUTPUT: ""
-  OUTPUT: "Fix failing tests or run without --blocking flag."
-  EXIT with error (non-zero)
-
-### Success Response
-
-IF {testStatus} == "passed":
-  ### Update Workflow Phase (if workflow exists)
-  IF currentTask.workflow exists:
-    SET: {now} = GetTimestamp()
-
-    SET: currentTask.workflow.phase = "test"
-    SET: currentTask.workflow.checkpoints.implement = {
-      "completedAt": "{now}",
-      "data": { "filesChanged": {count}, "commits": {count} }
-    }
-    SET: currentTask.workflow.checkpoints.test = {
-      "completedAt": "{now}",
-      "data": { "passed": {passed}, "coverage": "{coverage}" }
-    }
-    SET: currentTask.workflow.lastCheckpoint = "test"
-
-    WRITE: `{statePath}`
-
-    ### Log workflow events
-    APPEND to `{memoryPath}`:
-    ```json
-    {"timestamp":"{now}","action":"phase_advanced","taskId":"{currentTask.id}","from":"implement","to":"test"}
-    {"timestamp":"{now}","action":"checkpoint_completed","taskId":"{currentTask.id}","checkpoint":"implement"}
-    {"timestamp":"{now}","action":"checkpoint_completed","taskId":"{currentTask.id}","checkpoint":"test"}
-    ```
-
-    ### Queue sync event
-    APPEND to `{syncPath}`:
-    ```json
-    {"type":"workflow.phase_advanced","data":{"taskId":"{currentTask.id}","from":"implement","to":"test"},"timestamp":"{now}"}
-    ```
-
-  OUTPUT: "✅ All tests passing!"
-  OUTPUT: ""
-  OUTPUT: "📊 Results:"
-  OUTPUT: "• Passed: {passed}"
-  IF {coverage}:
-    OUTPUT: "• Coverage: {coverage}%"
-
-  IF currentTask.workflow exists:
-    OUTPUT: ""
-    OUTPUT: "Phase: test (4/11 checkpoints)"
-    OUTPUT: ""
-    OUTPUT: "Workflow:"
-    OUTPUT: "1. analyze ✓"
-    OUTPUT: "2. branch ✓"
-    OUTPUT: "3. implement ✓"
-    OUTPUT: "4. test ✓"
-    OUTPUT: "5. review ← next"
-    OUTPUT: ""
-    OUTPUT: "🎯 Next: p. review"
-  ELSE:
-    OUTPUT: ""
-    OUTPUT: "🎯 Next: /p:ship"
-
-### Failure Response
-
-IF {testStatus} == "failed":
-  OUTPUT: "❌ {failed} tests failing"
-  OUTPUT: ""
-  OUTPUT: "{testOutput}"  # Show relevant failure output
-  OUTPUT: ""
-  OUTPUT: "💡 Auto-fix: /p:test fix"
-  OUTPUT: ""
-  OUTPUT: "📊 Summary: {passed}/{passed + failed} passed"
-
-## Error Handling
-
-| Error | Response | Action |
-|-------|----------|--------|
-| No project | "No prjct project" | STOP |
-| No test runner | "No test runner detected" | Show setup options |
-| Tests timeout | "Tests timed out" | Suggest increasing timeout |
-
-## Examples
-
-### Example 1: Native Tests Pass
+Run tests:
+```bash
+{runnerCmd} 2>&1
 ```
-🧪 Running tests with npm...
 
-✅ All tests passing!
+Parse results: passed/failed count
 
-📊 Results:
-• Passed: 42
-• Coverage: 87%
+IF failed AND mode == "fix":
+  Try `{runnerCmd} -- -u` (update snapshots)
+  Re-run tests
 
-🎯 Next: /p:ship
+**Output (pass)**:
 ```
+✅ Tests passing
 
-### Example 2: Tests with Failures
-```
-🧪 Running tests with npm...
-
-❌ 3 tests failing
-
-[test output here]
-
-💡 Auto-fix: /p:test fix
+Passed: {count}
+Coverage: {%}
 
-📊 Summary: 39/42 passed
+Next:
+- Code review → `p. review`
+- Ship → `p. ship`
 ```
 
-### Example 3: Blocking Mode
+**Output (fail)**:
 ```
-🧪 Running tests with npm...
+❌ {failed} tests failing
 
-❌ 2 tests failed. Blocking.
+{test output}
 
-Fix failing tests or run without --blocking flag.
+Next:
+- Auto-fix → `p. test fix`
+- Fix manually and re-run
 ```

package/CLAUDE.md

@@ -1,211 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code when working with prjct-cli.
-
-## Project Overview
-
-**prjct-cli** is a developer momentum tool. Track progress through natural language commands (`p. <command>`) without meetings or traditional PM overhead.
-
-## HOW PRJCT WORKS
-
-When user types `p. <command>`, load the template from `templates/commands/{command}.md` and execute it **intelligently** - templates are GUIDANCE, not rigid scripts.
-
-```
-p. sync     → Analyze project, generate domain agents
-p. task X   → Start task with classification + breakdown
-p. done     → Complete current subtask
-p. ship X   → Ship feature with PR + version bump
-```
-
----
-
-## CRITICAL RULES
-
-### 1. Path Resolution (MOST IMPORTANT)
-**ALL writes go to global storage**: `~/.prjct-cli/projects/{projectId}/`
-- **NEVER** write to `.prjct/` (config only, read-only)
-- **NEVER** write to `./` (current directory)
-
-### 2. Before Any Command
-```
-1. Read .prjct/prjct.config.json → get projectId
-2. Set globalPath = ~/.prjct-cli/projects/{projectId}
-3. Execute using globalPath for all writes
-4. Log to {globalPath}/memory/events.jsonl
-```
-
-### 3. Timestamps & UUIDs
-```bash
-# Timestamp (NEVER hardcode)
-bun -e "console.log(new Date().toISOString())" 2>/dev/null || node -e "console.log(new Date().toISOString())"
-
-# UUID
-bun -e "console.log(crypto.randomUUID())" 2>/dev/null || node -e "console.log(require('crypto').randomUUID())"
-```
-
-### 4. Git Commit Footer (CRITICAL - ALWAYS INCLUDE)
-
-**Every commit MUST include the prjct signature:**
-
-```
-🤖 Generated with [p/](https://www.prjct.app/)
-Designed for [Claude](https://www.anthropic.com/claude)
-
-```
-
-**NON-NEGOTIABLE: The `🤖 Generated with [p/]` line identifies prjct-powered commits.**
-
----
-
-## ARCHITECTURE: Write-Through Pattern
-
-```
-User Action → Storage (JSON) → Context (MD) → Sync Events
-```
-
-| Layer | Path | Purpose |
-|-------|------|---------|
-| **Storage** | `storage/*.json` | Source of truth |
-| **Context** | `context/*.md` | Claude-readable summaries |
-| **Memory** | `memory/events.jsonl` | Audit trail (append-only) |
-| **Agents** | `agents/*.md` | Domain specialists |
-
-### File Structure
-```
-~/.prjct-cli/projects/{projectId}/
-├── storage/
-│   ├── state.json      # Current task (SOURCE OF TRUTH)
-│   ├── queue.json      # Task queue
-│   └── shipped.json    # Shipped features
-├── context/
-│   ├── now.md          # Current task (generated)
-│   └── next.md         # Queue (generated)
-├── memory/
-│   └── events.jsonl    # Audit trail
-├── agents/             # Domain specialists
-└── sync/
-    └── pending.json    # Backend events
-```
-
----
-
-## COMMANDS
-
-### Core Workflow
-| Trigger | Purpose |
-|---------|---------|
-| `p. init` | Initialize project with deep analysis |
-| `p. sync` | Analyze repo, generate agents |
-| `p. task <desc>` | Start task with agentic classification |
-| `p. done` | Complete current subtask |
-| `p. ship [name]` | Ship with PR + version bump |
-| `p. pause` | Pause active task |
-| `p. resume` | Resume paused task |
-| `p. bug <desc>` | Report bug with auto-priority |
-
-### Issue Tracker Integrations
-| Trigger | Purpose |
-|---------|---------|
-| `p. linear` | Linear issues (OAuth via MCP) |
-| `p. jira` | JIRA issues (OAuth/SSO via MCP) |
-| `p. github` | GitHub Issues (token via MCP) |
-| `p. monday` | Monday.com boards (OAuth via MCP) |
-| `p. enrich <ID>` | **AI-powered ticket enrichment** |
-
-### Ticket Enrichment (`p. enrich`)
-
-Transform vague PM tickets into technical PRDs:
-
-```
-PM creates: "Add user auth"
-            ↓
-p. enrich PRJ-59
-            ↓
-Architect analyzes codebase:
-- Similar implementations found
-- 5 files affected
-- OAuth2 approach recommended
-- 8 story points (not PM's guess of 2)
-            ↓
-Publishes PRD to tracker:
-- Technical approach
-- Acceptance criteria
-- LLM-ready prompt (for any AI tool)
-```
-
-**Subcommands:**
-- `p. enrich <ID>` - Enrich specific ticket
-- `p. enrich setup` - Configure team preferences (estimation, output)
-- `p. enrich batch` - Enrich all assigned tickets (backlog grooming)
-
-### Workflow
-```
-p. sync → p. task "description" → [work] → p. done → p. ship
-```
-
-### With Issue Tracker
-```
-p. linear → p. enrich PRJ-59 → p. linear start PRJ-59 → [work] → p. done → p. ship
-```
-
----
-
-## INTELLIGENT BEHAVIOR
-
-Templates provide guidance. Use your intelligence to:
-
-1. **Read before write** - Always read existing files first
-2. **Explore before coding** - Use Task(Explore) to understand codebase
-3. **Ask when uncertain** - Use AskUserQuestion to clarify
-4. **Load agents** - Read from `{globalPath}/agents/` for domain expertise
-5. **Adapt templates** - They're guidance, not rigid scripts
-6. **Log everything** - Append to memory/events.jsonl
-
----
-
-## OUTPUT FORMAT
-
-Concise responses (< 4 lines):
-```
-✅ [What was done]
-
-[Key metrics]
-Next: [suggested action]
-```
-
----
-
-## KEY RULES
-
-1. **Read files before editing** - Never assume structure
-2. **Use node/bun for timestamps** - Never hardcode dates
-3. **Follow template guidance** - But adapt intelligently
-4. **Log to memory** - Append to `memory/events.jsonl`
-5. **Suggest next actions** - Maintain user momentum
-6. **Use linked skills** - Agents have skills in frontmatter
-
----
-
-## SKILL INTEGRATION (v0.27)
-
-Agents are linked to Claude Code skills from claude-plugins.dev.
-
-### Agent → Skill Mapping
-
-| Agent | Skill |
-|-------|-------|
-| `frontend.md` | `frontend-design` |
-| `uxui.md` | `frontend-design` |
-| `backend.md` | `javascript-typescript` |
-| `testing.md` | `developer-kit` |
-| `devops.md` | `developer-kit` |
-| `prjct-planner.md` | `feature-dev` |
-| `prjct-shipper.md` | `code-review` |
-
-### Usage
-
-- `p. sync` installs required skills automatically
-- `p. task` invokes skills based on task type
-- Skills config: `{globalPath}/config/skills.json`
-
-See `templates/agentic/skill-integration.md` for details.

package/packages/shared/node_modules/@types/bun/LICENSE

@@ -1,21 +0,0 @@
-    MIT License
-
-    Copyright (c) Microsoft Corporation.
-
-    Permission is hereby granted, free of charge, to any person obtaining a copy
-    of this software and associated documentation files (the "Software"), to deal
-    in the Software without restriction, including without limitation the rights
-    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-    copies of the Software, and to permit persons to whom the Software is
-    furnished to do so, subject to the following conditions:
-
-    The above copyright notice and this permission notice shall be included in all
-    copies or substantial portions of the Software.
-
-    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-    SOFTWARE

package/packages/shared/node_modules/@types/bun/README.md

@@ -1,20 +0,0 @@
-# Installation
-> `npm install --save @types/bun`
-
-# Summary
-This package contains type definitions for bun (https://bun.com).
-
-# Details
-Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/bun.
-## [index.d.ts](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/bun/index.d.ts)
-````ts
-/// <reference types="bun-types" />
-
-````
-
-### Additional Details
- * Last updated: Thu, 18 Dec 2025 18:43:14 GMT
- * Dependencies: [bun-types](https://npmjs.com/package/bun-types)
-
-# Credits
-These definitions were written by [Jarred Sumner](https://github.com/Jarred-Sumner), [Robobun](https://github.com/robobun), [Dylan Conway](https://github.com/dylan-conway), [Meghan Denny](https://github.com/nektro), [Michael H](https://github.com/RiskyMH), and [Alistair Smith](https://github.com/alii).

package/packages/shared/node_modules/@types/bun/index.d.ts

@@ -1 +0,0 @@
-/// <reference types="bun-types" />

package/packages/shared/node_modules/@types/bun/node_modules/bun-types/CLAUDE.md

@@ -1,105 +0,0 @@
-Default to using Bun instead of Node.js.
-
-- Use `bun <file>` instead of `node <file>` or `ts-node <file>`
-- Use `bun test` instead of `jest` or `vitest`
-- Use `bun build <file.html|file.ts|file.css>` instead of `webpack` or `esbuild`
-- Use `bun install` instead of `npm install` or `yarn install` or `pnpm install`
-- Use `bun run <script>` instead of `npm run <script>` or `yarn run <script>` or `pnpm run <script>`
-- Use `bunx <package> <command>` instead of `npx <package> <command>`
-- Bun automatically loads .env, so don't use dotenv.
-
-## APIs
-
-- `Bun.serve()` supports WebSockets, HTTPS, and routes. Don't use `express`.
-- `bun:sqlite` for SQLite. Don't use `better-sqlite3`.
-- `Bun.redis` for Redis. Don't use `ioredis`.
-- `Bun.sql` for Postgres. Don't use `pg` or `postgres.js`.
-- `WebSocket` is built-in. Don't use `ws`.
-- Prefer `Bun.file` over `node:fs`'s readFile/writeFile
-- Bun.$`ls` instead of execa.
-
-## Testing
-
-Use `bun test` to run tests.
-
-```ts#index.test.ts
-import { test, expect } from "bun:test";
-
-test("hello world", () => {
-  expect(1).toBe(1);
-});
-```
-
-## Frontend
-
-Use HTML imports with `Bun.serve()`. Don't use `vite`. HTML imports fully support React, CSS, Tailwind.
-
-Server:
-
-```ts#index.ts
-import index from "./index.html"
-
-Bun.serve({
-  routes: {
-    "/": index,
-    "/api/users/:id": {
-      GET: (req) => {
-        return new Response(JSON.stringify({ id: req.params.id }));
-      },
-    },
-  },
-  // optional websocket support
-  websocket: {
-    open: (ws) => {
-      ws.send("Hello, world!");
-    },
-    message: (ws, message) => {
-      ws.send(message);
-    },
-    close: (ws) => {
-      // handle close
-    }
-  },
-  development: {
-    hmr: true,
-    console: true,
-  }
-})
-```
-
-HTML files can import .tsx, .jsx or .js files directly and Bun's bundler will transpile & bundle automatically. `<link>` tags can point to stylesheets and Bun's CSS bundler will bundle.
-
-```html#index.html
-<html>
-  <body>
-    <h1>Hello, world!</h1>
-    <script type="module" src="./frontend.tsx"></script>
-  </body>
-</html>
-```
-
-With the following `frontend.tsx`:
-
-```tsx#frontend.tsx
-import React from "react";
-import { createRoot } from "react-dom/client";
-
-// import .css files directly and it works
-import './index.css';
-
-const root = createRoot(document.body);
-
-export default function Frontend() {
-  return <h1>Hello, world!</h1>;
-}
-
-root.render(<Frontend />);
-```
-
-Then, run index.ts
-
-```sh
-bun --hot ./index.ts
-```
-
-For more information, read the Bun API docs in `docs/**.mdx`.

package/packages/shared/node_modules/@types/bun/node_modules/bun-types/README.md

@@ -1,33 +0,0 @@
-# TypeScript types for Bun
-
-<p align="center">
-  <a href="https://bun.com"><img src="https://bun.com/logo@2x.png" alt="Logo"></a>
-</p>
-
-These are the type definitions for Bun's JavaScript runtime APIs.
-
-# Installation
-
-Install the `@types/bun` npm package:
-
-```bash
-# yarn/npm/pnpm work too
-# @types/bun is an ordinary npm package
-bun add -D @types/bun
-```
-
-That's it! VS Code and TypeScript automatically load `@types/*` packages into your project, so the `Bun` global and all `bun:*` modules should be available immediately.
-
-# Contributing
-
-The `@types/bun` package is a shim that loads `bun-types`. The `bun-types` package lives in the Bun repo under `packages/bun-types`.
-
-To add a new file, add it under `packages/bun-types`. Then add a [triple-slash directive](https://www.typescriptlang.org/docs/handbook/triple-slash-directives.html) pointing to it inside [./index.d.ts](./index.d.ts).
-
-```diff
-+ /// <reference path="./newfile.d.ts" />
-```
-
-```bash
-bun build
-```