This pull request refactors how the RecipeRuntime type is used throughout the codebase, improving type inference and developer ergonomics when working with recipes. The main change is to use type inference and the as const satisfies RecipeRuntime pattern instead of explicit type annotations, and to introduce a new utility type for extracting variant prop types from a recipe definition. This makes recipe usage more type-safe and flexible, especially in test and consumer code.

Type inference and type safety improvements:

• Updated all test and consumer code to define recipe objects using const runtime = { ... } as const satisfies RecipeRuntime instead of explicit : RecipeRuntime type annotations. This enables TypeScript to infer literal types for variants and improves type safety. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35]

• Updated the createRecipe function to be generic over the recipe type, allowing it to infer the correct variant prop types from the recipe definition. The function now accepts a generic parameter and uses the new RecipeVariantProps<R> utility type for its props argument.

Type utility additions:

• Added a new RecipeVariantProps<R> utility type to types.ts that extracts the correct variant prop types from a given recipe definition. This enables better type inference for recipe props, ensuring that only valid variant keys and values are accepted.

Imports and type usage cleanup:

• Updated imports in runtime.ts to include the new RecipeVariantProps type and to reorder imports for clarity.