update gir url

README.md

@@ -11,10 +11,9 @@ Run as `root` on a Proxmox VE host:
 bash <(curl -fsSL https://go.scity.us/install-tapm)
 ```
 
-The installed launcher loads the shared iDSSYS defaults and opens the
-interactive menu. Update availability is checked in the background and cached;
-updates are installed only when explicitly selected or requested with
-`tapm update`.
+The installed launcher loads TA-ProxMenu's bundled defaults and colors, then
+opens the interactive menu. Updates are installed only when explicitly
+selected or requested with `tapm update`.
 
 On a clustered Proxmox host, both `tapm update` and the management-menu update
 update every online cluster node over Proxmox's root SSH trust, then update the
@@ -27,12 +26,6 @@ When testing this branch, use `tapm main` to switch the installed copy back to
 the published main branch. The command refuses to switch when local changes,
 local-only commits, or diverged branch history would be at risk.
 
-The required iDSSYS Defaults repository is handled separately: it is
-automatically refreshed before launch when its last successful check is more
-than four hours old. If the remote is unavailable, the installed copy is used.
-Updates are fast-forward-only. Local file changes, local-only commits, and
-diverged histories are preserved and reported instead of being overwritten.
-
 The TA-ProxMenu Management menu can safely switch TA-ProxMenu between branches published on
 its Git origin. Branch switching is refused when the installed repository has
 local changes or when the destination branch has commits that would be
@@ -73,8 +66,7 @@ portal without changing ProxMenu.
 
 - Proxmox VE and root privileges
 - Bash, Git, curl, wget, Python 3, and standard Debian package tools
-- `/opt/idssys/defaults/default.inc`
-- `/opt/idssys/defaults/colors.inc`
+- The bundled `defaults.inc` and `colors.inc` files
 
 The Keepalived deployment additionally requires a healthy, quorate Proxmox
 cluster and passwordless root SSH between cluster nodes.
@@ -111,7 +103,7 @@ Pulse can also be deployed without installing TA-ProxMenu. Run the standalone
 bootstrap as root on a Proxmox VE host:
 
 ```bash
-bash <(curl -fsSL https://git.schroedercity.com/TAI/TA-ProxMenu/raw/branch/V2/install-pulse.sh)
+bash <(curl -fsSL https://tagit.technologyarch.com/taiadmin/TA-ProxMenu/raw/branch/V2/install-pulse.sh)
 ```
 
 The bootstrap downloads the Pulse deployment module and its LXC storage helper
@@ -170,9 +162,9 @@ 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, and controls Gitea connectivity plus restoration
-of the `voltron/iDS-Defaults.git` repository. Repository updates do not
-overwrite the system configuration file.
+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