track: upstream entrius/gittensor planning/scoring tooling (#1460 gitt miner advisor, #630 scoring change)

[JSONbored]

Why

Upstream gittensor has open work that overlaps gittensory's planning/scoring and would shift our model if merged. Monitor + decide our response.

Watch list (entrius/gittensor)

• feat(mcp): expose maintainer-lane triage via gittensory_get_maintainer_lane #1460 'feat: add gitt miner advisor and gitt miner scan commands for miner optimization' (open, feature, 2026-06-09) — a planning/optimization tool inside gittensor. Decide gittensory's positioning + whether to consume it via the local scorer wrapper (feat(agent): local gittensor-root scorer MCP wrapper #782).
• test: verify reviewbot unified review (throwaway) #630 'Scoring deleted code with a lower weight' (open) — a scoring-weight change; if merged, gittensory's token/density scoring must account for it (feeds US3/US4 + the drift detector).

Deliverable

• Triage feat(mcp): expose maintainer-lane triage via gittensory_get_maintainer_lane #1460: complementary vs competitive; if it ships, plan to consume gitt miner advisor/scan output (ties feat(agent): local gittensor-root scorer MCP wrapper #782 local scorer wrapper + roadmap(pillar 5): MCP miner intelligence deepening #544 miner intelligence)
• Track test: verify reviewbot unified review (throwaway) #630 for merge; on merge, update the scoring model + verify the drift detector caught it
• Keep this issue updated as upstream evolves

Outcome

We never get surprised by an upstream scoring/planning change, and we make a deliberate build-vs-consume call on gitt-native planning. Milestone M1.