docs: replace the remaining live Alfajores references with Celo Sepolia

[palango]

Five pages still told readers to use Alfajores, which is retired, and the ODIS page's endpoint table was dead for mainnet too: every cloudfunctions.net URL on it returns 404. This moves the live instructions to Celo Sepolia and removes the release runbook for the attestation service, which no longer exists; the deletion and its redirects follow the pattern #2293 used for orphaned pages. Pages that mention Alfajores as history stay as they are. Closes #2290.

What changed

Page	Change
tooling/libraries-sdks/contractkit/odis.mdx	URL and key tables are now mainnet and Celo Sepolia, staging dropped. Values come from social-connect packages/identity/src/odis/query.ts and match the published @celo/identity@6.0.0-beta.0. Adds the getServiceContext(OdisContextName.CELO_SEPOLIA) snippet for 6.0.0-beta.0+, and says 5.1.2 needs the values passed in by hand.
tooling/libraries-sdks/contractkit/setup.mdx	Prose says Celo Sepolia; the code already used the Sepolia RPC.
tooling/contracts/uniswap-contracts.mdx	Drops the v3 Alfajores column and corrects the <Info> box, which claimed v3 was on Celo Sepolia.
tooling/libraries-sdks/portal/index.mdx	eip155:44787 → eip155:11142220 in the gateway config and the four receiveTestnetAsset examples.
contribute-to-celo/release-process/attestation-service.mdx	Deleted. It redirects to /contribute-to-celo/release-process, and the two older redirects that landed on it now go there directly. The nav entry and the link on the overview page are gone.

migrating-to-viem.mdx, listed in the issue, was already clean on main.

Caveats

• I could not verify the Portal change. Portal's chain list still names only Alfajores as a Celo testnet, and its RPC gateway returns 401 without an API key, so nothing confirms that eip155:11142220 works for the gateway or for receiveTestnetAsset. If it does not, the faucet link already on the page still works.
• I found no Uniswap v3 deployment on Celo Sepolia. The Alfajores and mainnet v3 addresses have no code on Celo Sepolia (eth_getCode returns 0x), and Uniswap's v3 Celo deployment page has only CELO and Alfajores columns. The page now says v3 has no published Celo Sepolia deployment and points testers at v4. If a deployment exists somewhere, the column can come back with checked addresses.
• Both ODIS combiners answer GET /status with {"version":"3.3.3"}. I did not run an identifier lookup, which needs an account with ODIS quota.
• Left for later: the ODIS page's auth examples pass contractKit to WalletKeySigner, which is the 5.x API. The pending @celo/identity 6.0.0 release switches that to sign191, so the page needs another pass when 6.0.0 ships.

Verification

• rg -nil 'alfajores|44787' --glob '*.mdx' . returns only the 14 pages the issue lists as out of scope.
• mint broken-links: no broken links found.
• mint dev: all three attestation-service paths return 307 to /contribute-to-celo/release-process, and the five edited pages return 200.

🤖 Generated with Claude Code

[GigaHierz]

head d306f47 · Check for broken links pass (CI) · ODIS URLs and keys rechecked against social-connect source · @celo/identity 5.1.2 and 6.0.0-beta.0 inspected from npm · Uniswap v3 addresses checked with eth_getCode on both networks · no e2e (docs only)

REQUEST-CHANGES. Three findings, all small; one is a live example the sweep missed.

Findings

1. Medium · home/protocol/transactions/transaction-types.mdx:309,331,335. The viem example still imports celoAlfajores from viem/chains and uses it for both clients (chain: celoAlfajores, // Celo testnet). This is a live instruction, not history, and it is the same class as the six pages this PR fixes (#2290). A reader who copies it points at the retired network.
   Fix: import and use celoSepolia (it exists in viem/chains; I checked the current package) and change the comment to "Celo Sepolia testnet".

2. Low · tooling/libraries-sdks/portal/index.mdx (five eip155: examples). The swap to eip155:11142220 is unverified, as the PR body says. Portal's own chain list names Celo mainnet (eip155:42220) and Alfajores (eip155:44787) and does not mention Celo Sepolia. The old value was already dead, so this is not worse than before, but the page now states a chain ID Portal does not document.
   Fix: either confirm with Portal that Celo Sepolia is supported and note it here, or add one line under the first example: "Portal's chain list does not yet name Celo Sepolia; confirm support with Portal before relying on it."

3. Low · tooling/contracts/uniswap-contracts.mdx:3. The frontmatter description still reads "Uniswap v4 and v3 contract addresses on Celo Mainnet and the Celo Sepolia Testnet". After this PR v3 is mainnet only, and the description is what llms.txt and search show.
   Fix: "Uniswap v4 contract addresses on Celo Mainnet and Celo Sepolia, and v3 addresses on Celo Mainnet".

Verified good

• ODIS endpoints: both new URLs return 200 on /status; the old cloudfunctions.net mainnet URL returns 404.
• ODIS keys and URLs: they match ODIS_MAINNET_CONTEXT_PNP and ODIS_CELO_SEPOLIA_CONTEXT_PNP in social-connect packages/identity/src/odis/query.ts, character for character. The PR uses the PNP keys, which is right for this phone-number page.
• Version claims: @celo/identity 6.0.0-beta.0 ships getServiceContext, OdisContextName.CELO_SEPOLIA and the Celo Sepolia contexts. 5.1.2 has getServiceContext but no Celo Sepolia context, so "5.1.2 has no Celo Sepolia context" is correct.
• Uniswap v3: the mainnet factory, SwapRouter02 and UniversalRouter have code on Celo mainnet and 0x on Celo Sepolia, so "no published Celo Sepolia deployment" holds for those addresses.
• Deleted page: attestation-service has a redirect; the two older redirects that landed on it now go straight to /contribute-to-celo/release-process; no other inbound references remain, and the nav entry and overview link are gone. No redirect chains.
• setup.mdx: the code already used the Sepolia RPC, so the prose now matches it.
• Remaining Alfajores mentions: I read all of them on this head. Apart from finding 1, they are history, notices or migration pages.

What the PR got right

Honest scoping: the caveats section names exactly the two things it could not verify. Replacing the dead ODIS table with values from the published source is the right fix, not just a rename. Deleting a runbook for a retired service, with redirects, is better than renaming networks inside it. This is one round of three targeted edits.

Merge-order hazards

docs.json redirects and nav are touched, so any PR editing those lines near release-process may need a rebase. #2353 adds redirects near the top of the list, so expect a trivial conflict if both are open. No other open PR touches these pages.

[palango]

All three are fixed in c927d24.

1. transaction-types.mdx now imports celoSepolia and uses it for both clients. I checked it with viem 2.55.10: createPublicClient({ chain: celoSepolia, transport: http() }).getChainId() returns 11142220 against the live RPC.
2. The Portal page has a <Warning> under the initialization examples. It says Portal's chain list does not yet name Celo Sepolia and that readers should confirm support with Portal. I haven't asked Portal yet.
3. The Uniswap description now reads "Uniswap v4 contract addresses on Celo Mainnet and Celo Sepolia, and v3 addresses on Celo Mainnet".

mint broken-links passes: "success no broken links found".