A doctor who also owns a clinic runs two environments, and a subscription
belongs to an environment, not to the user. The panel treated it as the
user's: the subscription query was keyed ['subscription-my'] with no
context, and switching environments never touched the react-query cache. So
upgrading the clinic left the personal practice showing the clinic's plan
with its feature-gated menu items unlocked, and vice versa.
The query key now carries the active dbUuid, and the context switch clears
the whole cache — every cached response belongs to the environment it was
fetched in, not just this one.
The API was already correct: DualEnvironmentSubscriptionTest pins that
granting one environment leaves the other on free.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
