Delete dead code: utils/SqlFormatter.ts

[openidle-dev]

Severity: P2 — hygiene

src/utils/SqlFormatter.ts is a legacy hand-rolled SQL formatter. The editor uses the sql-formatter npm package via the QueryEditor flow instead. No code path imports SqlFormatter.ts.

Fix

Delete the file, remove any orphaned imports, run a typecheck.

Source: `audit/app-bugs.md` item #8.

[NicolaasGrobler]

Verified before deleting — the issue's premise is wrong: src/utils/SqlFormatter.ts is not dead code.

src/utils/SqlFormatter.test.ts:2:import { formatSql } from "./SqlFormatter";
src/components/layout/MainContent.tsx:13:import { formatSql } from "../../utils/SqlFormatter";

MainContent.tsx imports formatSql and uses it inside handleFormatSql, which is wired to a real toolbar "Format SQL (Prettify)" button. That code path is the hand-rolled formatter, not the sql-formatter npm package.

CLAUDE.md is also misleading here — the "SQL formatting (via sql-formatter)" line conflates the npm dep with this file.

Suggested re-scope

Two options:

1. Migrate then delete. Wire the toolbar "Format SQL (Prettify)" button to dispatch the existing format-sql CustomEvent (same path Ctrl+Shift+L already uses, per CLAUDE.md). Once MainContent.tsx no longer imports formatSql, delete SqlFormatter.ts + SqlFormatter.test.ts and update CLAUDE.md to reflect that sql-formatter is the only formatter.
2. Keep both. If the hand-rolled formatter produces meaningfully different output than sql-formatter (worth a quick A/B), close this issue and just fix the CLAUDE.md wording.

I'd lean toward (1) — one formatter is simpler — but worth a look at sample output before committing.