chore: add a committed Graphify knowledge graph of the codebase

[AlaskanTuna]

Builds a persistent, queryable knowledge graph of the codebase and commits it, so architecture and relationship questions can be answered from a compact map instead of re-reading files. Most useful during the upcoming provider migration, where "what still depends on Supabase" is a question that gets asked repeatedly.

What's committed

• graphify-out/graph.json — the queryable graph (1630 nodes, 3624 edges, 128 communities)
• graphify-out/GRAPH_REPORT.md — human-readable report
• .gitignore — keeps the churny, regenerable artifacts local (graph.html at 1.5 MB, cost.json, manifest.json, cache/)

Cost

Zero. Built with graphify extract . --code-only (AST only) plus graphify cluster-only . --no-label, so community detection runs without LLM naming — 0 input / 0 output tokens, no API key used.

Scope

A local .graphifyignore restricts extraction to code: 312 files, 0 documents/images. Non-code files that would otherwise trigger per-file semantic extraction are excluded, as are all image directories.

Refresh

graphify update . after notable code changes — no LLM, free. Note graphify refuses to write a graph.json smaller than the existing one; any change that deletes a meaningful slice of source (such as the planned Supabase removal) will trip that guard and needs --force.

Sample queries, verified

Question	Answer
what calls the Google Solar API	backend/src/services/solarApiService.ts
where is flux recomputed for moved panels	backend/src/services/fluxRecomputeService.ts
what still depends on Supabase	config/supabase.ts, middleware/auth.ts, userService.ts, storageService.ts, env.ts

Closes #19

[coderabbitai]

Warning

Review limit reached

@AlaskanTuna, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dd92a6e3-f334-4ba1-9024-d02390fd4f72

📥 Commits

Reviewing files that changed from the base of the PR and between 5c2af1a and 464e8fd.

📒 Files selected for processing (5)

• .gitignore
• .prettierignore
• README.md
• graphify-out/GRAPH_REPORT.md
• graphify-out/graph.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}