Competitor prices and checkout retries stay inside your workspace

Two shared caches on the server were keyed by a name your integration chose rather than by your workspace. Both are now scoped to the workspace that made the request.

• Competitor price observations loaded through the built-in observation source for a pricing cycle are read and written only within your workspace, whatever key your connector settings use.
• Checkout retries: an Idempotency-Key you send when creating a checkout session only ever matches your own earlier requests. Reusing a key is still safe, and a different body with your own key still returns 409.

Nothing changes in how you call either feature.