v0.0.153

• Keep mermaid node labels readable on colored boxes in dark mode: the diagram renderer labels every node with the theme foreground even when the diagram sets its own fill via classDef or style, and those literal fills - usually light pastels - do not follow the theme, so dark mode painted white text over light boxes. The rendered SVG is produced once server-side and shared by both modes, so renderDiagram now bakes a literal contrast color into the labels of nodes whose shape carries a literal fill, chosen from the fill's perceived brightness: black on light fills, white on dark ones, correct in both modes at once. Nodes without a custom fill keep the theme-variable color so they continue to follow theme toggles, and a classDef that sets color: explicitly is left untouched

• Fall back generated site icons to icon.png: the default favicon constant still pointed at the legacy favicon.ico while generated sites standardize on icon.png under the icon file convention, so a project with no root icon.png and no config.json icon resolved its fallback to the old format. The fallback now resolves to icon.png like every other icon path

• Fix the browser-chrome color flipping back to the light primary on every route change: 0.0.151 served the theme-color meta from a static viewport export, and on each soft navigation Next re-asserts that React-owned tag with its baked-in light value, which then sticks because Cherry's post-hydration sync only re-runs on theme changes. The tag is script-owned again, as in the pre-release builds: the pre-paint script emits it via document.write with the resolved mode's primary already in it, so the right color is in place from the first paint, hydration has nothing to reconcile (a server-rendered tag corrected pre-paint is answered by React 19 hydration with a stale duplicate, which is what 0.0.150 shipped), and navigation never touches it. Cherry's $themeColor="primary" sync keeps it current across theme toggles, on the same primary token the script resolves. The Theme page's Browser chrome note in the generated starter documentation describes the restored behavior again

• Update generated app dependency tsx to ^4.23.6