fix(transcription): give the model-registry JSON import its type attribute

[gabrielste1n]

Three transcription paths have thrown needs an import attribute of "type: json" in packaged builds since 1.9.1, on every platform. One missing import attribute. Also prepares 1.9.2.

Fixes #1908

Root cause

policyRules.ts gained import modelRegistryData from "../models/modelRegistryData.json" in 1.9.1 via #1836. ipcHandlers.js reaches that module through Electron's bare Node ESM loader, which requires with { type: "json" } on JSON imports. Reproducible straight from the source tree, no packaging needed:

$ node -e 'import("./src/stores/policyRules.ts")'
ERR_IMPORT_ATTRIBUTE_MISSING: Module ".../src/models/modelRegistryData.json"
needs an import attribute of "type: json"

voiceSurfaceGeometry.mjs:1 already writes it the correct way, so the fix matches what is already in the tree.

Blast radius

I walked the main-process ESM graph: 7 modules, exactly one bad JSON import. ipcHandlers.js is the only main-process file that imports raw .ts, and it does so from three handlers:

Handler	Feature
proxy-xai-transcription	xAI dictation
retry-transcription	Re-transcribing a saved recording
transcribe-audio-file-byok	Bring-your-own-key file uploads

Ordinary dictation is unaffected, which matches the reports.

Narrower than the issue thread suggests. audioManager.js and discardedRecording.js are renderer modules (imported by ControlPanel.tsx and useAudioRecording.js), so Vite inlines their JSON. languageSupport.ts, prompts.ts and translations.ts are not in the main-process graph either — i18nMain.js bypasses prompts.ts and require()s the raw per-locale JSON. ModelRegistry.ts carries the same shape but every importer uses an extensionless specifier, which Node's resolver does not resolve, so it is latent rather than reachable. Only the one site is fixed here.

Why the existing tests passed

test/helpers/transcriptionRoute.test.js already imports the exact module that fails in production, 13 tests deep. The suite runs under node --import tsx, and tsx resolves attribute-less JSON imports:

node --import tsx --test  →  13 pass     # what CI runs
node --test               →  13 fail     # what the packaged app does

So adding another ordinary test would not have helped. The new test spawns each main-process ESM entry in a child process with NODE_OPTIONS stripped, so it exercises the loader the packaged app actually uses. Verified red-first: it fails without the one-line fix and passes with it.

eslint.config.js:8 also ignores helpers/** and utils/**, so no static rule could have caught this either.

1.9.2

Bumps the version and moves the changelog's Unreleased entries into a [1.9.2] section covering everything since 1.9.1:

• fix(windows): only hand explorer.exe URLs it can actually deliver #1932 — Windows desktop sign-in
• Text cleanup broken in packaged 1.9.x: modelRegistryData.json ESM-imported without with { type: "json" } (policyRules.ts / ModelRegistry.ts) #1908 — this fix
• fix(meetings): Add swipe dismissal to meeting notifications #1906 — swipe-to-dismiss on meeting prompts

Verification

Ran against a freshly installed node_modules (my local copy was stale, which had been masking two unrelated failures):

• npm run typecheck — clean
• npm run lint — clean, zero warnings
• npm run format — no changes to make
• npm test — 3314 tests, 0 failures, 185 skips (the usual local better-sqlite3 ABI skips)
• npm run build:renderer — builds

Prettier is clean on all touched files. Worth noting separately: the repo's format script runs Prettier from inside src, so test/** is never covered by it — 38 test files are currently unformatted. Identical count before and after this change, so I left them alone rather than burying a release fix in reformatting noise.

Follow-ups, not in this PR

• policyValidation.js:35 rejects forward-compatible policies. It validates server-sent provider ids against the client's own bundled registry, so a 1.9.0 client receiving gemini in allowedByokProviders fails isValidPolicyShape, workspacePolicyManager.js:288 throws "Malformed policy response", and policyRules.ts:24 fails closed — a personal account gets a locked model selector and a "Managed by your organization" badge. The same file already documents the right pattern for requiredLocalModels at lines 50-53, and both behaviors are pinned by contradictory tests (policyValidation.test.js:79 accepts unknown model ids, :121 rejects unknown providers). As written, every provider added server-side breaks every older client.
• Main process should not load raw TS. electron-builder.json hand-enumerates src/stores/policyRules.ts and src/services/transcriptionBaseUrl.ts file by file, which is the packaging config signalling how fragile this is. Bundling main would remove the whole bug class.
• The issue title says "text cleanup", but none of the three reachable handlers is cleanup — @lysacor's "re-transcribe a recording" is the accurate repro.