You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm version now bumps the website's version labels too. sync-version.sh rewrites the nav version pill on every page that carries
one, the landing hero's REV, and the book landing's REV, found by CSS class
so new pages are covered automatically; the hook stages exactly those files
with the manifests (--stage). 5.0.0 needed those 15 labels edited by hand. test-version-sync.sh now fails on a site label that drifts from package.json.
Fixed
The landing page's graph demos showed the retired engine's output. The
playground promised the engine's real output schema, but all six fixtures
used the old shapes (file-level hotspots, module cycles, files_by_depth,
doc/config buckets); they now match each wrapper's 5.0 output. The hero
ledger shows code · test only, as by_category does. The engine blog post
no longer tells readers to run /draft:graph for fresh results, and the May
walkthrough carries a note on the changed output. CONTRIBUTING's CI table,
the architecture template's module count, and the fetch script's header
are corrected too.
The landing-page hero overflowed on phones. Below 1100px the hero grid
switched to a 1fr track, whose minimum is its content's width, and the
install chip's no-wrap command held that at ~430px — so on a 390px screen
the tagline, install chip, stats row, and Impact Console were cut off at the
right edge. The track is now minmax(0, 1fr) and the command truncates with
an ellipsis beside its Copy button.