update new urls for V2

README.md

@@ -138,41 +138,20 @@ maintenance evacuation routing, HA affinity parsing, host-profile migration
 signatures and backups, and VirtIO filename validation. Tests use temporary
 files and mocked Proxmox output; they do not download installers or change a
 Proxmox host.
-## Deployment broker URL
+## Deployment service endpoints
 
-TA-ProxMenu exchanges deployment codes with the configured TAPM broker. The
-URL is selected in this order:
+TA-ProxMenu uses the built-in production endpoints:
 
-1. Existing `TAPM_BROKER_URL` environment variable
-2. `TAPM_BROKER_URL` in `/etc/ta-proxmenu/config.env`
-
-For a persistent per-system setting:
-
-```sh
-install -d -m 0755 /etc/ta-proxmenu
-install -m 0644 config.env.example /etc/ta-proxmenu/config.env
+```text
+Broker: https://tapm.technologyarch.com
+Git:    https://tagit.technologyarch.com
 ```
 
-The tracked example contains only:
-
-```dotenv
-TAPM_BROKER_URL=https://tapm.example.com
-GITEA_DOMAIN=git.example.com
-```
-
-Replace it with the deployed HTTPS origin, without an API path. There is no
-hard-coded operational broker URL; authorization fails with a configuration
-message when the variable is missing or invalid. `GITEA_DOMAIN` is a hostname,
-without `https://` or a path. Repository updates use the installed
-TA-ProxMenu checkout's configured Git `origin` and do not overwrite the system
-configuration file.
-
-On the first V2 launch after installation or upgrade, TA-ProxMenu detects a
-missing or incomplete `/etc/ta-proxmenu/config.env` and interactively requests
-both values. Inputs are validated and written atomically with mode `0600`
-before update checks or menu actions continue. A non-interactive launch without
-valid configuration stops with an explicit setup message instead of selecting
-a default company URL.
+No first-run prompt or `/etc/ta-proxmenu/config.env` file is required. For a
+controlled development or test environment only, `TAPM_BROKER_URL` and
+`GITEA_DOMAIN` environment variables can override the built-in values for that
+process. Repository updates continue to use the installed checkout's configured
+Git `origin`.
 
 ## Installation registry