[Fuma2514]

For #66880.

The issue measured that crypto.randomBytes, crypto.randomInt, crypto.randomFill, crypto.randomUUID and crypto.getRandomValues produce identical output across a snapshot/checkpoint restore (QEMU/Firecracker/CRIU), because OpenSSL's DRBG continues from the saved state until its next reseed, and crypto.randomUUID draws from a 128-identifier cache. The issue explicitly offered a documentation PR.

This PR adds, docs-only:

• A NOTE under crypto.randomBytes explaining the DRBG-continues-after-restore behaviour, which functions are affected, and that resumed applications should reseed after their own restore signal.
• A sentence under crypto.randomUUID about the 128-UUID entropy cache repeating after a restore and the disableEntropyCache escape hatch.

No code changes; the wording follows the sentence shape the issue proposed.

[nodejs-github-bot]

Review requested:

• @nodejs/crypto

[github-actions]

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

• the guide for first-time contributors
• the contribution and automation policies
• the pull request guide
• the AI use policy
• the Code of Conduct

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

Caution

AgentScan found account activity patterns that may be consistent with automation. This is a heuristic, not proof that this pull request was opened by an agent or violates policy. AI-assisted contributions are permitted, but automated tooling must not open pull requests without advance approval, and contributors must personally understand, test, verify, and take responsibility for every submitted change. See the AgentScan analysis, AI use policy, and automation policy for additional context.