feat(raycast): add maintainer queue commands

[JSONbored]

Parent roadmap: #82

Background

Maintainers need a quick way to inspect queue health, installation health, and Gittensory's public-surface decisions.

Goal

Add Raycast commands for repo queue intelligence, installation health, comment/label preview, and public-surface settings summary.

Current Behavior

Maintainer intelligence exists through API/GitHub App surfaces, but not in Raycast.

Desired Behavior

Repo maintainers can use Raycast to inspect private queue context without creating public GitHub output.

Implementation Requirements

• Add repo picker/input.
• Fetch repo intelligence and install health.
• Show comment/label/check mode.
• Add preview command for public-safe output.
• Keep private reviewability in local private view only.

Public/Private Output Boundaries

Raycast is a client surface over the existing Gittensory API/MCP concepts. It must not store GitHub PATs, upload source contents, or expose private scoreability in public GitHub output.

Acceptance Criteria

• Maintainer queue command works with mocked API.
• Install health command explains missing permissions.
• Preview command does not post.
• Private context is not copied into public packet by default.

Testing Requirements

• npm run test:ci must pass.
• Global coverage must remain at or above 97% for lines, statements, functions, and branches.
• Aim for 98%+ branch coverage locally to avoid CI variance.
• Add tests for every new branch, fallback path, sanitizer rule, and regression.
• Add invariant/property-style tests when behavior depends on sorting, gating, scoring, queue pressure, source-upload safety, public/private boundaries, or upstream drift.
• Public GitHub output must be tested against forbidden language: wallet, hotkey, raw trust score, payout, reward estimate, farming, private reviewability, and public score estimate.
• MCP/local tooling must prove source contents are not uploaded.

Additional Test Scenarios

• Healthy install mock.
• Missing permission mock.
• Preview no-post test.
• Public/private copy boundary test.