TRPCError code mismatch when client and server share AppRouter type but handle NOT_FOUND differently
Error code propagation inconsistency When a server procedure throws a TRPCError with code NOT_FOUND , the client receives an error object whose shape reflects the mapped HTTP status. However, the inferred type from the shared AppRouter does not appear to constrain the possible error codes per procedure, allowing the client to handle only a subset of codes at