fix(registry): preserve stored affected repo counts for legacy capped registry drift reports

[JSONbored]

Motivation

• A change to derive affectedRepos from stored (capped) events caused legacy reports that stored a pre-cap affectedRepoCount to be underreported when events were truncated at the cap.
• The goal is to keep deduplication of known repo identities across reports while preserving the stored legacy counts that exceed the capped event list so operator-facing summaries are not misleading.

Description

• Add an unidentifiedAffectedRepoCount field to the RegistryHyperparameterDriftPayload and default it in emptyRegistryHyperparameterDriftPayload to track stored counts not represented by identifiable repos (src/upstream/ruleset.ts).
• In readRegistryHyperparameterDriftPayload compute derivedAffectedRepos from affectedRepos or legacy events, preserve the parsed affectedRepoCount, and expose unidentifiedAffectedRepoCount as the positive difference between the stored count and the number of identifiable repos when applicable (src/upstream/ruleset.ts).
• In summarizeRegistryHyperparameterDriftReports union known repo names across reports and add the sum of all unidentifiedAffectedRepoCount values to the union size to produce affectedRepoCount, while still falling back to the event-derived summary when appropriate (src/upstream/ruleset.ts).
• Add a regression unit test preserves stored affected repo counts for legacy capped registry drift reports that inserts a legacy-shaped report with affectedRepoCount: 150 and only 100 capped event repos and asserts the aggregated status reports 150 affected repos (test/unit/upstream-ruleset.test.ts).

Testing

• Ran static type checking with npm run typecheck (tsc --noEmit) and it succeeded.
• Ran the targeted unit test file with npx vitest run test/unit/upstream-ruleset.test.ts and the tests covering the change passed.
• Ran the full unit suite with npm run test:unit and all tests passed (no regressions observed).

---

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	686d8b9	Commit Preview URL Branch Preview URL	Jun 10 2026, 08:20 AM

[ghost]

Important

Gittensory found maintainer review notes

Scoped related-work signals were found for this PR. They are advisory unless the gate reports a blocker.

Readiness score: 70/100

Signal	Result	Evidence	Action
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.	Explain no-issue PR.
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.	Review top overlaps.
Review load	❌ 8/20	Readiness component derived from cached public PR metadata and labels; size label size:S.	Add scope summary.
Validation evidence	✅ 25/25	PR body includes validation/test evidence.	No action.
Open PR queue	⚠️ 5/10	13 open PR(s), 5 likely reviewable, 8 unlinked.	Expect slower review.
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 68 PR(s), 309 issue(s).	No action.
Gate result	✅ Passing	No configured blocker found.	No action.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Review load = cached public PR metadata such as size labels, changed paths, and preflight status.
• Open PR queue = repo-wide review pressure; it is not a PR quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, JavaScript, Ruby, Go, Kotlin, MDX, Shell
• Official Gittensor activity: 68 PR(s), 309 issue(s).
• Related work: Titles/paths share 7 meaningful terms. (PR #515)
• Related work: Items reference the same linked issue feat(config): add Gittensory repo focus manifest #118. (issue #118, PR #389)
• Related work: Items reference the same linked issue [Feature]: Cross-repo queue health federation and comparative pressure index #479. (issue #479, PR #480)
• Additional title-only matches omitted; title-only overlap does not block.

Maintainer notes

• No linked issue detected: The planned PR does not reference a closing issue or explicit linked issue number.
• Possible duplicate or overlapping work: 8 related open work cluster(s) were detected.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Review top overlaps.
• Add scope summary.
• Expect slower review.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.
• Check active issues and PRs before submitting.

• Re-run Gittensory review

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. Learn more about Gittensor contribution workflows.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.