docs: add Arcade walkthrough for staging patches

src/content/docs/code-push/guides/staging-patches.mdx

@@ -9,6 +9,12 @@ import { CodeTabs, LinkCard } from 'starlight-theme-nova/components';
 import { Image } from 'astro:assets';
 import goLive from '~/assets/staging_patches_change_track_dropdown.png';
 import switchTrack from '~/assets/staging_patches_patch_context_menu.png';
+import ArcadeEmbed from '~/components/ArcadeEmbed.astro';
+
+<ArcadeEmbed
+  src="https://app.arcade.software/share/n22dgnzUR0qwvjNciQ2i"
+  title="Pushing a patch to staging track"
+/>
 
 This guide will walk you through how to validate a patch in Shorebird's staging
 environment before promoting the patch to production.

src/content/docs/code-push/tracks.mdx

@@ -8,6 +8,7 @@ sidebar:
 ---
 
 import { CodeTabs, LinkCard } from 'starlight-theme-nova/components';
+import ArcadeEmbed from '~/components/ArcadeEmbed.astro';
 
 **Tracks** are named deployment channels that control which devices receive a
 patch. Every Shorebird app has a built-in `stable` track, which is the default
@@ -51,6 +52,11 @@ for your team.
 
 ## Publishing a patch to a track
 
+<ArcadeEmbed
+  src="https://app.arcade.software/share/n22dgnzUR0qwvjNciQ2i"
+  title="Pushing a patch to staging track"
+/>
+
 Pass the `--track` flag to any `shorebird patch` command. If you omit the flag,
 the patch is published to `stable` by default.