fix(gittensor): guard Gittensor repo name normalization

[JSONbored]

Motivation

• Upstream Gittensor JSON can include non-string repositoryFullName values which caused .toLowerCase() calls to throw and crash contributor profile builds.
• The change aims to treat external Gittensor repo names as untrusted JSON and safely coerce or ignore malformed values so profile construction remains available.

Description

• Treat repositoryFullName as unknown and add asString() in src/gittensor/api.ts so non-string values map to the existing empty-string fallback before entering snapshots.
• Replace direct .toLowerCase() usages with a new normalizedRepoName() helper in src/signals/engine.ts and use it when deduping repo names for label aggregation.
• Add regression tests that exercise malformed/malformed-object repo names in test/unit/gittensor-api.test.ts and test/unit/signals-coverage.test.ts to ensure malformed upstream payloads are treated as absent rather than crashing.

Testing

• Ran npx vitest run test/unit/gittensor-api.test.ts test/unit/signals-coverage.test.ts and the targeted tests passed.
• Ran the repository unit test command npm run test:unit -- test/unit/gittensor-api.test.ts test/unit/signals-coverage.test.ts and the run succeeded.
• Ran type checking with npm run typecheck and it completed successfully.

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	8b71dda	Commit Preview URL Branch Preview URL	Jun 06 2026, 01:09 AM

[gittensory]

Note

Gittensory Gate skipped

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

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

---

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