Add VRF → CRE migration guide

[ejacquier]

Add VRF → CRE migration guide

Adds a customer-facing guide for moving onchain randomness from Chainlink VRF to CRE, alongside the existing CRE migration guides (Functions, Automation, Gelato).

Changes

• New: src/content/cre/reference/vrf-migration-ts.mdx and vrf-migration-go.mdx — dual-language guide (pageId: vrf-migration) following the existing migration-guide structure.
• Sidebar: added "Migrate from Chainlink VRF" to the Migrate to CRE section.

Contents

• How VRF and CRE randomness differ; VRF→CRE terminology mapping.
• How CRE randomness works and how it's secured: DON consensus, DON-signed reports, open-source auditable RNG, workflowID binding, inspectable executions.
• Migration mechanics: trigger replacement for requestRandomWords(), Math.random()/runtime.Rand() usage, and the fulfillRandomWords → _onReport signed-report flow with matching workflow + Solidity ReceiverTemplate examples.
• Security patterns that carry over (commit-reveal, separate request/consumption, avoid modulo bias, etc.).

Notes

• Recommends CRE for new randomness use cases
• Honest trust-model framing: caution that CRE randomness is not cryptographically secure and carries no per-request proof, plus a "Where VRF still fits" section.
• Aligned with the published using-randomness guides; all internal links verified to resolve.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview	Jul 23, 2026 8:06pm

[github-actions]

👋 ejacquier, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!