fix: support current UCP schema generation

[sakinaroufid]

Summary

Fix js-sdk model generation so it works with the current upstream UCP schema layout while keeping the existing generated SDK API intact.

Context

The SDK generator was built around the older split schema layout (*.create_req, *.update_req, *_resp). Upstream UCP has moved to unified schemas under source/, so generation in this repo had drifted away from the actual source of truth.

This change brings the generator back in line with upstream without forcing a consumer-facing API rewrite in js-sdk.

What changed

• updated generate_models.sh to handle both the legacy split layout and the current upstream source/ layout
• added a projection step that derives the legacy request/update/response inputs from the unified upstream schemas
• kept the existing quicktype-based generation flow in place after that projection step
• normalized duplicated quicktype output so the generated export surface stays stable
• regenerated src/spec_generated.ts

Why this approach

There were two obvious ways to deal with the upstream schema changes:

1. switch the SDK over to the unified upstream model directly
2. preserve the SDK’s current generated surface and adapt the generator

This takes the second approach. The problem here is generator drift, not that the SDK suddenly needs a new public API.

Validation

Ran locally:

• npm run generate -- /tmp/ucp-spec-test
• npm run build:noEmit
• npm run build

Notes

The largest part of the change is the projection layer. That is where the compatibility logic now lives, and it is what allows js-sdk to keep generating the same kind of output from the current upstream schema model.

[sakinaroufid]

@wry-ry tagging you here as I have submitted PR to fix schema generation

• @nearlyforget

[sakinaroufid]

Clarification: this PR fixes the repo-side schema generation issues that were causing drift against the current upstream UCP schema model while preserving the legacy generated API shape.

Thanks!

[artemii-karkusha]

We hit this in production while integrating with real merchants from https://merchants.awesomeucp.com/ (Everlane, Monos, etc.). The current spec_generated.ts breaks capability detection — capabilities parsed as an array returns empty when merchants send the spec-compliant object format, so checkout/fulfillment/discount are never detected.

Filed #19 with details and reproduction steps.

Would be great to get this merged — it's currently the main blocker for any JS client connecting to live UCP merchants.

[matijagrcic]

Can this be merged and new version of the package published. @igrigorik @westeezy

wrong spec -

js-sdk/src/spec_generated.ts

Lines 1074 to 1078 in fd95d6f

	export const UcpClassSchema = z.object({
	capabilities: z.array(CapabilityDiscoverySchema),
	services: z.record(z.string(), UcpServiceSchema),
	version: z.string(),
	});

schema - https://github.com/Universal-Commerce-Protocol/ucp/blob/release/2026-04-08/source/schemas/ucp.json

[cusell-google]

Please take a look at the styling/lint errors on https://github.com/Universal-Commerce-Protocol/js-sdk/actions/runs/24565943451/job/72880712623?pr=16 and fix them. Otherwise LG. Thanks @sakinaroufid for fixing the js-sdk!

[sakinaroufid]

Fixed! Thank you for your review! @cusell-google

[sakinaroufid]

Terrific! Thanks for merging @wry-ry

[matijagrcic]

can we get a new release/package published?

[wcielen]

this is exactly what I've been looking for