Skip to content

CLI mirror for loopover_get_maintainer_lane #6739

Description

@JSONbored

Context

The MCP tool loopover_get_maintainer_lane (src/mcp/server.ts:1863, via getMaintainerLane/loadMaintainerLaneReport) returns the same data already present as the .maintainerLane field of GET /v1/repos/:owner/:repo/intelligence (src/api/routes.ts:2362, built in buildRepoIntelligenceResponse). The CLI already has loopover_get_label_audit proxying to this same /intelligence endpoint and picking out .labelAudit (loopover-mcp.js:1521-1535) — maintainerLane sits right beside labelAudit in the same response but has no CLI extraction.

Requirements

  • Add registerStdioTool("loopover_get_maintainer_lane", { inputSchema: ownerRepoShape }, ...) that GETs {prefix}/intelligence and returns { repoFullName, generatedAt, maintainerLane: intelligence?.maintainerLane ?? null }, copying loopover_get_label_audit's implementation exactly.

Deliverables

  • registerStdioTool("loopover_get_maintainer_lane", ...)
  • Unit test asserting parity with loopover_get_label_audit's pattern

Test Coverage Requirements

99%+ Codecov patch coverage on every changed line and branch in the new route/tool/CLI code, plus a test asserting output parity between the mirrored surfaces for identical input.

Expected Outcome

Maintainer-lane data is queryable from the CLI, matching its sibling labelAudit field's existing extraction.

Links & Resources

Precedent: registerStdioTool("loopover_get_label_audit", ...) at loopover-mcp.js:1521-1535 — byte-for-byte the same pattern, different field.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is needed

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions