fix(tui): resolve Claude Code config import failure on clean Windows install

[wuxiaoweisjz]

Summary

Fixes the issue where Peri fails to import API keys from Claude Code configuration on Windows, causing the TUI to be blocked by the setup wizard.

Two related fixes:

1. Env var injection: inject_env_from_settings() now falls back from config.env to top-level env when the standard schema is absent. This handles config files written by migration or manual creation that use the top-level format.

2. Setup wizard bypass: needs_setup() no longer unconditionally blocks when providers is empty — it now checks LlmProvider::from_env() first, allowing users with environment-variable-only configuration to enter the conversation.

Changes:

File	What
peri-tui/src/main.rs	Extracted inject_env_from_file() shared helper for config + Claude path loading; added inject_env_from_claude_settings() for ~/.claude/settings.json env import; needs_setup check now considers from_env(); added 9 unit tests
peri-tui/src/app/setup_wizard/ops.rs	needs_setup() checks LlmProvider::from_env() when providers empty
peri-tui/src/app/setup_wizard/setup_wizard_test.rs	Updated tests for new env-aware logic

Test plan

• cargo check -p peri-tui — passes
• cargo test -p peri-tui -- --test-threads=1 — 660 tests pass
• End-to-end: peri -p "say hello" — LLM responds correctly
• End-to-end: peri (TUI mode) — no setup wizard blockage, provider detected

Root cause

On Windows 10, ~/.peri/settings.json had env at the top level ({"env": {...}}) instead of the expected {"config": {"env": {...}}}. This caused:

• inject_env_from_settings() to silently fail (looked for config.env)
• LlmProvider::from_config() to return None (no config.providers)
• needs_setup() to unconditionally show the wizard (empty providers → true)

The Claude Code settings path did not help because the env had already been migrated to Peri's config (in the wrong format) by the setup wizard.

🤖 Generated with Claude Code Best