refactor: rename code-server-linuxserver to code-server-lsio and set naming rules for compose names

CLAUDE.md

@@ -9,6 +9,20 @@ gitignored `.env`.
 Every service uses `compose.yml` — the current Compose spec name, and the
 shorter one. Not `docker-compose.yml`.
 
+## Names
+
+A service directory is named after the software it runs. When two services
+package the same software, the one that is not upstream's own image takes a
+suffix naming its source — `code-server-lsio` for LinuxServer's code-server —
+so both can coexist. The suffix is a directory name only, forced by the
+conflict; it is not a name to copy anywhere else.
+
+Inside `compose.yml`, service, volume and network names follow the upstream
+project's official Docker guide. Where the guide gives none, the main service
+takes the image's own name (`code-server`, not `code-server-lsio`), and a
+supporting container may be named for its role instead — `db`, `database`,
+`cache` and the like.
+
 ## Installing software in an image
 
 Follow the upstream project's own documented install method, or the one the
@@ -91,7 +105,7 @@ directory, one mounted at `/workspace`. The home volume holds settings,
 credentials and CLI logins; `/workspace` holds the code. Point whatever
 variable selects the working directory at `/workspace`.
 
-`code-server-linuxserver`, `paseo` and `webtop` all follow this. A service with no
+`code-server-lsio`, `paseo` and `webtop` all follow this. A service with no
 human inside it does not — an agent such as `hermes` or `openclaw` keeps the
 volume layout of its official Docker guide.
 
@@ -101,7 +115,7 @@ your extensions and logins.
 
 Check who owns `/workspace` on a fresh volume. Docker creates it `root:root`
 unless the image ships the directory, and an image that drops to a non-root
-user will not be able to write there. `code-server-linuxserver` and `webtop` need an
+user will not be able to write there. `code-server-lsio` and `webtop` need an
 explicit `chown` for this reason; `paseo` does not.
 
 ## Environment variable order
@@ -187,7 +201,7 @@ Compose interpolation reads the deploying shell's environment before the
 `.env` file, so a variable must not share a name with anything the shell
 already exports. `HOSTNAME` is the trap: it is set inside every container,
 including the one Coolify itself runs in, and would silently win. Hence
-`SERVICE_HOSTNAME` in `code-server-linuxserver` and `paseo`.
+`SERVICE_HOSTNAME` in `code-server-lsio` and `paseo`.
 
 ## Upstream sources