[huyplb]

What

• SQL Tracer on the page: utilities.trace (feat(utilities): SQL Tracer — live sessions and Fox activity #564) gets a feature card. The inventory is re-measured on main at b12bcd5607: 34 features, 158 routes, 18 server modules, 57 e2e specs in 35 groups, about 550 unit-test files. FEATURE_MAP.md takes the same counts.
• docs: compare window, app.write, and workspace ceiling #563's edits folded into the sources: docs: compare window, app.write, and workspace ceiling #563 edited docs/feature-map.html by hand, after docs(feature-map): keep the page's sources in the repo; npm run docs:feature-map #567 had made it a generated file. Its changes are now in docs/feature-map/data.js: No password for Redis and MongoDB, Compare 2,000 rows and the shared migrate cap, and the new e2e specs. Without this, the next rebuild would have dropped them. The rebuilt page also picks up the newer diagrams from FEATURE_MAP.md, which the hand-edited page was missing.
• Guard test: feature-map-build.test.ts now fails while the committed page differs from the build, so a hand edit can't land again. FEATURE_MAP.md says so.

Checks

• A/B: a one-character hand edit to the page fails the new test, and a rebuild passes it.
• The page opens in a browser with no console errors, all 11 diagrams render, and the SQL Tracer card shows.
• tsc, lint and doc-paths.test.ts pass.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation and generated HTML only, plus a CI guard test; no runtime product code changes.

Overview
Updates the feature map docs and generated HTML to match main at b12bcd5607: 34 features, 158 routes, 18 server modules, 57 e2e specs (~550 unit tests), plus refreshed system/workflow mermaid diagrams (including app.write / GET reads before workspace scope and the data compare → migrate path with the 2,000-row cap).

Adds utilities.trace (SQL Tracer) to the interactive inventory in docs/feature-map/data.js and rebuilds docs/feature-map.html. Prior hand-edits to the HTML (#563) are moved into data.js (e.g. Redis/MongoDB No password, route/coverage counts, e2e group list) so the next npm run docs:feature-map run does not drop them. FEATURE_MAP.md documents that the HTML must not be edited directly.

feature-map-build.test.ts now asserts the committed page equals buildStaticPage(buildBoardPage(readSources())), failing with a message to run npm run docs:feature-map when stale.

^{Reviewed by Cursor Bugbot for commit 311396a. Bugbot is set up for automated code reviews on this repo. Configure here.}