support 2026-07 version

[1415003719]

Summary

Regenerate the SDK for API version 2026-07 (16.0.0) with AfterShip/sdk-generator from OAS production/2026-07.

Changes vs 15.0.0 (2026-01)

All changes match the 2026-07 migration guide — no breaking type renames:

• Base URL → /tracking/2026-07/, SDK_VERSION → 16.0.0
• New models: TrackingShipmentDimensions, TrackingMultiPieceInfo (+Pieces/Type), TrackingProofOfDelivery, TrackingShipmentDirection (also on create/update requests), TrackingReturnShipment, TrackingForwardShipment
• New fields: Checkpoint::$hash, customers[].id
• New delivery sub-statuses need no code change (subtag is a plain string)

Verification

• php -l on all files passes; php-cs-fixer applied (PHP 8.1)
• All 16 OAS operations exercised against the live API with a test org key: full tracking write lifecycle (create → get → update → mark-completed → retrack → delete), couriers, courier-connections, EDD predict/predict-batch (both returned real 2xx predictions); all responses and business errors deserialized into SDK types, no parse failures
• New-field round-trip verified: shipment_direction (deserialized as TrackingShipmentDirection::FORWARD enum) and customers[].id written and read back; test data cleaned up

Known issue (pre-existing, not a regression)

Enum-typed request fields serialize incorrectly via Base::toRequestArray() (missing BackedEnumNormalizer), so e.g. passing CreateTrackingRequestShipmentDirection::FORWARD is rejected by the API — raw strings work since the props are untyped. Base.php is byte-identical to 15.0.0 (same issue existed with MarkTrackingCompletedByIdRequestReason); tracked as a generator template fix follow-up.

🤖 Generated with Claude Code