fix: make env-integration test cross-platform (Windows CI)

[Wirasm]

Summary

• Check for Windows env var equivalents (Path instead of PATH, USERPROFILE instead of HOME) in scenario 3 assertions
• On Windows, spreading process.env into a plain object preserves the OS-native casing (Path), and HOME doesn't exist (USERPROFILE is the equivalent)

Closes #1128

Test plan

• Windows CI passes on this PR
• Ubuntu/Docker CI still green

Summary by CodeRabbit

• Tests
  • Made environment-variable assertions tolerant of platform differences in casing and key names (e.g., Windows vs. Unix), using fallbacks when needed.
  • Improves cross-platform test reliability so CI and local runs on Windows, macOS, and Linux consistently validate shell-inherited variables without false failures.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d5dddb6e-2ba0-48d4-8188-d2e1d4520dac

📥 Commits

Reviewing files that changed from the base of the PR and between 2b5f23c and b812fa0.

📒 Files selected for processing (1)

• packages/providers/src/claude/provider.test.ts

---

📝 Walkthrough

Walkthrough

Updated two tests to make environment-variable assertions tolerant of platform differences by accepting Windows-style environment keys (e.g., Path, USERPROFILE) alongside Unix-style keys (PATH, HOME) using nullish/coalesce checks.

Changes

Cohort / File(s)	Summary
Paths env integration test packages/paths/src/env-integration.test.ts	Adjusted scenario 3 assertions to read subprocessEnv.PATH ?? subprocessEnv.Path and subprocessEnv.HOME ?? subprocessEnv.USERPROFILE before asserting definedness, making the check cross-platform.
Claude provider test packages/providers/src/claude/provider.test.ts	Made subprocess env comparisons platform-casing tolerant by deriving envPath/envHome and processPath/processHome with ?? fallbacks (PATH ⇄ Path, HOME ⇄ USERPROFILE) before asserting equality.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through envs both near and far,
Found PATH and Path beneath the same star,
HOME or USERPROFILE, whichever you send,
I shrug and accept them — rabbit-approved blend. 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete and lacks many required template sections (UX Journey, Architecture Diagram, Label Snapshot, Change Metadata, Validation Evidence, Security Impact, Compatibility, Human Verification, Side Effects, and Rollback Plan).	Complete the PR description by filling in all required template sections, particularly Validation Evidence, Security Impact, and other mandatory sections outlined in the repository template.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the primary change: making the env-integration test cross-platform to fix Windows CI failures.
Linked Issues check	✅ Passed	The PR correctly addresses the Windows CI failure by making env assertions cross-platform compatible with Windows environment variable naming (Path/USERPROFILE instead of PATH/HOME), directly resolving issue #1128.
Out of Scope Changes check	✅ Passed	All changes are within scope: two test files adjusted for Windows environment variable compatibility, with no modifications to exported/public entities or unrelated functionality.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/windows-env-test-1128

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}