[Claimed #2716] docs(integrations): stop recommending Corepack for pnpm

[github-actions]

Mirrored from external contributor PR #2716 after approval by @miguelg719.

Original author: @antonvishal
Original PR: #2716
Approved source head SHA: 2efa8a946ad33c6430c4bc668aa2e4d31e2d3006

@antonvishal, please continue any follow-up discussion on this mirrored PR. When the external PR gets new commits, this same internal PR will be marked stale until the latest external commit is approved and refreshed here.

Original description

Summary

• Replace corepack pnpm@11.10.0 with plain pnpm in the v4 integration docs (overview, Mastra, Eve, Vercel AI SDK, CrewAI).
• Link the integrations overview to the official pnpm install docs.

pnpm now says not to install via Corepack (Node also stopped shipping Corepack from v25). We already pin pnpm@11.10.0 via devEngines.packageManager, and CI uses pnpm/action-setup, so the docs only used Corepack as a one-shot version pin.

---

Summary by cubic

Stop recommending Corepack for pnpm in v4 integration docs and switch commands to plain pnpm. This aligns with pnpm guidance and Node 25 removing Corepack while keeping our version pinning and CI setup intact.

Review notes

• Replaced corepack pnpm@11.10.0 with pnpm in crewai.mdx, eve.mdx, mastra.mdx, vercel-ai-sdk.mdx, and overview.mdx.
• Linked the overview to the official pnpm installation docs and kept the requirement at pnpm 11.10.0.
• No code, build, or runtime changes; docs only.

^{Written for commit 2efa8a9. Summary will update on new commits.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
stagehand	🟢 Ready	View Preview	Aug 17, 2026, 9:07 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[github-actions]

This mirrored PR has been merged into main. The original external PR #2716 is now completed.

[changeset-bot]

⚠️ No Changeset found

Latest commit: fb77ad2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR