Skip to content

feat(mcp): expose the repo label-policy audit via gittensory_get_label_audit #1602

Description

@oktofeesh1

Context

The deterministic label audit (buildLabelAudit, src/signals/engine.ts) reports whether a repo's configured label set (.gittensory.yml / dashboard) matches the live GitHub labels and is trustworthy for label-multiplier scoring — surfacing missing configured labels, suspicious status/source-style labels, and the overall trusted-label-pipeline readiness.

It already powers the repo-intelligence response, but has no MCP surface, so agents/CLI can't pull it. It is also absent from gittensory_get_repo_context, which exposes a different subset (lane / queueHealth / queueTrends / collisions / configQuality / dataQuality).

Proposal

Add a maintainer-authenticated, advisory-only gittensory_get_label_audit MCP tool, mirroring the merged gittensory_get_maintainer_noise (#1414) and gittensory_get_outcome_calibration (#1174): a thin load-or-compute service that loads the repo's labels + cached signals and runs the existing buildLabelAudit builder, surfaced through the standard redactSensitiveForMcp public-safe wrapper.

  • No new REST route, migration, or auth-policy change — purely additive to the MCP surface (reuses requireRepoAccess).
  • Output is the same public-safe audit already served in the repo-intelligence response.

Value

Maintainers of owned repos can verify — from an agent/CLI, not just the dashboard — that their label pipeline is correctly configured and trustworthy for label-multiplier scoring, catching missing/suspicious labels before they distort contributor scoring.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions