Strawberry GraphQL 0.327.2

Apply the Python 3 prompt first. These rules cover Strawberry GraphQL 0.327.2 schemas, framework integrations, permissions, validation, caches, Relay, federation, uploads, and streaming transports.

Version and runtime scope

• Apply these rules to Strawberry GraphQL 0.327.2 on a maintained Python release satisfying >=3.10,<4.0. Lock strawberry-graphql and a graphql-core release inside the declared >=3.2.0,<3.4.0 range in the lock file, and test them together with the selected integration extra, host framework, and server.
• Move to Strawberry's newest release when a fix ships: Strawberry publishes each fix in its next release at the head of the 0.x line and doesn't patch older minors, and a release can change defaults, so rerun the deployment verification tests on every upgrade.
• Preserve this release's fail-closed synchronous permission checks, bounded parser and validation cache defaults, and legacy WebSocket completion cleanup; keep regression tests for these behaviors when changing dependencies or integrations.

Authentication context and authorization

• Authenticate through the host framework and put the verified principal and tenant in get_context or FastAPI's context_getter; Strawberry's permission hooks do not authenticate users automatically. Cover ordinary HTTP, uploads, WebSocket operations, and SSE.
• Keep the principal stable for the authenticated request or connection. Async HTTP batches and operations on one WebSocket share their context; do not overwrite its user, tenant, or transaction state for an individual operation.
• Attach