Delivery workflow

1. Select only a canonical Task whose Feature implementation gate and Focus admission are evidenced.
2. Confirm dependencies, owner capability, target version, acceptance outcomes, and blockers.
3. Move the Task to IN_PROGRESS from verified implementation activity.
4. Implement the smallest reviewable slice and record tests against the Task and linked requirements.
5. Move the Task to TO_BE_RELEASED only when implementation is complete and release handoff criteria are met.
6. Move it to DONE only after its release boundary or explicit non-releasable completion evidence passes.

For the current MVP, Harbor publication, GitOps onboarding, and deployed PayPal Sandbox verification remain release-boundary evidence. Production payment enablement is outside project authority.