package linthost

import (
  "os"
  "testing"
)

// TestLSPApplySuggestionResolvesLogicalProjectLink verifies suggestion
// discovery and execution use the same physical project boundary while the
// returned WorkspaceEdit keeps the editor's logical document URI.
//
// NativePluginSource runs the lint sidecar from PhysicalProjectRoot but keeps
// the logical URI supplied by an editor that opened a symlink or junction.
// Code-action discovery and execution must resolve both paths consistently
// without rejecting the action, reading a different file, or relaxing the
// outside-project and node_modules guards.
//
//  1. Expose one physical project through a logical directory link.
//  2. Discover and execute a manual suggestion for the logical URI.
//  3. Assert the edit is keyed by that URI and leaves the physical file alone.
//  4. Reuse the captured selection with outside and node_modules URIs and assert
//     both command boundaries still fail closed.
//
// @evidence contracts/testing.md#behavioral-verification Suggestion discovery and execution must return the authored rewrite under the logical URI, leave the physical source intact and reject outside/dependency URIs.
// @evidence contracts/testing.md#independent-expectations The literal prefer-as-const declaration rewrite and original disk bytes are independent answer keys; the editor URI is supplied by the fixture rather than derived from the resolved path.
// @evidence contracts/testing.md#distinguishing-cases A symlinked directory (the shared helper also serves a junction variant owned elsewhere) exposes the project under a logical URI. The suggestion must be keyed by that logical URI and not the physical one; a link to a directory outside the project must be refused with status two and an outside-cwd message, and a link to a node_modules directory must return null, so link resolution cannot widen either boundary. The test skips where a directory symlink cannot be created, which includes Windows accounts without the symlink privilege.
// @evidence contracts/testing.md#execution-ownership Creates a real directory symlink and calls run lsp-code-actions and lsp-execute-command in process through the shared link helper, plus lspProjectTargetOutsideCwd and lspProjectTargetHasSegment directly; no editor or built host is started, and the Windows junction variant is TestLSPApplySuggestionResolvesJunctionProjectLink.
func TestLSPApplySuggestionResolvesLogicalProjectLink(t *testing.T) {
  assertLSPLogicalProjectLink(t, func(t *testing.T, target string, link string) {
    t.Helper()
    if err := os.Symlink(target, link); err != nil {
      t.Skipf("directory symlink unavailable: %v", err)
    }
  })
}