fix(tests): use junction symlinks for Windows compatibility

[Hrishi75]

Summary

• Pass "junction" as the third argument to symlinkSync in two test files so they no longer fail with EPERM on Windows for users without admin privileges or Developer Mode
• Matches the existing pattern in production code at packages/plugins/workspace-worktree/src/index.ts where junctions are already used as a Windows fallback

Why

On Windows, symlinkSync(target, path) defaults to a directory symlink, which requires SeCreateSymbolicLinkPrivilege — i.e. Administrator privileges or Developer Mode. For non-admin contributors without Developer Mode, this fails with EPERM: operation not permitted, symlink .... Junctions are functionally equivalent for directory targets in these tests and do not require elevation.

The Node.js docs confirm the type argument is ignored on non-Windows OSes, so Linux/macOS behavior is unchanged.

Files changed

• packages/core/src/__tests__/project-resolver.test.ts:218 — test "matches a flat local config launched from a symlinked checkout"
• packages/web/src/__tests__/projects-route.test.ts:227 — test "POST /api/projects > reconnects to the existing project ID when the same path is registered again"

Test plan

• Reverted the change locally on Windows 11; both tests fail with EPERM at the symlinkSync call sites
• Re-applied the change; both tests pass
• pnpm --filter @aoagents/ao-core test — no regressions
• pnpm --filter @aoagents/ao-web test — no regressions
• pnpm typecheck clean
• CI on ubuntu-latest (verifies POSIX behavior unchanged)
• CI on windows-latest

[greptile-apps]

Greptile Summary

This PR fixes two test fixtures that create directory symlinks, passing "junction" as the third argument to symlinkSync so they succeed on Windows without requiring administrator privileges or Developer Mode. The "junction" type argument is ignored on macOS and Linux, so POSIX CI behavior is unchanged.

• packages/core/src/__tests__/project-resolver.test.ts — adds "junction" to the symlinked-checkout fixture at line 218.
• packages/web/src/__tests__/projects-route.test.ts — adds "junction" to the alias-directory fixture at line 227. Both changes match the existing fallback pattern already used in packages/plugins/workspace-worktree/src/index.ts.

Confidence Score: 5/5

Safe to merge — two minimal, targeted one-line fixes that bring test fixtures in line with the established production pattern.

Both changed lines are test-only fixtures that create directory symlinks. Passing "junction" is the correct, well-precedented approach for directory symlinks on Windows; Node.js documents that the argument is ignored on non-Windows platforms, so there is no risk to Linux/macOS CI runs. The fix matches existing production code in the same repo.

No files in the changeset require special attention. A follow-up could address the similar bare symlinkSync call on a directory at packages/plugins/agent-kimicode/src/index.test.ts:1005.

Important Files Changed

Filename	Overview
packages/core/src/tests/project-resolver.test.ts	Adds "junction" type to symlinkSync for the symlinked-checkout test fixture — correct fix for Windows EPERM; non-Windows ignores the argument.
packages/web/src/tests/projects-route.test.ts	Adds "junction" type to symlinkSync for the alias-directory test fixture — same correct pattern as the core change, no behavioral difference on POSIX.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["symlinkSync(target, path, 'junction')"] --> B{Platform?}
    B -->|Windows| C["Creates NTFS junction\n(no admin required)"]
    B -->|macOS / Linux| D["Creates directory symlink\n('junction' argument ignored)"]
    C --> E["Test passes ✓"]
    D --> E

Loading

Comments Outside Diff (1)

1. packages/plugins/agent-kimicode/src/index.test.ts, line 1005 (link)

   Untreated directory symlink — this call creates a directory symlink (real is created with mkdirSync) and will still fail with EPERM on Windows without admin privileges or Developer Mode, the same root cause fixed in the two files changed by this PR. Passing "junction" here would bring it in line with the updated tests and the production pattern in workspace-worktree/src/index.ts. The same pattern appears at lines 1046, 1047, and 1319 in this file, though those targets are .jsonl files rather than directories and would need a different resolution (hardlink or explicit skip).

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: packages/plugins/agent-kimicode/src/index.test.ts
   Line: 1005
   
   Comment:
   **Untreated directory symlink** — this call creates a directory symlink (`real` is created with `mkdirSync`) and will still fail with `EPERM` on Windows without admin privileges or Developer Mode, the same root cause fixed in the two files changed by this PR. Passing `"junction"` here would bring it in line with the updated tests and the production pattern in `workspace-worktree/src/index.ts`. The same pattern appears at lines 1046, 1047, and 1319 in this file, though those targets are `.jsonl` files rather than directories and would need a different resolution (hardlink or explicit skip).
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
packages/plugins/agent-kimicode/src/index.test.ts:1005
**Untreated directory symlink** — this call creates a directory symlink (`real` is created with `mkdirSync`) and will still fail with `EPERM` on Windows without admin privileges or Developer Mode, the same root cause fixed in the two files changed by this PR. Passing `"junction"` here would bring it in line with the updated tests and the production pattern in `workspace-worktree/src/index.ts`. The same pattern appears at lines 1046, 1047, and 1319 in this file, though those targets are `.jsonl` files rather than directories and would need a different resolution (hardlink or explicit skip).

_{Reviews (1): Last reviewed commit: "fix(tests): use junction symlinks for Wi..." | Re-trigger Greptile}