docs(upgrades): emulate the chain.base.org upgrades page on the Upgrades landing page

docs/base-chain/specs/upgrades/overview.mdx

@@ -1,18 +1,16 @@
 ---
 title: "Upgrades"
-description: "Base evolves through named hardforks. Each hardfork introduces protocol changes, new features, or parameter updates that take effect at a specific activation block. This tab tracks what changed, when, and how to migrate."
+description: "Track Base network upgrades and their activation status across Base Sepolia and Mainnet."
+mode: "wide"
 ---
 
-## Base Upgrades
+import { UpgradesOverview } from "/snippets/UpgradesOverview.jsx";
 
-| Upgrade | Status | Activation |
-|----------|--------|------------|
-| [Denim](/base-chain/specs/upgrades/denim/200ms-blocks) | Planning | TBD |
-| [Cobalt](/base-chain/specs/upgrades/cobalt/overview) | Upcoming | Sep 2026 |
-| [Beryl](/base-chain/specs/upgrades/beryl/overview) | Live | Jun 25, 2026 |
-| [Azul](/base-chain/specs/upgrades/azul/overview) | Live | May 28, 2026 |
+Base evolves through named network upgrades. Each upgrade introduces protocol changes, new features, or parameter updates that take effect at a specific activation time. This tab tracks what changed, when, and how to migrate.
 
-## Upstream (OP Stack) Hardforks
+<UpgradesOverview />
+
+## Upstream OP Stack Hardforks
 
 Base inherits upstream OP Stack hardforks. Each entry documents the changes Base adopted.
 
@@ -29,4 +27,4 @@ Base inherits upstream OP Stack hardforks. Each entry documents the changes Base
 
 ## Other Changes
 
-The [configuration changelog](/base-chain/network-information/configuration-changelog) tracks network parameter changes that don't belong to a specific hardfork.
+The [configuration changelog](/base-chain/network-information/configuration-changelog) tracks network parameter changes that don't belong to a specific upgrade.