[BUG] Greptile plugin trigger_code_review fails with 'Repository not found' for enabled repo

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The official Greptile plugin's trigger_code_review MCP tool fails with "Repository not found" for a repository that is fully enabled in the Greptile dashboard and successfully receives webhook-triggered reviews.

Steps to Reproduce

1. Have a repository enabled in Greptile dashboard (confirmed visible in Settings > Repositories as one of the enabled repos)
2. Open a PR on that repo
3. Call trigger_code_review via the MCP tool:

mcp__plugin_greptile_greptile__trigger_code_review(
    name: "owner/repo-name",
    remote: "github",
    prNumber: 92,
    branch: "feature-branch",
    defaultBranch: "main"
)

1. Observe error: "Repository not found: owner/repo-name on github"

Additional Observations

• Tried both the exact GitHub casing (idStar/claude-config) and lowercase (idstar/claude-config) — both fail, but with different errors:
• idStar/claude-config → "Repository not found: idStar/claude-config on github"
• idstar/claude-config → 404 - Cannot POST /
• Other Greptile MCP tools work fine for the same repo: list_code_reviews, get_code_review, list_merge_request_comments, get_merge_request all return data correctly
• Webhook-triggered reviews work: Adding the greptile-review label to the PR triggers a Greptile review successfully via webhook. The review completes with full analysis.
• The repo appears in list_code_reviews output as idstar/claude-config with completed reviews

Environment

• OS: macOS (Darwin 25.2.0)
• Plugin version: greptile@claude-plugins-official version 2cd88e7947b7 (git SHA e30768372b4150ca1bc0839d93283e8edc30d60d)
• Greptile plan: Active, 7 repos enabled

Expected Behavior

trigger_code_review should trigger a review for any repo that is enabled in the Greptile dashboard and accessible via other Greptile MCP tools.

Actual Behavior

trigger_code_review returns "Repository not found" despite the repo being enabled and other MCP tools working for the same repo.

Workaround

Use label-based triggering instead of the MCP tool:

gh pr edit "$PR_NUMBER" --add-label "greptile-review"

Greptile's webhook detects the label and auto-triggers the review. Then poll with list_code_reviews + get_code_review by ID.