Add cheatcode documentation

[popescuoctavian]

This PR adds documentation for Solidity test cheatcodes.

Notes:

• The Foundry book was used for cheatcodes that are already documented there and are supported by HH/EDR. This was updated to remove unsupported references and adapted to match our implementation.
• Documentation was generated for the others using the documentation comments in vm.rs.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
hardhat-website	Ready	Preview, Comment	Jan 14, 2026 1:27pm

[Copilot]

Pull request overview

This PR adds comprehensive documentation for Solidity test cheatcodes, covering utilities, types, state snapshots, signing, RPC, fuzzer, forking, file operations, external interactions, and environment manipulation.

Key changes:

• Added documentation for 200+ cheatcode functions and types
• Includes function signatures, descriptions, and practical examples
• Content adapted from Foundry Book (MIT licensed) where applicable

Reviewed changes

Copilot reviewed 227 out of 228 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
utilities/*.mdx	Documentation for utility cheatcodes (string manipulation, random generation, parsing, etc.)
types/*.mdx	Type definitions for cheatcode structs and enums
state-snaptshots/*.mdx	State snapshot management cheatcodes
signing/*.mdx	Cryptographic signing operations
rpc/*.mdx	RPC endpoint configuration and usage
fuzzer/*.mdx	Fuzzing test configuration cheatcodes
forking/*.mdx	Blockchain forking and fork management
file/*.mdx	File system operations
external/*.mdx	External data handling (JSON, TOML, environment variables)
environment/*.mdx	EVM state manipulation cheatcodes

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The function signature shows bytes calldata key but environment variable names should be strings. This should be string calldata key to match the pattern used in other env* cheatcodes.

Suggested change

	function envBytes(bytes calldata key) external returns (bytes value);
	```
	```solidity
	function envBytes(
	bytes calldata key,
	function envBytes(string calldata key) external returns (bytes value);

function envBytes(
  string calldata key,

[Copilot]

The function signature shows bytes calldata key but environment variable names should be strings. This should be string calldata key to match the pattern used in other env* cheatcodes.

[Copilot]

The description incorrectly states the function returns address[] for arrays, but the signature shows it returns bytes32[] memory values. Should be "Read an environment variable as bytes32 or bytes32[]."

Suggested change

	Read an environment variable as `bytes32` or `address[]`.
	Read an environment variable as `bytes32` or `bytes32[]`.

[agostbiro]

This looks really good, thank you!

I reviewed by browsing the preview website and noted the following things:

• A conceptual explanation of cheatcodes would be nice, but probably out of scope for this PR
• We shouldn't include private methods in the docs (_expectCheatcodeRevert, _expectInternalRevert)
• Possibly move types next to relevant methods instead of a separate section?
• Foundry spells cheatcodes in one word, so we should follow that consistently

[popescuoctavian]

Thanks for the feedback, @agostbiro! Added the changes to the PR (except for point 1, which will be done in a separate PR).

[popescuoctavian]

@fvictorio, @alcuadrado I believe the content in now ready. Could you please review the PR? The part that I'm most interested in being reviewed is the integration with the website (navigation bar, categorization, etc.). Thanks!

[alcuadrado]

lgtm