pure-point-guard 0.2.0 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pure-point-guard",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "type": "module",
   "description": "Pure Point Guard — local orchestration runtime for parallel CLI coding agents",
   "bin": {
@@ -46,6 +46,7 @@
   "license": "MIT",
   "dependencies": {
     "commander": "^14.0.0",
+    "cron-parser": "^5.5.0",
     "execa": "^9.5.2",
     "nanoid": "^5.1.5",
     "proper-lockfile": "^4.1.2",
@@ -55,8 +56,8 @@
   "devDependencies": {
     "@types/node": "^22.13.4",
     "@types/proper-lockfile": "^4.1.4",
-    "tsx": "^4.19.3",
     "tsup": "^8.4.0",
+    "tsx": "^4.19.3",
     "typescript": "^5.7.3",
     "vitest": "^3.0.6"
   },

package/skills/ppg/SKILL.md

@@ -8,6 +8,6 @@ user-invocable: true
 
 Read and follow the conductor hub instructions in `~/.claude/skills/ppg-conductor/SKILL.md`.
 
-Run pre-flight checks. Classify the user's request as swarm or batch mode. Decompose into concrete tasks with descriptive names and self-contained prompts. Spawn immediately — do not ask for confirmation. Drive the full conductor loop: spawn, poll, aggregate, (merge if batch), summarize.
+Run pre-flight checks. Classify the user's request as swarm or batch mode. Decompose into concrete tasks with descriptive names and self-contained prompts. Spawn immediately — do not ask for confirmation. Drive the full conductor loop: spawn, poll, aggregate, (agents create PRs), summarize.
 
 If the user provides no arguments (just `/ppg`), ask what they'd like to parallelize.

package/skills/ppg-conductor/SKILL.md

@@ -46,8 +46,9 @@ After classifying the mode:
 - **Always use `--no-open`** to suppress Terminal.app windows (you're driving programmatically, not watching panes)
 - **Poll every 5 seconds** — `ppg status --json` in a loop until all agents reach a terminal state
 - **One concern per worktree** — in batch mode, each task gets its own isolated worktree for clean merges
-- **Surface results and let the user decide next steps** — present what agents produced, then ask: create PRs, merge directly, review diffs, or do nothing
-- **Never auto-merge or auto-PR** — always stop after presenting results and wait for the user to choose
+- **Agents create PRs** — agents handle the full lifecycle (commit, push, PR creation). Conductor reads PR URLs from result files and presents them.
+- **Surface PR links and let the user decide next steps** — present PR URLs and summaries from agent results, then ask what to do next
+- **Prefer `gh pr merge` over `ppg merge`** — for integration, prefer remote merge via `gh pr merge <url> --squash --delete-branch`. `ppg merge` is a power-user tool for local squash merge.
 - **Report failures clearly** — if an agent fails, show its ID, the error, and offer to re-spawn or skip
 - **Never auto-resolve merge conflicts** — escalate to the user with the conflict details
 - **Prompt quality matters** — each agent prompt must be self-contained with full context. The agent has no memory of this conversation.

package/skills/ppg-conductor/references/commands.md

@@ -4,7 +4,7 @@ Quick reference for all ppg commands relevant to conductor workflows. Always use
 
 ## ppg init
 
-Initialize ppg in the current git repository. Creates `.pg/` directory structure, default config, empty manifest, and sample template.
+Initialize ppg in the current git repository. Creates `.ppg/` directory structure, default config, empty manifest, and sample template.
 
 ```bash
 ppg init --json
@@ -12,7 +12,7 @@ ppg init --json
 
 **JSON output:**
 ```json
-{ "success": true, "projectRoot": "/path/to/repo", "sessionName": "ppg-repo", "pgDir": "/path/to/repo/.pg" }
+{ "success": true, "projectRoot": "/path/to/repo", "sessionName": "ppg-repo", "ppgDir": "/path/to/repo/.pg" }
 ```
 
 **Errors:** `NOT_GIT_REPO`, `TMUX_NOT_FOUND`
@@ -49,7 +49,7 @@ ppg spawn --name <name> --prompt-file /path/to/prompt.md --json --no-open
 | `-a, --agent <type>` | Agent type from config (default: `claude`) |
 | `-p, --prompt <text>` | Inline prompt text |
 | `-f, --prompt-file <path>` | Path to file containing prompt |
-| `-t, --template <name>` | Template name from `.pg/templates/` |
+| `-t, --template <name>` | Template name from `.ppg/templates/` |
 | `--var <KEY=value>` | Template variable (repeatable) |
 | `-b, --base <branch>` | Base branch (default: current branch) |
 | `-w, --worktree <id>` | Add agent to existing worktree instead of creating new one |
@@ -109,7 +109,7 @@ ppg status --watch                   # Live-refresh in terminal
           "status": "running",
           "tmuxTarget": "ppg-repo:1",
           "prompt": "...",
-          "resultFile": "/path/.pg/results/ag-xyz12345.md",
+          "resultFile": "/path/.ppg/results/ag-xyz12345.md",
           "startedAt": "2025-01-01T00:00:00.000Z"
         }
       },
@@ -166,7 +166,7 @@ ppg aggregate <worktree-id> --json      # Specific worktree
 }
 ```
 
-Results come from `.pg/results/<agentId>.md`. If no result file exists, falls back to tmux pane capture.
+Results come from `.ppg/results/<agentId>.md`. If no result file exists, falls back to tmux pane capture.
 
 ## ppg pr
 
@@ -269,7 +269,7 @@ Cleanup sequence: kill tmux window, teardown env, `git worktree remove --force`,
 
 ## ppg swarm
 
-Run a predefined swarm template — spawns multiple agents from `.pg/swarms/` with prompts from `.pg/prompts/`.
+Run a predefined swarm template — spawns multiple agents from `.ppg/swarms/` with prompts from `.ppg/prompts/`.
 
 ```bash
 # Run a swarm template (creates new worktree, spawns all agents)
@@ -487,7 +487,7 @@ ppg attach <agent-id>                   # Attach to agent's tmux pane
 |------|---------|----------|
 | `TMUX_NOT_FOUND` | tmux not installed | Fatal — user must install tmux |
 | `NOT_GIT_REPO` | Not inside a git repository | Fatal — user must cd to a repo |
-| `NOT_INITIALIZED` | `.pg/` directory missing | Auto-fix: run `ppg init --json` |
+| `NOT_INITIALIZED` | `.ppg/` directory missing | Auto-fix: run `ppg init --json` |
 | `MANIFEST_LOCK` | Could not acquire manifest lock | Retry after brief delay (rare) |
 | `WORKTREE_NOT_FOUND` | Worktree ID/name not in manifest | Check `ppg status --json` for valid IDs |
 | `AGENT_NOT_FOUND` | Agent ID not in manifest | Check `ppg status --json` for valid IDs |

package/skills/ppg-conductor/references/conductor.md

@@ -21,7 +21,7 @@ ppg spawn --name "<name>" --prompt "<self-contained prompt>" --json --no-open
 
 **Store a tracking table** with: worktree ID, agent IDs, name, and branch for each spawned task.
 
-**Swarm templates** — If a matching swarm template exists in `.pg/swarms/`, prefer `ppg swarm` over manual multi-spawn:
+**Swarm templates** — If a matching swarm template exists in `.ppg/swarms/`, prefer `ppg swarm` over manual multi-spawn:
 ```bash
 # Use a predefined swarm template (much simpler than manual spawning)
 ppg swarm code-review --var CONTEXT="Review the auth module" --json --no-open
@@ -140,29 +140,29 @@ Returns:
 
 **For batch mode:**
 
-Present a results table:
+Present a results table with PR links:
 ```
 Completed:
-  [1] fix-auth-bug (wt-abc123) — ppg/fix-auth-bug
-  [2] add-dark-mode (wt-def456) — ppg/add-dark-mode
+  [1] fix-auth-bug (wt-abc123) — PR: https://github.com/org/repo/pull/42
+  [2] add-dark-mode (wt-def456) — PR: https://github.com/org/repo/pull/43
 
 Failed:
-  [3] issue-15 (wt-ghi789) — ppg/issue-15
+  [3] issue-15 (wt-ghi789) — no PR created
 
 What would you like to do?
-  - Create PRs: "pr 1,2" or "pr all"
-  - Merge directly: "merge 1,2" or "merge all"
-  - Review diffs first: "diff 1"
+  - Review PRs on GitHub
+  - Merge remotely: "gh pr merge <url> --squash --delete-branch"
+  - Merge locally (power-user): "ppg merge <wt-id>"
+  - Iterate: send more prompts to agents
   - Do nothing for now
 ```
 
-**When the user chooses PRs:**
+**When the user chooses remote merge:**
 ```bash
-ppg pr <wt-id> --json
+gh pr merge <url> --squash --delete-branch
 ```
-This pushes the branch and creates a GitHub PR. The worktree stays alive for the PR lifecycle.
 
-**When the user chooses direct merge:**
+**When the user chooses local merge (power-user):**
 ```bash
 ppg merge <wt-id> --json
 ```
@@ -173,10 +173,10 @@ ppg merge <wt-id> --json
 - Offer options: "resolve manually", "skip this merge", "force merge"
 - **Never auto-resolve conflicts** — the user must decide
 
-**Cleanup after PRs are merged externally:**
+**Cleanup:**
 ```bash
-ppg reset --json        # Refuses if unmerged work exists
-ppg reset --force --json  # Force cleanup
+ppg reset --json        # Skips worktrees with open PRs
+ppg reset --force --json  # Force cleanup including open PRs
 ppg clean --json        # Clean only terminal-state worktrees
 ```
 

package/skills/ppg-conductor/references/modes.md

@@ -81,12 +81,13 @@ Each command creates a separate worktree on its own `ppg/<name>` branch.
 **Post-completion:**
 1. Aggregate results: `ppg aggregate --all --json`
 2. Present a summary table: task name, status, branch, key findings
-3. **Stop and ask the user what to do next.** Options:
-   - Create PRs: `ppg pr <wt-id> --json` (pushes branch, creates GitHub PR)
-   - Merge directly: `ppg merge <wt-id> --json` (squash by default)
-   - Review diffs first: `ppg diff <wt-id> --json`
+3. **Stop and ask the user what to do next.** Agents already created PRs. Options:
+   - Review PRs on GitHub (present the PR URLs from result files)
+   - Merge remotely: `gh pr merge <url> --squash --delete-branch`
+   - Merge locally (power-user): `ppg merge <wt-id> --json`
+   - Iterate: send more prompts to agents
    - Do nothing — leave worktrees for manual review
-4. After PRs are merged externally: `ppg reset --json` to clean up
+4. After PRs are merged: `ppg reset --json` to clean up (skips worktrees with open PRs)
 
 **Important:** Never auto-merge or auto-PR. Always present results and let the user choose the next step.