@pareto4/pp-core 1.7.1 → 1.8.1

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

@@ -1,6 +1,6 @@
 # Reapply Local Patches Workflow
 
-Invoked by `/pp:update --reapply` (`commands/gsd/update.md`).
+Invoked by `/pp:update --reapply` (`commands/pp-update.md`).
 
 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.
 

package/pp-core/workflows/ship.md

@@ -442,7 +442,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, apply **prefix-aware resolution**: if `ref.skill` already begins with a runtime-resolvable stem (e.g. `pareto-`), dispatch it verbatim with no phase/workspace args — `Skill(skill=ref.skill)` — because the skill handles its own invocation (e.g. `pareto-sync-board` triggers bare). Otherwise, fall back to the existing stem behavior: `Skill(skill="gsd-${ref.skill}", args="${PHASE_NUMBER} --auto ${GSD_WS}")`. This prevents a `pareto-` skill from being incorrectly prefixed to a non-existent `gsd-pareto-*` name.
+- If `ref.skill` is set, apply **prefix-aware resolution**: if `ref.skill` already begins with a runtime-resolvable stem (e.g. `pareto-`), dispatch it verbatim with no phase/workspace args — `Skill(skill=ref.skill)` — because the skill handles its own invocation (e.g. `pareto-sync-board` triggers bare). Otherwise, fall back to the existing stem behavior: `Skill(skill="pp-${ref.skill}", args="${PHASE_NUMBER} --auto ${GSD_WS}")`. This prevents a `pareto-` skill from being incorrectly prefixed to a non-existent `pp-pareto-*` name.
 
 Each dispatch is best-effort: if it errors, record a warning and continue — never re-raise (`onError: skip`).
 </step>

package/pp-core/workflows/thread.md

@@ -1,6 +1,6 @@
 # Thread Workflow
 
-Invoked by `/pp:thread` (`commands/gsd/thread.md`).
+Invoked by `/pp:thread` (`commands/pp-thread.md`).
 
 Create, list, close, or resume persistent context threads for cross-session work.
 

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

@@ -467,7 +467,7 @@ Resolve active step hooks from `VERIFY_POST_HOOKS_JSON` where `kind == "step"` a
 If an active secure-phase step hook exists AND `SECURITY_FILE` is empty, dispatch the registry-provided skill stem:
 
 ```
-Skill(skill="gsd-${ref.skill}", args="{phase}")
+Skill(skill="pp-${ref.skill}", args="{phase}")
 ```
 
 After the skill returns, refresh `SECURITY_FILE`:
@@ -619,12 +619,13 @@ On return:
 <step name="verify_gap_plans">
 **Verify fix plans with checker:**
 
-Display:
+Run this Bash command to emit the branded Validate stage banner (renders on stderr, auto-degrades on non-TTY — do NOT print an inline ASCII banner, that would double-print):
+```bash
+pp_run banner validate "VERIFYING"
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- pp-core ► VERIFYING FIX PLANS
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
+Then announce the spawn:
+```
 ◆ Spawning plan checker... (runs in a subagent — no output until it returns, ~1–5 min; expected, not a freeze)
 ```
 

package/scripts/lint-allow-test-rule-refs.allowlist.json

@@ -260,6 +260,7 @@
   "tests/orphaned-hooks.test.cjs :: structural-regression-guard",
   "tests/package-legitimacy-gate.test.cjs :: source-text-is-the-product",
   "tests/parallel-dependent-plans.test.cjs :: source-text-is-the-product",
+  "tests/pareto-skill-bundle.install.test.cjs :: source-text-is-the-product",
   "tests/path-replacement.test.cjs :: source-text-is-the-product",
   "tests/phase-dependency-levels.test.cjs :: source-text-is-the-product",
   "tests/phase.test.cjs :: source-text-is-the-product",