Summary
#1238's Windows-path fix in packages/opencode/src/altimate/native/connections/registry.ts:128 (resolveStorePaths, using path.isAbsolute() || path.win32.isAbsolute()) is explicitly documented in its own commit message as "by-inspection only — no Windows CI." resolveStorePaths is currently unexported and has zero test references anywhere in packages/opencode/test/ — registry-env-loading.test.ts doesn't cover Windows paths either.
path.win32.isAbsolute() behavior is deterministic and fully testable on any OS (no Windows runner required) — this is a cheap gap to close.
Proposed fix
Export resolveStorePaths (or a thin testable wrapper) and add a unit test asserting a C:\...-style global-config path is left absolute rather than mangled by path.resolve, per the gap the #1238 commit already identified in its own message.
Provenance
Found during the v0.11.0 stable release's Tech Lead persona review.
Summary
#1238's Windows-path fix inpackages/opencode/src/altimate/native/connections/registry.ts:128(resolveStorePaths, usingpath.isAbsolute() || path.win32.isAbsolute()) is explicitly documented in its own commit message as "by-inspection only — no Windows CI."resolveStorePathsis currently unexported and has zero test references anywhere inpackages/opencode/test/—registry-env-loading.test.tsdoesn't cover Windows paths either.path.win32.isAbsolute()behavior is deterministic and fully testable on any OS (no Windows runner required) — this is a cheap gap to close.Proposed fix
Export
resolveStorePaths(or a thin testable wrapper) and add a unit test asserting aC:\...-style global-config path is left absolute rather than mangled bypath.resolve, per the gap the#1238commit already identified in its own message.Provenance
Found during the v0.11.0 stable release's Tech Lead persona review.