vibebridge-main-installlisted

# VibeBridge Main Install Use this skill when the task is to install, deploy, or reconfigure the VibeBridge Main server. ## Ask first Before editing `configs/main.toml`, rebuilding the frontend, or starting a long-running process, ask the user for the required deployment values instead of guessing: - whether the install target is the current machine or a machine reached through SSH - if the target is remote, the SSH user, host, port, and whether the SSH session is already open - repo path on the target machine - whether this must be a fresh isolated environment, and the desired venv path - whether this is a new Main instance or a change to an existing one - bind `host` and `port` - whether the browser will access Main directly or through a reverse proxy - if exposed publicly, the public URL or domain and which port/gateway is already open - database path for Main - whether to reuse the committed `dist/` bundle or rebuild the frontend - preferred run style: `nohup`, `systemd`, `launchd`, or manual - whether a fixed `jwt_secret` is required or auto-generated per installation is acceptable - whether compatibility options such as `main.node_addresses` or `main.node_register_tokens` are intentionally needed If any required values are missing, stop and ask. Do not silently invent public URLs, firewall assumptions, database locations, or process managers. ## Defaults and preferences - Prefer a fresh role-specific venv such as `.venv-vibebridge-main`. - For production-like run