feat: recipe UX variants — V1 (4-button), V2 (2-button), V3 (step-by-step)

[aaronbrezel]

Summary

Three A/B test UX variant panels for the Document Summarization recipe, implemented as throwaway prototypes on a dedicated branch. Each explores a different interaction pattern before we settle on an official recipe UX direction.

• V1 (4-button) — Explicit prep step required; Test and Cook fire inference directly without going through ConfigureAIRunPanel; Configure AI is the escape hatch. 5-state machine: idle → prepping → prepped → testing/cooking → prepped.
• V2 (2-button) — No prep step; Test silently preps + runs first 10 rows; Cook silently preps + runs all rows. Designed to feel like a true one-click pipeline.
• V3 (didactic step-by-step) — Three named stages: Import Files → Import Prompt → Run. Steps 2 and 3 unlock sequentially. Editing Step 1 re-locks Step 3 only (Step 2 prompt config is independent of folder choice).

Architecture

• 3 new panel files (recipe-v1.ts, recipe-v2.ts, recipe-v3.ts) plus test files
• 3 new recipe entries in RECIPES with variant field for routing
• buildRunTemplate exported from recipe.ts for variant panels to import
• RecipesListPanel routes by definition.variant; falls back to "recipe" for originals
• Output column created at inference time via runBatchAI → findOrCreateColumn, not during prep
• No server code touched; all variant code is self-contained and removable

Test Plan

• 530 tests pass (npm test)
• Deploy to add-on: npm run deploy
• Open SSI Tools → Run AI → Browse Recipes — verify V1, V2, V3 entries appear
• V1: Prep → columns appear in sheet; Test → AI output in row 2; Cook → all rows get output; Configure AI → opens settings panel
• V2: Test → silently preps + runs first 10 rows; Cook → silently preps + runs all rows
• V3: Import Files (Step 1) → Step 2 unlocks; Import Prompt (Step 2) → Step 3 unlocks; Test/Cook/Configure AI work as expected
• Editing any input in V3 re-locks Step 3 but not Step 2

Removal Plan

To remove a variant: delete its panel file, its recipe entry in recipes.ts, its registration line in sidebar-entry.ts, and its routing case in recipes-list.ts. No server code is touched.

🤖 Generated with Claude Code