gitnexus 1.6.6-rc.99 → 1.6.6

package/dist/core/ingestion/languages/swift/query.js

@@ -0,0 +1,194 @@
+/**
+ * Tree-sitter query for Swift scope captures (RFC §5.1).
+ *
+ * Captures the structural skeleton the generic scope-resolution
+ * pipeline consumes: scopes (module/class/function), declarations
+ * (class-likes, methods, init, properties), imports, type bindings
+ * (parameter annotations, property/field annotations, constructor
+ * inference, receiver self), and references (call sites, member calls).
+ *
+ * Swift specifics that shape this query (all verified against
+ * tree-sitter-swift 0.7.1 live s-expressions):
+ *
+ *   - `class`, `struct`, AND `extension` all parse to a single node
+ *     type `class_declaration`. They are distinguished by the `name:`
+ *     field node type: class/struct name is a bare `(type_identifier)`,
+ *     while an extension's name field wraps the extended type in a
+ *     `(user_type (type_identifier))`. The capture below grabs all
+ *     three under `@scope.class` + `@declaration.class`; the captures
+ *     orchestrator (`captures.ts`) re-tags extensions via the
+ *     user_type discriminator so extension members hoist onto the
+ *     extended type.
+ *   - `protocol_declaration` is its own node; its bodyless method
+ *     requirements are `protocol_function_declaration` (NOT
+ *     `function_declaration`).
+ *   - `init_declaration` has no `name:` field — identity is the `init`
+ *     keyword. The captures layer synthesizes its `@declaration.name`.
+ *   - Inside a `parameter`, BOTH the label and the type use the field
+ *     name `name:` — disambiguate by child node type (simple_identifier
+ *     = label, user_type = type). Parameter type bindings are therefore
+ *     synthesized in `captures.ts`, not matched here.
+ *   - A labeled call argument wraps its label in a dedicated
+ *     `value_argument_label` node.
+ *   - `self` is its own node `self_expression`; a `self.member()` call
+ *     is `call_expression > navigation_expression(target: self_expression,
+ *     suffix: navigation_suffix > simple_identifier)`.
+ *   - `import_declaration` carries the module path as an `(identifier
+ *     (simple_identifier)+)` — one `simple_identifier` per dotted
+ *     segment. `@testable` and other attributes surface as a leading
+ *     `(modifiers (attribute (user_type (type_identifier))))`.
+ *
+ * Exposes lazy `Parser` and `Query` singletons so callers don't pay
+ * tree-sitter init cost per file.
+ */
+import Parser from 'tree-sitter';
+import Swift from 'tree-sitter-swift';
+const SWIFT_SCOPE_QUERY = `
+;; ── Scopes ──────────────────────────────────────────────────────────
+(source_file) @scope.module
+
+;; class / struct / extension all parse to class_declaration; the
+;; captures orchestrator splits extensions out via the user_type
+;; name discriminator.
+(class_declaration) @scope.class
+(protocol_declaration) @scope.class
+
+(function_declaration) @scope.function
+(protocol_function_declaration) @scope.function
+(init_declaration) @scope.function
+(deinit_declaration) @scope.function
+
+;; ── Declarations — types ────────────────────────────────────────────
+;; class / struct: name is a bare type_identifier.
+(class_declaration
+  name: (type_identifier) @declaration.name) @declaration.class
+
+;; extension: name is (user_type (type_identifier)). Captured separately
+;; so captures.ts can re-tag it as an extension of the wrapped type.
+(class_declaration
+  name: (user_type) @declaration.name) @declaration.extension
+
+(protocol_declaration
+  name: (type_identifier) @declaration.name) @declaration.interface
+
+;; ── Declarations — methods / init / properties ──────────────────────
+(function_declaration
+  name: (simple_identifier) @declaration.name) @declaration.method
+
+(protocol_function_declaration
+  name: (simple_identifier) @declaration.name) @declaration.method
+
+;; init has no name field — captures.ts synthesizes @declaration.name = "init".
+(init_declaration) @declaration.constructor
+
+(property_declaration
+  name: (pattern
+    bound_identifier: (simple_identifier) @declaration.name)) @declaration.property
+
+;; ── Imports ─────────────────────────────────────────────────────────
+;; Single anchor per import; the captures layer decomposes the module
+;; path (and detects @testable) into @import.kind/source/name markers.
+(import_declaration) @import.statement
+
+;; ── Type bindings — property annotations: \`var owner: Owner\` ─────────
+(property_declaration
+  name: (pattern
+    bound_identifier: (simple_identifier) @type-binding.name)
+  (type_annotation
+    (user_type (type_identifier) @type-binding.type))) @type-binding.annotation
+
+;; ── Type bindings — stored / local-var constructor inference:
+;; \`let p = Product(...)\` (constructor) and \`let u = getUser()\`
+;; (free-call result; chain-follow resolves getUser → its return type).
+;; property_declaration is the node for both class-level stored
+;; properties AND let/var inside a function body. ───────────────────
+(property_declaration
+  name: (pattern
+    bound_identifier: (simple_identifier) @type-binding.name)
+  value: (call_expression
+    (simple_identifier) @type-binding.type)) @type-binding.constructor
+
+;; \`let u = await fetchUser()\` — unwrap the await wrapper to the call.
+(property_declaration
+  name: (pattern
+    bound_identifier: (simple_identifier) @type-binding.name)
+  value: (await_expression
+    (call_expression
+      (simple_identifier) @type-binding.type))) @type-binding.constructor
+
+;; \`let r = try parseRepo()\` — unwrap the try wrapper to the call.
+(property_declaration
+  name: (pattern
+    bound_identifier: (simple_identifier) @type-binding.name)
+  value: (try_expression
+    (call_expression
+      (simple_identifier) @type-binding.type))) @type-binding.constructor
+
+;; ── Optional binding anchors: if-let / guard-let. In tree-sitter-swift
+;; 0.7.1 these are if_statement / guard_statement with a flat shape — a
+;; \`bound_identifier:\` field for the name plus separate \`condition:\`
+;; children (one of which is the bound value expression). A static .scm
+;; pattern can't pair the name with the value across those sibling
+;; condition fields, so we only ANCHOR the statement here and synthesize
+;; the @type-binding.constructor in captures.ts (synthesizeOptionalBinding)
+;; by walking the node. (A nonexistent if_let_binding node type would throw
+;; TSQueryErrorNodeType and break the WHOLE query — do not reintroduce it.)
+(if_statement
+  bound_identifier: (simple_identifier)) @optional.binding
+(guard_statement
+  bound_identifier: (simple_identifier)) @optional.binding
+
+;; NOTE: parameter-type bindings (\`func f(u: User)\`) and function
+;; return-type bindings (\`func getUser() -> User\`) are NOT matched by
+;; tree-sitter patterns here. Swift's grammar reuses the SAME \`name:\`
+;; field for the function name, each parameter's label, AND the return
+;; type, so a two-\`name:\`-field query cross-assigns and produces garbage
+;; bindings (\`save: save\`). They are synthesized in code instead —
+;; \`captures.ts\` reads the function node via
+;; \`swiftMethodConfig.extractParameters\` / \`extractReturnType\`, which
+;; handle the grammar correctly. (Mirrors how receiver + arity are
+;; synthesized rather than queried.)
+
+;; ── References — field reads: \`u.address\` (member access that is NOT a
+;; call callee or assignment LHS). Emit-side filtering in captures.ts
+;; drops call targets and write LHS so only genuine reads emit ACCESSES.
+(navigation_expression
+  target: (_) @reference.receiver
+  suffix: (navigation_suffix
+    suffix: (simple_identifier) @reference.name)) @reference.read.member
+
+;; ── References — free calls: \`foo(...)\` ─────────────────────────────
+(call_expression
+  (simple_identifier) @reference.name) @reference.call.free
+
+;; ── References — member / method calls: \`obj.method(...)\` ───────────
+;; navigation_expression carries the receiver (target:) and the member
+;; (suffix > navigation_suffix > simple_identifier). \`self\` is a
+;; self_expression; other receivers are simple_identifier / nested
+;; navigation_expression — capture the whole target as @reference.receiver.
+(call_expression
+  (navigation_expression
+    target: (_) @reference.receiver
+    suffix: (navigation_suffix
+      suffix: (simple_identifier) @reference.name))) @reference.call.member
+
+;; ── References — constructor calls handled via @reference.call.free
+;; (a Swift \`Foo(...)\` is a call_expression with a simple_identifier
+;; callee; pickConstructorOrClass in free-call fallback targets the
+;; type's Constructor). No separate object_creation node in Swift.
+`;
+let _parser = null;
+let _query = null;
+export function getSwiftParser() {
+    if (_parser === null) {
+        _parser = new Parser();
+        _parser.setLanguage(Swift);
+    }
+    return _parser;
+}
+export function getSwiftScopeQuery() {
+    if (_query === null) {
+        _query = new Parser.Query(Swift, SWIFT_SCOPE_QUERY);
+    }
+    return _query;
+}

package/dist/core/ingestion/languages/swift/receiver-binding.d.ts

@@ -0,0 +1,40 @@
+/**
+ * Synthesize `@type-binding.self` captures for Swift instance methods —
+ * one for `self` (always on non-static methods inside a type body) and
+ * optionally one for `super` (only on class methods when the enclosing
+ * class declares a superclass).
+ *
+ * Mirrors `languages/csharp/receiver-binding.ts`. tree-sitter can't
+ * express "the implicit receiver of a non-static member of a
+ * class/struct/extension/protocol" via a static `.scm` pattern because
+ * the receiver isn't a parameter — it's implicit. Synthesis in code is
+ * the same approach C#/Python use for `this`/`self`.
+ *
+ * Swift AST facts (tree-sitter-swift 0.7.1, verified):
+ *   - class / struct / extension all parse to `class_declaration`. For
+ *     class/struct the `name:` field is `(type_identifier)`; for an
+ *     extension it is `(user_type (type_identifier))` wrapping the
+ *     EXTENDED type — so `self` in an extension binds to the extended
+ *     type, which is exactly what we want for method dispatch.
+ *   - `protocol_declaration` has a `(type_identifier)` name.
+ *   - the method body is the `body:` field (`function_body`); a bodyless
+ *     `protocol_function_declaration` has no function scope to anchor to.
+ *   - a superclass / conformance is an `(inheritance_specifier
+ *     inherits_from: (user_type (type_identifier)))` child of the
+ *     class_declaration.
+ */
+import type { CaptureMatch } from '../../../../_shared/index.js';
+import { type SyntaxNode } from '../../utils/ast-helpers.js';
+/**
+ * Build zero, one, or two `@type-binding.self` matches for `fnNode`:
+ *  - `null`/`[]` if the function is free (no enclosing type), static, or
+ *    the enclosing type has no resolvable name, or the function is
+ *    bodyless (no scope to anchor to).
+ *  - one match (`self`) for instance methods of a class/struct/extension/
+ *    protocol.
+ *  - two matches (`self` + `super`) only when the function lives in a
+ *    `class` (keyword) declaration with a declared superclass.
+ *
+ * Caller must guarantee `FUNCTION_NODE_TYPES.has(fnNode.type)`.
+ */
+export declare function synthesizeSwiftReceiverBinding(fnNode: SyntaxNode): CaptureMatch[];

package/dist/core/ingestion/languages/swift/receiver-binding.js

@@ -0,0 +1,161 @@
+/**
+ * Synthesize `@type-binding.self` captures for Swift instance methods —
+ * one for `self` (always on non-static methods inside a type body) and
+ * optionally one for `super` (only on class methods when the enclosing
+ * class declares a superclass).
+ *
+ * Mirrors `languages/csharp/receiver-binding.ts`. tree-sitter can't
+ * express "the implicit receiver of a non-static member of a
+ * class/struct/extension/protocol" via a static `.scm` pattern because
+ * the receiver isn't a parameter — it's implicit. Synthesis in code is
+ * the same approach C#/Python use for `this`/`self`.
+ *
+ * Swift AST facts (tree-sitter-swift 0.7.1, verified):
+ *   - class / struct / extension all parse to `class_declaration`. For
+ *     class/struct the `name:` field is `(type_identifier)`; for an
+ *     extension it is `(user_type (type_identifier))` wrapping the
+ *     EXTENDED type — so `self` in an extension binds to the extended
+ *     type, which is exactly what we want for method dispatch.
+ *   - `protocol_declaration` has a `(type_identifier)` name.
+ *   - the method body is the `body:` field (`function_body`); a bodyless
+ *     `protocol_function_declaration` has no function scope to anchor to.
+ *   - a superclass / conformance is an `(inheritance_specifier
+ *     inherits_from: (user_type (type_identifier)))` child of the
+ *     class_declaration.
+ */
+import { nodeToCapture, syntheticCapture } from '../../utils/ast-helpers.js';
+import { swiftQualifiedBaseTail } from './base-type.js';
+import { swiftMethodConfig } from '../../method-extractors/configs/swift.js';
+const TYPE_DECL_NODE_TYPES = new Set(['class_declaration', 'protocol_declaration']);
+const FUNCTION_NODE_TYPES = new Set([
+    'function_declaration',
+    'init_declaration',
+    'deinit_declaration',
+]);
+/** Walk up to the enclosing type declaration (class/struct/extension/
+ *  protocol). Nested local functions still see `self` from the enclosing
+ *  type, so don't stop at function-like nodes. */
+function findEnclosingTypeDeclaration(node) {
+    let cur = node.parent;
+    while (cur !== null) {
+        if (TYPE_DECL_NODE_TYPES.has(cur.type))
+            return cur;
+        cur = cur.parent;
+    }
+    return null;
+}
+/** Bare type name of the enclosing type. class/struct → type_identifier
+ *  text; extension → the wrapped user_type's identifier text; protocol →
+ *  type_identifier text. */
+function enclosingTypeName(typeNode) {
+    const nameNode = typeNode.childForFieldName('name');
+    if (nameNode === null)
+        return null;
+    if (nameNode.type === 'user_type') {
+        // extension Foo { } → name is (user_type (type_identifier)).
+        // extension Foo.Bar { } → (user_type (type_identifier Foo)
+        // (type_identifier Bar)); the extended type — and therefore `self` —
+        // is the TRAILING identifier `Bar` (lastNamedChild), not `Foo`. For a
+        // single identifier first === last, so this is unchanged.
+        const inner = nameNode.lastNamedChild;
+        return inner?.text ?? nameNode.text;
+    }
+    return nameNode.text;
+}
+/** Is this declaration a `class` (vs `struct`/`extension`)? Only classes
+ *  have a meaningful `super`. Detected by the leading keyword token —
+ *  class/struct/extension share the `class_declaration` node type. */
+function isClassKeyword(typeNode) {
+    for (let i = 0; i < typeNode.childCount; i++) {
+        const child = typeNode.child(i);
+        if (child !== null && !child.isNamed) {
+            const t = child.text.trim();
+            if (t === 'class')
+                return true;
+            if (t === 'struct' || t === 'extension' || t === 'enum' || t === 'actor')
+                return false;
+        }
+    }
+    return false;
+}
+/** First inherited type (superclass or first protocol) as raw text, or
+ *  null. For a class the first `inheritance_specifier` is conventionally
+ *  the superclass — `super.x()` only compiles when that is true. For a
+ *  `user_type` base the name is its trailing `type_identifier` segment (see
+ *  `swiftQualifiedBaseTail`), falling back to the raw node text when there is
+ *  no `type_identifier` child. */
+function firstInheritedType(typeNode) {
+    for (let i = 0; i < typeNode.namedChildCount; i++) {
+        const child = typeNode.namedChild(i);
+        if (child === null || child.type !== 'inheritance_specifier')
+            continue;
+        const inheritsFrom = child.childForFieldName('inherits_from') ?? child.firstNamedChild;
+        if (inheritsFrom === null)
+            return null;
+        if (inheritsFrom.type === 'user_type') {
+            return swiftQualifiedBaseTail(inheritsFrom)?.text ?? inheritsFrom.text;
+        }
+        return inheritsFrom.text;
+    }
+    return null;
+}
+/** A Swift type method (`static func` OR `class func`) has no `self`
+ *  instance receiver. Delegate to `swiftMethodConfig.isStatic`, which is
+ *  the single source of truth: `static func` emits the modifier under a
+ *  `modifiers > property_modifier` wrapper, but `class func` emits a BARE
+ *  anonymous `class` token directly under `function_declaration` (verified,
+ *  tree-sitter-swift 0.7.1). `swiftMethodConfig.isStatic` covers both via
+ *  `hasKeyword(node, 'static'|'class')` (scans direct children) and
+ *  `hasModifier(...)` — so reusing it avoids re-deriving the same scan and
+ *  fixes the prior `modifiers`-only check that missed `class func`. */
+function isStaticMethod(fnNode) {
+    return swiftMethodConfig.isStatic(fnNode);
+}
+/**
+ * Build zero, one, or two `@type-binding.self` matches for `fnNode`:
+ *  - `null`/`[]` if the function is free (no enclosing type), static, or
+ *    the enclosing type has no resolvable name, or the function is
+ *    bodyless (no scope to anchor to).
+ *  - one match (`self`) for instance methods of a class/struct/extension/
+ *    protocol.
+ *  - two matches (`self` + `super`) only when the function lives in a
+ *    `class` (keyword) declaration with a declared superclass.
+ *
+ * Caller must guarantee `FUNCTION_NODE_TYPES.has(fnNode.type)`.
+ */
+export function synthesizeSwiftReceiverBinding(fnNode) {
+    if (!FUNCTION_NODE_TYPES.has(fnNode.type))
+        return [];
+    if (isStaticMethod(fnNode))
+        return [];
+    const enclosingType = findEnclosingTypeDeclaration(fnNode);
+    if (enclosingType === null)
+        return [];
+    const enclosingName = enclosingTypeName(enclosingType);
+    if (enclosingName === null)
+        return [];
+    // Anchor inside the function scope. `body:` is the function_body; its
+    // range is guaranteed inside the function scope (unlike the method's
+    // start position, which maps to the enclosing type scope via
+    // positionIndex). Bodyless declarations have no function scope.
+    const anchorNode = fnNode.childForFieldName('body');
+    if (anchorNode === null)
+        return [];
+    const out = [buildReceiverMatch(anchorNode, 'self', enclosingName)];
+    // `super` only for class methods with a declared superclass.
+    if (isClassKeyword(enclosingType)) {
+        const superType = firstInheritedType(enclosingType);
+        if (superType !== null) {
+            out.push(buildReceiverMatch(anchorNode, 'super', superType));
+        }
+    }
+    return out;
+}
+function buildReceiverMatch(anchorNode, name, typeText) {
+    const m = {
+        '@type-binding.self': nodeToCapture('@type-binding.self', anchorNode),
+        '@type-binding.name': syntheticCapture('@type-binding.name', anchorNode, name),
+        '@type-binding.type': syntheticCapture('@type-binding.type', anchorNode, typeText),
+    };
+    return m;
+}

package/dist/core/ingestion/languages/swift/scope-resolver.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Swift `ScopeResolver` registered in `SCOPE_RESOLVERS` and consumed by
+ * the generic `runScopeResolution` orchestrator (RFC #909 Ring 3,
+ * issue #937 — the final per-language migration).
+ *
+ * Closest reference: C# (`csharpScopeResolver`) — both are OOP with
+ * classes, structs, interfaces/protocols, and explicit instance
+ * receivers. MRO follows Kotlin's shape (single superclass + multiple
+ * protocol conformance).
+ *
+ * ## Swift specifics
+ *
+ *   - **Extensions** add members to an existing type. `emitSwiftScopeCaptures`
+ *     re-keys an `extension Foo { … }` to a `class_declaration`-style def
+ *     named `Foo`, so its members land on `Foo`'s scope and the shared
+ *     `populateClassOwnedMembers` stamps them with `Foo`'s ownerId — the
+ *     same mechanism C# uses for `partial class`. No separate hoist pass.
+ *   - **Labeled arguments** narrow by ARITY only (count-primary, labels
+ *     soft) — see `arity.ts`. Label-precise dispatch is deferred to the
+ *     type-binding layer.
+ *   - **Same-module visibility**: every file in an SPM target sees its
+ *     siblings' top-level defs without an `import`. Modeled via
+ *     `populateSwiftTargetSiblings`, grouped by the SPM target *subtree*
+ *     (`Sources/<Target>/…`) via `groupSwiftFilesBySpmTarget` fed from the
+ *     `loadResolutionConfig` SPM map, mirroring Go's package siblings. With
+ *     no scanned source dir (no `Sources/`/`Package/Sources/`/`src/`) the
+ *     map is null and all files form one `__default__` module.
+ *   - **`super`** is the superclass receiver (`super.method()`); plain
+ *     `self` is the instance receiver. Both synthesized in
+ *     `receiver-binding.ts`.
+ *
+ * ## Known limitations (conscious migration trade-offs; parity gate flags
+ * anything that matters in the corpus)
+ *
+ *   1. **Protocol associated types / generic constraints** (`extension
+ *      Array where Element: Equatable`) are not narrowed — the `Self`
+ *      type of a protocol method resolves to the protocol, not the
+ *      conforming type.
+ *   2. **Cross-module `import` resolution** is still directory-segment
+ *      based (`import Foo` → files under a `Foo/` dir); explicit imports do
+ *      not yet consult the SPM target map (follow-up, tracked under #1935).
+ *      Same-target visibility (the common case) IS SPM-target-subtree
+ *      accurate — handled by sibling augmentation grouped via
+ *      `groupSwiftFilesBySpmTarget`, not by explicit imports.
+ *   3. **Operator / subscript overloads** dispatch by name only.
+ *   4. **`@_exported import` re-exports** are treated as plain imports.
+ */
+import type { ScopeResolver } from '../../scope-resolution/contract/scope-resolver.js';
+declare const swiftScopeResolver: ScopeResolver;
+export { swiftScopeResolver };

package/dist/core/ingestion/languages/swift/scope-resolver.js

@@ -0,0 +1,189 @@
+/**
+ * Swift `ScopeResolver` registered in `SCOPE_RESOLVERS` and consumed by
+ * the generic `runScopeResolution` orchestrator (RFC #909 Ring 3,
+ * issue #937 — the final per-language migration).
+ *
+ * Closest reference: C# (`csharpScopeResolver`) — both are OOP with
+ * classes, structs, interfaces/protocols, and explicit instance
+ * receivers. MRO follows Kotlin's shape (single superclass + multiple
+ * protocol conformance).
+ *
+ * ## Swift specifics
+ *
+ *   - **Extensions** add members to an existing type. `emitSwiftScopeCaptures`
+ *     re-keys an `extension Foo { … }` to a `class_declaration`-style def
+ *     named `Foo`, so its members land on `Foo`'s scope and the shared
+ *     `populateClassOwnedMembers` stamps them with `Foo`'s ownerId — the
+ *     same mechanism C# uses for `partial class`. No separate hoist pass.
+ *   - **Labeled arguments** narrow by ARITY only (count-primary, labels
+ *     soft) — see `arity.ts`. Label-precise dispatch is deferred to the
+ *     type-binding layer.
+ *   - **Same-module visibility**: every file in an SPM target sees its
+ *     siblings' top-level defs without an `import`. Modeled via
+ *     `populateSwiftTargetSiblings`, grouped by the SPM target *subtree*
+ *     (`Sources/<Target>/…`) via `groupSwiftFilesBySpmTarget` fed from the
+ *     `loadResolutionConfig` SPM map, mirroring Go's package siblings. With
+ *     no scanned source dir (no `Sources/`/`Package/Sources/`/`src/`) the
+ *     map is null and all files form one `__default__` module.
+ *   - **`super`** is the superclass receiver (`super.method()`); plain
+ *     `self` is the instance receiver. Both synthesized in
+ *     `receiver-binding.ts`.
+ *
+ * ## Known limitations (conscious migration trade-offs; parity gate flags
+ * anything that matters in the corpus)
+ *
+ *   1. **Protocol associated types / generic constraints** (`extension
+ *      Array where Element: Equatable`) are not narrowed — the `Self`
+ *      type of a protocol method resolves to the protocol, not the
+ *      conforming type.
+ *   2. **Cross-module `import` resolution** is still directory-segment
+ *      based (`import Foo` → files under a `Foo/` dir); explicit imports do
+ *      not yet consult the SPM target map (follow-up, tracked under #1935).
+ *      Same-target visibility (the common case) IS SPM-target-subtree
+ *      accurate — handled by sibling augmentation grouped via
+ *      `groupSwiftFilesBySpmTarget`, not by explicit imports.
+ *   3. **Operator / subscript overloads** dispatch by name only.
+ *   4. **`@_exported import` re-exports** are treated as plain imports.
+ */
+import { SupportedLanguages } from '../../../../_shared/index.js';
+import { loadSwiftPackageConfig } from '../../language-config.js';
+import { buildMro, defaultLinearize } from '../../scope-resolution/passes/mro.js';
+import { populateClassOwnedMembers, isClassLike } from '../../scope-resolution/scope/walkers.js';
+import { resolveDefGraphId } from '../../scope-resolution/graph-bridge/ids.js';
+import { swiftProvider } from '../swift.js';
+import { swiftArityCompatibility, swiftMergeBindings, interpretSwiftImport, resolveSwiftImportTarget, populateSwiftTargetSiblings, emitSwiftImplicitImportEdges, mirrorSwiftSiblingTypeBindings, } from './index.js';
+const ZERO_RANGE = { startLine: 0, startCol: 0, endLine: 0, endCol: 0 };
+const swiftScopeResolver = {
+    language: SupportedLanguages.Swift,
+    languageProvider: swiftProvider,
+    importEdgeReason: 'swift-scope: import',
+    // Load the SPM target map (Sources/<Target>/ subtree mapping) once per
+    // workspace pass. Threaded through the orchestrator as `resolutionConfig`
+    // and consumed by the three same-module grouping hooks
+    // (`emitImplicitImportEdges`, `populateNamespaceSiblings`,
+    // `mirrorNamespaceTypeBindings`) via `coerceSwiftTargets` so they group by
+    // the SPM target subtree, not the immediate directory. Mirrors
+    // `goScopeResolver`'s `loadGoModulePath`.
+    loadResolutionConfig: (repoPath) => loadSwiftPackageConfig(repoPath),
+    resolveImportTarget: (targetRaw, fromFile, allFilePaths) => {
+        const ws = { fromFile, allFilePaths };
+        return resolveSwiftImportTarget(interpretSwiftImport({
+            '@import.source': { name: '@import.source', text: targetRaw, range: ZERO_RANGE },
+        }) ?? { kind: 'namespace', localName: targetRaw, importedName: targetRaw, targetRaw }, ws);
+    },
+    // Swift shadowing: local declarations hide imports.
+    mergeBindings: (existing, incoming) => [...swiftMergeBindings([...existing, ...incoming])],
+    // Adapter: swiftArityCompatibility uses (def, callsite); contract is (callsite, def).
+    arityCompatibility: (callsite, def) => swiftArityCompatibility(def, callsite),
+    buildMro: (graph, parsedFiles, nodeLookup) => buildSwiftMro(graph, parsedFiles, nodeLookup),
+    // Methods/properties/init are owned by their enclosing class/struct/
+    // extension(→extended type)/protocol. Extension members hoist for free
+    // because captures.ts re-keys the extension to a Class def named after
+    // the extended type.
+    populateOwners: (parsed) => populateClassOwnedMembers(parsed),
+    // `super.method()` dispatches through the superclass chain.
+    isSuperReceiver: (text) => text.trim() === 'super',
+    // Whole-module same-target visibility without `import`.
+    populateNamespaceSiblings: populateSwiftTargetSiblings,
+    // Same-target File→File IMPORTS edges (no syntactic `import`). The
+    // generic finalized-ImportEdge pipeline has nothing to emit here, so
+    // these whole-module-visibility edges are emitted directly.
+    emitImplicitImportEdges: emitSwiftImplicitImportEdges,
+    // Mirror sibling files' return-type typeBindings into each file's
+    // module scope so cross-file chains (`let u = siblingFn(); u.m()`)
+    // resolve. Whole-module visibility has no import edge for
+    // `propagateImportedReturnTypes` to follow, so this directory-sibling
+    // mirror feeds it (mirrors Go's namespace-typeBinding mirror).
+    mirrorNamespaceTypeBindings: mirrorSwiftSiblingTypeBindings,
+    // Swift is statically typed — type info is reliable; the field-fallback
+    // heuristic over-connects, so keep it off. Return-type propagation on.
+    fieldFallbackOnMethodLookup: false,
+    propagatesReturnTypesAcrossImports: true,
+    // Swift has no `new` keyword: `UserService()` is a bare call that
+    // resolves to the type's Constructor/Class. With whole-module sibling
+    // visibility, the callee is reachable workspace-wide, so allow the
+    // global free-call fallback (as Python/Go/Ruby/COBOL do for the same
+    // no-`new` constructor + cross-file free-call shape).
+    allowGlobalFreeCallFallback: true,
+    // Swift's call graph models `Type(...)` as a reference to the type
+    // itself, not its `init` — both the legacy DAG and this test suite link
+    // `Foo()` to the Class node even when an explicit `init` exists.
+    constructorCallTargetsClass: true,
+};
+export { swiftScopeResolver };
+/**
+ * Swift MRO — `defaultLinearize` (EXTENDS-only superclass chain) extended
+ * with protocol ancestors discovered via `IMPLEMENTS` edges. Protocols
+ * with default method implementations (via protocol extensions) are
+ * inherited by conforming types without an explicit `override`; the
+ * generic EXTENDS-only MRO would miss them because the conformer has no
+ * EXTENDS link to the protocol.
+ *
+ * Mirrors `buildKotlinMro`: append protocols after the superclass chain
+ * (Swift requires an explicit implementation on ambiguity, so first-seen
+ * ordering approximates method lookup). Transitive protocol inheritance
+ * (`protocol A: B`) is closed via BFS.
+ */
+function buildSwiftMro(graph, parsedFiles, nodeLookup) {
+    const mro = buildMro(graph, parsedFiles, nodeLookup, defaultLinearize);
+    const defIdByGraphId = new Map();
+    for (const parsed of parsedFiles) {
+        for (const def of parsed.localDefs) {
+            if (!isClassLike(def.type))
+                continue;
+            const graphId = resolveDefGraphId(parsed.filePath, def, nodeLookup);
+            if (graphId !== undefined)
+                defIdByGraphId.set(graphId, def.nodeId);
+        }
+    }
+    const directImpls = new Map();
+    for (const rel of graph.iterRelationshipsByType('IMPLEMENTS')) {
+        const source = defIdByGraphId.get(rel.sourceId);
+        const target = defIdByGraphId.get(rel.targetId);
+        if (source === undefined || target === undefined)
+            continue;
+        let list = directImpls.get(source);
+        if (list === undefined) {
+            list = [];
+            directImpls.set(source, list);
+        }
+        if (!list.includes(target))
+            list.push(target);
+    }
+    for (const [classDefId, extendsMro] of mro) {
+        const ancestorChain = [classDefId, ...extendsMro];
+        const seeds = [];
+        for (const ancestorId of ancestorChain) {
+            for (const ifaceId of directImpls.get(ancestorId) ?? [])
+                seeds.push(ifaceId);
+        }
+        if (seeds.length === 0)
+            continue;
+        const protocols = closeProtocols(seeds, directImpls);
+        mro.set(classDefId, [...extendsMro, ...protocols.filter((i) => !extendsMro.includes(i))]);
+    }
+    // Types that only conform to protocols (no superclass) still need an MRO.
+    for (const [classDefId, ifaces] of directImpls) {
+        if (mro.has(classDefId))
+            continue;
+        mro.set(classDefId, closeProtocols([...ifaces], directImpls));
+    }
+    return mro;
+}
+function closeProtocols(seeds, directImpls) {
+    const out = [];
+    const seen = new Set();
+    const queue = [...seeds];
+    while (queue.length > 0) {
+        const cur = queue.shift();
+        if (seen.has(cur))
+            continue;
+        seen.add(cur);
+        out.push(cur);
+        for (const next of directImpls.get(cur) ?? []) {
+            if (!seen.has(next))
+                queue.push(next);
+        }
+    }
+    return out;
+}

package/dist/core/ingestion/languages/swift/sibling-type-bindings.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Swift same-module return-type typeBinding mirroring for the
+ * `mirrorNamespaceTypeBindings` hook.
+ *
+ * Swift gives every file in a module (an SPM target) visibility of every
+ * sibling's top-level declarations without a syntactic `import`. For a
+ * chained call like
+ *
+ *   App.swift:    let user = getUser(); user.save()   // user → getUser → ?
+ *   Models.swift: func getUser() -> User { … }        // getUser → User
+ *
+ * to resolve `user.save()` cross-file, App.swift's scope chain must be
+ * able to follow `getUser → User`. The function return-type binding
+ * (`getUser → User`) lives on Models.swift's module scope, so we mirror
+ * sibling module-scope typeBindings into the importer's module scope —
+ * the same trick Go uses (`mirrorGoNamespaceTypeBindings`), but Swift has
+ * no namespace-import edges, so module membership is the SPM target
+ * subtree (`Sources/<Target>/…`): threaded in via the SPM target map
+ * (`resolutionConfig` → `coerceSwiftTargets`) and grouped by
+ * `groupSwiftFilesBySpmTarget` (replicating legacy `groupSwiftFilesByTarget`;
+ * no-source-dir → all files form one `__default__` module).
+ *
+ * Runs after `populateNamespaceSiblings` and before
+ * `propagateImportedReturnTypes`, so the SCC-ordered propagation pass
+ * sees the mirrored bindings and chains `user → getUser → User` to the
+ * terminal class. Each mirrored binding is chain-followed inside its
+ * source module first so we mirror the terminal type, not an intermediate
+ * intra-module reference. `Scope.typeBindings` is mutated via the
+ * sanctioned non-frozen Map cast (Contract Invariant I6).
+ */
+import type { ParsedFile } from '../../../../_shared/index.js';
+import type { ScopeResolutionIndexes } from '../../model/scope-resolution-indexes.js';
+import type { WorkspaceResolutionIndex } from '../../scope-resolution/workspace-index.js';
+export declare function mirrorSwiftSiblingTypeBindings(parsedFiles: readonly ParsedFile[], indexes: ScopeResolutionIndexes, workspaceIndex: WorkspaceResolutionIndex, resolutionConfig?: unknown): void;