tools: one expert atlas, not two — retire expert_atlas.py, analyze.py gains --web for the dashboard

c/tools/expert_atlas/README.md

@@ -7,10 +7,16 @@ histogram, and turns them into a per-expert topic-affinity vector.
 cd c
 export COLI_MODEL=/path/to/glm52_i4
 ./tools/expert_atlas/sweep.sh                             # 30 probes (10 topics x 3 prompts)
-python3 tools/expert_atlas/analyze.py  --stats atlas_out/stats --out atlas_out/experts.json
+python3 tools/expert_atlas/analyze.py  --stats atlas_out/stats --out atlas_out/experts.json \
+        --web web/dist/experts.json                       # optional: feed the web dashboard Atlas
 python3 tools/expert_atlas/validate.py atlas_out/stats 200 # leave-one-prompt-out check
 ```
 
+`--web` writes the same atlas in the shape the web dashboard consumes (the Atlas galaxy and the
+Brain hover tooltips): keyed `"layer:expert"` with `affinity`/`entropy`/`top`/`label`. It replaces
+the retired `tools/expert_atlas.py`, whose API-driven probing ran through a live server and was
+exposed to exactly the traps above (server-side `--topp`, speculative drafts, shared `.coli_usage`).
+
 ## Read this before you trust any atlas
 
 Four things silently corrupt this measurement. The sweep script controls all of them; if you