Current state: renderPluginAt in sdk/frontend/testing.tsx builds its own QueryClient and never seeds a session, so a plugin test that wants a screen rendered for a specific tier has to build its own provider instead. That path works today through seedSession and the canned sessions the testing module exports, so nothing is blocked, but the common case costs a provider every time. Proposal: give renderPluginAt an optional user parameter defaulting to the canned admin session. Trigger: the first plugin test that actually renders a screen differently for an admin and for a member.
Current state: renderPluginAt in sdk/frontend/testing.tsx builds its own QueryClient and never seeds a session, so a plugin test that wants a screen rendered for a specific tier has to build its own provider instead. That path works today through seedSession and the canned sessions the testing module exports, so nothing is blocked, but the common case costs a provider every time. Proposal: give renderPluginAt an optional user parameter defaulting to the canned admin session. Trigger: the first plugin test that actually renders a screen differently for an admin and for a member.