fix: use $PSScriptRoot instead of MyCommand.Path in install.ps1

[attolee]

this fixes a powershell source install error where $MyInvocation.MyCommand.Path can be null in some environments.

using $PSScriptRoot is the standard and more reliable way to resolve the script directory on powershell 3.0+.

fixes the failure where install.ps1 -Source can raise:
ParentContainsErrorRecordException: The property Path cannot be found

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d9e1607c-e220-4bf6-927e-6a3f9de0d649

📥 Commits

Reviewing files that changed from the base of the PR and between acec13c and b28a3d5.

📒 Files selected for processing (1)

• scripts/install.ps1

---

📝 Walkthrough

Walkthrough

The PowerShell install script now uses $PSScriptRoot directly to determine the script directory instead of deriving it from $MyInvocation.MyCommand.Path. This single-line change simplifies the approach to locating the repository root path during script execution.

Changes

Cohort / File(s)	Summary
Script Path Resolution scripts/install.ps1	Changed $scriptDir initialization from Split-Path -Parent $MyInvocation.MyCommand.Path to $PSScriptRoot for more direct directory detection.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 The script hops faster now, you see,
No winding path through MyInvocation tree,
$PSScriptRoot knows where it ought to be,
A simpler hop, more direct and free! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title mentions replacing 'System.Management.Automation.InvocationInfo.MyCommand.Path' but omits the replacement variable, making it incomplete and unclear what the fix actually introduces.	Update the title to explicitly state what $PSScriptRoot is being used for, e.g., 'fix: use $PSScriptRoot instead of MyCommand.Path in install.ps1' for clarity.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 unit tests (beta)

• Create PR with unit tests

---

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.}

[chumyin]

thanks for your efforts here! have approved workflows to run, after all CIs are green, it looks good to be merged.

[attolee]

merge dev to solve cargo audit failure.

[chumyin]

hey @attolee, thanks for chasing this powershell edge case. i rebased the branch onto current dev, cleaned up the pr title/body so the variable is explicit, and rechecked the thread plus the final diff. the switch to $PSScriptRoot looks right here, so im merging this now. nice catch.