next.js

9ff761f2 - Stop requiring build-all when bootstrapping a fresh clone or worktree (#100600)

Stop requiring build-all when bootstrapping a fresh clone or worktree (#100600) The agent instructions required a full `pnpm build-all` (JS and Rust) after every worktree creation or branch switch. That is unnecessary when bootstrapping a new clone or worktree: `pnpm install` already pulls in recent published native bindings, so there is nothing to build until source changes. The new guidance: - Bootstrapping a new clone or worktree does not start with `pnpm build-all`. Build only what your work changes: `pnpm --filter=next build` for core-only JS edits, `pnpm build` when JS changes span packages. - Switching branches or pulling can still require a build when it moves JS or Rust source relative to your build outputs; rebuild the affected parts before running tests. - `pnpm build-all` is reserved for Rust/Turbopack changes, or for when Next.js fails to start because native binding changes landed on canary after the last npm publish (cross-referenced from the Stale Native Binary section). The `backport-pr` skill repeated the old branch-switch rule and is updated to the same policy. <!-- NEXT_JS_LLM --> Co-authored-by: Claude Code <noreply@anthropic.com>