Universal Commerce Protocol: Checkout capability missing

What it detects

A valid UCP profile exists but declares no dev.ucp.shopping.checkout capability.

Why it matters

Discovery without a checkout capability tells an agent the merchant is UCP-aware but still leaves it with no standardized way to actually complete a purchase.

How to fix

- Check the (valid) UCP profile at `/.well-known/ucp` for a `dev.ucp.shopping.checkout` entry under `ucp.capabilities` (the older `dev.ucp.commerce.checkout` name is not the protocol's checkout capability). - Add a `dev.ucp.shopping.checkout` capability entry (`version`, `schema`) served by a binding of your `dev.ucp.shopping` service, per ucp.dev/specification/checkout. - Wire these endpoints to real backend checkout logic — the capability declaration must correspond to a working implementation, not a placeholder. - Verify: `curl` the UCP profile, confirm the checkout capability is present and valid, and exercise the declared checkout endpoint end-to-end (create session → complete order).

References

• Universal Commerce Protocol specification