@pareto4/pp-core 1.5.3 → 1.6.0

package/pp-core/workflows/ship.md

@@ -106,6 +106,29 @@ Verify the work is ready to ship:
      ```
 
    If no active security `ship:pre` gate hook is present (security enforcement off), skip this check silently.
+
+   **Generic `check.query` gate enforcement (capability-driven).**
+
+   For each active entry in `activeHooks` where `kind == "gate"` and a `check.query` is present (covers any capability-registered query gate, e.g. the `pareto-stack` platform-drift gates — skip entries already handled by the `security` predicate branch above):
+
+   ```bash
+   GATE_RESULT=$(pp_run check ${hook.check.query} --raw)
+   CHECK_EXIT=$?
+   ```
+
+   - If `CHECK_EXIT` is non-zero or output is unparseable: if `hook.onError == "skip"` (the default for all capability-registered query gates), log a warning and continue to the next hook.
+   - Read `status` from `GATE_RESULT`:
+     - If `hook.blocking == true` and `status == "block"` → halt the ship with `PARETO_DRIFT_SHIP_GATE_BLOCKED`:
+       ```
+       ⚠ Ship gate blocked: {hook.check.query} reports a drift condition that exceeds the configured threshold.
+       Pinned: {GATE_RESULT.pinned} — Latest: {GATE_RESULT.latest}
+       Update .platform-bindings.json or adjust the block threshold before shipping.
+       ```
+     - If `hook.blocking == false`, or `status` is `warn`, `pass`, or `inert` → emit an advisory line for non-trivial statuses (`warn` only) and continue:
+       ```
+       ℹ Ship gate advisory ({hook.check.query}): {status}{GATE_RESULT.severity ? ` — ${GATE_RESULT.severity} drift detected` : ''} (non-blocking or below blocking threshold). Continuing.
+       ```
+     - If `status` is `pass` or `inert`: continue silently.
 </step>
 
 <step name="push_branch">
@@ -419,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, dispatch with `Skill(skill="gsd-${ref.skill}", args="${PHASE_NUMBER} --auto ${GSD_WS}")` (Prepend `gsd-` to `ref.skill`).
+- 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.
 
 Each dispatch is best-effort: if it errors, record a warning and continue — never re-raise (`onError: skip`).
 </step>

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

@@ -642,6 +642,7 @@ Agent(
 
 <files_to_read>
 - {phase_dir}/*-PLAN.md (Plans to verify)
+- CLAUDE.md (Project instructions, if exists — follow project-specific guidelines and coding conventions)
 </files_to_read>
 
 ${AGENT_SKILLS_CHECKER}

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

@@ -272,6 +272,7 @@
   "tests/plan-phase-ui-redirect.test.cjs :: source-text-is-the-product",
   "tests/plan-review-convergence.test.cjs :: source-text-is-the-product",
   "tests/planner-decomposition.test.cjs :: source-text-is-the-product",
+  "tests/pp-init.test.cjs :: source-text-is-the-product",
   "tests/planner-language-regression.test.cjs :: source-text-is-the-product",
   "tests/playwright-ui-verify.test.cjs :: source-text-is-the-product",
   "tests/policy-160-route0-resume.test.cjs :: source-text-is-the-product",