fix(javascript): distinguish resolver discovery from module loading

Preserve load and resolve operations through semantic facts, worker transfer and graph Evidence. Only loads propagate executable ownership. Project ambient member writes and escapes through the shared path- and site-aware mutation owner; retain source literals, bases and uncertainty. Cover ownership and mutation boundaries through CLI and MCP.

src/application/javascript/JavaScriptArtifactGraphFindings.ts

@@ -205,6 +205,7 @@ const addReference = (
       ? null
       : resolveReference(context, input.file.path, input.value, input.coverage);
   if (
+    input.value.operation === "load" &&
     (input.value.kind === "static-import" ||
       input.value.kind === "dynamic-import" ||
       input.value.kind === "require") &&
@@ -222,6 +223,7 @@ const addReference = (
     resolved !== null &&
     resolved.path !== null &&
     resolved.file !== null &&
+    input.value.operation === "load" &&
     (input.value.kind === "static-import" ||
       input.value.kind === "dynamic-import" ||
       input.value.kind === "require")
@@ -305,6 +307,7 @@ const addReference = (
     relation: resolved?.file?.kind === "native-addon" ? "loads" : "imports",
     properties: {
       kind: input.value.kind,
+      operation: input.value.operation,
       specifier: input.value.specifier,
       expression: input.value.expression,
       resolution_base_path: input.value.resolution_base_path ?? null,