fix(orders): tighten shipping address, line, and item schema constraints

[leofischer]

Summary

Aligns the OpenAPI schemas for order shipping address, shipping line, and line item with the validations actually enforced by payments-api's v200 param sanitizers. These fields were documented as free-form strings with no required markers or length limits, despite the API rejecting them.

Targets release/v2.3.0.

Changes

Consolidation (shared address component)

• New schemas/customers/shipping_contact_address.yml; the create and update shipping-contact schemas now $ref it instead of each carrying a duplicated inline address block. The shipping_contact used by orders (order_request, order_update_request, split_order_request) already routes through these schemas, so the order shipping address is covered by the same definition.

Required markers (matching ShippingContacts::Validator#validate_on_create)

• address.street1, address.postal_code, address.country are now required on create; the update path leaves them optional.

Format / descriptions

• Documented the MX rule (country == MX -> 5-digit postal code) on postal_code.
• Added per-field descriptions to the address fields (previously only country had one).

Length constraints (matching StringValidator)
The sanitizer uses strict comparisons: length >= less_than -> too_long, length <= greater_than -> too_short. So a 250-char value is rejected; the maximum accepted length is 249, and minLength = greater_than + 1.

• maxLength: 249 on all sanitizer-bounded strings: address street1/street2/city/state/country; shipping line carrier/tracking_number/method; line-item name/description/brand/sku and tags[] items (create + update).
• minLength: street1/country 2; carrier/tracking_number/method/name/description 3; brand 2; sku 1; tags[] items 2; tags minItems: 1.
• postal_code keeps maxLength: 250: the sanitizer only type-checks it, so its only length cap is the model-level validates :zip, length: { maximum: 250 } (inclusive).

Build

• Regenerated _build/api.yaml via make merge; all $refs resolve and the create-path required markers survive bundling.

Notes

• The 249 vs 250 split is intentional and correct: 249 reflects the sanitizer's exclusive < 250; postal_code's 250 reflects the inclusive model bound.
• No Jira ticket was provided; consistent with other doc-fix PRs in this repo.

🤖 Generated with Claude Code

[atlantis-conekta]

Error: This repo is not allowlisted for Atlantis.