feat(ecc2): finalize rc1 release surface

docs/releases/2.0.0-rc.1/demo-prompts.md

@@ -0,0 +1,42 @@
+# Hermes x ECC Demo Prompts
+
+## Prompt 1: ECC Builds ECC
+
+Use the current ECC repo and the public release pack at `docs/releases/2.0.0-rc.1/`.
+
+Do 4 things in order:
+
+1. Inspect git status and the current repo diff, then give me a concise ECC v2.0.0-rc.1 PR or release summary that proves ECC is being used to build ECC itself.
+2. Finalize one strong X thread.
+3. Finalize one strong LinkedIn post.
+4. Tell me the exact 3 recordings I should do next plus what Hermes can generate automatically after I record.
+
+Keep it decisive and practical.
+
+## Prompt 2: Turn Recording Into Assets
+
+Assume I just recorded:
+
+- one face-camera hook
+- one screen capture of Hermes using ECC to ship ECC v2.0.0-rc.1
+- one setup walkthrough of the Hermes x ECC workspace
+
+Give me:
+
+1. a short-form edit plan for X, LinkedIn, TikTok, and YouTube Shorts
+2. a voiceover script if I want to re-record clean audio
+3. the exact repo-relative filenames and folders I should use for raw footage
+4. the assets Hermes can generate automatically after I drop the files in place
+
+Keep it operational.
+
+## Prompt 3: Public Launch Push
+
+Using the ECC v2.0.0-rc.1 release pack, give me:
+
+1. one release tweet
+2. one follow-up tweet
+3. one LinkedIn comment I can paste under the post
+4. one short Telegram handoff I can send to Hermes later to keep distributing this launch across channels
+
+Make it sound like an operator shipping real work, not a launch thread cliche.