feat: create an order from a quote

[korsvanloon]

Fixes #412.

Endpoints

Endpoint	Draft
POST /{projectKey}/orders/quotes	OrderFromQuoteDraft
POST /{projectKey}/me/orders/quotes	MyOrderFromQuoteDraft

Both land on a new OrderRepository.createFromQuote; the /me route maps { id, version, quoteStateToAccepted } onto the full draft.

Behaviour

As the issue notes, the guards are the part worth having:

• The quote must be in Pending state → InvalidOperation (400) otherwise.
• The quote must not be past its validTo → InvalidOperation (400) otherwise.
• The draft version is checked against the stored quote → ConcurrentModification (409) on a stale version.
• An unknown quote reference → ReferencedResourceNotFound (400), which is what resolving a reference in a draft returns everywhere else in the mock.
• quoteStateToAccepted: true moves the quote to Accepted and bumps its version; without it the quote is left alone.

The order carries the quote's line items, custom line items, prices and taxed price as-is — nothing is re-priced, which is the point of converting rather than rebuilding a cart — plus quote as a reference and origin: "Quote".

Note on validation

The draft is validated in the repository rather than through a generated zod schema: scripts/generate-schemas.ts needs the commercetools-api-reference checkout, which I do not have here, so OrderFromQuoteDraft is not in src/schemas/generated. Happy to add it to DRAFT_SCHEMAS and regenerate if you'd prefer that.

Coverage

order-from-quote.test.ts: create, quoteStateToAccepted transitioning the quote, the quote left untouched without it, non-pending quote, expired quote, stale version, unknown quote, and the /me variant.

Full suite: 798 passing.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0c6462b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@labdigital/commercetools-mock	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[korsvanloon]

Addressed the note on validation — you were right that this should go through the generator rather than be hand-rolled.

• OrderFromQuoteDraft and MyOrderFromQuoteDraft added to DRAFT_SCHEMAS/DRAFT_FILE_MAP and generated with pnpm generate:schemas.
• Both routes now validate through those schemas in strict mode, the way AbstractService.post does for the standard create route. The hand-written if (!draft?.quote?.id …) check is gone.
• Two tests for it: a draft without a quote reference, and a /me draft without a version.

Two things worth a look when reviewing:

1. Spec drift. Running the generator regenerated everything, and the spec has moved since the last run. That drift is in this PR: optional fields on extensions (dependencies, expansionPaths, additionalContext), inventory entries (stockLevels, reservationExpirationInMinutes), shipping methods (stores, carrier) and stores (storefront), plus reservation/variant reference type ids and the ReserveOnCart inventory mode. All additive and optional. Happy to split it into its own PR if you'd rather keep this one narrow.
2. The generator emits unformatted output, so pnpm generate:schemas on its own produces a diff against every committed file. It needs pnpm biome format --write src/schemas/generated afterwards. I noted that in AGENTS.md along with the rest of the workflow, but folding the format step into the generator script itself would make the diff honest by default.