@codeatlas/mcp 2.0.0 → 2.0.2

package/README.md

@@ -149,9 +149,19 @@ A tab opens at `http://localhost:7742` showing six linked diagram layers: system
 
 Set `CODEATLAS_EDITOR=<cmd>` to pick the editor (defaults to `$EDITOR`, then `code`, `cursor`, `subl`, `nvim`, `vim`).
 
+### Run a Code Review from the browser
+
+The home page has a **Code Review** card that fans the review out across every entry point. **Changed only** restricts it to entry points whose code differs from baseline. **Specific review** opens a textarea so you can tell the AI exactly what to focus on. **Cancel** stops the in-flight LLM call immediately; **Clear** wipes findings and resets state.
+
+When findings exist, the **Findings popover** opens with a top-down summary: an "Interpretation" line that names the dominant pattern across all findings (auth gaps, validation risks, secret leakage, N+1 queries…), per-layer breakdowns that name the actual clusters / routes / files affected, and a "Top concerns (focus here first)" shortlist. Every finding row carries **Resolve / Ignore / Comment / Copy** buttons. A "Copy ▾" dropdown copies all findings — or just errors / warnings / info — as Markdown ready to paste into a PR or ticket.
+
+Inside every diagram (System Design, Feature Areas, API List, Sequence, File, Function Flow), entities with findings show a colored count marker. Click it to open the popover (same actions) right where the issue lives — state changes propagate to every open tab immediately.
+
+Each finding is tagged with the commit SHA it was reviewed against (or a content-hash for non-git workspaces). Re-running with the same code + guidelines surfaces a **"Nothing changed since last review"** badge instead of burning another LLM call.
+
 ### Connect an LLM
 
-AI Review and natural-language search use any OpenAI-compatible provider. Pick one:
+Code Review and natural-language search use any OpenAI-compatible provider. Pick one:
 
 | Provider | Env var | `provider` setting |
 |----------|---------|--------------------|