-
-
Notifications
You must be signed in to change notification settings - Fork 87
Dashboard 'registered vs installed' copy audit #5026
Copy link
Copy link
Closed
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is needed
Description
Metadata
Metadata
Assignees
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is needed
Part of #5016. Low priority — cosmetic, no functional change. Best done last, after #1-#6 land so the "registered vs installed" split is fully accurate everywhere.
Context
/v1/app/overview(src/api/routes.ts:1230-1231),buildDigestItems(src/api/routes.ts:4568-4575),src/services/weekly-value-report.ts:134-135, andsrc/services/operator-dashboard.ts:141-142already trackinstalledReposandregisteredReposas two separate, correctly-computed metrics side by side — this is not a bug.src/services/control-panel-roles.ts:75,111(access-scope authorization) already usesisInstalledexclusively — the correct existing precedent this whole epic is generalizing.Target
No functional change. Once gittensor is opt-in (see the plugin-toggle PR, landing separately from this epic), "0 registered" becomes the normal, expected state for most self-host operators. Audit dashboard/digest copy and confirm nothing reads as broken or alarming in that state (e.g. a stat tile that implies something is wrong when registered=0 but installed>0).
Deliverables
registeredRepos).