fix(cli): detect slot recipes by defineSlotRecipe helper

[tobigumo]

Problem

When adding a slot-recipe component (e.g. tabs) via the CLI, the recipe is registered under recipes instead of slotRecipes in the generated theme/recipes/index.ts:

// generated (wrong)
export const recipes = { tabs }   // ← slot recipe lands here
export const slotRecipes = {}

Root cause

packages/cli/src/utils/install.ts decides the recipe type with:

type: file.content.includes('slotRecipe') ? 'slotRecipe' : 'recipe',

Recipe sources define slot recipes with defineSlotRecipe (capital S). Because String.prototype.includes is case-sensitive, the lowercase slotRecipe substring is never present in "defineSlotRecipe", so the check returns false, the type collapses to 'recipe', and updateRecipeIndex routes it into recipes.

This affects every slot recipe (all 42 published *-recipe items), not just tabs. The downstream routing in recipes.ts is correct; only the type detection in install.ts was wrong.

Fix

Match the helper name defineSlotRecipe instead:

type: file.content.includes('defineSlotRecipe') ? 'slotRecipe' : 'recipe',

All 42 slot recipes call defineSlotRecipe, and no regular recipe contains that string as a substring (defineRecipe ⊄ defineSlotRecipe), so the two-way classification stays correct.

Verification

Ran the real updateRecipeIndex against the actual published registry contents:

• tabs-recipe (slot) — old logic → recipes (reproduces the bug); fixed → slotRecipes ✅
• button-recipe (defineRecipe) — both old and fixed → recipes ✅ (no regression)