test(csharp): companion fixture for #1066 frozen-bucket regression

[mann1x]

Summary

Adds a small-file companion fixture for the freeze-contract regression fixed in #1082. The merged csharp-large-cache-miss-resolution fixture reproduces the failure via the >32 KB tree-sitter cache-miss reparse path; this fixture trips the same Object.freeze contract in populateCsharpNamespaceSiblings through a different trigger that doesn't depend on file size:

An importer locally declares a class with the same simple name as a sibling reachable through using, so scope-extractor pre-populates (and freezes) User in the importer's Module bindings before the populator's namespace-import loop tries to append the cross-file Collision.Models.User.

Pre-#1082 the populator pushed onto the frozen array → TypeError: Cannot add property N, object is not extensible → the whole scopeResolution phase aborted for the repo. Post-#1082 the augmentation channel keeps both bindings visible to readers; the local Collision.App.User shadows the namespace-imported one per origin precedence.

This is the trigger we originally hit on the PersistentWindows real-world WinForms repo and used to reproduce the bug in the (now-closed) #1083 — adding it here as resolver coverage so the freeze contract is locked-in on both reproduction paths.

Fixture

test/fixtures/lang-resolution/csharp-frozen-binding-collision/:

• Models/User.cs — namespace Collision.Models { public class User { ... } }
• App/Program.cs — using Collision.Models; + namespace Collision.App { public class User { ... } public class Program { ... } }

Tiny by design — the bug is shape-driven, not size-driven, so the fixture stays small and fast (567 ms for the new describe vs ~25 s for the cache-miss fixture in the same suite).

Tests

New describe block in test/integration/resolvers/csharp.test.ts, sibling to the merged 'C# large-file + frozen-bucket regression (issue #1066)' block:

• completes scopeResolution without throwing on the colliding bucket — the freeze regression itself.
• detects both User declarations across the two namespaces — pins augmentation visibility.
• resolves Program.Run -> local Collision.App.User constructor (origin:local shadows namespace) — pins the precedence contract that makes the augmentation channel architecturally correct (not just non-throwing).

Crossreference: test/integration/resolvers/csharp.test.ts:2454 (cache-miss-reparse trigger) ↔ new block (collision-via-using-import trigger). Both anchor on the same bindingAugmentations machinery added in #1082; either one reverting reproduces #1066.

Validation

• npx vitest run test/integration/resolvers/csharp.test.ts → 207 passed / 0 failed (was 204; +3 new).
• npx tsc --noEmit → clean.
• Pre-commit hook (typecheck) green.
• Verified end-to-end on PersistentWindows after rebuilding from upstream/main (fix(ingestion): two-channel binding lifecycle (closes #1066) + scope-resolution I8 hardening #1082 merged): 0 freeze errors, 1113 nodes / 2987 edges / 39 clusters / 97 flows vs 1025 / 1715 / 28 / 25 with the closed fix(csharp): copy-on-read frozen binding arrays in namespace-siblings #1083 workaround. The augmentation channel reaches ~74 % more cross-file edges than copy-on-read could.

Test plan

• npx vitest run test/integration/resolvers/csharp.test.ts (full file)
• npx tsc --noEmit in gitnexus/
• New describe runs in <1 s isolated; doesn't slow the resolver suite materially
• Each new test fails on a hypothetical revert of fix(ingestion): two-channel binding lifecycle (closes #1066) + scope-resolution I8 hardening #1082's Step 4 (write target back to indexes.bindings) — same shape as the merged Analysis failed: Phase 'scopeResolution' failed: Cannot add property 2, object is not extensible #1066 fixture's bidirectional revert verification

[vercel]

@mann1x is attempting to deploy a commit to the NexusCore Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

CI Report

✅ All checks passed

Pipeline Status

Stage	Status	Details
✅ Typecheck	success	tsc --noEmit
✅ Tests	success	unit tests, 3 platforms
✅ E2E	success	gitnexus-web changes only

Test Results

Tests	Passed	Failed	Skipped	Duration
7569	7472	0	97	285s

✅ All 7472 tests passed

97 test(s) skipped — expand for details

• Swift MethodExtractor > isTypeDeclaration > recognizes class_declaration
• Swift MethodExtractor > isTypeDeclaration > recognizes protocol_declaration
• Swift MethodExtractor > isTypeDeclaration > rejects import_declaration
• Swift MethodExtractor > visibility > extracts public method
• Swift MethodExtractor > visibility > extracts private method
• Swift MethodExtractor > visibility > defaults to internal when no modifier
• Swift MethodExtractor > protocol methods > marks protocol method as abstract
• Swift MethodExtractor > static and class methods > detects static func as isStatic
• Swift MethodExtractor > static and class methods > detects class func as isStatic
• Swift MethodExtractor > parameters > extracts parameters with types and default values
• Swift MethodExtractor > return type > extracts return type from -> annotation
• Swift MethodExtractor > annotations > extracts @objc attribute
• Swift MethodExtractor > isFinal > detects final func
• Swift MethodExtractor > isFinal > is false when not final
• Swift MethodExtractor > isAsync > detects async func
• Swift MethodExtractor > isOverride > detects override method
• buildTypeEnv > constructor inference (Tier 1 fallback) > lookupClassByName regression coverage > Swift lookupClassByName regression coverage > Swift cross-file constructor inference uses lookupClassByName
• buildTypeEnv > constructor inference (Tier 1 fallback) > lookupClassByName regression coverage > Swift lookupClassByName regression coverage > Swift explicit init inference uses lookupClassByName
• buildTypeEnv > constructor inference (Tier 1 fallback) > lookupClassByName regression coverage > Swift lookupClassByName regression coverage > Swift cross-file constructor inference does not bind plain functions
• buildTypeEnv > known limitations (documented skip tests) > Ruby block parameter: users.each { |user| } — closure param inference, different feature
• Swift constructor-inferred type resolution > detects User and Repo classes, both with save methods
• Swift constructor-inferred type resolution > resolves user.save() to Models/User.swift via constructor-inferred type
• Swift constructor-inferred type resolution > resolves repo.save() to Models/Repo.swift via constructor-inferred type
• Swift constructor-inferred type resolution > emits exactly 2 save() CALLS edges (one per receiver type)
• Swift self resolution > detects User and Repo classes, each with a save function
• Swift self resolution > resolves self.save() inside User.process to User.save, not Repo.save
• Swift parent resolution > detects BaseModel and User classes plus Serializable protocol
• Swift parent resolution > emits EXTENDS edge: User → BaseModel
• Swift parent resolution > emits IMPLEMENTS edge: User → Serializable (protocol conformance)
• Swift cross-file User.init() inference > resolves user.save() via User.init(name:) inference
• Swift cross-file User.init() inference > resolves user.greet() via User.init(name:) inference
• Swift return type inference > detects User class and getUser function
• Swift return type inference > detects save function on User (Swift class methods are Function nodes)
• Swift return type inference > resolves user.save() to User#save via return type of getUser() -> User
• Swift return-type inference via function return type > resolves user.save() to User#save via return type of getUser()
• Swift return-type inference via function return type > user.save() does NOT resolve to Repo#save
• Swift return-type inference via function return type > resolves repo.save() to Repo#save via return type of getRepo()
• Swift implicit imports (cross-file visibility) > detects UserService class in Models.swift
• Swift implicit imports (cross-file visibility) > resolves UserService() constructor call across files (no explicit import)
• Swift implicit imports (cross-file visibility) > resolves service.fetchUser() member call across files
• Swift implicit imports (cross-file visibility) > creates IMPORTS edges between files in the same module
• Swift extension deduplication > detects Product class
• Swift extension deduplication > resolves Product() constructor despite extension creating duplicate class node
• Swift extension deduplication > resolves product.save() to Product.swift (primary definition)
• Swift constructor call fallback (no new keyword) > resolves OCRService() as constructor call across files
• Swift constructor call fallback (no new keyword) > resolves ocr.recognize() member call via constructor-inferred type
• Swift export visibility (internal vs private) > resolves PublicService() constructor across files
• Swift export visibility (internal vs private) > resolves internalHelper() across files (internal = module-scoped)
• Swift if let / guard let binding resolution > detects User and Repo classes
• Swift if let / guard let binding resolution > resolves user.save() inside if-let to User#save
• Swift if let / guard let binding resolution > resolves repo.save() inside guard-let to Repo#save
• Swift if let / guard let binding resolution > user.save() in if-let does NOT resolve to Repo#save
• Swift await / try expression unwrapping > resolves user.save() via await fetchUser() return type
• Swift await / try expression unwrapping > resolves repo.save() via try parseRepo() return type
• Swift await / try expression unwrapping > detects fetchUser and parseRepo as functions
• Swift for-in loop element type inference > detects User and Repo classes
• Swift for-in loop element type inference > creates implicit import edges between files
• Swift field-type resolution > detects classes and their properties
• Swift field-type resolution > emits HAS_PROPERTY edges from class to field
• Swift field-type resolution > resolves field-chain call user.address.save() → Address#save
• Swift field-type resolution > emits ACCESSES edges for field reads in chains
• Swift field-type resolution > populates field metadata (visibility, declaredType) on Property nodes
• Swift call-result binding > resolves call-result-bound method call user.save() → User#save
• Swift call-result binding > getUser() is present as a defined function
• Swift call-result binding > emits processUser -> getUser CALLS edge for let-assigned free function call
• Swift method enrichment > detects Animal protocol and Dog class
• Swift method enrichment > emits IMPLEMENTS edge Dog -> Animal
• Swift method enrichment > emits HAS_METHOD edges for Dog methods
• Swift method enrichment > marks protocol Animal.speak as isAbstract
• Swift method enrichment > marks Dog.speak as NOT isAbstract
• Swift method enrichment > marks breathe as isFinal
• Swift method enrichment > marks classify as isStatic
• Swift method enrichment > captures @objc annotation on breathe
• Swift method enrichment > populates parameterTypes for classify(_ name: String)
• Swift method enrichment > records parameterCount for classify
• Swift method enrichment > records returnType for speak
• Swift method enrichment > resolves dog.speak() CALLS edge
• Swift method enrichment > resolves Dog.classify("dog") CALLS edge
• Swift abstract dispatch > detects Repository protocol and SqlRepository class
• Swift abstract dispatch > emits IMPLEMENTS edge SqlRepository -> Repository
• Swift abstract dispatch > emits HAS_METHOD edges for Repository.find and Repository.save
• Swift abstract dispatch > emits HAS_METHOD edges for SqlRepository.find and SqlRepository.save
• Swift abstract dispatch > marks base Repository.find as isAbstract
• Swift abstract dispatch > marks base Repository.save as isAbstract
• Swift abstract dispatch > marks concrete SqlRepository.find as NOT isAbstract
• Swift abstract dispatch > resolves repo.find(id: 42) CALLS edge
• Swift abstract dispatch > resolves repo.save(entity: user) CALLS edge
• Swift abstract dispatch > populates parameterTypes for Repository.find
• Swift abstract dispatch > populates parameterTypes for Repository.save
• Swift abstract dispatch > records returnType for SqlRepository.find
• Swift abstract dispatch > emits METHOD_IMPLEMENTS edges from SqlRepository methods → Repository protocol methods
• Swift overloaded method disambiguation > detects 2 distinct find Method nodes on SqlRepository
• Swift overloaded method disambiguation > emits METHOD_IMPLEMENTS edges for both find overloads
• Swift overloaded method disambiguation > emits METHOD_IMPLEMENTS edge for save
• Swift overloaded method disambiguation > emits exactly 3 METHOD_IMPLEMENTS edges total
• Swift Child extends Parent — inherited method resolution (SM-9) > detects Parent and Child classes
• Swift Child extends Parent — inherited method resolution (SM-9) > resolves c.parentMethod() to Parent.parentMethod via first-wins MRO walk

Code Coverage

Tests

Metric	Coverage	Covered	Base	Delta	Status
Statements	75.59%	21951/29037	75.59%	＝ 0.0	🟢 ███████████████░░░░░
Branches	64.53%	14060/21787	64.51%	📈 +0.0	🟢 ████████████░░░░░░░░
Functions	80.8%	2126/2631	80.8%	＝ 0.0	🟢 ████████████████░░░░
Lines	78.4%	19807/25264	78.39%	📈 +0.0	🟢 ███████████████░░░░░

---

_{📋 View full run · Generated by CI}