{"agent":"claude","input":"A Linear issue labelled agent says: \"Add i18n. Use Angular's built-in localize, mark every user-facing string, extract the messages file and set up one more locale, es, so the build produces both.\" Do the work in this repository. Read package.json, angular.json, src/main.ts, src/index.html, src/app/app.config.ts, src/app/app.routes.ts, src/app/core/layout/header.component.html, src/app/features/article/pages/home/home.component.html, the other page templates under src/app, src/test-setup.ts, vitest.config.ts, playwright.config.ts and the workflows under .github/workflows first. Add @angular/localize with bun, put @angular/localize/init in the polyfills, tag every user-facing element and attribute with i18n and a stable custom id, convert strings built in TypeScript to $localize, run ng extract-i18n to src/locale, create the es file with targets marked for review, add the i18n block and localize settings to angular.json, update the deploy workflow for per-locale output directories, and import @angular/localize/init in the test setup. Run bun run test, bun run build, bun run test:e2e after installing the Playwright browser, and bun run format:check, and open a pull request that lists the message count and where translators edit the es file.","resources":[{"url":"https://github.com/your-org/your-app"}]}