test(wizard): sweep tests/test_wizard.py for DeepSeek V3 → V4 provider names #228

Context

PR #226 migrates the bundled config.yaml and the routing-touching test files from deepseek-chat / deepseek-reasoner (V3.2) to deepseek-v4-flash / deepseek-v4-pro. tests/test_wizard.py was deliberately deferred and excluded with --ignore=tests/test_wizard.py because:

• 79 occurrences of the legacy V3 provider names — wide blast radius.
• The wizard tests use those names as fixtures both for "user picked X" and for asserting "wizard suggested X". Bulk find/replace would change the assertions but might not match the wizard's actual current suggestions, masking real regressions behind a green test.

Scope

1. Audit each tests/test_wizard.py reference to the legacy names — is it a fixture (operator chose X) or an assertion (wizard recommended X)?
2. Update fixtures verbatim: deepseek-chat → deepseek-v4-flash, deepseek-reasoner → deepseek-v4-pro, deepseek/chat → deepseek/v4-flash, deepseek/reasoner → deepseek/v4-pro.
3. For assertions: re-run the wizard against a fresh config and confirm the new V4 names are what the wizard actually suggests now. If not, open a separate issue for the wizard's recommendation logic.
4. Remove the --ignore=tests/test_wizard.py from any CI pipelines / dev scripts that have it.

Pointers

• faigate/wizard.py — wizard logic that emits the recommendations.
• packages/providers/catalog.v1.json — recommendation source.
• faigate/assets/metadata/catalog.v1.json — bundled catalog already has deepseek-chat → deepseek-v4-flash recommended_model edge, so the wizard's V3 suggestions may already auto-resolve.

Why deferred from PR #226

The PR was scoped to the routing-layer fix + the user's config.yaml migration. Sweeping 79 wizard references in the same PR would have made the diff harder to review and risked hiding semantic test changes inside a bulk rename.

🤖 Generated with Claude Code