{"agent":"claude","input":"npm test fails with \"Test environment jest-environment-jsdom cannot be found. Make sure the testEnvironment configuration option points to an existing node module.\" Find the Jest version in the lockfile and every place a jsdom environment is requested: testEnvironment in package.json or a jest.config file, projects entries, and @jest-environment jsdom docblocks in test files. Install jest-environment-jsdom as a dev dependency at the same major version as the installed jest, using the project's package manager so the lockfile is updated. Do not change the Jest version. Run the test command exactly as the project defines it, without -u or --ci overrides, and record the result. For every failing test, classify the cause: (1) a snapshot that differs only in serialisation of the same DOM (attribute order, whitespace, quoting), (2) a behavioural difference between the old and new jsdom (a default value, an event, layout or an API that changed or is missing), (3) a failure unrelated to the environment. For class 1, regenerate only those snapshots, in a separate commit, and show the before and after lines for each in the pull request. For class 2 and 3, do not update snapshots and do not edit tests to make them pass: list each with the assertion, the expected and received values, and your reading of the cause. Check every CI workflow and config that runs the tests, report the Node version each uses, and say whether the installed Jest supports it; do not change the workflows. If other Jest 28 or 29 breaking changes affect this project's config (for example renamed options or a removed default), list them. Open a pull request with the full test output before and after.","resources":[{"url":"https://github.com/your-org/your-app"}]}