@pareto4/pp-core 1.5.2 → 1.5.3

package/pp-core/workflows/settings-advanced.md

@@ -1,5 +1,5 @@
 <purpose>
-Interactive configuration of GSD power-user knobs — plan bounce, node repair, subagent timeouts,
+Interactive configuration of pp-core power-user knobs — plan bounce, node repair, subagent timeouts,
 inline plan threshold, cross-AI execution, base branch, branch templates, response language,
 context window, gitignored search, graphify build timeout, runtime model tier overrides, and
 model policy configuration (provider + budget → canonical tier mapping, or manual model ID
@@ -340,7 +340,7 @@ AskUserQuestion([
 
 ### Section 7 — Runtime Model Tiers
 
-This section lets the user inspect and override the built-in model IDs GSD resolves for each
+This section lets the user inspect and override the built-in model IDs pp-core resolves for each
 profile tier (`opus` / `sonnet` / `haiku`) on their configured runtime.
 
 **Step A — Show current runtime and built-in defaults:**
@@ -571,10 +571,10 @@ the central setter.
 ### Section 8 — Model Policy
 
 This section configures the `model_policy` key in `.planning/config.json`. Model policy
-defines which AI models GSD uses at each cost tier (low / medium / high), independently
+defines which AI models pp-core uses at each cost tier (low / medium / high), independently
 of the `runtime` and `model_profile` selections above. Two paths are offered:
 
-- **Known provider:** choose a provider and a budget level; GSD materializes the canonical
+- **Known provider:** choose a provider and a budget level; pp-core materializes the canonical
   tier mapping for that provider.
 - **Generic provider:** enter low / medium / high model IDs manually.
 
@@ -604,7 +604,7 @@ AskUserQuestion([
     header: "Model Policy",
     multiSelect: false,
     options: [
-      { label: "Known provider", description: "Choose a provider (Claude / OpenAI / Gemini / Qwen) and a budget level — GSD writes the canonical tier mapping automatically." },
+      { label: "Known provider", description: "Choose a provider (Claude / OpenAI / Gemini / Qwen) and a budget level — pp-core writes the canonical tier mapping automatically." },
       { label: "Generic provider", description: "Enter low / medium / high model IDs manually for any provider or custom deployment." },
       { label: "Keep current", description: "Leave model_policy unchanged." }
     ]
@@ -743,7 +743,7 @@ Display:
 
 ```text
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► ADVANCED SETTINGS UPDATED
+ pp-core ► ADVANCED SETTINGS UPDATED
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 | Setting                                    | Value |

package/pp-core/workflows/settings-integrations.md

@@ -1,5 +1,5 @@
 <purpose>
-Interactive configuration of third-party integrations for GSD — search API keys
+Interactive configuration of third-party integrations for pp-core — search API keys
 (Brave / Firecrawl / Exa), code-review CLI routing (`review.models.<cli>`), and
 agent-skill injection (`agent_skills.<agent-type>`). Writes to
 `.planning/config.json` via `pp-tools` so unrelated keys are
@@ -263,7 +263,7 @@ output under any circumstance.**
 
 ```text
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► INTEGRATIONS UPDATED
+ pp-core ► INTEGRATIONS UPDATED
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Search Integrations

package/pp-core/workflows/settings.md

@@ -1,5 +1,5 @@
 <purpose>
-Interactive configuration of GSD workflow agents (research, plan_check, verifier) and model profile selection via multi-question prompt. Updates .planning/config.json with user preferences. Optionally saves settings as global defaults (~/.gsd/defaults.json) for future projects.
+Interactive configuration of pp-core workflow agents (research, plan_check, verifier) and model profile selection via multi-question prompt. Updates .planning/config.json with user preferences. Optionally saves settings as global defaults (~/.gsd/defaults.json) for future projects.
 </purpose>
 
 <required_reading>
@@ -540,7 +540,7 @@ Display:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SETTINGS UPDATED
+ pp-core ► SETTINGS UPDATED
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 | Setting              | Value |

package/pp-core/workflows/ship.md

@@ -14,7 +14,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 </required_reading>
 
 <available_agent_types>
-Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
+Valid pp-core subagent types (use exact names — do not fall back to 'general-purpose'):
 - pp-mempalace-curator — Ship-time MemPalace curation (diary, KG mirror, cross-project tunnels, wing-scoped prune); dispatched at ship:post when the mempalace capability is enabled.
 </available_agent_types>
 
@@ -419,7 +419,7 @@ Read the `activeHooks` array directly from `SHIP_POST_HOOKS_JSON` in-context (do
   ```
 
   `Agent(subagent_type=ref.agent, prompt="Ship-time capability hook for phase ${PHASE_NUMBER}. Phase dir: ${PHASE_DIR}. Consume: ${consumed_files}. Follow your agent instructions.", model="{balanced_model}")`
-- If `ref.skill` is set, dispatch with `Skill(skill="gsd-${ref.skill}", args="${PHASE_NUMBER} --auto ${GSD_WS}")` (prepend `gsd-` to `ref.skill`).
+- If `ref.skill` is set, dispatch with `Skill(skill="gsd-${ref.skill}", args="${PHASE_NUMBER} --auto ${GSD_WS}")` (Prepend `gsd-` to `ref.skill`).
 
 Each dispatch is best-effort: if it errors, record a warning and continue — never re-raise (`onError: skip`).
 </step>

package/pp-core/workflows/sketch-wrap-up.md

@@ -14,7 +14,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 <step name="banner">
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SKETCH WRAP-UP
+ pp-core ► SKETCH WRAP-UP
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 </step>
@@ -240,7 +240,7 @@ pp_run query commit "docs(sketch-wrap-up): package [N] sketch findings into proj
 <step name="report">
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SKETCH WRAP-UP COMPLETE ✓
+ pp-core ► SKETCH WRAP-UP COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **Curated:** {N} sketches ({included} included, {excluded} excluded)

package/pp-core/workflows/sketch.md

@@ -22,7 +22,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 <step name="banner">
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SKETCHING
+ pp-core ► SKETCHING
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -313,7 +313,7 @@ After all sketches complete:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SKETCH COMPLETE ✓
+ pp-core ► SKETCH COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ## Design Direction

package/pp-core/workflows/spec-phase.md

@@ -195,7 +195,7 @@ ones). Reference: @~/.claude/pp-core/references/edge-probe.md.
 **Runtime coverage compute — resolve and invoke edge-probe.cjs:**
 
 ```bash
-# Resolve the compiled edge-probe.cjs against the GSD install dir via RUNTIME_DIR (#448)
+# Resolve the compiled edge-probe.cjs against the pp-core install dir via RUNTIME_DIR (#448)
 # — NOT the consuming project's git root — falling back to git toplevel / $HOME/.claude.
 # Mirrors the ui-safety-gate.cjs resolution idiom at autonomous.md:290 / plan-phase.md:631.
 _GSD_RT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"
@@ -209,10 +209,10 @@ EDGE_PROBE_JS=$(for _c in \
 done)
 
 # Graceful degradation — never silent skip (RR-04). Build ONLY when $_GSD_RT is a verified
-# GSD source checkout (has tsconfig.build.json + src/edge-probe.cts), and pin npm to it with
+# pp-core source checkout (has tsconfig.build.json + src/edge-probe.cts), and pin npm to it with
 # --prefix so we never trigger the CONSUMING project's own build:lib (its cwd package scripts:
 # codegen/migrations/writes) during a spec workflow. Real installs ship the compiled .cjs via
-# prepublishOnly, so this build path only matters in a GSD dev checkout (review High).
+# prepublishOnly, so this build path only matters in a pp-core dev checkout (review High).
 if [ -z "$EDGE_PROBE_JS" ]; then
   if [ -f "$_GSD_RT/tsconfig.build.json" ] && [ -f "$_GSD_RT/src/edge-probe.cts" ]; then
     npm --prefix "$_GSD_RT" run build:lib 2>/dev/null || true
@@ -226,7 +226,7 @@ if [ -z "$EDGE_PROBE_JS" ]; then
     done)
   fi
   if [ -z "$EDGE_PROBE_JS" ]; then
-    echo "ERROR: edge-probe.cjs not found — reinstall GSD or run \`npm run build:lib\` in your GSD checkout." >&2
+    echo "ERROR: edge-probe.cjs not found — reinstall pp-core or run \`npm run build:lib\` in your pp-core checkout." >&2
     exit 1
   fi
 fi

package/pp-core/workflows/spike-wrap-up.md

@@ -14,7 +14,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 <step name="banner">
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SPIKE WRAP-UP
+ pp-core ► SPIKE WRAP-UP
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 </step>
@@ -254,7 +254,7 @@ pp_run query commit "docs(spike-wrap-up): package [N] spike findings into projec
 <step name="report">
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SPIKE WRAP-UP COMPLETE ✓
+ pp-core ► SPIKE WRAP-UP COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **Processed:** {N} spikes

package/pp-core/workflows/spike.md

@@ -17,7 +17,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 <step name="banner">
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SPIKING
+ pp-core ► SPIKING
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -396,7 +396,7 @@ pp_run query commit "docs(spikes): update conventions" --files .planning/spikes/
 <step name="report">
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SPIKE COMPLETE ✓
+ pp-core ► SPIKE COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ## Verdicts

package/pp-core/workflows/sync-skills.md

@@ -1,4 +1,4 @@
-# sync-skills — Cross-Runtime GSD Skill Sync
+# sync-skills — Cross-Runtime pp-core Skill Sync
 
 **Command:** `/pp-sync-skills`
 
@@ -59,7 +59,7 @@ Use `install.js --skills-root` to resolve paths — this reuses the single autho
 
 ```bash
 INSTALL_JS="$(dirname "$0")/../pp-core/bin/install.js"
-# If running from a global install, resolve relative to the GSD package
+# If running from a global install, resolve relative to the pp-core package
 INSTALL_JS_GLOBAL="$HOME/.claude/pp-core/bin/install.js"
 [[ ! -f "$INSTALL_JS" ]] && INSTALL_JS="$INSTALL_JS_GLOBAL"
 
@@ -73,7 +73,7 @@ done
 **Guard:** If the source skills root does not exist, print:
 ```
 error: source skills root not found: <path>
-       Is GSD installed globally for the '<runtime>' runtime?
+       Is pp-core installed globally for the '<runtime>' runtime?
        Run: node ~/.claude/pp-core/bin/install.js --global --<runtime>
 ```
 Then exit.
@@ -96,11 +96,11 @@ DST_SKILLS=$(ls -1 "$DEST_ROOT" 2>/dev/null | grep '^gsd-')
 # Diff:
 # CREATE  — in SRC but not in DST
 # UPDATE  — in both; content differs (compare recursively via checksums)
-# REMOVE  — in DST but not in SRC (stale GSD skill no longer in source)
+# REMOVE  — in DST but not in SRC (stale pp-core skill no longer in source)
 # SKIP    — in both; content identical (already up to date)
 ```
 
-**Non-GSD preservation:** Only `gsd-*` entries are ever created, updated, or removed. Entries in the destination that do not start with `gsd-` are never touched.
+**Non-pp-core preservation:** Only `gsd-*` entries are ever created, updated, or removed. Entries in the destination that do not start with `gsd-` are never touched.
 
 ---
 
@@ -177,6 +177,6 @@ Sync complete: <N> skills synced to <M> runtime(s).
 
 ## Limitations
 
-- Sync copies files verbatim and does not apply runtime-specific content transformations. Use the GSD installer directly for runtimes that require format conversion.
+- Sync copies files verbatim and does not apply runtime-specific content transformations. Use the pp-core installer directly for runtimes that require format conversion.
 - Cross-project skills (`.agents/skills/`) are out of scope — this command only touches global runtime skills roots.
 - Bidirectional sync is not supported. Choose one canonical source with `--from`.

package/pp-core/workflows/thread.md

@@ -209,7 +209,7 @@ updated: {today ISO date}
 - The value is in Context and Next Steps — a cold-start session can pick up immediately
 - Threads can be promoted to phases or backlog items when they mature:
   /pp-add-phase or /pp-add-backlog with context from the thread
-- Thread files live in .planning/threads/ — no collision with phases or other GSD structures
+- Thread files live in .planning/threads/ — no collision with phases or other pp-core structures
 - Thread status values: `open`, `in_progress`, `resolved`
 </notes>
 

package/pp-core/workflows/ui-phase.md

@@ -9,7 +9,7 @@ UI-SPEC.md locks spacing, typography, color, copywriting, and design system deci
 </required_reading>
 
 <available_agent_types>
-Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
+Valid pp-core subagent types (use exact names — do not fall back to 'general-purpose'):
 - pp-ui-researcher — Researches UI/UX approaches
 - pp-ui-checker — Reviews UI implementation quality
 </available_agent_types>
@@ -115,7 +115,7 @@ If "Update": continue to step 5.
 Display:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► UI DESIGN CONTRACT — PHASE {N}
+ pp-core ► UI DESIGN CONTRACT — PHASE {N}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning UI researcher... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -180,7 +180,7 @@ Display blocker details and options. Exit workflow.
 Display:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► VERIFYING UI-SPEC
+ pp-core ► VERIFYING UI-SPEC
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning UI checker... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -269,7 +269,7 @@ Use AskUserQuestion for the choice.
 Display:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► UI-SPEC READY ✓
+ pp-core ► UI-SPEC READY ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **Phase {N}: {Name}** — UI design contract approved

package/pp-core/workflows/ui-review.md

@@ -1,5 +1,5 @@
 <purpose>
-Retroactive 6-pillar visual audit of implemented frontend code. Standalone command that works on any project — GSD-managed or not. Produces scored UI-REVIEW.md with actionable findings.
+Retroactive 6-pillar visual audit of implemented frontend code. Standalone command that works on any project — pp-core-managed or not. Produces scored UI-REVIEW.md with actionable findings.
 </purpose>
 
 <required_reading>
@@ -7,7 +7,7 @@ Retroactive 6-pillar visual audit of implemented frontend code. Standalone comma
 </required_reading>
 
 <available_agent_types>
-Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
+Valid pp-core subagent types (use exact names — do not fall back to 'general-purpose'):
 - pp-ui-auditor — Audits UI against design requirements
 </available_agent_types>
 
@@ -31,7 +31,7 @@ UI_AUDITOR_MODEL=$(pp_run query resolve-model pp-ui-auditor --raw)
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► UI AUDIT — PHASE {N}: {name}
+ pp-core ► UI AUDIT — PHASE {N}: {name}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -118,7 +118,7 @@ Display score summary:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► UI AUDIT COMPLETE ✓
+ pp-core ► UI AUDIT COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **Phase {N}: {Name}** — Overall: {score}/24

package/pp-core/workflows/ultraplan-phase.md

@@ -1,6 +1,6 @@
 # Ultraplan Phase Workflow [BETA]
 
-Offload GSD's plan phase to Claude Code's ultraplan cloud infrastructure.
+Offload pp-core's plan phase to Claude Code's ultraplan cloud infrastructure.
 
 ⚠ **BETA feature.** Ultraplan is in research preview and may change. This workflow is
 intentionally isolated from /pp:plan-phase so upstream changes to ultraplan cannot
@@ -14,7 +14,7 @@ Display the stage banner:
 
 ```text
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► ULTRAPLAN PHASE  ⚠ BETA
+ pp-core ► ULTRAPLAN PHASE  ⚠ BETA
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Ultraplan is in research preview (Claude Code v2.1.91+).
 Use /pp:plan-phase for stable local planning.
@@ -63,7 +63,7 @@ Use /pp:plan-phase for local planning instead.
 Parse phase number from `$ARGUMENTS`. If no phase number is provided, detect the next
 unplanned phase from the roadmap (same logic as /pp:plan-phase).
 
-Load GSD phase context:
+Load pp-core phase context:
 
 ```bash
 _PP_SHIM_NAME="pp-tools.cjs"; _PP_RUNTIME_ROOT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"; PP_TOOLS="${_PP_RUNTIME_ROOT}/pp-core/bin/${_PP_SHIM_NAME}"; if [ -f "$PP_TOOLS" ]; then pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${_PP_RUNTIME_ROOT}/.claude/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${_PP_RUNTIME_ROOT}/.claude/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${_PP_RUNTIME_ROOT}/.codex/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${_PP_RUNTIME_ROOT}/.codex/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif command -v pp-tools >/dev/null 2>&1; then PP_TOOLS="$(command -v pp-tools)"; pp_run() { "$PP_TOOLS" "$@"; }; elif [ -f "$HOME/.claude/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="$HOME/.claude/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${HERMES_HOME:-$HOME/.hermes}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${HERMES_HOME:-$HOME/.hermes}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${CURSOR_CONFIG_DIR:-$HOME/.cursor}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${CURSOR_CONFIG_DIR:-$HOME/.cursor}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${CODEX_HOME:-$HOME/.codex}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${CODEX_HOME:-$HOME/.codex}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${GEMINI_CONFIG_DIR:-$HOME/.gemini}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${GEMINI_CONFIG_DIR:-$HOME/.gemini}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${COPILOT_CONFIG_DIR:-$HOME/.copilot}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${WINDSURF_CONFIG_DIR:-$HOME/.codeium/windsurf}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${WINDSURF_CONFIG_DIR:-$HOME/.codeium/windsurf}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${AUGMENT_CONFIG_DIR:-$HOME/.augment}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${AUGMENT_CONFIG_DIR:-$HOME/.augment}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${TRAE_CONFIG_DIR:-$HOME/.trae}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${TRAE_CONFIG_DIR:-$HOME/.trae}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${QWEN_CONFIG_DIR:-$HOME/.qwen}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${QWEN_CONFIG_DIR:-$HOME/.qwen}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${CODEBUDDY_CONFIG_DIR:-$HOME/.codebuddy}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${CODEBUDDY_CONFIG_DIR:-$HOME/.codebuddy}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${CLINE_CONFIG_DIR:-$HOME/.cline}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${CLINE_CONFIG_DIR:-$HOME/.cline}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${GROK_AGENTS_HOME:-$HOME/.agents}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${GROK_AGENTS_HOME:-$HOME/.agents}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${ANTIGRAVITY_CONFIG_DIR:-$HOME/.gemini/antigravity}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${ANTIGRAVITY_CONFIG_DIR:-$HOME/.gemini/antigravity}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${OPENCODE_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/opencode}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${OPENCODE_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/opencode}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${KILO_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/kilo}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${KILO_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/kilo}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; else echo "ERROR: pp-tools.cjs not found at $PP_TOOLS and pp-tools is not on PATH. Run: npx -y @pareto4/pp-core@latest --claude --local" >&2; exit 1; fi; if [ -n "${CLAUDE_ENV_FILE:-}" ] && [ -n "${PP_TOOLS:-}" ]; then printf "export PATH='%s':\"\$PATH\"\n" "${PP_TOOLS%/*}" >> "$CLAUDE_ENV_FILE" 2>/dev/null || true; fi
@@ -96,7 +96,7 @@ Phase {N}: {phase name}
 
 <step name="build_prompt">
 
-Build the ultraplan prompt from GSD context.
+Build the ultraplan prompt from pp-core context.
 
 1. Read the phase scope from ROADMAP.md — extract the goal, deliverables, and scope for
    the target phase.
@@ -126,7 +126,7 @@ Plan phase {phase_number}: {phase_name}
 
 ## Output Format
 
-Produce a GSD PLAN.md with the following YAML frontmatter:
+Produce a pp-core PLAN.md with the following YAML frontmatter:
 
 ---
 phase: "{padded_phase}-{phase_slug}"
@@ -173,7 +173,7 @@ When ◆ ultraplan ready appears in your terminal:
   6. Note the file path Claude prints
   7. Run: /pp:import --from <the file path>
 
-/pp:import will run conflict detection, convert to GSD format,
+/pp:import will run conflict detection, convert to pp-core format,
 validate via plan-checker, update ROADMAP.md, and commit.
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

package/pp-core/workflows/undo.md

@@ -1,5 +1,5 @@
 <purpose>
-Safe git revert workflow. Rolls back GSD phase or plan commits using the phase manifest with dependency checks and a confirmation gate. Uses git revert --no-commit (NEVER git reset) to preserve history.
+Safe git revert workflow. Rolls back pp-core phase or plan commits using the phase manifest with dependency checks and a confirmation gate. Uses git revert --no-commit (NEVER git reset) to preserve history.
 </purpose>
 
 <required_reading>
@@ -14,7 +14,7 @@ Display the stage banner:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► UNDO
+ pp-core ► UNDO
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 </step>
@@ -32,7 +32,7 @@ If no valid argument is provided, display usage and exit:
 Usage: /pp:undo --last N | --phase NN | --plan NN-MM
 
 Modes:
-  --last N      Show last N GSD commits for interactive selection
+  --last N      Show last N pp-core commits for interactive selection
   --phase NN    Revert all commits for phase NN
   --plan NN-MM  Revert all commits for plan NN-MM
 
@@ -53,11 +53,11 @@ Run:
 git log --oneline --no-merges -${COUNT}
 ```
 
-Filter for GSD conventional commits matching `type(scope): message` pattern (e.g., `feat(04-01):`, `docs(03):`, `fix(02-03):`).
+Filter for pp-core conventional commits matching `type(scope): message` pattern (e.g., `feat(04-01):`, `docs(03):`, `fix(02-03):`).
 
 Display a numbered list of matching commits:
 ```
-Recent GSD commits:
+Recent pp-core commits:
   1. abc1234 feat(04-01): implement auth endpoint
   2. def5678 docs(03-02): complete plan summary
   3. ghi9012 fix(02-03): correct validation logic
@@ -265,7 +265,7 @@ Display the completion banner:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► UNDO COMPLETE ✓
+ pp-core ► UNDO COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 

package/pp-core/workflows/update.md

@@ -1,5 +1,5 @@
 <purpose>
-Check for GSD updates via npm, display changelog for versions between installed and latest, obtain user confirmation, and execute clean installation with cache clearing.
+Check for pp-core updates via npm, display changelog for versions between installed and latest, obtain user confirmation, and execute clean installation with cache clearing.
 </purpose>
 
 <required_reading>
@@ -9,7 +9,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 <process>
 
 <step name="get_installed_version">
-Detect the installed GSD version, scope, runtime, and config dir.
+Detect the installed pp-core version, scope, runtime, and config dir.
 
 First, derive `PREFERRED_CONFIG_DIR` and `PREFERRED_RUNTIME` from the invoking prompt's `execution_context` path — this is the one input only the workflow knows:
 - If the path contains `/pp-core/workflows/update.md`, strip that suffix and store the remainder as `PREFERRED_CONFIG_DIR`.
@@ -65,7 +65,7 @@ Parse output:
 - Line 1 = installed version (`0.0.0` means unknown version)
 - Line 2 = install scope (`LOCAL`, `GLOBAL`, or `UNKNOWN`)
 - Line 3 = target runtime (`claude`, `opencode`, `gemini`, `kilo`, `codex`, `antigravity`)
-- Line 4 = resolved GSD config dir (e.g. `/Users/me/.claude`, `/Users/me/.gemini`); empty if scope is `UNKNOWN`. Capture this as `GSD_DIR` and pass it to subsequent steps so they don't re-derive the runtime path.
+- Line 4 = resolved pp-core config dir (e.g. `/Users/me/.claude`, `/Users/me/.gemini`); empty if scope is `UNKNOWN`. Capture this as `GSD_DIR` and pass it to subsequent steps so they don't re-derive the runtime path.
 - If scope is `UNKNOWN`, proceed to install using the `--claude --global` fallback.
 
 `update-context` reproduces the previous detection cascade — preferred-config-dir fast path, local-over-global with same-path dedup (so `CWD=$HOME` does not misdetect as LOCAL), env-var overrides (`CLAUDE_CONFIG_DIR`, `OPENCODE_CONFIG_DIR`, `KILO_CONFIG`, `XDG_CONFIG_HOME`, `CODEX_HOME`, …), and semver validation — but as a tested projection rather than ~280 lines of inline bash. Branch coverage lives in `tests/issue-498-update-context.test.cjs`.
@@ -152,7 +152,7 @@ When `TAG=next`, the "latest" value is the release candidate published under `@n
 
 **If installed == latest:**
 ```
-## GSD Update
+## pp-core Update
 
 **Installed:** X.Y.Z
 **Latest:** X.Y.Z
@@ -164,7 +164,7 @@ Exit.
 
 **If installed > latest:**
 ```
-## GSD Update
+## pp-core Update
 
 **Installed:** X.Y.Z
 **Latest:** A.B.C
@@ -197,7 +197,7 @@ curl -fsSL "https://gitlab.com/pareto4/pp-core/-/raw/main/CHANGELOG.md" -o "$CHA
 
 GSD_CHANGESET_CLI="$GSD_DIR/scripts/changeset/cli.cjs"
 if [ ! -f "$GSD_CHANGESET_CLI" ]; then
-  CHANGELOG_PREVIEW="(Changelog CLI not found at $GSD_CHANGESET_CLI — reinstall GSD to restore preview. Update will still proceed.)"
+  CHANGELOG_PREVIEW="(Changelog CLI not found at $GSD_CHANGESET_CLI — reinstall pp-core to restore preview. Update will still proceed.)"
 else
   EXTRACT_JSON=$(node "$GSD_CHANGESET_CLI" extract \
     --from "$INSTALLED_VERSION" \
@@ -226,7 +226,7 @@ rm -f "$CHANGELOG_TMP"
 3. Display preview and ask for confirmation, using `$CHANGELOG_PREVIEW` from the extract step above:
 
 ```
-## GSD Update Available
+## pp-core Update Available
 
 **Installed:** {INSTALLED_VERSION}
 **Latest:** {LATEST_VERSION}
@@ -238,7 +238,7 @@ rm -f "$CHANGELOG_TMP"
 
 ────────────────────────────────────────────────────────────
 
-⚠️  **Note:** The installer performs a clean install of GSD folders:
+⚠️  **Note:** The installer performs a clean install of pp-core folders:
 - `commands/gsd/` will be wiped and replaced
 - `pp-core/` will be wiped and replaced
 - `agents/pp-*` files will be replaced
@@ -253,7 +253,7 @@ Your custom files in other locations are preserved:
 - Custom hooks ✓
 - Your CLAUDE.md files ✓
 
-If you've modified any GSD files directly, they'll be automatically backed up to `pp-local-patches/` and can be reapplied with `/pp:update --reapply` after the update.
+If you've modified any pp-core files directly, they'll be automatically backed up to `pp-local-patches/` and can be reapplied with `/pp:update --reapply` after the update.
 ```
 
 
@@ -269,7 +269,7 @@ Use AskUserQuestion:
 
 <step name="backup_custom_files">
 Before running the installer, detect and back up any user-added files inside
-GSD-managed directories. These are files that exist on disk but are NOT listed
+pp-core-managed directories. These are files that exist on disk but are NOT listed
 in `pp-file-manifest.json` — i.e., files the user added themselves that the
 installer does not know about and will delete during the wipe.
 
@@ -341,7 +341,7 @@ JSEOF
 Then inform the user:
 
 ```
-⚠️  Found N custom file(s) inside GSD-managed directories.
+⚠️  Found N custom file(s) inside pp-core-managed directories.
     These have been backed up to pp-user-files-backup/ before the update.
     Restore them after the update if needed.
 ```
@@ -463,7 +463,7 @@ Format completion message (changelog was already shown in confirmation step):
 
 ```
 ╔═══════════════════════════════════════════════════════════╗
-║  GSD Updated: v1.5.10 → v1.5.15                           ║
+║  pp-core Updated: v1.5.10 → v1.5.15                           ║
 ╚═══════════════════════════════════════════════════════════╝
 
 ⚠️  Restart your runtime to pick up the new commands.

package/pp-core/workflows/validate-phase.md

@@ -7,7 +7,7 @@ Audit Nyquist validation gaps for a completed phase. Generate missing tests. Upd
 </required_reading>
 
 <available_agent_types>
-Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
+Valid pp-core subagent types (use exact names — do not fall back to 'general-purpose'):
 - pp-nyquist-auditor — Validates verification coverage
 </available_agent_types>
 
@@ -33,7 +33,7 @@ Resolve active step hooks from `VERIFY_POST_HOOKS_JSON` where `kind == "step"` a
 
 If no active validate-phase step hook exists: exit with "Nyquist validation is disabled. Enable via /pp:settings."
 
-Display banner: `GSD > VALIDATE PHASE {N}: {name}`
+Display banner: `pp-core > VALIDATE PHASE {N}: {name}`
 
 ## 1. Detect Input State
 
@@ -151,14 +151,14 @@ pp_run query commit "docs(phase-${PHASE}): add/update validation strategy"
 
 **Compliant:**
 ```
-GSD > PHASE {N} IS NYQUIST-COMPLIANT
+pp-core > PHASE {N} IS NYQUIST-COMPLIANT
 All requirements have automated verification.
 ▶ Next: /pp:audit-milestone ${GSD_WS}
 ```
 
 **Partial:**
 ```
-GSD > PHASE {N} VALIDATED (PARTIAL)
+pp-core > PHASE {N} VALIDATED (PARTIAL)
 {M} automated, {K} manual-only.
 ▶ Retry: /pp:validate-phase {N} ${GSD_WS}
 ```

package/pp-core/workflows/verify-work.md

@@ -12,7 +12,7 @@ User tests, Claude records. One test at a time. Plain text responses.
 </purpose>
 
 <available_agent_types>
-Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
+Valid pp-core subagent types (use exact names — do not fall back to 'general-purpose'):
 - pp-planner — Creates detailed plans from phase scope
 - pp-plan-checker — Reviews plan quality before execution
 </available_agent_types>
@@ -171,7 +171,7 @@ PHASE_GOAL=$(pp_run query roadmap.get-phase "${phase_number}" ${GSD_WS} --pick g
 USER_STORY_VALID=$(pp_run query user-story.validate --story "$PHASE_GOAL" --pick valid)
 if [ "$USER_STORY_VALID" != "true" ]; then
   echo "Phase ${phase_number} has '**Mode:** mvp' in ROADMAP.md but the **Goal:** is not in user-story format."
-  echo "Run /gsd mvp-phase ${phase_number} to set a user-story goal before verifying."
+  echo "Run /pp:mvp-phase ${phase_number} to set a user-story goal before verifying."
   exit 1
 fi
 ```
@@ -572,7 +572,7 @@ Diagnosis runs automatically - no user prompt. Parallel agents investigate simul
 Display:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PLANNING FIXES
+ pp-core ► PLANNING FIXES
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning planner for gap closure... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -622,7 +622,7 @@ On return:
 Display:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► VERIFYING FIX PLANS
+ pp-core ► VERIFYING FIX PLANS
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning plan checker... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -728,7 +728,7 @@ Wait for user response.
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► FIXES READY ✓
+ pp-core ► FIXES READY ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **Phase {X}: {Name}** — {N} gap(s) diagnosed, {M} fix plan(s) created