fix(gittensor): drop empty-name repos from contributor snapshot

[philluiz2323]

Summary

buildGittensorContributorSnapshot (src/gittensor/api.ts:246) filtered the snapshot's repositories list by activity only, not by a valid repoFullName -- unlike the pull-request and issue lists right beside it, which both require a non-empty repoFullName:

repositories: (...).map(toRepositoryEvaluation).filter((repo) => repo.pullRequests + repo.openIssues + repo.closedIssues > 0), // no name guard
pullRequests: (...).filter((pr) => pr.repoFullName && pr.number > 0),    // guarded
issues: (...).filter((issue) => issue.repoFullName && issue.number > 0), // guarded

#437 made repositoryFullName an untrusted unknown and coerces malformed/missing values to "" (asString), but did not add the empty-name filter to the repositories list. So a malformed repo evaluation with nonzero stats leaks in as { repoFullName: "", ... }. Closes #444.

Observable impact

snapshot.repositories feeds buildGittensorContributorProfile (src/signals/engine.ts):

• reposTouched (engine.ts:1119) keeps the empty-name repo (nonzero stats), so it leaks into registeredRepoActivity.reposTouched as "".
• evidenceScore = clamp(... + reposTouched.length * 10 + ..., 0, 100) (engine.ts:1137): one phantom repo adds +10 on a 0-100 scale, which can bump trustSignals.level a tier (new < 25, emerging 25-59, established >= 60).

Reachable because #437 itself treats upstream Gittensor repository names as untrusted JSON that can be malformed.

Scope

• src/gittensor/api.ts -- add repo.repoFullName && to the repositories filter, matching the PR/issue lists and fix(gittensor): guard Gittensor repo name normalization #437's intent.
• test/unit/gittensor-api.test.ts -- the fix(gittensor): guard Gittensor repo name normalization #437 malformed-payload test asserted the empty-name repo was included; updated to assert it is dropped (repositories is ["owner/repo"] only) with an explicit no-leak check.

Validation

• npx tsc --noEmit -- clean.
• npx vitest run test/unit/gittensor-api.test.ts -- 8/8.
• Full suite -- 1207 passed, 1 skipped (excluding the two unparseable upstream test files and one unrelated mcp-cli timeout that passes in isolation).
• Branch coverage at/above the 97% gate; gittensor/api.ts 100% line.

Safety

• Behavior is unchanged for well-formed snapshots (valid repo names pass the added guard exactly as before). Only malformed/empty-name entries are now dropped, consistent with the PR/issue lists.
• No response-shape change; the snapshot simply no longer contains phantom ""-named repositories.

[gittensory]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#445 is no longer open.	No action.

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[JSONbored]

@philluiz2323 this is good to land.

A few notes:

• The empty-name repository guard matches the existing PR/issue filtering behavior.
• The updated test now verifies malformed repo names are dropped instead of carried into the contributor snapshot.
• This resolves #444 cleanly without changing behavior for valid repository records.
• No code changes requested.