fix: use HTTPS for Chrome APT repo and align README browser wording

Co-authored-by: netzulo <11871932+netzulo@users.noreply.github.com>

Author: Copilot

README.md

@@ -152,7 +152,7 @@ Optional build flags:
 - `COPILOT_CLI_INSTALL_METHOD` = `auto` | `script` | `npm`
 - `COPILOT_CLI_VERSION` = specific version (optional)
 - `COPILOT_CLI_PREFIX` = install prefix (default `/usr/local`)
-- `BROWSERS_ENABLED=true` to install Chromium for MCP browser automation
+- `BROWSERS_ENABLED=true` to install Google Chrome (`google-chrome-stable`) for MCP browser automation
 
 ### MCP seed template
 

src/scripts/install_browsers.sh

@@ -17,7 +17,7 @@ apt-get install -y --no-install-recommends wget gnupg ca-certificates
 
 install -m 0755 -d /etc/apt/keyrings
 wget -qO- https://dl.google.com/linux/linux_signing_key.pub | gpg --dearmor -o /etc/apt/keyrings/google-chrome.gpg
-echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/google-chrome.gpg] http://dl.google.com/linux/chrome/deb/ stable main" > /etc/apt/sources.list.d/google-chrome.list
+echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/google-chrome.gpg] https://dl.google.com/linux/chrome/deb/ stable main" > /etc/apt/sources.list.d/google-chrome.list
 
 apt-get update
 apt-get install -y --no-install-recommends google-chrome-stable