docs: make agent feedback command work in npm workspaces (#100135)
## Summary - Replace the managed agent-feedback command with `npx --no-install next internal agent-feedback-instructions`, so it resolves a workspace-hoisted `next` binary without downloading another version. - Keep the runtime generator, `create-next-app` template, docs, and generated-block test in sync. - Shorten the always-loaded retention rule while leaving detailed qualification guidance in the on-demand feedback protocol. Finding: https://next-maintainer-agent.vercel.tools/agent-feedback/1434 ## Verification - `pnpm exec jest --runInBand packages/next/src/server/lib/generate-agent-files.test.ts` (15 tests) - `HEADLESS=true pnpm test-dev-turbo test/development/app-dir/agent-rules-auto-generate/agent-rules-auto-generate.test.ts` (16 tests) - `HEADLESS=true pnpm test-start-turbo test/production/create-next-app/index.test.ts -t "should write the agent feedback block"` - From a nested workspace package with `next` available only in the root `node_modules`, `NEXT_TELEMETRY_DISABLED=1 npx --no-install next internal agent-feedback-instructions` exits successfully. - `pnpm --filter=next build` - `pnpm --filter=create-next-app build` - `pnpm lint` stops on two existing `no-map-async-cell` diagnostics in `crates/next-napi-bindings/src/next_api/analyze.rs`. - `pnpm build-all` stops while parsing an existing Cargo workspace dependency because `default-features = false` cannot override the workspace default. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment