Create WaveEnv narrowing for WaveConfig View

[Copilot]

The waveconfig WaveEnv narrowing work did not need its own dedicated waveconfig.test.tsx. This change removes that file and leaves the implementation-only changes in place.

• Scope

  • Delete frontend/app/view/waveconfig/waveconfig.test.tsx
  • Keep the waveconfig view/model WaveEnv narrowing intact

• Result

  • Reduces test surface added for the WaveEnv refactor
  • Avoids carrying a bespoke test file for behavior already covered sufficiently elsewhere in the frontend suite

- frontend/app/view/waveconfig/waveconfig.test.tsx

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[cloudflare-workers-and-pages]

Deploying waveterm with    Cloudflare Pages

Latest commit:	608a368
Status:	✅  Deploy successful!
Preview URL:	https://98b03b47.waveterm.pages.dev
Branch Preview URL:	https://copilot-add-waveenv-narrowin.waveterm.pages.dev

View logs

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Overview

This PR refactors the waveconfig view to use WaveEnv narrowing (dependency injection) instead of global imports. This follows the same pattern used elsewhere in the codebase.

Changes Summary

• waveconfig-model.ts: Refactored to use WaveConfigEnv for all dependencies (RPC, atoms, electron API)
• waveconfig.tsx: Added useWaveEnv hook to access environment-specific atoms
• waveconfigenv.ts: New file defining the WaveConfigEnv type

Key Improvements

1. Better testability: Dependencies are now injected rather than imported globally
2. Runtime evaluation: isWindows() is now called at runtime via this.env.isWindows() instead of at module load time
3. Consistent pattern: Follows the WaveEnv narrowing pattern used in other views

Files Reviewed (3 files)

• frontend/app/view/waveconfig/waveconfig-model.ts - No issues
• frontend/app/view/waveconfig/waveconfig.tsx - No issues
• frontend/app/view/waveconfig/waveconfigenv.ts - No issues