Improve agent feedback reporting reliability (#99591)
## What? - Keep qualifying feedback candidates through the reporting pass after an agent resolves or works around the issue. - Always include generated review URLs in the final response, regardless of whether the browser tab opened. - Let the anonymization eval accept alternate valid source fixes instead of requiring one function shape. ## Why? Codex and OpenCode completed the positive feedback eval but dropped the feedback candidate after fixing the application. The protocol also only required the review URL when opening the form failed, which could leave a successfully opened background tab difficult to find. ## How? - Clarify the short managed `AGENTS.md` block and full reporting protocol. - Assert the new managed-block guidance in the development test. - Reject the known broken route-helper signature in the eval while allowing equivalent valid implementations. ## Verification - `pnpm prettier --with-node-modules --ignore-path .prettierignore --write ...` - `npx eslint --config eslint.config.mjs --fix ...` - The focused development test packaged successfully, but the isolated local fixture could not start because a linked workspace dependency (`@next/env`) was unavailable. CI will run it in the complete workspace. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment