docs(recipes): Rewrite as scenario-driven workflows

why: Recipes showed raw JSON tool calls that didn't reflect how
developers actually use the tools. Real usage is scenario-driven:
discover existing state, decide what to do, then act.

Refined through brainstorm-and-refine session (9 originals from
Claude/Gemini/GPT, 3 refinement passes, converged at pass 3).

what:
- Replace 10 JSON-heavy recipes with 6 scenario-driven workflows
- Lead with real ~/work/cv Vite/Playwright discovery example
- Each recipe: Situation → Discover → Decide → Act → The non-obvious part
- Tool calls embedded in reasoning narrative, not standalone JSON
- Uses {tool} for badged refs, {toolref} for inline prose refs
- All params verified against source across 3 refinement passes
- Closes with "What to read next" linking to prompting and gotchas

Author: tony