Problem

Several contributor-facing commands are effectively validated only through bash-style environments. Recent examples included commands that worked in Git Bash/CI but failed in native PowerShell due to shell assumptions.

Why It Matters

• Native Windows contributors discover shell-specific failures late.
• CI can stay green while a common local workflow is broken.
• Regressions around PowerShell support are easy to reintroduce when scripts assume Unix utilities.

Suggested Scope

Add a lightweight Windows PowerShell smoke job for a small set of high-value contributor commands, such as:

• pnpm check:docs
• pnpm build:strict-smoke
• other shell-sensitive commands that are expected to work for local contributors

Acceptance Criteria

• At least one CI lane runs selected contributor commands under native PowerShell, not only bash.
• Shell-specific failures are caught in CI before users report them.
• The job stays intentionally small so it does not duplicate the full existing Windows matrix.