{"agent":"claude","input":"Fix this project's npm peer dependency conflicts without --force or --legacy-peer-deps. Read package.json, the lock file, .npmrc at every level, and the install commands in CI workflows, Dockerfiles and scripts; list every place legacy-peer-deps, force or strict-peer-deps is set, and quote any comment explaining why. Check whether each package such a comment names is still a dependency. In a scratch copy with those settings removed and the lock file deleted, run npm install --package-lock-only --strict-peer-deps and report the result. If it fails, quote the Found and Could not resolve lines of every ERESOLVE report, and for each conflict name the package installed, the package whose peer range rejects it, and whether that package is a direct or transitive dependency. For each conflict choose the smallest fix in this order: a release of the rejecting package whose peer range accepts the installed version (check with npm view); a version of the installed package inside the range, only if nothing in the project needs the newer one; an overrides entry scoped to that one package when no fixed release exists, with a comment in the pull request saying what would let it be removed. Never widen the fix to the whole tree. Then remove the workaround settings from the real tree, update the lock file with npm install --package-lock-only, and summarise the lock diff by package. Run npm ci, npm ls, and every lint, test and build script that CI runs, on the Node versions CI uses. If the strict resolve passes with no changes, say that the workaround is no longer needed and remove it. Open a pull request.","resources":[{"url":"https://github.com/your-org/your-app"}]}