Revert "Update next steps in explainer"

pages/stack/interop.mdx

@@ -13,10 +13,7 @@ Documentation covering Cross Chain Message, Explainer, Message Passing, Op Super
 <Cards>
   <Card title="Interoperability explainer" href="/stack/interop/explainer" />
 
-  <Card title="Architecture" href="/stack/interop/architecture" />  
-
-  <Card title="Anatomy of a cross-chain message" href="/stack/interop/cross-chain-message" />
-
+  <Card title="Architecture" href="/stack/interop/explainer#interoperability-architecture" />  
 
   <Card title="Interop message passing overview" href="/stack/interop/message-passing" />
 
@@ -31,4 +28,6 @@ Documentation covering Cross Chain Message, Explainer, Message Passing, Op Super
   <Card title="Interoperability predeploys" href="/stack/interop/predeploy" />
 
   <Card title="Cross-chain security" href="/stack/interop/security" />
+
+    <Card title="Interop assets" href="/stack/interop/tools" />
 </Cards>

pages/stack/interop/explainer.mdx

@@ -104,7 +104,7 @@ The call to `CrossL2Inbox`, also known as the *executing message*, needs to [ide
 
 `CrossL2Inbox` can either [validate the message exists](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L171-L185), or [call a contract if the message exists](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L171-L185).
 
-[For more information, see the  cross-chain messages anatomy page](./cross-chain-message).
+[For more information, see the  cross-chain messages anatomy page](#how-messages-get-from-one-chain-to-the-other).
 
 ## Block safety levels
 
@@ -211,7 +211,7 @@ flowchart LR
     A <--> C <--> E <--> B <--> D <--> A
 ```
 
-Each blockchain in the Superchain interop cluster shares the same security model to mitigate the weakest-link scenario. As outlined in the [Standard Rollup Charter](superchain/blockspace-charter), these chains share the same L1 `ProxyAdmin` Owner. Any changes to the Superchain interop cluster must follow the standard Protocol Upgrade vote procedure—the established governance process for Superchain modifications.
+Each blockchain in the Superchain interop cluster shares the same security model to mitigate the weakest-link scenario. As outlined in the [Standard Rollup Charter](/superchain/blockspace-charter), these chains share the same L1 `ProxyAdmin` Owner. Any changes to the Superchain interop cluster must follow the standard Protocol Upgrade vote procedure—the established governance process for Superchain modifications.
 
 {/* 
 ## Interop assets
@@ -226,7 +226,6 @@ This means ETH and ERC-20s can seamlessly and securely move across L2s, and inte
 
 ## Next steps
 
-*   Watch this video that gives an [overview of OP Stack interoperability](https://www.youtube.com/watch?v=FKc5RgjtGes).
-*   Learn more about the [predeploys that have been added to the OP Stack to enable interoperability](stack/interop/predeploy).
-*   Use [Supersim](stack/interop/tools/supersim), a local dev environment that simulates interop for testing applications against a local version of the Superchain.
+*   Want to learn more? Read our guide on the anatomy of a [cross-chain message](#how-messages-get-from-one-chain-to-the-other) or check out this [interop design video walk-thru](https://www.youtube.com/watch?v=FKc5RgjtGes).
+*   Ready to get started? Use [Supersim](/builders/app-developers/tools/supersim.mdx), a local dev environment that simulates interop for testing applications against a local version of the Superchain.
 *   For more info about how OP Stack interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html).

pages/stack/interop/message-passing.mdx

@@ -61,6 +61,6 @@ For a practical example, see our [cross-chain ping pong tutorial](https://supers
 
 ## Next steps
 
-*   Read about the [anatomy of a cross-chain message](/stack/interop/cross-chain-message)
+*   Read about the [anatomy of a cross-chain message](/stack/interop/explainer#how-messages-get-from-one-chain-to-the-other)
 *   Try [Supersim](supersim) for testing cross-chain messages locally
 *   Learn about [manually relaying messages](https://supersim.pages.dev/guides/interop/viem?#viem-to-send-and-relay-interop-messages)

pages/stack/interop/op-supervisor.mdx

@@ -68,5 +68,5 @@ Benefits:
 
 ## Next steps
 
-*   Want to learn more? Read our guide on the anatomy of a [cross-chain message](/stack/interop/cross-chain-message) or check out this [interop design video walk-thru](https://www.youtube.com/watch?v=FKc5RgjtGes).
+*   Want to learn more? Read our guide on the anatomy of a [cross-chain message](/stack/interop/explainer#how-messages-get-from-one-chain-to-the-other) or check out this [interop design video walk-thru](https://www.youtube.com/watch?v=FKc5RgjtGes).
 *   For more info about how OP Stack interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html).

pages/stack/interop/tools.mdx

@@ -0,0 +1,18 @@
+---
+title: Assets
+description: Documentation covering Interop devnet, Supersim in the Interop section of the OP Stack ecosystem.
+lang: en-US
+---
+
+import { Card, Cards } from 'nextra/components'
+
+# Interop
+
+Documentation covering Interop devnet, Supersim in the Interop section of the OP Stack ecosystem.
+
+<Cards>
+  <Card title="Supersim" href="/stack/interop/tools/supersim" />
+
+  <Card title="Interop devnet(Beta)" href="/stack/interop/tools/devnet" />
+
+</Cards>

pages/stack/interop/tools/_meta.json

@@ -1,4 +1,4 @@
 {
     "supersim": "Supersim Multichain Development Environment",
-    "devnet": "Interop devnet - coming soon" 
+    "devnet": "Interop devnet(Beta)" 
 }

pages/stack/interop/tools/devnet.mdx

@@ -1,12 +1,12 @@
 ---
-title: Interop Devnet - Coming Soon
+title: Interop devnet(Beta)
 lang: en-US
 description: Details on the public interoperability devnets.
 ---
 
 import { Callout, Tabs, Steps } from 'nextra/components'
 
-# Interop Devnet - Coming Soon
+# Interop devnet(Beta)
 
 <Callout>
   Interop devnet is currently in active development and may experience periods of instability, including potential outages, as the networks is regularly updated and improved. Developers should expect some level of unreliability when interacting with the devnet. The devnet is intended for testing and development purposes only, and should not be relied upon for mission-critical applications.
@@ -63,6 +63,6 @@ NOTE: The current Interop devnet has been deprecated. This page will be updated
 ## Next steps
 
 *   Want to start with local development? Use [Supersim](/stack/interop/supersim), a local dev environment that simulates interop for testing applications against a local version of the Superchain.
-*   Read about [interop message passing](/stack/interop/cross-chain-message) to see how you can implement it yourself on this devnet.
+*   Read about [interop message passing](/stack/interop/explainer#how-messages-get-from-one-chain-to-the-other) to see how you can implement it yourself on this devnet.
 
 */}