feat(installer): detect and update PowerShell profiles on Windows

[rhuanbarreto]

Summary

• Unifies the Windows installer's shell-profile section so both Git Bash and PowerShell profiles are detected and (with consent) updated in a single batched prompt.
• Detect-only — never creates profiles that don't already exist.
• Per-file try/catch around reads and writes so one failed file doesn't abort the whole batch; failures surface as Write-Warning with a "manually append" fallback message.

What's detected

Shell	Path
Git Bash / MSYS2	~/.bashrc, ~/.bash_profile, ~/.profile (first match wins)
PowerShell 5.1	<MyDocuments>/WindowsPowerShell/Microsoft.PowerShell_profile.ps1
PowerShell 7+	<MyDocuments>/PowerShell/Microsoft.PowerShell_profile.ps1

<MyDocuments> is resolved via [Environment]::GetFolderPath('MyDocuments') so OneDrive-redirected Documents folders work correctly.

Why

The existing installer already updated the Windows User PATH (registry) and Git Bash profiles, but skipped PowerShell's own $PROFILE system entirely. The User PATH update covers PowerShell on new sessions in the common case, but adding $PROFILE lines is a useful belt-and-suspenders for:

• Locked-down corporate machines where group policy strips User PATH writes
• Custom $PROFILEs that override $env:PATH
• Symmetry with how Git Bash already gets its profile updated

Test plan

• PowerShell AST parse clean ([System.Management.Automation.Language.Parser]::ParseFile)
• Smoke test against fixture profiles: detection, "already configured" skip, write phase, and read-only-file error path all behave correctly
• bun run validate passes (lint, typecheck, format, 695 tests, 23/23 ADR checks, build:check)
• Manual test on a fresh Windows VM with no existing PowerShell profile (should be skipped) and with existing profile (should be detected and updated after Y)
• Manual test on a Windows machine with OneDrive-redirected Documents folder

Notes

A non-obvious gotcha caught during development: install.ps1 has no UTF-8 BOM, so PowerShell 5.1 reads it as ANSI/Windows-1252 and breaks on multi-byte characters like em-dashes. All comments and strings in the installer must stay ASCII. Captured in agent memory.

[cloudflare-workers-and-pages]

Deploying archgate-cli with    Cloudflare Pages

Latest commit:	91a2ec7
Status:	✅  Deploy successful!
Preview URL:	https://57d71b47.archgate-cli.pages.dev
Branch Preview URL:	https://claude-condescending-perlman.archgate-cli.pages.dev

View logs