docs: re-add remaining mocha-4 endpoints as providers migrate to mocha-5

Tracking follow-up to #2565, which trimmed the Mocha testnet page down to endpoints verified to serve `mocha-5`. Everything removed there needs re-checking and re-adding once its provider migrates. `mocha-4` shuts down September 1, 2026, so this should close before then.

## Status as of 2026-08-21

Already re-added on the #2565 branch (verified `mocha-5` by reading each endpoint's chain ID directly):

- `rpc-1` / `rpc-2.testnet.celestia.nodes.guru`
- `celestia-testnet-rpc.itrocket.net:443`
- `api-1` / `api-2.testnet.celestia.nodes.guru`
- `celestia-testnet-api.itrocket.net`
- `grpc-1` / `grpc-2.testnet.celestia.nodes.guru:10790`
- `celestia-testnet-grpc.itrocket.net:443`

Still outstanding:

| Endpoint / item | Section | Status 2026-08-21 |
| --- | --- | --- |
| `public-endpoint.celestia-mocha.quiknode.pro` | Public RPC endpoint | `mocha-4` at height 14067670. Listed with an inline warning; drop the warning when it migrates |
| `mocha.api.cumulo.me` | Community API | `mocha-4` |
| `mocha.grpc.cumulo.me:443` | Community gRPC | `mocha-4` |
| `celestia-testnet-consensus.itrocket.net` | Community consensus, JSON-RPC (`:26658`) | No response on 443, 26657, or 26658 |
| `celestiam.grpc.lava.build:443`, `celestiam.jsonrpc.lava.build`, `celestiam.tendermintrpc.lava.build` | gRPC, JSON-RPC, Tendermint RPC | Unverifiable: JSON-RPC returns 403, gRPC reflection returns `PermissionDenied`, Tendermint RPC `/status` unreachable |
| `full.consensus.{mochaChainId}.celestia-mocha.com` (+ `:9090`) | Community consensus, gRPC | No DNS for the `mocha-5` host. The `mocha-4` host still answers and reports `mocha-4` |
| `da-bridge-{mochaChainId}*.celestia-mocha.com`, `bridge-{mochaChainId}*.da.celestia-mocha.com` | Community bridge node endpoints | No DNS. Section currently says the `mocha-5` DA network launches the week of August 24, 2026 — replace with real endpoints once it is live |
| ITRocket node setup / state sync table | Node setup and tools | Removed in #2565. ITRocket's consensus RPC is on `mocha-5`, but their state sync artifacts were not re-verified |
| Celenium indexer | Explorers callout | `api-mocha.celenium.io/v1/head` reports `chain_id: mocha-4` at height 14067699. Drop the callout when it switches |

## Also from the #2565 description

- The QuickNode public endpoint appears in examples on 9 other pages (light node quickstart and advanced, CLI reference, keys and wallets, trusted hash recovery, post/retrieve blob, IBC relayer, and the Mocha page). Those examples return `mocha-4` data until QuickNode migrates.
- `app/operate/maintenance/snapshots/page.mdx` still lists ITRocket `mocha-4` testnet snapshots.
- `app/operate/data-availability/ibc-relayer/page.mdx` uses `grpc.celestia-mocha.com`, which has no DNS, and IBC state did not carry over to `mocha-5`.

## How to re-verify

```sh
# consensus / Tendermint RPC
curl -s https:///status | jq -r '.result.node_info.network // .node_info.network'

# REST API
curl -s https:///cosmos/base/tendermint/v1beta1/blocks/latest | jq -r .block.header.chain_id

# gRPC
grpcurl -insecure : cosmos.base.tendermint.v1beta1.Service/GetLatestBlock | jq -r .block.header.chainId
```

Note that provider migrations are landing fast — nodes.guru and ITRocket moved to `mocha-5` within a day of #2565 being opened, so this list goes stale quickly. Worth a re-check before the September 1 shutdown regardless.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Start with the Mocha testnet page and the related paths named in the issue, including app/operate/maintenance/snapshots/page.mdx and app/operate/data-availability/ibc-relayer/page.mdx. Re-run the listed curl and grpcurl checks for each outstanding provider, then update endpoint listings, warnings, examples, and callouts only when they verify mocha-5; completion means the remaining references are re-added or removed before the September 1 shutdown.

Written by the indexing model from the issue text.