feat(raycast): add miner command center

[JSONbored]

Parent roadmap: #82

Background

Miners should be able to quickly ask what to work on, what blocks them, and what to do with open PRs without switching context.

Goal

Add Raycast commands for plan next work, analyze current repo, show open PRs, copy PR packet, and explain blockers.

Current Behavior

No Raycast commands exist today.

Desired Behavior

Raycast provides a compact miner workflow backed by existing Gittensory API outputs.

Implementation Requirements

• Add commands for agent plan, branch analysis, open PRs, PR packet, and blockers.
• Reuse API/MCP response shapes.
• Keep local repo inspection metadata-only.
• Provide copy actions for public-safe packets.
• Handle auth/rate-limit/API errors cleanly.

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

• Commands return useful output with mocked API.
• Copy PR packet is public-safe.
• Rate limits show retry guidance.
• Source contents are never read/uploaded.

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

• Agent plan mock.
• Branch analysis mock.
• Open PRs mock.
• Rate-limit fixture.
• Source guard test.