The palette with nothing typed shows what you used last #10674

With nothing typed, the command palette now lists the rows you opened before, most-used and most-recent first. I ran bun x tsc --noEmit, bun scripts/gate.ts and the three palette test files (palette, keys-palette, palette-entries), and all pass. I didn't run the rest of the suite or try it in a browser.

• Ordering: frecencyOrder(uses, now) in src/web/palette.ts is a pure, self-contained function that ships in paletteHelpersJs. A row scores its open count halved for every week since it was last opened. Ties go to the later open.
• Storage: in src/web/client.ts, opening a row records it in localStorage under the existing forge.palette.recent key, now with a count and a last-opened time. At most 50 are kept, and nothing is sent to the server.
• Display: the empty palette shows the top 8 by frecency, ahead of the other rows.
• Old entries: entries saved in the old format (no count) are read as opened once.
• Tests: four new tests in test/palette.test.ts: recent-and-frequent beats old-and-rare, a hand-calculated case, ties and no mutation of the input, and a check that the function is embedded in the shell script.

I didn't add per-visit history. The decay is applied to the whole count, which needs no extra storage but is only an approximation of full frecency.

To try it: open a few rows from the palette (Cmd/Ctrl K), then reopen it with nothing typed.

git push was rejected until the branch had a "Try:" commit message, so I added an empty commit carrying the try-it line.

Closes #10658

With nothing typed, the command palette now lists the rows you opened before, most-used and most-recent first. I ran bun x tsc --noEmit, bun scripts/gate.ts and the three palette test files (palette, keys-palette, palette-entries), and all pass. I didn't run the rest of the suite or try it in a browser.

• Ordering: frecencyOrder(uses, now) in src/web/palette.ts is a pure, self-contained function that ships in paletteHelpersJs. A row scores its open count halved for every week since it was last opened. Ties go to the later open.
• Storage: in src/web/client.ts, opening a row records it in localStorage under the existing forge.palette.recent key, now with a count and a last-opened time. At most 50 are kept, and nothing is sent to the server.
• Display: the empty palette shows the top 8 by frecency, ahead of the other rows.
• Old entries: entries saved in the old format (no count) are read as opened once.
• Tests: four new tests in test/palette.test.ts: recent-and-frequent beats old-and-rare, a hand-calculated case, ties and no mutation of the input, and a check that the function is embedded in the shell script.

I didn't add per-visit history. The decay is applied to the whole count, which needs no extra storage but is only an approximation of full frecency.

To try it: open a few rows from the palette (Cmd/Ctrl K), then reopen it with nothing typed.

git push was rejected until the branch had a "Try:" commit message, so I added an empty commit carrying the try-it line.

I've addressed all four review points and pushed. tsc, scripts/gate.ts and test/palette.test.ts, keys-palette.test.ts and readme-cap.test.ts pass.

• Tests: I took the second option and moved the recording into pure functions in src/web/palette.ts. recordUse increments the count, re-sorts by frecency and cuts to the cap. readUses validates stored entries, migrates legacy ones and drops off-origin links. Both ride in paletteHelpersJs, and remember and readRecent in src/web/client.ts now just call them.
• New tests: they fail if the count or the cap is removed. They cover count increment, the 50 cap with the least useful row falling off, an often-opened old row surviving a small cap, and legacy-entry migration. I replaced the old string-contains check. The remaining client check only pins that the script calls the helpers and uses limits of 50 and 8. The 8-shown behaviour is not run against a stub localStorage, so that line of the script is covered only by that string check.
• Docs: docs/features/palette-recent.md covers what the empty palette shows, that it is local to the browser, and the 50 and 8 limits.
• Clean: the unused i parameter is gone.
• Terminal: the doc says the terminal palette (src/tui/) has its own ranking and no browser storage, so it is out of scope.