[palango]

A few pages still described Celo as a chain in the middle of moving from L1 to L2: eleven pages opened with a banner saying the docs "may be outdated as updates are in progress", the Build landing page carried the 2024 transition announcement and testnet timeline, and the Remix guide warned about a compiler limit on Celo L1. This removes them, so the docs describe the current chain and keep the move itself on the History and About Celo L1 pages, as AGENTS.md section 4 asks.

The Build page loses its "Celo L2 Mainnet", "What does this mean for our ecosystem?" and "Important Dates" sections and links to Our History instead. Every date in that timeline was already on learn/history.mdx, which now also links the audit results. "1-second block finality compared to formerly 5 seconds" becomes "1-second blocks", per AGENTS.md section 7.

The banner was the only thing linking to /build#celo-l2-mainnet, so no anchor breaks. mint broken-links --check-redirects, mint validate and scripts/check-orphans.sh pass locally with mint 4.2.746.

Closes celo-org/celo-blockchain-planning#1173

[GigaHierz]

The removals check out. build/index.mdx no longer has the anchor target, nothing in the branch links to /build#celo-l2-mainnet, and every date in the dropped timeline is already on learn/history.mdx.

One banner is left: build/tools/libraries-sdks/contractkit/notes-web3-with-contractkit.mdx lines 10-16 still has the same "As of block height 31,056,500 ... may be outdated as updates are in progress" warning. It links /build/index instead of /build#celo-l2-mainnet, which is probably why the anchor check missed it. git grep "block height 31,056,500" on this branch returns only that file. Please drop it too.

Two small things, neither blocking:

• The description says ten pages carried the banner. The diff removes the banner from 11 pages (and the Remix warning), so the count is off by one.
• The Remix warning is gone, which is right for Celo Sepolia. I did not check that Solidity 0.8.20+ with the default EVM version deploys on Celo mainnet. If it has not been tried, a quick deploy would confirm it.

Otherwise this looks good to me.

[GigaHierz]

The last banner is gone (no block height 31,056,500 left on the branch), the body count is fixed, it merges cleanly, and validate and broken-links pass.

[karlb]

The changes look fine, but there seems to be more related work (only spot checked):

The PR description also has an error:

• It missed an 11th banner. build/tools/libraries-sdks/contractkit/notes-web3-with-contractkit.mdx:11 still says "documentation may be outdated as updates are in progress". It links to /build/index rather than /build#celo-l2-mainnet, so a search for the anchor didn't find it. That link
  now points at a Build page with no L2 content.

Pages still written as pre-migration:

• learn/protocol/security-council.mdx:6: the banner is gone, but the page still says "the proposed Security Council", "work in progress based on the proposal" and "Proposed Multisig Structure".
• learn/protocol/transactions/overview.mdx:7, :39: "In Celo's transition to a Layer 2… several key changes have been proposed", plus a "work in progress" note.
• operate/specification/index.mdx:13: "has decided to transition…" and "Celo L2 will retain…". The PR's new "Layer 2 Specification" link lands on this page.
• contribute/community-rpc-nodes/validator-rpc-faq.mdx:14: future tense throughout, including a registration deadline ("before the migration block") that passed in March 2025.
• contribute/community-rpc-nodes/penalties.mdx:8: "work in progress based on the proposal… during the transition to L2".
• operate/specification/l2-migration.mdx:29, :433–442: "will be deprecated", "planned for removal".

Pages that present L1 behaviour as current:

• contribute/release-process/blockchain-client.mdx: with the banner removed, the celo-blockchain release process reads as current, but that client stopped syncing at the migration. I'd delete the page and redirect to /learn/celo-l1, or rewrite it for op-reth/op-node.
• contribute/release-process/smart-contracts.mdx:229, :69: the checklist still includes attestation rounds, --blsKey registration and downtime slashing, all retired with the L1. It also expects a celo-blockchain RPC on port 8545.
• learn/manage/release-gold.mdx:9, self-custody.mdx:133, :248: these say locked CELO secures Proof-of-Stake consensus, and recommend a "Local Celo Blockchain node".