ComradeSwarog 597c690dbc fix(opencode): add Windows junction fallback for node_modules EPERM symlink error (#187) ... On Windows 10 without Developer Mode, the OpenCode runtime fails to create a symlink from shared-cache/config-node_modules to the profile's node_modules directory. The EPERM error blocks the entire OpenCode provider catalog, leaving it unavailable. Changes: - New openCodeWindowsNodeModulesJunction module that pre-creates a Windows directory junction (no Developer Mode required) before the runtime call when an EPERM symlink error is detected - On Windows, loadView and loadProviderDirectory now detect EPERM symlink errors, extract the profile ID, create the junction, and retry the runtime command once before falling back to the error response - Updated diagnostic hints to accurately reflect that the runtime does not yet include junction fallback, and that the next runtime update will include it - Added unit tests for the junction module and retry behavior		2026-05-28 13:08:54 +03:00
..
codex-runtime-installer	fix(ci): stabilize runtime release checks	2026-05-22 00:55:29 +03:00
runtime-provider-management	fix(opencode): add Windows junction fallback for node_modules EPERM symlink error (#187)	2026-05-28 13:08:54 +03:00
tmux-installer	fix: harden team runtime liveness	2026-04-24 20:52:26 +03:00