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.