{"agent":"claude","input":"Set up Jest and write unit tests for this Gatsby blog, then open a pull request. Read package.json, package-lock.json, .prettierrc, gatsby-config.js, gatsby-node.js, gatsby-browser.js, gatsby-ssr.js, src/components/layout.js, src/components/bio.js, src/components/seo.js, src/templates/blog-post.js, src/pages/index.js, src/pages/404.js and src/pages/using-typescript.tsx first. Follow the Gatsby unit-testing guide the test script links to: add jest, babel-jest, babel-preset-gatsby, jest-environment-jsdom, identity-obj-proxy, @testing-library/react and @testing-library/jest-dom with npm install --save-dev, add jest.config.js with jest-preprocess.js, a file mock for images and fonts, identity-obj-proxy for css, __PATH_PREFIX__ in globals and jsdom as the environment, and add __mocks__/gatsby.js and __mocks__/gatsby-plugin-image.js. Replace the failing test script with jest. Write tests under src/__tests__ for Layout on the root and a nested path, Bio with and without an author name, Seo's title and description fallback, the blog-post template's previous and next links, the index page's empty state and post list, and gatsby-node's createPages previous and next id chain and onCreateNode slug field, using a fake graphql and spies for the actions. Match the repository's Prettier style with no semicolons. Run npm test and npm run build and paste both outputs in the pull request. Do not change any component, page or gatsby-node logic.","resources":[{"url":"https://github.com/your-org/your-app"}]}