fix(webapp): gemma-2-2b default graph follows the selected source set

[hijohnnylin]

Problem

Switching source sets on the gemma-2-2b graph page reloads to /gemma-2-2b/graph?sourceSet=<name> with no slug. The no-slug branch then hardcodes gemma-fact-dallas-austin, a gemmascope-transcoder-16k graph, regardless of the selected source set. Its pinned ids and supernodes (20_15589_* etc.) are transcoder feature ids, so on clt-hp the page showed a graph from the wrong source set.

Fix

In apps/webapp/app/[modelId]/graph/page.tsx, when modelId === 'gemma-2-2b' and the resolved source set is clt-hp, pick factthecapitalof-1789506352829 instead. That graph is not featured, so it is not in the preloaded metadata map for most visitors; the pick falls back to the same prisma.graphMetadata.findUnique lookup the slug branch uses and adds it to the map.

Every other source set keeps the existing gemma-fact-dallas-austin pick, unchanged.

Checks

• prettier --check, eslint (pre-existing any warnings only), tsc --noEmit pass.

Made with Cursor