The command palette still says Code, Commits and New issue on every studio page #246

The palette is on every page and is the keyboard front door. In the studio its per-app rows are half converted (repoPalette, src/web/chrome.ts:293-315):

{ t: `${name} — Code`,       h: base },                                   // dev's noun
{ t: `${name} — ${studio ? "Told" : "Issues"}`,        h: tellsHref },   // converted (#174)
{ t: `${name} — ${studio ? "Changes" : "Pull requests"}`, h: changesHref },// converted (#174)
{ t: `${name} — Commits`,    h: `${base}/commits` },                     // dev's page
{ t: `${name} — New issue`,  h: `${base}/issues/new` },                  // dev's noun and page
{ t: `${name} — Runs`,       h: `${base}/runs` },
{ t: `${name} — Settings`,   h: `${base}/settings` },

So on an app's studio page, pressing the palette open offers Code, Commits and New issue — two of them landing on dev's pages — beside Told and Changes, which #174 taught to speak. The studio's own first verb, Tell the crew, is in the palette nowhere: the only Create row anywhere is New app (STATIC_PALETTE_STUDIO, src/web/layout.ts:278-289).

Why this survived the vocabulary table: test/studio-words.test.ts reads <main id="main"> with every <script> stripped — and the palette index rides as <script type="application/json" id="palette-index"> (layout.ts:300-321). The one surface on every page is the one surface the table cannot see.

Done looks like

• [ ] In studio mode the palette's per-app rows speak the studio's nouns and go to the studio's pages — the row for an app's first page is not called Code, and rows that only exist in dev are either absent or plainly marked as dev's.
• [ ] The studio's own verb is reachable: telling the crew about the app you are on is a palette row, going wherever a tell is written.
• [ ] Dev mode's rows are unchanged, exactly as today.
• [ ] The nouns come from src/web/studio/nouns.ts, like every other converted call site — no strings rebuilt in chrome.ts.
• [ ] test/studio-words.test.ts can see the palette: either it stops stripping this one data block, or a sibling test asserts the palette's items for a studio page directly. Whichever, dev's nouns in the palette fail the build from now on.
• [ ] Tests fail on today's code.

Files I expect to change

src/web/chrome.ts (repoPalette), src/web/layout.ts (STATIC_PALETTE_STUDIO, if the verb lives there), src/web/studio/nouns.ts (reuse), test/studio-words.test.ts.

Risks

The palette's rows are also matched by the browser's own folding of remote search results (layout.ts's studio flag rides along so those build the same addresses) — keep one idea of the noun, or the local rows and the remote ones will disagree in the same list. And the data block's escaping of < is what keeps it from closing its own script tag: anything new added here keeps going through JSON.stringify and that replacement.

Suggested: Quill.

Parked by the crew: the check failed and the decider saw no point in another try (pull #259 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.