docs: add smoke-test step to release-tasks skill

Adds step 10: extract, install, start, and verify the built offline
ZIP on the current platform before releasing. Catches issues like
missing wheels or dependency conflicts early.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: raffelino

.claude/skills/release-tasks/SKILL.md

@@ -68,4 +68,40 @@ bash scripts/build-online-mac-and-linux.sh
 Verify:
 - All ZIPs are created under `dist/`
 - Spot-check at least one ZIP: extract it, confirm it contains `frontend_dist/`, `backend/`, install/start scripts, and wheels
-- Ensure the version in the built artifacts matches the release version
+- Ensure the version in the built artifacts matches the release version
+
+## 10. Smoke-Test the Distribution ZIP
+
+Before releasing, do a real smoke-test of the built archive for the current platform:
+
+```bash
+# 1. Extract the ZIP into a temporary directory
+SMOKE_DIR=$(mktemp -d)
+unzip dist/roboscope-offline-*.zip -d "$SMOKE_DIR"
+cd "$SMOKE_DIR/roboscope-offline-"*
+
+# 2. Run the install script (macOS/Linux)
+bash install.sh
+# On Windows: install-windows.bat
+
+# 3. Start the server
+bash start.sh &
+# On Windows: start-windows.bat
+
+# 4. Wait for startup and verify
+sleep 5
+curl -sf http://localhost:8145/api/v1/health && echo "Health OK"
+curl -sf http://localhost:8145/ | head -5 && echo "Frontend OK"
+
+# 5. Clean up
+kill %1 2>/dev/null
+rm -rf "$SMOKE_DIR"
+```
+
+Verify:
+- Install script completes without dependency resolution errors
+- Server starts and responds on the configured port
+- Frontend is served correctly
+- Health endpoint returns OK
+
+If the smoke-test fails (e.g., missing wheels, dependency conflicts), fix the build script and rebuild before proceeding.