chore(labels): relabel 81 metagraphed issues mislabeled gittensor:bug instead of gittensor:feature (2026-07-05 batch) + review gittensor:priority dilution

[JSONbored]

Context

Auditing all 170 open metagraphed issues for point-label accuracy: 86 issues were bulk-created by @JSONbored in a single session on 2026-07-05, all stamped gittensor:bug (0.5x multiplier). Classifying each by its title/verb and hand-checking the boundary cases:

• 81 of the 86 are unambiguous new-feature work, e.g. "Add a network operations leaderboard (serving + prometheus telemetry) to the explorer page," "Add a validator × subnet participation heatmap to the validator directory," "Add /validators route + global validator directory page," "Surface per-account stake-flow chart on the account detail page," "Add copy-to-clipboard buttons on hash/address cells." Every one adds a UI surface, route, chart, or interaction that doesn't exist today — none are fixing broken existing behavior. These should carry gittensor:feature (1.25x), not gittensor:bug (0.5x) — a 2.5x under-payment today for whoever picks each one up.
• 5 of the 86 are genuinely bug/refactor-shaped and correctly labeled as-is: fix(signals): classify .mts and .cts source maps as generated #3347 (fix wrong route), test(signals): extend repo-policy-compiler branch coverage #3425/fix(agent): restrict tracker suggestions to PR lifecycle actions #3426/feat(enrichment): flag deployment-trigger and webhook URLs in secret-scan #3428 (extract shared component / dedup), feat(enrichment): flag managed-database connection strings in secret-scan #3486 (replace calls with a rollup).
• Corroborating signal: issues feat(review): read-only auto-merge conditions table via review.auto_merge_summary #3730, fix(signals): classify C# and Dart gRPC service stubs as generated #3732, feat(review): read-only auto-merge conditions table via review.auto_merge_summary #3734 — created later the same day, with the identical "Surface X on the account page" phrasing as the mislabeled batch — ARE correctly tagged gittensor:feature. Whatever produced these labels self-corrected partway through the day but was never applied retroactively to the earlier ~81.
• Separately: 13 of metagraphed's 14 gittensor:priority issues (1.75x, "reserved for outstanding work") stack on gittensor:feature, and 11 of those 13 are ALSO tagged good first issue — the entire early "Enrich SNxx — add OpenAPI/Swagger spec" batch (Reward-risk next-actions are truncated *before* deduplication, dropping distinct steps #463, Burden-forecast medium tier ignores queueGrowthRisk, under-classifying queue-growth pressure #465, fix(signals): include queue-growth risk in medium burden tier #466, owner-led: visual-change PR auto-review (before/after screenshots) #577, BYOK: separate BYOK advisory spend from the free Workers-AI daily neuron budget #672, BYOK: maintainer-facing documentation (coordinate with #648) #675, feat(notifications): miner-facing post-merge reward & outcome attribution (#702) #714, chore(raycast): remove unused Raycast scaffolding #720, feat(slop): BYOK frontier model for the AI slop advisory #728, feat(scoring): upstream time-decay, behind a default-off flag (#703) #731, feat(scoring): per-repo time-decay hyperparameters + go live (#703) #733). Worth a deliberate call on whether that batch still merits the "reserved for outstanding work" multiplier, or whether it's scope creep from a one-time bootstrap incentive that should be pared back.

Requirements

1. Relabel each of the 81 issues listed below from gittensor:bug to gittensor:feature in JSONbored/metagraphed.
2. Confirm the 5 exceptions are left as-is (no action needed, listed below for completeness/audit trail).
3. Decide whether the 11 "good first issue" + gittensor:priority OpenAPI-enrichment issues should keep gittensor:priority, or have it removed.

Deliverables — relabel bug → feature (81, in JSONbored/metagraphed)

3340, 3341, 3342, 3343, 3344, 3345, 3346, 3349, 3350, 3351, 3352, 3353, 3354, 3355, 3356, 3359, 3360, 3361, 3362, 3363, 3364, 3365, 3367, 3368, 3369, 3370, 3372, 3373, 3374, 3375, 3376, 3378, 3379, 3381, 3382, 3383, 3384, 3385, 3386, 3388, 3389, 3390, 3392, 3393, 3394, 3395, 3396, 3397, 3398, 3399, 3400, 3401, 3403, 3404, 3407, 3422, 3423, 3424, 3432, 3433, 3434, 3435, 3451, 3452, 3453, 3454, 3463, 3464, 3465, 3466, 3468, 3469, 3470, 3472, 3473, 3474, 3475, 3481, 3482, 3487, 3489

Confirmed-correct as-is (no action needed): 3347, 3425, 3426, 3428, 3486

Priority-dilution review (decide keep/remove gittensor:priority): 463, 465, 466, 577, 672, 675, 714, 720, 728, 731, 733

Expected outcome

Contributor point-payout for these 81 metagraphed issues matches the actual size/value of the work.

Non-goals

• Not a code change — filed in gittensory per request, but the actual relabeling happens on the metagraphed issue tracker.

[linear-code]

JSO-2865

[JSONbored]

Priority-dilution review resolved — no change needed. Confirmed with @JSONbored: subnet-enrichment issues (Enrich SN... — add OpenAPI/Swagger spec etc.) are intentionally always gittensor:priority, regardless of good first issue/effort size — they're small changes that wouldn't be worth much on their own, so priority is the deliberate incentive to get them done. Checked all 13 open Enrich...-titled issues: the 12 real subnet-enrichment ones (#463, #465, #466, #577, #672, #675, #714, #720, #728, #731, #733, #1275) already carry gittensor:priority consistently. The 13th (#3400, "Enrich the accounts-lookup invalid-address empty state") is unrelated UI-copy work that happens to share the word "enrich" — correctly excluded, and already relabeled to gittensor:feature as part of the 81-issue batch above.

81-issue relabel: done. All 81 issues verified gittensor:feature with no gittensor:bug remaining (2 of them — #3452/#3453 — were closed by unrelated merged PRs mid-session; their label was already fixed before that happened).

Closing this out.