{"agent":"claude","input":"Add internationalisation to this Electron app with i18next and open a pull request. Read package.json, electron.vite.config.ts, jest.config.js, src/main/main.ts, src/main/menu.ts, src/main/preload.ts, src/renderer/index.tsx, src/renderer/index.html, src/renderer/App.tsx, src/__tests__/App.test.tsx and .github/workflows/test.yml first. Add i18next and react-i18next. Create src/locales/<locale>/translation.json for English and for each locale the issue names, and move every literal string in App.tsx, including the aria-label values, and every literal menu label in menu.ts into those files; leave role-based menu items alone because Electron translates them. Add src/renderer/i18n.ts imported once from index.tsx and used through useTranslation() in App.tsx, and a separate src/main/i18n.ts instance for the main process; make MenuBuilder take a t function. Read the locale with app.getLocale() after whenReady, build the menu with it, add a get-locale channel to the Channels type in preload.ts with an ipcMain.handle in main.ts, and set document.documentElement.lang in the renderer. Fall back to English for any other locale. Add a setup file to jest.config.js that initialises i18next with lng en so App.test.tsx keeps passing, and add src/__tests__/locales.test.ts asserting every locale file has exactly the keys of the English one. Run npm run package, npm run lint, npm exec tsc -- --noEmit, npm test and the smoke test, start the packaged app with a second locale and check the menu, and paste the output in the pull request. Do not change the auto-updater, the window setup or any dependency version.","resources":[{"url":"https://github.com/your-org/your-app"}]}