Summary

The Windows CI (test (windows-latest)) is consistently failing on packages/paths/src/env-integration.test.ts:136 — scenario 3: "nothing from CWD .env leaks to subprocess".

The test expects a value to be defined but receives undefined on Windows. This failure is present on main, dev, and all feature branches.

Reproduction

The failure occurs in every recent "Test Suite" workflow run on Windows:

• main branch: https://github.com/coleam00/Archon/actions/runs/24303365337
• dev branch: https://github.com/coleam00/Archon/actions/runs/24303334117

Ubuntu and Docker builds pass consistently.

Error

@archon/paths:test | error: expect(received).toBeDefined()
@archon/paths:test | Received: undefined
@archon/paths:test | at <anonymous> (packages/paths/src/env-integration.test.ts:136:32)
@archon/paths:test | (fail) env isolation integration > scenario 3: nothing from CWD .env leaks to subprocess

Impact

The Windows test failure causes SIGINT to propagate to other package test runs (@archon/workflows, @archon/server, @archon/core, @archon/adapters, @archon/cli), making the entire Windows CI red even though those packages have no failures.

Likely Cause

The env isolation test spawns a subprocess and checks that CWD .env keys are stripped. On Windows, the subprocess env handling or path resolution likely differs, causing the expected key to not be found.

Labels

• bug
• ci
• paths