redoing auto labeling using z score instead of clustering lowkey the …

[zander-raycraft]

…method

[github-actions]

PR description is too short

This PR's description is 7 characters, but the minimum is 50.

Please update the PR description to explain:

• What this PR changes
• Why the change is needed

Use the PR template as a guide. This check will re-run when you edit the description.

[github-actions]

CI Report

✅ All checks passed   4031562

Pipeline

Stage	Status	Ubuntu	Windows	macOS
Typecheck	✅ success	—	—	—
Tests	✅ success	✅	✅	✅

Tests

Metric	Value
Total	3600
Passed	3572
Skipped	20
Files	1028
Duration	1m 54s

✅ All 3572 tests passed across 1028 files

20 test(s) skipped

• withTestLbugDB(search-pool) > searchFTSFromLbug — MCP pool adapter (with repoId) > returns ranked results via pool adapter
• withTestLbugDB(search-pool) > searchFTSFromLbug — MCP pool adapter (with repoId) > results are ordered by descending score via pool adapter
• withTestLbugDB(search-pool) > searchFTSFromLbug — MCP pool adapter (with repoId) > returns empty array for non-matching query via pool adapter
• withTestLbugDB(search-pool) > searchFTSFromLbug — MCP pool adapter (with repoId) > respects limit parameter via pool adapter
• withTestLbugDB(search-pool) > unhappy paths > returns empty array for empty query via pool
• withTestLbugDB(search-pool) > unhappy paths > returns empty array for whitespace-only query via pool
• withTestLbugDB(search-pool) > unhappy paths > handles special characters in query via pool
• withTestLbugDB(search-pool) > unhappy paths > handles limit of 0 via pool
• buildTypeEnv > known limitations (documented skip tests) > Ruby block parameter: users.each { |user| } — closure param inference, different feature
• Python match/case as-pattern type binding > resolves u.save() to User#save via match/case as-pattern binding
• Python match/case as-pattern type binding > does NOT resolve u.save() to Repo#save (negative disambiguation)
• 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()

Coverage

Metric	Coverage	Covered	Base (main)	Delta
Statements	68.96%	9079/13164	68.97%	＝
Branches	60.11%	6162/10250	60.11%	＝
Functions	71.47%	802/1122	71.56%	📉 -0.1%
Lines	71.22%	8094/11364	71.22%	＝

---

_{📋 Full run · Coverage from Ubuntu · Generated by CI}