docs(8004): rename Related Protocols to the standard Related heading

[GigaHierz]

Scope, honestly

This is one line, and it is all that is left of #2340. I wrote that issue describing a page state that was already out of date when I filed it — work on the #2331 branch had already done the substantive parts. Rather than open a PR duplicating them, this covers only the remainder.

Here is #2340's acceptance criteria checked against the current GigaHierz/erc8004-register-services-section head:

Criterion	State
No @chaoschain/sdk example remains	already done — grep -c chaoschain → 0
No web3-style tx.events.Transfer.returnValues.tokenId	already done — grep -c returnValues → 0
One registration path, service case folded in	already done — one ### Register heading
Agent ID read from Registered on a mined receipt	already done — parseEventLogs on the receipt
## Related Protocols → ## Related	this PR

The change

AGENTS.md §3 names the two closing sections: ## Resources, then ## Related. The section's content already matched the Related spec — a bullet list of internal pages, each with a dash and a half-sentence on why. Only the heading was non-standard, so this renames the heading and touches nothing else.

Why no redirect or link update

Renaming a heading changes its anchor, so I checked for inbound references:

$ grep -rn --include='*.mdx' 'related-protocols' .
(no matches)

Nothing links #related-protocols, so there is nothing to update. Anchors are not page paths, so no docs.json redirect applies.

Conflict check with #2331

#2331 is open on the same file. It does not touch this section — the ## Related Protocols block is byte-identical on main and on that branch:

$ diff <(sed -n '/## Related Protocols/,$p' main:8004.mdx) \
       <(sed -n '/## Related Protocols/,$p' 2331:8004.mdx)
(identical)

So these two merge cleanly in either order.

What this does NOT do

Four other pages carry the same class of non-standard closing heading, all ## Additional Resources, which AGENTS.md §3 also rules out:

• tooling/explorers/analytics.mdx
• build-on-celo/scaling-your-app.mdx
• build-on-celo/build-with-ai/vibe-coding.mdx
• build-on-celo/build-with-ai/mcp/index.mdx

Deliberately not bundled. Each needs a judgement call this page did not — whether the content is a link table (## Resources) or a bullet list of internal pages (## Related) — and that is a different review from a rename where the content already fits. Happy to do them as a follow-up if you want the family cleaned up.

Verification

$ npx mintlify@4.2.920 validate
success build validation passed
$ npx mintlify@4.2.920 broken-links --check-redirects
success no broken links found
$ bash scripts/check-orphans.sh
No orphan pages found.

Closes #2340.

🤖 Generated with Claude Code