v3.1.0 — Per-Task Plan Decomposition

Per-Task Plan Decomposition

pocket-structuring now decomposes every plan into execution-plan/index.md + per-task files under execution-plan/tasks/, instead of passthrough below 7 tasks — phase manifests (phase-N.md) are written only when phaseCount > 1. structure gains --reset to rebuild layout and replace log.json when execution progress exists (explicit, discards state); --force now only rebuilds + reconciles when there's no execution progress, refusing otherwise, and always refreshes the log's pipeline marker (PIPELINE 3 → 4) when it rebuilds.

Fixed

• A log.json that exists but fails to parse is now refused (LOG_JSON_UNPARSEABLE) instead of being silently treated as absent — --reset is the explicit way to discard it.
• --force rebuilding a log no longer leaves a stale pipeline marker behind (previously could strand a plan with a mismatched pipeline generation and confusing recovery advice).
• index.md's Task Index table now renders in phase-group (execution) order instead of numeric task ID, matching phase-N.md and the Execution Flow diagram. For single-phase plans this is also the order log init uses to seed dispatch state — a plan authored out of numeric sequence now dispatches in the order it's written, not by ID.

Before updating

This release bumps the pipeline generation (PIPELINE 3 → 4). Plans that already have a log.json are unaffected until you next run structure against them — a plain run repairs/no-ops without touching state; a source-plan change with execution progress still requires --force or --reset as before.

If a plan's log.json reports PIPELINE_TOO_OLD with a numeric (not absent) pipeline marker, pin npx -y pocketto-pi@3.0.1 to finish it under the old pipeline, then update once it's closed.

Full detail: README § Migrating to 3.1.0.

npm: https://www.npmjs.com/package/pocketto-pi/v/3.1.0

v3.0.1 — Release Artifact Cleanup

Completes the v3 cleanup by removing deprecated skill references and aligning every published artifact.

Fixed

• Removed remaining pocket-review and pocket-correction references from active documentation.
• Rebuilt bundled .skill archives from their canonical source directories.
• Updated the pipeline diagram and inventory to all 13 current skills.
• Standardized per-task review artifacts as <task_id>-review.json.
• Added the required blocked_category contract for REVIEW_BLOCKED reports.
• Added regression coverage for documentation, archives, diagrams, and review contracts.

npm: https://www.npmjs.com/package/pocketto-pi/v/3.0.1

v3.0.0 — In-Loop Build Cycle

In-Loop Build Cycle

pocket-development now runs a read-only audit per task (spec compliance, code quality, QUALITY BAR, verified refactor) and one phase-level pass before handoff — no more shallow gate → separate pocket-review round-trip. pocket-review and pocket-correction skills are deprecated (CLI correction machinery retained and reused).

Breaking: plans started under an older pipeline are refused, not repaired. log.json gains a pipeline-version marker; a log without one (or with a lower one) makes any state-changing CLI command exit non-zero rather than continuing on stale assumptions. CONTRACT stays at 2 — the JSON shape is unchanged, only behavior is breaking.

Before updating

Close any in-flight plan first. A log.json from before 3.0.0 will be refused by the new CLI on the next state-changing command — nothing is lost (the refusal writes nothing), but the plan is stuck until you act.

If you're already updated and stuck mid-plan:

• CLI: run the plan out with npx -y pocketto-pi@2.4.4 … until it closes.
• Plugin (Claude Code): don't run /plugin update or reinstall until the plan closes — the marketplace entry tracks latest commit with no version pin, so there's no version to roll back to.

Once closed, drop the pin and update normally — new plans initialize with the current pipeline marker.

Full detail: README § Migrating to 3.0.0.