vibebridge-node-installlisted

# VibeBridge Node Install Use this skill when the task is to install, deploy, or reconfigure a VibeBridge Node. ## Ask first Before editing `configs/node.toml` 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 a fresh isolated environment is required, and the desired venv path - connection mode: - `main_server_url` for direct `Node -> Main` WebSocket - `main_register_url` for HTTP registration followed by Main callback - the actual Main URL for the chosen mode - `register_token` - node listen `host` and `port` - whether Main can reach the callback address if HTTP registration mode is chosen - optional node identity overrides: `id`, `name`, `labels`, `capabilities` - preferred run style: `nohup`, `systemd`, `launchd`, or manual - whether Codex must work on this node; if yes, confirm the `codex` CLI path or install method If any of the required values are missing, stop and ask. Do not silently invent network addresses, tokens, or service managers. ## Defaults and preferences - Prefer a fresh role-specific venv such as `.venv-vibebridge-node`. - For long-running deployment, use `python -m uvicorn app:app ...`. - Do not use `python app.py` for production-like runs because the repo entrypoint e