observatory

# Observatory tracking `jcodemunch-mcp`, `jdocmunch-mcp`, and `jdatamunch-mcp` are tracked weekly at https://jgravelle.github.io/jcodemunch-observatory/ alongside Express, FastAPI, Gin, Pydantic, Django, Flask, NestJS, and Cobra (11 repos total). Cron: Mondays 06:00 UTC. Config edits auto-trigger a rebuild via the workflow's push-on-paths filter. ⚠⚠ **MONDAY 2026-08-31 IS THE FIRST HONEST BUILD, AND IT WILL LOOK LIKE A REGRESSION.** Until v1.108.303 the pipeline cloned with `--depth=1`, so `churn_surface` read churn 1 for every file in every repo and the axis ranked nothing but complexity — **every published score was flattered, ours included.** Expect a step change across the roster with no upstream cause: jcm goes **81.3 (B) -> 75.6 (C)**, and gin's grade holds at 91.8 (A) while its `churn_surface` raw moves 55.45 -> 39.42 because a different symbol becomes top hotspot. **Do NOT chase this as a new defect and do NOT attribute it to any release.** jjg decided on 2026-08-27 to let the cron publish it rather than trigger a rebuild early. Delete this note once that build is up. **Scores are NOT transcribed here.** Pull them from the live `index.json` before quoting them anywhere ([[feedback_verify_observatory_output]]). A transcription is always stale: the cron is Mondays 06:00 UTC, so it lags any same-week release. As of the 2026-07-20 build, suite ranking holds: jdatamunch > jdocmunch > jcodemunch — smaller, more focused tools score higher; jcm carries more surface area. ...