docs: finalize visual presentation and launch readiness meta

Author: manishklach

README.md

@@ -14,14 +14,21 @@ Conversely, passing technical specs to non-technical agencies or standard AI vid
 
 ## Gallery & Visuals
 
-The engine is optimized for high-fidelity technical storytelling. Expected artifacts from the render pipeline include:
+TechDemoForge focuses on technical honesty and structural precision. These visuals demonstrate the transition from engineering specs to verifiable video assets.
 
-*   **Storyboards**: [gallery/storyboard-sample.png](gallery/storyboard-sample.png)
-*   **Media Assets**: [gallery/scene-render-sample.mp4](gallery/scene-render-sample.mp4)
-*   **Final Output**: [gallery/final-demo-release.mp4](gallery/final-demo-release.mp4)
+| 1. Source Ingestion | 2. MiniMax-M2.7 Storyboard |
+| :--- | :--- |
+| ![Ingestion](docs/assets/screenshots/01-ingestion.png) | ![Storyboard](docs/assets/screenshots/02-storyboard.png) |
+| *Ingest dense READMEs or specs.* | *MiniMax-M2.7 plans the narrative.* |
 
+| 3. Async Media Workers | 4. Final Render Output |
+| :--- | :--- |
+| ![Background Jobs](docs/assets/screenshots/03-workers.png) | ![Final Render](docs/assets/screenshots/04-render.png) |
+| *Track jobs via persistent workers.* | *FFmpeg muxes the final artifacts.* |
+
+### Interactive Walkthrough
 > [!TIP]
-> Use the **Mock Mode** during initial setup to generate watermarked placeholders for these assets without incurring API costs.
+> View the [Full Pipeline Demo GIF](docs/assets/demo/walkthrough-pipeline.gif) to see the end-to-end flow from planning to MP4 export.
 
 ## Architecture & Workflow
 
@@ -131,6 +138,14 @@ Best for development if you have Python 3.10+ and Node.js installed locally.
 - **Video Generation**: Wired and active when configured. targetting `MiniMax-Hailuo-02` via async background workers.
 - **Mock Mode**: Fully functional zero-configuration fallback for offline testing.
 
+## Demo Asset Guidelines
+
+When contributing screenshots or demo GIFs to `docs/assets/`:
+- **Resolution**: 1280x720 (720p) is preferred for a balance of clarity and file size.
+- **GIF Duration**: Keep walkthrough GIFs under 15 seconds; use high compression (e.g., via `ffmpeg` or `ezgif`).
+- **Formatting**: Use descriptive names (e.g., `01-ingestion.png`) to maintain logical ordering in the documentation.
+- **No Sensitive Data**: Ensure all API keys and personal identifiers are redacted or cleared before capture.
+
 ## Manual QA Checklist
 
 Before each push or release tag, verify the following: