feat: remove vision and add demo

pages/omni-account/_meta.json

@@ -1,6 +1,10 @@
 {
   "index": "Overview",
   "getting-started": "Getting Started",
+  "demo": {
+    "title": "Omni Account Demo",
+    "href": "https://wallet.rhinestone.wtf"
+  },
   "-": {
     "type": "separator",
     "title": "Conceptual"

pages/omni-account/index.mdx

@@ -58,11 +58,3 @@ Play with the [demo](https://wallet.rhinestone.wtf/) to experience instant cross
 - **M-to-1 chains to destination chain and M-to-n input tokens to output tokens.** Use an arbitrary number of origin chains and tokens to fund a single intent on a single destination chain. 
 - **Supports same-chain intents, a faster and cheaper alternative to ERC-4337.** Use Omni Account's underlying intent system to perform same-chain intents with solvers sponsoring gas and performing swaps. 
 - **Lazy deployment to enable cross-chain intents even if the user has no account on the target chain.** Omni Account is “everything everywhere all at once” for the user. In the background, Rhinestone’s infrastructure abstracts away the complexity of executing transactions on new chains whilst ensuring assets moved to the new chain are instantly spendable on any other chain.
-
-## Vision for Omni Account
-
-**The vision for Omni Account goes beyond solving Ethereum’s fragmented liquidity.** Omni Account allows users to express any intent to a specialized execution layer without the strict requirement of atomized settlement. Our vision is to enable application-specific Orchestrators to plug into Omni Account and process intents against a single resource-locked balance per user. 
-
-From debit card integrations to offchain order books, Omni Account’s architecture is designed to make resource locks fully open and composable to any developer. One single balance with infinite possibilities—everything **everywhere, all at once.** 
-
-The underlying substrate between these application-specific Orchestrators, of which Chain Abstraction is one, is a single source of truth for intents in flight and the sequencing. If you’re interested in learning more and becoming a design partner for the Orchestration Layer, [please reach out](mailto:[email protected]).