docs: build out the CAST PRO-1 section

Add the CAST PRO-1 pages modeled on the CAST-1 section: FAQ, getting
started (labeled ports, USB-C power, Ethernet, hotspot and Improv setup,
Audio Output), sensor definitions, ESPHome Device Builder, Analog In as a
Music Assistant Sendspin Source, TTS and announcements, WizMote control,
boot mode, reflash, boot button status check and factory reset, and
teardown and reassembly.

Expand the LED strip page with the Effect A and B slots, the pattern
list, the photosensitivity warning, the LED Strip Test step, and a
partition example for splitting the strip into segments.

Add the hero image, labeled ports photo, hotspot onboarding clip, audio
hookup clips, and teardown clips. Add a CAST PRO-1 naming rule to the
style guide and AGENTS.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: WestwardWinds

AGENTS.md

@@ -28,9 +28,10 @@ Read the full style guide, but these are the ones worth checking twice:
 
 - Product IDs are uppercase with a hyphen: **AIR-1**, **MTR-1**, never
   `Air-1` or `air1`.
-- **R PRO-1** is the exception: a space after the R, not a hyphen, in
-  all display text. Keep `rpro1`, `r-pro-1`, and `R_PRO-1` only in file
-  names, URLs, hostnames, and literal device names.
+- **R PRO-1** and **CAST PRO-1** are the exceptions: a space before
+  PRO, not a hyphen, in all display text. Never `CAST-1 PRO`. Keep
+  `rpro1`, `r-pro-1`, `R_PRO-1`, `castpro1`, and `cast-pro-1` only in
+  file names, URLs, hostnames, entity IDs, and literal device names.
 - **US English** spelling: color, center, meter, behavior.
 - Flag must-know info with admonitions (`note` for prerequisites,
   `tip`, `warning`, `success` for a "Next step" box with a primary

STYLE_GUIDE.md

@@ -105,7 +105,7 @@ Product IDs are always uppercase with a hyphen: **AIR-1**, **MTR-1**,
 Never `Air-1`, `air1`, or `AIR1` in body copy. mkdocs.yml is the source
 of truth for the canonical form.
 
-**R PRO-1** is the one exception: its name has a space after the R, not
+**R PRO-1** is an exception: its name has a space after the R, not
 a hyphen. Write **R PRO-1** in titles, headings, nav labels, and body
 copy, never `R-PRO-1`. The hyphenated and underscored forms survive
 only where a space isn't allowed or where you quote the device
@@ -117,6 +117,16 @@ literally, and those must not be changed:
 - The device name Home Assistant and Homey show: **Apollo R_PRO-1**
 - The setup hotspot: **Apollo R PRO 1 Hotspot**
 
+**CAST PRO-1** follows the same pattern: a space after CAST, then
+**PRO-1**. Never `CAST-1 PRO`, `CAST-PRO-1`, or `Cast Pro`. It's a
+different product from the **CAST-1**, so don't shorten it to CAST-1.
+The same literal forms keep their own spelling:
+
+- File and folder names and URLs: `castpro1/`, `cast-pro-1-intro-image.webp`
+- Entity IDs: `media_player.apollo_cast_pro_1_xxxxxx_player`
+- The device name Home Assistant and Music Assistant show: **Apollo CAST_PRO-1**
+- The setup hotspot: **Apollo CAST_PRO-1 Hotspot**
+
 ### First mention per page
 
 On the first mention of a product in body copy, use the full brand name: