@pareto4/pp-core 1.5.2 → 1.5.3

package/pp-core/workflows/new-project.md

@@ -7,7 +7,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-project-researcher — Researches project-level technical decisions
 - pp-research-synthesizer — Synthesizes findings from parallel research agents
 - pp-roadmapper — Creates phased execution roadmaps
@@ -69,7 +69,7 @@ Parse JSON for: `researcher_model`, `synthesizer_model`, `roadmapper_model`, `co
 
 **If `agents_installed` is false:** Display a warning before proceeding:
 ```text
-⚠ GSD agents not installed. The following agents are missing from your agents directory:
+⚠ pp-core agents not installed. The following agents are missing from your agents directory:
   {missing_agents joined with newline}
 
 Runtime checked: {agent_runtime}
@@ -87,7 +87,7 @@ definitions to be installed for this runtime.
 Subagent spawns (pp-project-researcher, pp-research-synthesizer, pp-roadmapper) will fail
 with "agent type not found" if `required_agents_installed` is false. Run the installer with --global to make agents available:
 
-  npx @opengsd/pp-core@latest --global
+  npx @pareto4/pp-core@latest --global
 
 Proceeding without research subagents — roadmap will be generated inline.
 ```
@@ -331,7 +331,7 @@ If spike/sketch findings skills exist, read their SKILL.md files to inform the q
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► QUESTIONING
+ pp-core ► QUESTIONING
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -810,7 +810,7 @@ Strip the `./` prefix to get directory names (e.g., `./backend` → `backend`).
 Use AskUserQuestion:
 
 - header: "Multi-Repo Workspace"
-- question: "I detected separate git repos in this workspace. Which directories contain code that GSD should commit to?"
+- question: "I detected separate git repos in this workspace. Which directories contain code that pp-core should commit to?"
 - multiSelect: true
 - options: one option per detected directory
   - "[directory name]" — Separate git repo
@@ -847,7 +847,7 @@ Display stage banner:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► RESEARCHING
+ pp-core ► RESEARCHING
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Researching [domain] ecosystem...
@@ -1081,7 +1081,7 @@ Display research complete banner and key findings:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► RESEARCH COMPLETE ✓
+ pp-core ► RESEARCH COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ## Key Findings
@@ -1101,7 +1101,7 @@ Display stage banner:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► DEFINING REQUIREMENTS
+ pp-core ► DEFINING REQUIREMENTS
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -1270,7 +1270,7 @@ Display stage banner:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► CREATING ROADMAP
+ pp-core ► CREATING ROADMAP
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning roadmapper... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -1425,7 +1425,7 @@ Use AskUserQuestion:
 pp_run query generate-claude-md --output "$INSTRUCTION_FILE"
 ```
 
-This ensures new projects get the default GSD workflow-enforcement guidance and current project context in `$INSTRUCTION_FILE`.
+This ensures new projects get the default pp-core workflow-enforcement guidance and current project context in `$INSTRUCTION_FILE`.
 
 **Commit roadmap (after approval or auto mode):**
 
@@ -1439,7 +1439,7 @@ Present completion summary:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PROJECT INITIALIZED ✓
+ pp-core ► PROJECT INITIALIZED ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **[Project Name]**
@@ -1555,7 +1555,7 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qi "UI hint.*yes" && echo "true"
 - [ ] ROADMAP.md created with phases, requirement mappings, success criteria
 - [ ] STATE.md initialized
 - [ ] REQUIREMENTS.md traceability updated
-- [ ] `$INSTRUCTION_FILE` generated with GSD workflow guidance (AGENTS.md for Codex, `.claude/CLAUDE.md` otherwise; an existing hand-crafted file without GSD markers is left untouched unless `--force`)
+- [ ] `$INSTRUCTION_FILE` generated with pp-core workflow guidance (AGENTS.md for Codex, `.claude/CLAUDE.md` otherwise; an existing hand-crafted file without pp-core markers is left untouched unless `--force`)
 - [ ] User knows next step is `/pp:discuss-phase 1`
 
 **Atomic commits:** Each phase commits its artifacts immediately. If context is lost, artifacts persist.

package/pp-core/workflows/new-workspace.md

@@ -204,7 +204,7 @@ Workspace created: $TARGET_PATH
 
 Next steps:
   cd "$TARGET_PATH"
-  /pp:new-project    # Initialize GSD in the workspace
+  /pp:new-project    # Initialize pp-core in the workspace
 ```
 
 **If some repos failed:**
@@ -217,14 +217,14 @@ Workspace created with $SUCCESS_COUNT of $TOTAL_COUNT repos: $TARGET_PATH
 
 Next steps:
   cd "$TARGET_PATH"
-  /pp:new-project    # Initialize GSD in the workspace
+  /pp:new-project    # Initialize pp-core in the workspace
 ```
 
-**Offer to initialize GSD (if not `--auto`):**
+**Offer to initialize pp-core (if not `--auto`):**
 
 Use AskUserQuestion:
-- header: "Initialize GSD"
-- question: "Would you like to initialize a GSD project in the new workspace?"
+- header: "Initialize pp-core"
+- question: "Would you like to initialize a pp-core project in the new workspace?"
 - options:
   - "Yes — run /pp:new-project" → tell user to `cd "$TARGET_PATH"` first, then run `/pp:new-project`
   - "No — I'll set it up later" → done

package/pp-core/workflows/next.md

@@ -1,5 +1,5 @@
 <purpose>
-Detect current project state and automatically advance to the next logical GSD workflow step.
+Detect current project state and automatically advance to the next logical pp-core workflow step.
 Reads project state to determine: discuss → plan → execute → verify → complete progression.
 </purpose>
 
@@ -30,7 +30,7 @@ Extract:
 
 If no `.planning/` directory exists:
 ```
-No GSD project detected. Run `/pp:new-project` to get started.
+No pp-core project detected. Run `/pp:new-project` to get started.
 ```
 Exit.
 </step>
@@ -287,7 +287,7 @@ if [ "$PLAN_STRATEGY" = "converge" ]; then
       '' \
       'Enable plan convergence with:' \
       '' \
-      '  gsd config-set workflow.plan_review_convergence true' \
+      '  pp config-set workflow.plan_review_convergence true' \
       '' \
       'Then re-run with --converge.'
     exit 1
@@ -298,7 +298,7 @@ fi
 Display the determination:
 
 ```
-## GSD Next
+## pp-core Next
 
 **Current:** Phase [N] — [name] | [progress]%
 **Status:** [status description]

package/pp-core/workflows/note.md

@@ -101,7 +101,7 @@ If a scope has no directory or no entries, show: `(no notes)`
 1. Run the **list** logic to build the numbered index (both scopes)
 2. Find entry N from the numbered list
 3. If N is invalid or refers to an already-promoted note, tell the user and stop
-4. **Requires `.planning/` directory** — if it doesn't exist, warn: "Todos require a GSD project. Run `/pp:new-project` to initialize one."
+4. **Requires `.planning/` directory** — if it doesn't exist, warn: "Todos require a pp-core project. Run `/pp:new-project` to initialize one."
 5. Ensure `.planning/todos/pending/` directory exists
 6. Generate todo ID: `{NNN}-{slug}` where NNN is the next sequential number (scan both `.planning/todos/pending/` and `.planning/todos/completed/` for the highest existing number, increment by 1, zero-pad to 3 digits) and slug is the first ~4 meaningful words of the note text
 7. Extract the note text from the source file (body after frontmatter)

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

@@ -20,7 +20,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-phase-researcher — Researches technical approaches for a phase
 - pp-pattern-mapper — Analyzes codebase for existing patterns, produces PATTERNS.md
 - pp-planner — Creates detailed plans from phase scope
@@ -261,7 +261,7 @@ fi
 2. Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PRD EXPRESS PATH
+ pp-core ► PRD EXPRESS PATH
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Using PRD: {PRD_FILE}
@@ -353,7 +353,7 @@ pp_run query commit "docs(${padded_phase}): generate context from PRD" --files "
 
 **If `--ingest <path-or-glob>` provided:**
 
-1. Display banner: `GSD ► ADR Ingest Express Path` with `{INGEST_PATH}` and `{INGEST_FORMAT}`.
+1. Display banner: `pp-core ► ADR Ingest Express Path` with `{INGEST_PATH}` and `{INGEST_FORMAT}`.
 2. Parse each resolved ADR through `pp-core/bin/lib/adr-parser.cjs` (`--input`, `--format`) and collect normalized records.
 3. Status gate: reject `superseded`/`rejected`/`deprecated`; warn on `proposed`; missing status defaults to `accepted`.
 4. Empty-decisions fallback: if all parsed ADRs have zero `decisions[]`, emit `ADR ingest produced no locked decisions; fall back to discuss-phase for this phase.` and exit with `/pp:discuss-phase {N}` guidance.
@@ -491,7 +491,7 @@ If user selects "Skip research": skip to step 6.
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► RESEARCHING PHASE {X}
+ pp-core ► RESEARCHING PHASE {X}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning researcher... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -501,7 +501,7 @@ Display banner:
 
 ```bash
 if pp_run query teams-status --active >/dev/null 2>&1; then
-  echo "⚠️  CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS detected. GSD's multi-agent orchestration is not validated under claude-code agent-teams and may stall (a subagent's completion can fail to route to the orchestrator). Recommend disabling agent-teams for GSD workflows. See https://github.com/open-gsd/pp-core/issues/1355" >&2
+  echo "⚠️  CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS detected. pp-core's multi-agent orchestration is not validated under claude-code agent-teams and may stall (a subagent's completion can fail to route to the orchestrator). Recommend disabling agent-teams for GSD workflows. See https://github.com/open-gsd/pp-core/issues/1355" >&2
 fi
 ```
 
@@ -600,7 +600,7 @@ Display banner:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► SECURITY THREAT MODEL REQUIRED (ASVS L{SECURITY_ASVS})
+ pp-core ► SECURITY THREAT MODEL REQUIRED (ASVS L{SECURITY_ASVS})
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Each PLAN.md must include a <threat_model> block.
@@ -764,7 +764,7 @@ Pattern mapper activation is owned by the `pattern-mapper` capability's `plan:pr
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PATTERN MAPPING PHASE {X}
+ pp-core ► PATTERN MAPPING PHASE {X}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning pattern mapper... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -818,7 +818,7 @@ Continue to step 8.
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PLANNING PHASE {X}
+ pp-core ► PLANNING PHASE {X}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning planner... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -1174,7 +1174,7 @@ Use AskUserQuestion for each gap (or batch if multiple gaps).
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► VERIFYING PLANS
+ pp-core ► VERIFYING PLANS
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning plan checker... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -1373,7 +1373,7 @@ BOUNCE_SCRIPT=$(pp_run query config-get workflow.plan_bounce_script 2>/dev/null
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► BOUNCING PLANS (External Refinement)
+ pp-core ► BOUNCING PLANS (External Refinement)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Script: ${BOUNCE_SCRIPT}
@@ -1639,7 +1639,7 @@ fi
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► AUTO-ADVANCING TO EXECUTE
+ pp-core ► AUTO-ADVANCING TO EXECUTE
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Plans ready. Launching execute-phase...
@@ -1656,7 +1656,7 @@ The `--no-transition` flag tells execute-phase to return status after verificati
 - **PHASE COMPLETE** → Display final summary:
   ```
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-   GSD ► PHASE ${PHASE} COMPLETE ✓
+   pp-core ► PHASE ${PHASE} COMPLETE ✓
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
   Auto-advance pipeline finished.
@@ -1680,7 +1680,7 @@ Route to `<offer_next>` (existing behavior).
 Output this markdown directly (not as a code block):
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PHASE {X} PLANNED ✓
+ pp-core ► PHASE {X} PLANNED ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **Phase {X}: {Name}** — {N} plan(s) in {M} wave(s)

package/pp-core/workflows/plan-review-convergence.md

@@ -56,7 +56,7 @@ pp-plan-review-convergence is disabled (workflow.plan_review_convergence=false).
 This feature automates the plan→review→replan loop using external AI reviewers.
 Enable it with:
 
-  gsd config-set workflow.plan_review_convergence true
+  pp config-set workflow.plan_review_convergence true
 
 Then re-run: /pp:plan-review-convergence {PHASE}
 ```
@@ -86,7 +86,7 @@ Display startup banner:
 
 ```text
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PLAN CONVERGENCE — Phase {phase_number}
+ pp-core ► PLAN CONVERGENCE — Phase {phase_number}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
  Reviewers: {REVIEWER_FLAGS}
@@ -263,7 +263,7 @@ pp_run state planned-phase --phase "${PHASE}" --name "${phase_name}" --plans "${
 Display:
 ```text
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► CONVERGENCE COMPLETE ✓
+ pp-core ► CONVERGENCE COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
  Phase {phase_number} converged in {cycle} cycle(s).

package/pp-core/workflows/plant-seed.md

@@ -73,7 +73,7 @@ Write `.planning/seeds/SEED-{PADDED}-{slug}.md` immediately with sensible defaul
 id: SEED-{PADDED}
 status: dormant
 planted: {ISO date}
-planted_during: {current milestone/phase from STATE.md, or "unknown" if not in a GSD project}
+planted_during: {current milestone/phase from STATE.md, or "unknown" if not in a pp-core project}
 trigger_when: when relevant
 scope: unknown
 ---

package/pp-core/workflows/pr-branch.md

@@ -1,7 +1,7 @@
 <purpose>
 Create a clean branch for pull requests by filtering out transient .planning/ commits.
 The PR branch contains only code changes and structural planning state — reviewers
-don't see GSD transient artifacts (PLAN.md, SUMMARY.md, CONTEXT.md, RESEARCH.md, etc.)
+don't see pp-core transient artifacts (PLAN.md, SUMMARY.md, CONTEXT.md, RESEARCH.md, etc.)
 but milestone archives, STATE.md, ROADMAP.md, and PROJECT.md changes are preserved.
 
 Uses git cherry-pick with path filtering to rebuild a clean history.
@@ -34,7 +34,7 @@ fi
 Display:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► PR BRANCH
+ pp-core ► PR BRANCH
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Branch: {CURRENT_BRANCH}

package/pp-core/workflows/profile-user.md

@@ -66,7 +66,7 @@ Display consent screen:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD > PROFILE YOUR CODING STYLE
+ pp-core > PROFILE YOUR CODING STYLE
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Claude starts every conversation generic. A profile teaches Claude
@@ -404,7 +404,7 @@ If nothing changed: Display "No changes detected -- your profile is already up t
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD > PROFILE COMPLETE ✓
+ pp-core > PROFILE COMPLETE ✓
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Your profile:    $HOME/.claude/pp-core/USER-PROFILE.md

package/pp-core/workflows/progress.md

@@ -752,5 +752,5 @@ Then for each failed check, add a concrete next action:
 - [ ] What's next clearly explained
 - [ ] Smart routing: /pp:execute-phase if plans exist, /pp:plan-phase if not
 - [ ] User confirms before any action
-- [ ] Seamless handoff to appropriate gsd command
+- [ ] Seamless handoff to appropriate pp-core command
       </success_criteria>

package/pp-core/workflows/quick.md

@@ -1,5 +1,5 @@
 <purpose>
-Execute small, ad-hoc tasks with GSD guarantees (atomic commits, STATE.md tracking). Quick mode spawns pp-planner (quick mode) + pp-executor(s), tracks tasks in `.planning/quick/`, and updates STATE.md's "Quick Tasks Completed" table.
+Execute small, ad-hoc tasks with pp-core guarantees (atomic commits, STATE.md tracking). Quick mode spawns pp-planner (quick mode) + pp-executor(s), tracks tasks in `.planning/quick/`, and updates STATE.md's "Quick Tasks Completed" table.
 
 With `--full` flag: enables the complete quality pipeline — discussion + research + plan-checking + verification. One flag for everything.
 
@@ -17,7 +17,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-phase-researcher — Researches technical approaches for a phase
 - pp-planner — Creates detailed plans from phase scope
 - pp-plan-checker — Reviews plan quality before execution
@@ -60,7 +60,7 @@ Display banner based on active flags:
 If `$FULL_MODE` (all phases enabled — `--full` or all granular flags):
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► QUICK TASK (FULL)
+ pp-core ► QUICK TASK (FULL)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Discussion + research + plan checking + verification enabled
@@ -69,7 +69,7 @@ If `$FULL_MODE` (all phases enabled — `--full` or all granular flags):
 If `$DISCUSS_MODE` and `$VALIDATE_MODE` (no research):
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► QUICK TASK (DISCUSS + VALIDATE)
+ pp-core ► QUICK TASK (DISCUSS + VALIDATE)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Discussion + plan checking + verification enabled
@@ -78,7 +78,7 @@ If `$DISCUSS_MODE` and `$VALIDATE_MODE` (no research):
 If `$DISCUSS_MODE` and `$RESEARCH_MODE` (no validate):
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► QUICK TASK (DISCUSS + RESEARCH)
+ pp-core ► QUICK TASK (DISCUSS + RESEARCH)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Discussion + research enabled
@@ -87,7 +87,7 @@ If `$DISCUSS_MODE` and `$RESEARCH_MODE` (no validate):
 If `$RESEARCH_MODE` and `$VALIDATE_MODE` (no discuss):
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► QUICK TASK (RESEARCH + VALIDATE)
+ pp-core ► QUICK TASK (RESEARCH + VALIDATE)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Research + plan checking + verification enabled
@@ -96,7 +96,7 @@ If `$RESEARCH_MODE` and `$VALIDATE_MODE` (no discuss):
 If `$DISCUSS_MODE` only:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► QUICK TASK (DISCUSS)
+ pp-core ► QUICK TASK (DISCUSS)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Discussion phase enabled — surfacing gray areas before planning
@@ -105,7 +105,7 @@ If `$DISCUSS_MODE` only:
 If `$RESEARCH_MODE` only:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► QUICK TASK (RESEARCH)
+ pp-core ► QUICK TASK (RESEARCH)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Research phase enabled — investigating approaches before planning
@@ -114,7 +114,7 @@ If `$RESEARCH_MODE` only:
 If `$VALIDATE_MODE` only:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► QUICK TASK (VALIDATE)
+ pp-core ► QUICK TASK (VALIDATE)
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Plan checking + verification enabled
@@ -263,7 +263,7 @@ Skip this step entirely if NOT `$DISCUSS_MODE`.
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► DISCUSSING QUICK TASK
+ pp-core ► DISCUSSING QUICK TASK
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Surfacing gray areas for: ${DESCRIPTION}
@@ -390,7 +390,7 @@ Skip this step entirely if NOT `$RESEARCH_MODE`.
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► RESEARCHING QUICK TASK
+ pp-core ► RESEARCHING QUICK TASK
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Investigating approaches for: ${DESCRIPTION} (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -518,7 +518,7 @@ Skip this step entirely if NOT `$VALIDATE_MODE`.
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► CHECKING PLAN
+ pp-core ► CHECKING PLAN
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning plan checker... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -858,7 +858,7 @@ Skip this step entirely if NOT `$VALIDATE_MODE`.
 Display banner:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► VERIFYING RESULTS
+ pp-core ► VERIFYING RESULTS
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Spawning verifier... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
@@ -993,7 +993,7 @@ Display completion output:
 ```
 ---
 
-GSD > QUICK TASK COMPLETE (VALIDATED)
+pp-core > QUICK TASK COMPLETE (VALIDATED)
 
 Quick Task ${quick_id}: ${DESCRIPTION}
 
@@ -1011,7 +1011,7 @@ Ready for next task: /pp:quick ${GSD_WS}
 ```
 ---
 
-GSD > QUICK TASK COMPLETE
+pp-core > QUICK TASK COMPLETE
 
 Quick Task ${quick_id}: ${DESCRIPTION}
 

package/pp-core/workflows/reapply-patches.md

@@ -2,7 +2,7 @@
 
 Invoked by `/pp:update --reapply` (`commands/gsd/update.md`).
 
-After a GSD update wipes and reinstalls files, this workflow merges user's previously saved local modifications back into the new version. Uses three-way comparison (pristine baseline, user-modified backup, newly installed version) to reliably distinguish user customizations from version drift.
+After a pp-core update wipes and reinstalls files, this workflow merges user's previously saved local modifications back into the new version. Uses three-way comparison (pristine baseline, user-modified backup, newly installed version) to reliably distinguish user customizations from version drift.
 
 **Critical invariant:** Every file in `pp-local-patches/` was backed up because the installer's hash comparison detected it was modified. The workflow must NEVER conclude "no custom content" for any backed-up file — that is a logical contradiction. When in doubt, classify as CONFLICT requiring user review, not SKIP.
 
@@ -112,14 +112,14 @@ Read `backup-meta.json` from the patches directory.
 No local patches found. Nothing to reapply.
 
 Local patches are automatically saved when you run /pp:update
-after modifying any GSD workflow, command, or agent files.
+after modifying any pp-core workflow, command, or agent files.
 ```
 Exit.
 
 ## Step 2: Determine baseline for three-way comparison
 
-The quality of the merge depends on having a **pristine baseline** — the original unmodified version of each file from the pre-update GSD release. This enables three-way comparison:
-- **Pristine baseline** (original GSD file before any user edits)
+The quality of the merge depends on having a **pristine baseline** — the original unmodified version of each file from the pre-update pp-core release. This enables three-way comparison:
+- **Pristine baseline** (original pp-core file before any user edits)
 - **User's version** (backed up in `pp-local-patches/`)
 - **New version** (freshly installed after update)
 
@@ -160,7 +160,7 @@ Extract the pristine version from the matched commit:
 git -C "$CONFIG_DIR" show "${BASELINE_COMMIT}:${file_path}"
 ```
 
-**Why this matters:** `git log --diff-filter=A` returns the commit that *first added* the file, which is the wrong baseline on repos that have been through multiple GSD update cycles. The `pristine_hashes` field in `backup-meta.json` records the SHA-256 of the file as it existed in the pre-update GSD release — matching against it finds the correct baseline regardless of how many updates have occurred.
+**Why this matters:** `git log --diff-filter=A` returns the commit that *first added* the file, which is the wrong baseline on repos that have been through multiple pp-core update cycles. The `pristine_hashes` field in `backup-meta.json` records the SHA-256 of the file as it existed in the pre-update pp-core release — matching against it finds the correct baseline regardless of how many updates have occurred.
 
 ### Option B: Pristine snapshot directory
 Check if a `pp-pristine/` directory exists alongside `pp-local-patches/`:
@@ -328,7 +328,7 @@ Recommended: manually inspect each file above and confirm your customisations su
 ```text
 HALT: {DRIFTED_COUNT} file(s) were skipped by the deterministic verifier because the
 pp-pristine/ snapshot on disk does not match the hash recorded in backup-meta.json
-(pristine drift — the snapshot was refreshed to a newer GSD version after the backup
+(pristine drift — the snapshot was refreshed to a newer pp-core version after the backup
 was captured).  These files were NOT diff-verified; their user customisations may or
 may not have survived the merge.
 

package/pp-core/workflows/remove-workspace.md

@@ -1,5 +1,5 @@
 <purpose>
-Remove a GSD workspace, cleaning up git worktrees and deleting the workspace directory.
+Remove a pp-core workspace, cleaning up git worktrees and deleting the workspace directory.
 </purpose>
 
 <required_reading>

package/pp-core/workflows/review.md

@@ -61,7 +61,7 @@ Reviewer-selection precedence:
 4. No key + no flags → all detected reviewers
 
 `review.default_reviewers` behavior:
-- Value must be a non-empty array of slug strings (configured via `gsd config-set review.default_reviewers '["gemini","codex"]'`)
+- Value must be a non-empty array of slug strings (configured via `pp config-set review.default_reviewers '["gemini","codex"]'`)
 - Unknown slugs warn and are ignored
 - Known-but-undetected slugs emit an info note and are ignored
 - If all configured reviewers are unavailable, fail with an actionable message
@@ -613,7 +613,7 @@ If a CLI or local server fails, log the error and continue with remaining review
 Display progress:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► CROSS-AI REVIEW — Phase {N}
+ pp-core ► CROSS-AI REVIEW — Phase {N}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 ◆ Reviewing with {CLI}... done ✓
@@ -737,7 +737,7 @@ Display summary:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- GSD ► REVIEW COMPLETE
+ pp-core ► REVIEW COMPLETE
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Phase {N} reviewed by {count} AI systems.

package/pp-core/workflows/scan.md

@@ -8,7 +8,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-codebase-mapper — Maps project structure and dependencies
 </available_agent_types>
 

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

@@ -7,7 +7,7 @@ Verify threat mitigations for a completed phase. Confirm PLAN.md threat register
 </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-security-auditor — Verifies threat mitigation coverage
 </available_agent_types>
 
@@ -33,7 +33,7 @@ Resolve active step hooks from `VERIFY_POST_HOOKS_JSON` where `kind == "step"` a
 
 If no active secure-phase step hook exists: exit with "Security enforcement disabled. Enable via /pp:settings."
 
-Display banner: `GSD > SECURE PHASE {N}: {name}`
+Display banner: `pp-core > SECURE PHASE {N}: {name}`
 
 ## 1. Detect Input State
 
@@ -140,7 +140,7 @@ Handle return:
 **ENFORCING GATE:** If `threats_open > 0` after all options exhausted (user did not accept, not all verified closed):
 
 ```
-GSD > PHASE {N} SECURITY BLOCKED
+pp-core > PHASE {N} SECURITY BLOCKED
 {K} threats open — phase advancement blocked until threats_open: 0
 ▶ Fix mitigations then re-run: /pp:secure-phase {N}
 ▶ Or document accepted risks in SECURITY.md and re-run.
@@ -158,7 +158,7 @@ pp_run query commit "docs(phase-${PHASE}): add/update security threat verificati
 
 **Secured (threats_open: 0):**
 ```
-GSD > PHASE {N} THREAT-SECURE
+pp-core > PHASE {N} THREAT-SECURE
 threats_open: 0 — all threats have dispositions.
 ▶ /pp:validate-phase {N}    validate test coverage
 ▶ /pp:verify-work {N}       run UAT

package/pp-core/workflows/session-report.md

@@ -61,7 +61,7 @@ mkdir -p .planning/reports
 Write `.planning/reports/SESSION_REPORT.md` (or `.planning/reports/YYYYMMDD-session-report.md` if previous reports exist):
 
 ```markdown
-# GSD Session Report
+# pp-core Session Report
 
 **Generated:** [timestamp]
 **Project:** [from PROJECT.md title or directory name]