Release: v0.20.4

Preflight is now optional, not a gate

The Implementation Readiness marker that forced a pending prompt on every work plan has been removed. Preflight (/recipe-prepare-implementation) is now a genuinely optional, advisory step.

• Removed the Implementation Readiness work-plan marker and the gates that read it across the build and implement recipes.
• recipe-prepare-implementation presents its Readiness Report in-session instead of writing it into the (ephemeral) work plan.
• recipe-plan suggests preflight only when the plan has E2E skeletons or references not-yet-created commands/interfaces.

Test skeletons stay green under static gates

• acceptance-test-generator now emits comment-only skeletons — no imports of unbuilt modules, no test-runner syntax — so a freshly committed skeleton passes typecheck/lint/build. The implementing task adds the executable code, keeping the Red→Green transition within a single commit.

Other

• Clarified the integration-e2e behavior-verification criterion to target the implemented test.