docs: backport v5.2.0 developer and node docs to v5-next

[AztecBot]

Backport of the merged #25266 (docs: release v5.2.0 developer and node docs, merged into next as 2e32f82a9db) onto the v5-next line.

Summary

Cuts the v5.2.0 developer and network/operator documentation snapshots, points both the mainnet and testnet selectors at that shared snapshot, and removes the superseded snapshot. All generated references (Aztec.nr, TypeScript, Aztec.js, aztec / aztec-wallet / aztec-up CLI, operator aztec start CLI, Node JSON-RPC) regenerated at the v5.2.0 tag.

The release artifacts are byte-identical to what merged in #25266: the version-v5.2.0 developer and network snapshots, both sidebars, and the generated aztec-nr-api / typescript-api static directories were taken verbatim from the merged next tree (git diff origin/next over those paths is empty). That includes the post-review improvements #25266 picked up while resolving conflicts with next:

• the Aztec.js reference regenerated with the new generator from #25248 (proper github-slugger anchors, code blocks for multi-line types) against the tag's aztec.js source
• the teardownGasLimits is-carved-out-of-gasLimits clarification from #25220, verified true at the tag (yarn-project/stdlib/src/gas/gas_settings.ts)

Also brought across so the two lines behave the same:

• docs/scripts/aztecjs_reference_generation/ (the docs: regenerate the aztec.js API reference #25248 generator plus update_docs.sh --check from #25249), and the check_generated_refs CI hook grafted into this line's docs/bootstrap.sh (hunk-only — the file legitimately diverges from next in its toolchain paths, so it was not overwritten). --check passes on this branch: the committed source reference matches what the generator produces from v5-next's aztec.js source, which is identical to the tag's.
• the source-tree how_to_pay_fees.md gasLimits clarification and the source Aztec.js reference page (same content as the snapshot, since this line's aztec.js is the tag's).

Deliberately not brought across: next's post-tag fast-inbox / AZIP-22 doc changes (MessageSent signature, message-availability wording, AZTEC_INBOX_LAG removal) — that work is not in v5.2.0 or on this line.

What differs from #25266 (each branch's starting tree)

	next (#25266, merged)	v5-next (this PR)
snapshot superseded	version-v5.1.0	version-v5.0.1
version config before	{"mainnet":"v5.1.0","testnet":"v5.1.0"}	{"mainnet":"v5.0.1","testnet":"v5.0.1"}
## TBD migration entries	left untouched (real on that line)	two removed, one corrected (below)
operator L1 address refresh (d00f0582d96)	already present	backported here
networks.md	already current	taken from next
aztec.js JSDoc typo fixes (on-chain, meatadata)	fixed upstream on next	carried here (not on this line)

The v5.1.0 docs release (#25085) merged into next only, so this line never had a v5.1.0 snapshot; "deprecate v5.1.0" lands here as the v5.2.0 cut superseding and removing version-v5.0.1.

Migration notes corrected on this line only

Both bogus entries arrived via c85280dbbf3 "docs: backport next docs baseline to v5-next", which imported next's (6.0.0-line) migration notes wholesale. Neither describes code that exists at v5.2.0:

• Protocol contracts removed from @aztec/noir-contracts.js and at(wallet) to withWallet(wallet) — both from #24998, which is not an ancestor of v5.2.0; following either note on v5.2.0 throws. Removed.
• Standard contracts re-pinned at new addresses claimed all standard contracts moved, but standard_addresses.nr is byte-identical between v5.1.0 and v5.2.0. Restored to the accurate v5.1.0 wording (HandshakeRegistry only) under ## 5.1.0.

Everything else matches #25266: the pub note-visibility entry under ## 5.2.0, plus the four new entries (zero-peer proposing gate, -32600 to -32603, GET /status JSON body, deserializeArrayFromVector removal).

Everything else

Identical in substance to #25266 — see that PR for the full breakdown: the three non-pub #[note] doc snippets, all eight new operator env vars via the regenerated CLI reference, the new changelog/v5.2.md, the own-validator slashing signal, the peerless-node behaviour, the governance-payload auto-stop, the eth_getLogs note, and the re-derived networks.md (Version row stays 5.1.0 for both columns per the release instruction). The operator pages were reviewed on #25266's deploy preview.

The open SponsoredFPC question also carries over unchanged: v5.2.0 tooling derives 0x2ece607a...e7315b, which is not deployed on testnet; the docs keep the deployed and funded 0x130925fb...923296.

Validation

MAINNET_TAG=5.2.0 TESTNET_TAG=5.2.0 RELEASE_TYPE=mainnet COMMIT_TAG=v5.2.0 yarn build, run on this branch after merging origin/v5-next (which had moved two commits, neither touching docs or aztec.js):

• CSpell: 682 files, 0 issues
• Redirect targets: 185 checked, all valid
• API reference links: 112 checked, 0 broken, 0 version mismatches
• Docusaurus production build: successful
• ./scripts/aztecjs_reference_generation/update_docs.sh --check: ✓ Reference matches aztec.js
• git diff origin/next over both versioned snapshot trees and both generated API static directories: empty

Remaining broken-anchor warnings are the same six pre-existing ones as on next; onBrokenAnchors is warn, so the build passes.

Not run: the functional validation pass (walking guides and tutorials against a live local network) — no Docker daemon in this container; same caveat as #25266.

---

Created by claudebox · group: slackbot · requested by Alejo Amiras · Slack thread