chore(raycast): remove unused Raycast scaffolding

[JSONbored]

What

Removes src/raycast/ (local-repo-analyzer.ts + maintainer-commands.ts) and their two unit tests. These were scaffolding for a Raycast extension that was never built.

Why it's safe

Verified the footprint is fully self-contained dead code:

• Nothing outside src/raycast/ (or its 2 tests) imports it — no MCP tool, route, barrel export, package, or script references Raycast anywhere in the repo.
• No Raycast extension, apps/ entry, package, or build script exists.

This also retires the one non-hermetic test (raycast-local-repo-analyzer's temp-repo git commit -m initial inherited the developer's global git config and failed under SSH/TouchID commit signing) — by deletion rather than a signing-agnostic patch, since the whole module is going.

If a Raycast extension is ever built, the local-branch analysis already lives as first-class signals (src/signals/local-branch.ts) + MCP tools to build on.

Verification

Dead-code removal only. typecheck, the 97% coverage gate (now 97.05% branches), workers tests, and git diff --check all stay green.

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#720 is no longer open.	No action.

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[ghost]

gittensory · advisory review

Reviewed 4 changed file(s) — two independent AI reviewers.

Suggested action: ✅ Safe to merge — both reviewers found no blocking issues.

Reviewer A · gpt-oss-120b — recommends ✅ merge
This PR deletes the entire Raycast local‑repo analyzer and maintainer‑commands modules along with their unit tests, as they are apparently unused scaffolding. The removal is straightforward and does not introduce new code or behavior.

Suggestions

• Run the full TypeScript build after merging to confirm no remaining imports reference the deleted modules.
• Update any documentation or changelog to note that Raycast support has been removed.
• If Raycast integration is still desired in the future, consider adding a clear deprecation path rather than outright deletion.

Worth double-checking

• If any part of the codebase (or external tooling) still imports these modules, the build will fail.
• Removal may break any existing Raycast extension that relied on this scaffolding.

Reviewer B · nemotron-3-120b-a12b — recommends ✅ merge
The PR removes the entire Raycast scaffolding (four files: src/raycast/local-repo-analyzer.ts, src/raycast/maintainer-commands.ts, and their corresponding test files) as unused code. This is a cleanup chore with no functional impact if the code is indeed unused. The removed code was isolated to the Raycast module and did not appear to integrate with core Gittensory functionality (API, UI, or MCP).

Worth double-checking

• Undiscovered imports or usage of the removed Raycast modules elsewhere in the codebase could cause breakage.
• If the Raycast code was intended for future use or was mistakenly considered unused, removal may discard useful work.
• Ensure no configuration, documentation, or references to Raycast remain that could confuse users.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.