@pennyfarthing/core 11.0.0 → 11.1.1

package/pennyfarthing-dist/commands/pf-parallel-work.md

@@ -1,71 +1,11 @@
 ---
-description: Start parallel work in a new worktree
+deprecated: true
+redirect: removed
+description: "DEPRECATED: Parallel worktrees replaced by sister directories."
 ---
 
-```bash
-pf agent start "sm"
-```
+# /parallel-work - REMOVED
 
-<parallel-work-flow>
-## Parallel Work Setup
+Parallel worktree sessions have been replaced by sister directories.
 
-Start a new story in a worktree while keeping main checkout intact.
-
-### Step 1: Create Worktree
-
-```bash
-# Get story info from user
-read -p "Story ID (e.g., 5-3a): " STORY_ID
-read -p "Branch name (e.g., feat/5-3a-feature): " BRANCH_NAME
-
-# Create worktree
-WORKTREE_NAME="wt-${STORY_ID}"
-.pennyfarthing/scripts/git/worktree-manager.sh create "$WORKTREE_NAME" "$BRANCH_NAME"
-
-# Get port configuration
-eval $(.pennyfarthing/scripts/git/worktree-manager.sh ports "$WORKTREE_NAME")
-```
-
-### Step 2: Create Session File
-
-Create `.session/${STORY_ID}-session.md` with:
-
-```markdown
-# Story ${STORY_ID}: [Title]
-
-## Worktree Context
-worktree: ${WORKTREE_NAME}
-path: ${WORKTREE_PATH}
-api_port: ${API_PORT}
-ui_port: ${UI_PORT}
-
-## Story Info
-- **Epic:** [from sprint]
-- **Points:** [from sprint]
-- **Repos:** Both
-
-## Phase
-sm
-
-## Status
-setup
-
-## Acceptance Criteria
-- [ ] AC1
-- [ ] AC2
-```
-
-### Step 3: Hand to SM
-
-Invoke SM to complete story setup in the worktree context.
-</parallel-work-flow>
-
-<agent-activation>
-1. Load persona from theme config → `agents.sm`
-2. Load and follow `.pennyfarthing/agents/sm.md`
-3. SM will detect worktree session and work in that context
-</agent-activation>
-
-<agent-exit>
-On exit: Capture learnings to sidecar.
-</agent-exit>
+Instead of worktrees, use sister project directories for parallel work.

package/pennyfarthing-dist/commands/pf-release.md

@@ -1,81 +1,16 @@
 ---
-description: Interactive stepped release with verification gates
+deprecated: true
+redirect: pf-git
+description: "DEPRECATED: Use /pf-git release instead."
 ---
 
-<purpose>
-Release a new version of Pennyfarthing using an interactive stepped workflow with gates at every critical point. An 11-step process that verifies each stage before proceeding.
-</purpose>
+# /release - DEPRECATED
 
-<usage>
-```bash
-# Start the interactive release workflow
-/release
+Git commands have been consolidated into `/pf-git`. Use:
 
-# The workflow will ask for bump type during preflight:
-#   Stable: major/minor/patch
-#   Prerelease: premajor/preminor/prepatch (creates alpha)
-#   If already on prerelease: prerelease (bump N), promote (go stable),
-#     graduate-beta, graduate-rc
-```
-</usage>
-
-<workflow>
-This command starts the `release` stepped workflow (BikeLane):
-
-1. **Preflight** — Clean state, compute version, conflict checks
-2. **Bump** — Update all version files, show diff ← GATE
-3. **Changelog** — Generate entries from commits (`/pf-changelog`) ← GATE
-4. **README** — Audit feature counts, update content
-5. **CLAUDE.md** — Verify version, build commands, project structure
-6. **Retro** — Optional retrospective (`/retro`)
-7. **Commit** — Stage, commit, merge to develop, verify staging ← GATE
-8. **Merge** — Merge develop → main, create tag
-9. **Push & Tag** — Push branches + tag (point of no return) ← GATE
-10. **Publish** — npm publish all packages (core, cyclist, theme packs) ← GATE
-11. **Finalize** — GitHub release, summary
-
-Gates pause for user approval. You can abort, revise, or continue at each gate.
-</workflow>
-
-<instructions>
-Start the release stepped workflow:
-
-```bash
-# Start the workflow
-/pf-workflow start release
-```
-
-If already in progress:
-```bash
-# Resume where you left off
-/pf-workflow resume
-```
-
-To check status:
-```bash
-/pf-workflow status
-```
-</instructions>
-
-<when-to-use>
-- After completing a sprint or set of features (stable release)
-- When develop is stable and ready for production (stable release)
-- Before deploying to production environments (stable release)
-- For early testing of new features before a stable cut (alpha/beta/rc prerelease)
-- To iterate on a prerelease (bump alpha.0 → alpha.1)
-- To promote a tested prerelease to stable
-</when-to-use>
-
-<prerequisites>
-- Clean working directory (no uncommitted changes)
-- On develop branch
-- Origin remote configured
-- npm authentication configured (for publish step)
-- `gh` CLI authenticated (for GitHub release step)
-</prerequisites>
-
-<skills>
-- `/pf-changelog` - For changelog format reference and auto-generation
-- `/retro` - For optional release retrospective
-- `/pf-workflow` - For workflow management commands
-</skills>
+| Old Command | New Command |
+|-------------|-------------|
+| `/repo-status` | `/pf-git status` |
+| `/git-cleanup` | `/pf-git cleanup` |
+| `/create-branches-from-story` | `/pf-git branches` |
+| `/release` | `/pf-git release` |

package/pennyfarthing-dist/commands/pf-repo-status.md

@@ -1,49 +1,16 @@
 ---
-description: Check git status of all project repos
+deprecated: true
+redirect: pf-git
+description: "DEPRECATED: Use /pf-git status instead."
 ---
 
-# Repository Status Check
+# /repo-status - DEPRECATED
 
-Check the git status of all project repos at once.
+Repository commands have been consolidated into `/pf-git`. Use:
 
-## Configuration
-
-Repos are configured in `.pennyfarthing/repos.yaml`. The script automatically reads this configuration.
-
-## Instructions
-
-Run this command to show the status of all repos:
-
-```bash
-$CLAUDE_PROJECT_DIR/scripts/git/git-status-all.sh
-```
-
-For a brief one-line-per-repo summary:
-
-```bash
-$CLAUDE_PROJECT_DIR/scripts/git/git-status-all.sh --brief
-```
-
-## What It Shows
-
-For each configured repo:
-- Current branch
-- Whether there are uncommitted changes
-- Whether the repo is ahead/behind origin
-- Unpushed commits (if any)
-
-## Adding More Repos
-
-To add repos, edit `.pennyfarthing/repos.yaml`:
-
-```yaml
-repos:
-  my-api:
-    path: my-api        # relative to project root
-    type: api
-    language: go
-  my-ui:
-    path: my-ui
-    type: ui
-    language: typescript
-```
+| Old Command | New Command |
+|-------------|-------------|
+| `/repo-status` | `/pf-git status` |
+| `/git-cleanup` | `/pf-git cleanup` |
+| `/create-branches-from-story` | `/pf-git branches` |
+| `/release` | `/pf-git release` |

package/pennyfarthing-dist/commands/pf-run-ci.md

@@ -1,116 +1,13 @@
 ---
-description: Detect and run CI locally
+deprecated: true
+redirect: pf-ci
+description: "DEPRECATED: Use /pf-ci run instead."
 ---
 
-<purpose>
-Run CI locally by detecting the project's CI system and executing the appropriate commands. Thin wrapper that delegates to project configuration.
-</purpose>
+# /run-ci - DEPRECATED
 
-<when-to-use>
-- Before pushing to verify CI will pass
-- To reproduce CI failures locally
-- To run the full CI pipeline without pushing
-- When you want to know what CI system the project uses
-</when-to-use>
+CI commands have been consolidated into `/pf-ci`. Use:
 
-<execution>
-
-## Running CI Locally
-
-Use the run-ci.sh script:
-
-```bash
-# Run CI locally (auto-detects CI system)
-$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/run-ci.sh
-
-# Show what CI system is detected without running
-$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/run-ci.sh --detect-only
-
-# Show what command would run without executing
-$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/run-ci.sh --dry-run
-
-# Show help
-$CLAUDE_PROJECT_DIR/.pennyfarthing/scripts/run-ci.sh --help
-```
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--help`, `-h` | Show help message |
-| `--detect-only` | Show detected CI system without running |
-| `--dry-run` | Show what would run without executing |
-
-</execution>
-
-<detection-order>
-
-## CI System Detection
-
-The script detects CI systems in this order:
-
-| Priority | System | Detection | Command |
-|----------|--------|-----------|---------|
-| 1 | Justfile | `just --list` shows `ci` recipe | `just ci` |
-| 2 | GitHub Actions | `.github/workflows/*.yml` exists | `act` |
-| 3 | GitLab CI | `.gitlab-ci.yml` exists | `gitlab-runner exec` |
-| 4 | npm fallback | `package.json` exists | `npm run build && npm test && npm run lint` |
-
-### Package Manager Detection
-
-For npm fallback, the script detects package manager:
-- `pnpm-lock.yaml` or `pnpm-workspace.yaml` → `pnpm`
-- `yarn.lock` → `yarn`
-- Otherwise → `npm`
-
-</detection-order>
-
-<output-format>
-
-## Output Examples
-
-### --detect-only
-```
-Detected CI system: github-actions
-Would run: act
-```
-
-### --dry-run
-```
-Detected: github-actions
-Would run: act
-```
-
-### Running CI
-```
-Running CI: github-actions
-Command: act
-
-[act output follows...]
-```
-
-Exit codes:
-- `0` - CI ran successfully
-- `1` - CI failed or no CI system detected
-
-</output-format>
-
-<requirements>
-
-## Tool Requirements
-
-| CI System | Required Tool | Installation |
-|-----------|--------------|--------------|
-| GitHub Actions | `act` | `brew install act` |
-| GitLab CI | `gitlab-runner` | See GitLab docs |
-| Justfile | `just` | `brew install just` |
-| npm fallback | `npm`/`pnpm`/`yarn` | Comes with Node.js |
-
-If a required tool is not installed, the script will show a warning.
-
-</requirements>
-
-<reference>
-- **Script:** `.pennyfarthing/scripts/misc/run-ci.sh`
-- **Story:** 21-4 (Command & Skill Expansion)
-</reference>
+| Old Command | New Command |
+|-------------|-------------|
+| `/run-ci` | `/pf-ci run` |

package/pennyfarthing-dist/commands/pf-session.md

@@ -0,0 +1,51 @@
+---
+description: Session lifecycle - start new work and resume checkpoints
+args: "[new|continue] [args...]"
+---
+
+# Session Management
+
+<purpose>
+Manage work session lifecycle. Start new stories from the backlog or resume from saved checkpoints after context circuit breaker.
+</purpose>
+
+## Commands
+
+### `/pf-session new`
+
+Start the next available story from the sprint backlog.
+
+```bash
+pf session new
+```
+
+Equivalent to `pf sprint work next`. Auto-selects the highest priority story.
+
+### `/pf-session continue [--list] [--story-id ID]`
+
+Resume work from a saved checkpoint after context circuit breaker.
+
+```bash
+pf session continue            # Interactive checkpoint selection
+pf session continue --list     # Show available checkpoints
+pf session continue --story-id MSSCI-12345  # Resume specific story
+```
+
+## Quick Reference
+
+| Command | Description |
+|---------|-------------|
+| `/pf-session new` | Start next available story |
+| `/pf-session continue` | Resume from checkpoint |
+
+## CLI Equivalent
+
+```bash
+pf session new
+pf session continue [--list] [--story-id ID]
+```
+
+## Related
+
+- `/pf-work` — Smart entry point (resumes or starts new)
+- `/pf-sprint work` — Interactive story selection