Preserved project links during adopt resync

[TIR44]

Summary

• Passed the project root through the shared adopt apply path before re-syncing targets.
• Kept project-mode symlink and merge target re-sync on the existing relative-link behavior instead of falling back to absolute links.
• Updated the project adopt integration assertion to resolve symlink targets across macOS /private/var canonicalization and to catch absolute project links on non-Windows platforms.

Context

Follow-up to #181. The failing macOS integration job showed TestAdoptProject_MigratesAndResyncs comparing a canonical /private/var/... symlink target against the logical temp path. While checking that, I found the re-sync path was passing an empty project root, so project-mode adopt created absolute links instead of the portable relative links used by normal project sync.

Tests

• go build -o bin/skillshare ./cmd/skillshare
• SKILLSHARE_TEST_BINARY=$PWD/bin/skillshare go test -v -race ./tests/integration -run '^TestAdoptProject_MigratesAndResyncs$' -count=1
• go test ./internal/adopt ./cmd/skillshare -run 'TestApply_ReSyncHonorsCopyMode|TestAdopt' -count=1
• make test-unit

[gemini-code-assist]

Code Review

This pull request introduces support for passing the ProjectRoot through the adopt process, enabling project-mode sync behavior such as portable relative links for targets under the project root. Feedback on the changes suggests explicitly handling errors from filepath.EvalSymlinks in the integration tests to prevent potential silent test failures where unresolved paths could erroneously match.

[gemini-code-assist]

Ignoring the errors returned by filepath.EvalSymlinks can lead to silent test failures or false positives. If both evaluations fail (e.g., if the paths do not exist), they will both return empty strings (""), causing the assertion got != want to evaluate to false and the test to pass.

Instead, explicitly check and handle the errors returned by filepath.EvalSymlinks.

		got, err := filepath.EvalSymlinks(got)
		if err != nil {
			t.Fatalf("failed to resolve got symlink: %v", err)
		}
		want, err := filepath.EvalSymlinks(filepath.Join(projectSource, "firecrawl"))
		if err != nil {
			t.Fatalf("failed to resolve want symlink: %v", err)
		}

[TIR44]

Addressed the EvalSymlinks error handling review note in 0baecf2. Re-ran the targeted macOS-relevant integration test locally:

SKILLSHARE_TEST_BINARY=$PWD/bin/skillshare go test -v -race ./tests/integration -run '^TestAdoptProject_MigratesAndResyncs$' -count=1