Commerce Sprint Plan

This plan is the execution baseline for the commerce profile after the docs and module-packaging foundation sprint.

Objective

Ship operational commerce capabilities without breaking profile isolation or contract/audience governance.

Scope

• Purchase/order operations for admin teams.
• Provider reliability and operational visibility.
• React Email templates for transactional events.
• Strong env/config validation for provider adapters.

Sequence

Phase 1: Core operations

1. C2 Order operations admin slice.
2. C3 Purchase state operations (retry/cancel/refund intent boundaries).
3. C4 Billing webhook operations UI.

Phase 2: Provider reliability

1. C5 React Email foundation.
2. C6 Provider env hardening.
3. C7 Provider health telemetry.

Phase 3: Developer velocity and governance

1. C8 Frontend decomposition completion pass.
2. C9 Scaffolding v2 for contract/procedure/feature hooks.
3. C10 Operational runbooks.
4. C11 Audience policy audit.
5. C12 Sprint closeout.

Non-negotiable constraints

• Contract-first oRPC for new endpoints.
• Audience projection split (public, client, admin) for every endpoint.
• No direct provider SDK usage outside infrastructure adapters.
• Feature routes/screens remain orchestration-only.

Completion criteria

Each task is complete when:

1. Code is merged to the sprint branch.
2. Structural gates pass (typecheck, depcruise, contract/projection checks).
3. Canonical docs are updated in apps/docs/content/docs.
4. docs/roadmap.md status and completion date are updated.