fix: compatibilidad GTX 1060 (sm_61) y modo host

[jhoavera]

Resumen:\n- Añade DEBIAN_FRONTEND=noninteractive al Dockerfile generado.\n- Manejo defensivo de RuntimeError en cierre de WebSocket (demo/web/app.py).\n- El generador systemd respeta VIBE_API_MODE=host para evitar arrancar la API en Docker.\n- Documentación: LEEME y README (modo host).\n\nEste PR aplica un conjunto limpio de cambios enfocados en compatibilidad con GPUs GTX 1060 (sm_61) y en mejorar la experiencia de ejecución en 'host venv'.

[Copilot]

Pull request overview

This pull request adds GTX 1060 (sm_61) GPU compatibility and improves the host venv execution mode for VibeVoice. The changes include defensive WebSocket error handling, systemd service configuration for host mode, enhanced documentation, and a complete modular installation system for Ubuntu 22.04/24.04.

Key Changes

• Enhanced error messages and WebSocket connection handling in the web application
• Added DEBIAN_FRONTEND=noninteractive to Dockerfile for non-interactive builds
• Systemd service respects VIBE_API_MODE=host to avoid starting API in Docker
• Comprehensive Spanish and English documentation for host mode setup

Reviewed changes

Copilot reviewed 20 out of 20 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
demo/web/app.py	Improved MODEL_PATH error message and defensive WebSocket closing
Servicio/Instalacion-Base-VibeVoice/modulos/06-systemd-service.sh	Systemd service with host mode support and new API service function
Servicio/Instalacion-Base-VibeVoice/modulos/05-docker-compose.sh	Docker Compose configuration with Dockerfile generation including DEBIAN_FRONTEND
Servicio/Instalacion-Base-VibeVoice/LEEME.md	Spanish documentation with host mode and GPU configuration guidance
README.md	Added GTX 1060 compatibility note with host mode recommendation
.github/workflows/validate-scripts.yml	CI workflow for shell script validation

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The broad exception handler with pragma: no cover could mask unexpected errors. While the RuntimeError handler for race conditions is appropriate, catching all exceptions with Exception might hide bugs. Consider logging more details about unexpected exceptions (e.g., exception type, stack trace) to help diagnose issues that aren't race conditions, even though they're defensive.

Suggested change

	print(f"Error while closing websocket: {exc}")
	print(f"Error while closing websocket: {type(exc).__name__}: {exc}")
	traceback.print_exc()

[Copilot]

The Dockerfile has a leading space on line 406 before the RUN command. This will cause the Docker build to fail with a syntax error. The line should start with 'RUN' without any leading whitespace.

Suggested change

	RUN apt-get update && apt-get install -y --no-install-recommends build-essential gcc git libpq-dev && rm -rf /var/lib/apt/lists/*
	RUN apt-get update && apt-get install -y --no-install-recommends build-essential gcc git libpq-dev && rm -rf /var/lib/apt/lists/*

[Copilot]

The ExecStart command uses shell conditionals inline which could be fragile. The check 'if [ "${VIBE_API_MODE:-docker}" = "host" ]' works but skipping docker-compose up entirely when in host mode means the data services (PostgreSQL, Redis, Kafka) won't start. Consider whether this is the intended behavior, or if the services should still start even in host mode while only the API runs on the host.

Suggested change

	ExecStart=/bin/sh -c 'if [ "${VIBE_API_MODE:-docker}" = "host" ]; then echo "VIBE_API_MODE=host: skipping docker-compose up"; exit 0; fi; /usr/bin/docker-compose -f ${VIBE_DIR_CONFIG}/docker-compose.yml up -d --build'
	ExecStart=/bin/sh -c 'if [ "${VIBE_API_MODE:-docker}" = "host" ]; then /usr/bin/docker-compose -f ${VIBE_DIR_CONFIG}/docker-compose.yml up -d postgres redis kafka; else /usr/bin/docker-compose -f ${VIBE_DIR_CONFIG}/docker-compose.yml up -d --build; fi'

[Copilot]

The function generar_servicio_api_host is defined but never called. This function creates a systemd service for running the API in host venv mode, which appears to be a key feature of this PR. Without calling this function, the host mode service won't be created, and users won't be able to use the documented host mode functionality.

[Copilot]

The error message improvement is helpful, but it references a path that may not exist for all users. The message assumes the config file is at /opt/vibevoice/config/.env, but this path is only created during installation. For users running the application before installation completes, this could be confusing. Consider making the error message more generic or checking if the path exists before suggesting it.

Suggested change

	raise RuntimeError("MODEL_PATH not set in environment. Set MODEL_PATH in /opt/vibevoice/config/.env or export MODEL_PATH before starting the service.")
	raise RuntimeError("MODEL_PATH not set in environment. Please set the MODEL_PATH environment variable before starting the service (e.g., by exporting it or adding it to your environment configuration).")