tRPC Context Scope Gap After Router Merges

Investigate how tRPC's context middleware propagates least‑privilege scope claims when procedures are versioned or merged across router boundaries, given the framework's lack of a declarative permission model.

tRPC does not enforce token expiration or automatically reject expired credentials; developers must implement custom validation, and error handling treats authentication failures identically to other errors, which can mask security violations in client logs.

• How should scope claims be synchronized when a router is split into multiple files?
• What error code or signal should indicate an expired or revoked token without breaking existing error handling?
• Can tRPC provide a built‑in mechanism for least‑privilege enforcement that remains compatible with custom middleware?