Skip to content

feat(install): support Windows PowerShell installs - #4

Closed
Mineru98 wants to merge 2 commits into
release/bootstrapfrom
Q00/codex/windows-powershell-install
Closed

feat(install): support Windows PowerShell installs#4
Mineru98 wants to merge 2 commits into
release/bootstrapfrom
Q00/codex/windows-powershell-install

Conversation

@Mineru98

@Mineru98 Mineru98 commented Jul 1, 2026

Copy link
Copy Markdown
Owner

Summary

  • add Windows PowerShell install support
  • ignore local generated artifacts in .gitignore

Verification

  • git status --short --branch
  • git log -1 --oneline --decorate

@Mineru98 Mineru98 closed this Jul 1, 2026
Mineru98 added a commit that referenced this pull request Jul 21, 2026
Three Windows-only mix test failures surfaced by windows-ci.yml, none of
which are production bugs:

- Ports (#1 StdioTest, #5 HelperPortTest): the port test helper spawned
  `elixir` (elixir.bat on Windows), whose batch shim breaks the port stdout
  pipe ("The pipe is being closed") and adds boot latency. Drive the echo/
  shell programs with `erl` directly instead, passing operations as a base64
  term (no escaping). Behaviour is identical on Linux (41 tests, 0 failures).
- Registry skill paths (#2/#3/#4): the code returns Path.expand'd skill paths
  (forward slashes, lowercased drive on Windows); tests compared against raw
  Path.join values. Wrap the expected values in Path.expand, matching the
  existing source_id assertions. Idempotent on Linux.
- Frontmatter CRLF (Ouro-labs#6): the parser already handles CRLF; the failure came
  from the .exs fixture being checked out CRLF on Windows. Add .gitattributes
  (eol=lf) so text files are LF on every platform.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant