# Decisions

Durable choices for this repository. Dates are the commit date or the day the decision was recorded.

## 2026-10-09 — Wrap Eugen's image

**Decision:** `entrypoint-unraid.sh` writes settings and execs `/server/entrypoint2.sh`. This repo does not copy Eugen's server launch arguments.

**Rationale:** Game updates should come from `eugensystems/warno`. The wrapper only supplies the Unraid form. Recorded in commit `b8466df`.

## 2026-10-09 — Host networking

**Decision:** The template uses `<Network>host</Network>` and does not publish a Docker port. Operators forward `EXPOSEDPORT` as TCP and UDP. The default port is `10400`.

**Rationale:** Eugen recommends host networking and requires both protocols. Unraid host networking does not show a port mapping. `10400` is this template's default, not a port named by Eugen.

## 2026-10-09 — Form-written settings

**Decision:** `WRITE_CONFIG` defaults to true and rewrites `login.ini`, `variables.ini`, and `params_for_ai.json` on each start. Set it false only for hand-edited files.

**Rationale:** The Unraid form is the supported way to configure a server. Hand edits would otherwise be mistaken for the source of truth. Recorded in commit `b8466df`.

## 2026-10-09 — Keys stay out of git

**Decision:** Dedicated keys belong in the Unraid container settings on the server. `.gitignore` ignores `login.ini` and `/settings/`. Samples keep placeholders.

**Rationale:** A key committed once remains in git history after deletion. The Unraid form shows the key in clear text. That display stays on the server, not in this repository.

## 2026-10-09 — One container per server

**Decision:** Each server is its own container, with its own name, game port, and settings folder. Additional servers may reuse the same login and key.

**Rationale:** Eugen allows a maximum of five servers for one login and key pair. Unraid reinstall replaces the existing container, so a second server is a new container.

## 2026-10-09 — Rebuild when Eugen publishes

**Decision:** `.github/workflows/rebuild-image.yml` publishes `ghcr.io/suchamoneypit/warhost:latest` when the Eugen manifest digest changes, or when the wrapper build inputs change on `main`.

**Rationale:** Players on a new WARNO patch need a rebuilt dedicated server. A normal game patch should not require an edit to this repo.

## 2026-10-09 — Jungle Law preset, RCON unset

**Decision:** The published defaults are 2v2 Conquest for workshop item `3811913066`, with Map `RDPort_JungleLaw_2v2_CONQ`. A base-game scenario ID is valid when Workshop Mod List is cleared. RCON is not on the form. The 2026-10-10 entry "Base-game defaults, workshop fields start empty" replaces these defaults; RCON is still not on the form.

**Rationale:** The first template commit (`6ee0739`) left RCON out. The Map default was empty until the scenario IDs from the Red Dragon mod files were recorded.

## 2026-10-09 — Handoff length

**Decision:** `/handoff` prints under 400 words. Words past a short status go to leftover intent, a do-not-redo list with a command, URL, or `file:line`, and git state (branch, commit, pushed or not). The paste points at `docs/` instead of restating them. The 2026-10-11 entry removes the command.

**Rationale:** A 250-word cap fit a long template session. A multi-thousand-word paste would reload that session into the next chat. The extra room is for intent and checks that the docs do not store.

## 2026-10-09 — Agent guidance and checks

**Decision:** Always-on project rules live in `.cursor/rules/`. Specialist reviewers live in `.cursor/agents/`. Durable notes live in `docs/`. `scripts/check_repo.sh` checks XML well-formedness and local repository invariants.

**Rationale:** Template review, upstream research, and independent verification are different jobs. A parsed XML file still needs an Unraid install test before it can be treated as working.

## 2026-10-09 — Diff-scoped documentation check

**Decision:** `.cursor/agents/docs-consistency.md` is part of the generic set. It runs after a functional change that alters a user-facing name, default, description, port, path, image, or command. It compares only that change with the paired template, README, and install-doc lines. The parent applies the sentences it names. It does not review untouched docs, prose, or template structure, and it states no WARNO facts.

**Rationale:** A template field description can change while the README sentence for that field stays old. Checking the whole doc set on every edit costs more than the mismatches it finds.

## 2026-10-09 — Generic and WARNO-specific guidance kept apart

**Decision:** `.cursor/rules/agent-workflow.mdc`, `.cursor/rules/unraid-template.mdc`, `.cursor/agents/unraid-template-reviewer.md`, `.cursor/agents/verifier.md`, the commands in `.cursor/commands/`, and `docs/UNRAID-TEMPLATE-GUIDE.md` contain no WARNO facts beyond a labeled project-specifics paragraph. WARNO facts live in `.cursor/rules/warno-project.mdc`, `.cursor/agents/warno-researcher.md`, `README.md`, `docs/INSTALL-UNRAID.md`, and the other `docs/` files. Subagents are launched by the main agent per the delegation table in `agent-workflow.mdc` or by the user with `/<name>`; nothing runs continuously.

**Rationale:** The generic half should move into a template repository for other game servers without editing. Rules reference docs by path instead of restating them, so the always-on context stays short.

## 2026-10-09 — Install route for Unraid 7

**Decision:** The install docs tell users to copy the template XML to `/boot/config/plugins/dockerMan/templates-user/my-<Name>.xml` and pick it from **Add Container → Template → User templates**, with the Community Applications `private/` folder as the alternative. The raw GitHub URL is only the download source. The flash filename uses `<Name>` as written, with a `my-` prefix.

**Rationale:** The Community Applications author states that Unraid 6.10 removed the Template Repositories field, so the earlier "paste the template URL" instruction cannot be followed on Unraid 7. Unraid's Template dropdown labels the file from its name with `my-` removed, and Unraid's own save path is `my-<Name>.xml` with that case kept. A download saved as `warno-dedicated-server.xml` was tried, and the dropdown showed that lowercase filename. `my-WARNO-Dedicated-Server.xml` has not been confirmed on a server yet. The private-folder route has not been executed.

## 2026-10-09 — Red Dragon ModList version

**Decision:** On 2026-10-09 the preset was `3811913066/15` and the wrapper warned only for `3811913066/0`; the 2026-10-10 entry replaces both.

**Rationale:** Eugen's Docker Hub page says the `ModList` version is usually `0`. This mod's `Config.ini`, read 2026-10-09, says `Version = 15` and tells the author to increment it when an update is incompatible. The operator's start with `3811913066/0` registered with matchmaking and produced no server line about the rejected join. The operator reported that `3811913066/15` allowed a client to join. The container has no copy of `Config.ini`, so a later increment has to be copied into the form by hand.

## 2026-10-09 — Which form fields stay visible

**Decision:** Max Players, Minimum Players, Team Size, and Combat Rule use `Display="always"`. Map, Workshop Mod List, and Workshop Mod Tags use `Display="advanced"`, after Write Config From Form, with Map and Workshop Mod List last. The Overview tells the operator to open Show more settings for the map and the mods.

**Rationale:** Those four player fields change with the map, and the preset is easy to miss if they sit behind Show more settings. Unraid prints each description under the input (`CreateDocker.php` `templateDisplayConfig`, read 2026-10-09), so the scenario-ID and workshop catalogs would make the default page very long. The Jungle Law preset is already filled in, so a first install can leave Show more settings closed. Map stays required; it is hidden because it is prefilled, not because it is optional.

Replaced the same day by the next entry, after those catalogs moved to `README.md`.

## 2026-10-09 — Map on the main form

**Decision:** Map uses `Display="always"` and follows Server Name, before Max Players. Workshop Mod List, Write Config From Form, and Workshop Mod Tags use `Display="advanced"`, in that order.

**Rationale:** The scenario-ID and workshop catalogs are in `README.md`, so the Map line on the form is one sentence. Map is the lobby operators change with the server, so it stays on the main form under Server Name. Workshop Mod List, the write-config switch, and Workshop Mod Tags stay behind Show more settings.

## 2026-10-09 — Template icon

**Decision:** `icon.png` is the Community Applications / Unraid Docker icon. The template and `ca_profile.xml` `<Icon>` tags point at the raw GitHub URL of `icon.png` on `main`. The asset is a generated NATO-vs-Pact illustration with a WARHOST wordmark and a server-rack motif, chosen for this repository (not an Eugen press-kit file).

**Rationale:** Unraid and CA load the icon from that raw URL. Eugen's [Terms of Use](https://eugensystems.com/terms-of-use/) do not grant a trademark license; no official free logo kit was found. The chosen art is still fan/generated branding, not a Steam capsule or Eugen-distributed mark.

## 2026-10-09 — Day-to-day commits stay on dev

**Decision:** Commits land on `dev` and are pushed to `origin/dev` when the maintainer asks to commit. `main` changes only when the maintainer explicitly asks to publish the accumulated work. Community Apps reads the template, icon, and `ca_profile.xml` from `main`. `.github/workflows/rebuild-image.yml` rebuilds `ghcr.io/suchamoneypit/warhost:latest` from `main` only.

**Rationale:** `main` is the snapshot strangers install. Template and doc commits there update the Apps listing on the Community Apps feed. `Dockerfile`, `entrypoint-unraid.sh`, and the rebuild workflow on `main` publish an image Unraid offers as a container update. Rapid work stays on `dev`, which neither feed reads.

## 2026-10-09 — Brand the project WARHOST

**Decision:** The product name is WARHOST. The Unraid `<Name>` is `WARHOST`, which is the Docker container name and the user-template label `my-WARHOST.xml`. The template file is `templates/warhost.xml`. The image the template installs is `ghcr.io/suchamoneypit/warhost:latest`. WARNO stays in the overview, `<ExtraSearchTerms>` (`WARNO WARNO server dedicated server game server mods modded`), the README title, and descriptive text. The host settings folder stays `/mnt/user/appdata/warno/settings`. Ports, map, mod list, and the other form defaults stay as they were.

**Rationale:** `<Name>` is one field. Docker container names, and `scripts/print_template_fetch.sh`, allow letters, digits, dots, underscores, and hyphens. `WARHOST - WARNO Dedicated Server` cannot be that field. Community Apps searches `<ExtraSearchTerms>` as well as the name and overview, so WARNO remains a search term without renaming saved appdata. The GitHub repository is `WARHOST`. URLs in the template point at `suchamoneypit/WARHOST`. GitHub redirects the old repository URL. The template path change does not: `templates/warhost.xml` replaces `templates/warno-dedicated-server.xml` on `main`.

## 2026-10-09 — Show the last 4 characters of the dedicated key

**Decision:** The Eugen dedicated key stays `Mask="true"`. A second always-visible field, Key last 4 (`EUGEN_KEY_LAST4`), must equal the last 4 characters of that key when Write Config From Form is true, or that start stops. It is not written to `login.ini`. The startup line names those 4 characters and not the rest of the key.

**Rationale:** One login can run five servers, and an operator may have two keys across several containers. Unraid's masked field hides the whole value, so the form cannot reveal four characters inside that box. The companion field is what stays readable when the container is opened later.

## 2026-10-09 — Keep scenario and mod catalogs in the README

**Decision:** Base-game scenario IDs and the named workshop mods live in `README.md`. Unraid field descriptions are one or two sentences and point at that README. `scripts/check_repo.sh` fails a Config description longer than 240 characters or one that contains a `br` tag.

**Rationale:** Unraid prints each description under its field. The Map and Workshop Mod List descriptions rendered as walls of IDs on 2026-10-09, including after `<br>` broke them into sections. A README table can be scanned. The form cannot.

## 2026-10-09 — Do not claim a 2v2 map accepts eight players

**Decision:** Max Players says the lobby is not locked to the map and that 8 slots on a 2v2 map is untested. Team Size stays the per-side count. The README gives the usual lobby for each size once and does not claim that eight slots work on a 2v2 map. The wrapper still accepts any Max Players from 1 to 20.

**Rationale:** Eugen's Docker Hub text, fetched 2026-10-09, defines `NbMaxPlayer` as how many players can join (maximum 20) and `MaxTeamSize` as the maximum on one side. It never says those must match the size in the scenario ID. Whether `RDPort_JungleLaw_2v2_CONQ` with 8 and 4 opens a 4v4 lobby has not been run.

## 2026-10-09 — Publish only the warhost image

**Decision:** `.github/workflows/rebuild-image.yml` pushes `ghcr.io/suchamoneypit/warhost:latest` and does not tag `ghcr.io/suchamoneypit/warno-unraid`.

**Rationale:** The project is still pre-alpha and the only operator already uses WARHOST. The second package was an alias for a container still pointed at the previous image name.

## 2026-10-09 — Show the dedicated key in clear text

**Decision:** `EUGEN_DEDICATED_KEY` uses `Mask="false"`. There is no Key last 4 field. This supersedes "Show the last 4 characters of the dedicated key." The key still never enters git. The startup line still names only the last 4 characters.

**Rationale:** Unraid's `Mask="true"` hides every character of a password input. [CreateDocker.php](https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php), read on 2026-10-09, has no control that reveals four characters inside that box. The edit page is how an operator tells servers apart. A companion field had to be typed by hand and could stop a start when it did not match.

## 2026-10-09 — Keep the Eugen login in clear text on the form

**Decision:** `EUGEN_LOGIN` uses `Mask="false"`, the same as `EUGEN_DEDICATED_KEY`. Clear text on those two Unraid form fields is accepted. The Docker edit page is an admin screen. The login and the key still never enter git, samples, issues, or chat. The startup line still names only the last 4 characters of the key. `.cursor/agents/credential-reviewer.md` and `.cursor/commands/credential-review.md` are WARNO-specific. The main agent launches that reviewer only for `/credential-review`, or when a change writes, logs, templates, or documents the Eugen login, dedicated key, or `login.ini`. It is not part of `/review-and-verify`.

**Rationale:** The edit page is where an admin enters the pair from Eugen's reply. Masking the login would hide it on the same screen that already shows the key. An always-on review would rerun that audit on unrelated edits. The checklist lives in the agent so a later review does not recommend masking the form. This adds those two files to the WARNO-specific set from "Generic and WARNO-specific guidance kept apart."

## 2026-10-09 — Several servers on one host

**Decision:** Each added container uses the previous Game Port plus 1, its own settings folder, and a different Server Name. The same Public WAN IP is reused. The same login and key run five servers; this wrapper does not count them. The wrapper locks `warhost.lock` in the settings folder for the life of the process and refuses a Game Port that is already listening on TCP or bound on UDP. A TCP socket in TIME_WAIT does not count. `WARHOST_PORT_TABLE` is a test seam, not a form field. Docker stores the image once. This repo does not add a volume for a game library.

**Rationale:** Eugen's Docker Hub page, fetched 2026-10-09, documents one exposed port, forwarded as TCP and UDP, and a maximum of five servers per login/apikey pair. Players join by Server Name. Sharing a settings folder lets the last start overwrite the others. The image has no Steam library, so a library volume would invite a multi-gig copy per server. A shared mount waits until a running server shows a large directory and its path.

## 2026-10-09 — Stage settings in a private directory

**Decision:** The wrapper writes `login.ini`, `variables.ini`, and `params_for_ai.json` in one mode-`700` directory under the settings folder. The name starts with `.warhost-stage.` and ends in a unique suffix. A symlink at `login.ini`, `variables.ini`, or `params_for_ai.json` is removed instead of followed. A directory at one of those names stops the start. `umask 077` is set first. `mktemp -d` creates the directory when that command exists; otherwise a `mkdir` retry does. The directory is removed on `EXIT`, `HUP`, `INT`, and `TERM`. After `warhost.lock` is held, leftover real directories with that prefix are removed. Symlinks with that prefix are left in place. `WRITE_CONFIG=false` still does not rewrite the three files, and it sets `login.ini` to mode `600`. A crash, `SIGKILL`, or power loss can leave a mode-`700` staging directory until the next locked start. That leftover is accepted. The form fields and the last-four startup line stay as they are.

**Rationale:** A fixed `.login.ini.new` path opened with `>` follows a symlink planted in the settings folder. Traps do not run after `SIGKILL` or a host crash. The next start that holds the settings lock deletes those leftovers. Clearing them without the lock could delete another container's in-progress directory when `flock` is missing.

## 2026-10-09 — Settings folder path includes the game port

**Decision:** The default host settings folder is `/mnt/user/appdata/warno/10400/settings`, the same number as Game Port `10400`. Each added container uses that path with its own Game Port, so port `10401` uses `/mnt/user/appdata/warno/10401/settings`. The Settings Folder description tells the next container to use this path with the port number plus 1. A shared-folder stop names this Game Port's folder, and the folder for the port plus 1 when that path is the one in use. A taken-port stop names the settings folder for that new port, for example `/mnt/user/appdata/warno/10401/settings`. The startup line names that same next folder. This supersedes the host-folder sentence in "Brand the project WARHOST." The container path stays `/server/settings`. The appdata directory name stays `warno`.

**Rationale:** A shared `/mnt/user/appdata/warno/settings` made a second container look like a copy of the first. On 2026-10-09 that shared folder stopped the second container, and both servers showed online with `/mnt/user/appdata/warno/10400/settings` and `/mnt/user/appdata/warno/10401/settings`. The plus-1 step is then the same one already used for Game Port.

## 2026-10-09 — MIT covers the repository, not the container image

**Decision:** `LICENSE` at the repository root is the standard MIT license, copyright 2026 suchamoneypit. It covers the templates, metadata, documentation, and `entrypoint-unraid.sh`. The template `<License>` tag is the raw URL of that file on `main`. `<ReadMe>` is the raw URL of `README.md` on `main`. The Dockerfile leaves `org.opencontainers.image.licenses` unset.

**Rationale:** Community Apps [submission help](https://ca.unraid.net/submit/help), fetched 2026-10-09, requires an OSI-approved `LICENSE` at the repository root before a submission can be finalized. The Before you begin step says that license is for repository contents (templates, metadata, and docs) and that container image licenses are separate. GitHub detects a license from a standard `LICENSE` file ([licensing a repository](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)). The GitHub API reported this repository as `MIT` on 2026-10-09. The Docker Hub API for `eugensystems/warno`, fetched the same day, states no license. An image license label of MIT would present that base image under this repository's license. `<ReadMe>` is the field the [starter template](https://github.com/unraid/unraid-community-apps-starter/blob/main/templates/example-app.xml) gives moderators for the long description. The [repository XML](https://ca.unraid.net/submit/help/repository-xml) page says moderators review from `<Name>` and `<Overview>`.

## 2026-10-09 — Number each publish to main

**Decision:** Every push to `main` gets a git tag and a GitHub Release from `.github/workflows/release.yml`. The first is `v0.90`. Later publishes add one to the two-digit minor part (`v0.91`, `v0.99` then `v1.00`, `v1.00` then `v1.01`) unless that publish includes a higher `VERSION` file. `1.0` in that file is `v1.00`. A file that still equals the latest tag increments. A file below the latest tag stops the release. The 2026-10-10 entry "A stale VERSION does not stop the release" replaces that stop. The annotated tag is created when that name is missing. A later run on a commit that already has a version tag keeps the lowest of those tags. The Unraid template stays on `ghcr.io/suchamoneypit/warhost:latest`. Daily and manual image rebuilds do not create a version.

**Rationale:** Publishes are occasional snapshots of `dev`. The number is how those snapshots are told apart. `:latest` still moves when Eugen's image digest changes between publishes, so a frozen image tag would not be the container Unraid is running.

## 2026-10-10 — Slop review is a command in a new chat

**Decision:** `.cursor/commands/slop-review.md` reviews what the repository ships the way a Community Applications moderator, a first-time installer, a security-minded homelabber, a WARNO host, and a technical editor would read it. It runs in the main chat of a new Agent session, on the model the maintainer picks. Until its report is written, it launches none of this repository's subagents and does not open `.cursor/plans/` or past chats. It reports and stops, and later applies only the finding IDs the maintainer names. It is not part of `/review-and-verify`. The body is generic; the WARHOST facts are in its Project specifics section.

**Rationale:** The project discloses AI use, so the question is whether the shipped text reads as reviewed work, not whether an AI wrote it. A subagent returns one message to the parent, and this repository keeps those messages short. This report is long by design, and the apply step needs its findings in the same chat. A new chat starts without the sessions that wrote the text, and this repository's subagents carry the same authoring assumptions. The template, README, install guide, wrapper, and icon get line-by-line scrutiny. Scripts, tests, workflows, and `.cursor/` are checked only for breakage, leaks, and contradictions.

## 2026-10-10 — Red Dragon ModList version 27

**Decision:** The preset Workshop Mod List is `3811913066/27`. The wrapper warns when that item is listed as `3811913066/0` or `3811913066/15` and still writes that value through. It does not query Steam for a newer `Version`. The next entry keeps `3811913066/27` as the Red Dragon example and makes the template default empty. The entry "Workshop Version read at container start" makes the example `3811913066` and reads `Version` from Steam at each start.

**Rationale:** `Config.ini` for workshop item `3811913066`, read 2026-10-10 from the local Steam library, says `Version = 27`. The author's change note the same day says Mod Version = 27 and 28 scenarios: https://steamcommunity.com/sharedfiles/filedetails/changelog/3811913066. The previous preset `3811913066/15` matched Version 15 on 2026-10-09 and does not match 27. Clients compare the number after the slash with that `Version`. The container has no copy of `Config.ini`, so a later increment has to be copied into the form by hand.

## 2026-10-10 — Base-game defaults, workshop fields start empty

**Decision:** The template defaults are Map `_2x2_Hesse_2vs2_CONQ` and Server Name `WARHOST - Hesse 2v2`. Workshop Mod List and Workshop Mod Tags are empty in both the `Default` attribute and the element text. The Red Dragon values, Map `RDPort_JungleLaw_2v2_CONQ`, `3811913066/27`, and `Maps-Scenarios`, are examples in the Map and Workshop field descriptions and in the README workshop mods section, where Red Dragon is the first row. The wrapper treats an unset variable and `none`, in any case, as empty for both workshop fields. When the list contains `3811913066` and Map does not start with `RDPort_`, the wrapper prints one warning and still writes the list. Max Players `4`, Team Size `2`, and Combat Rule `2` are unchanged. The entry "Workshop Version read at container start" changes the Workshop Mod List example to `3811913066`.

**Rationale:** Unraid's [Helpers.php](https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix.docker.manager/include/Helpers.php), read 2026-10-10, fills a blank `<Config>` value from its `Default` in the edit form (`xmlToVar`) and in the `docker run` variables (`xmlToCommand`). With `Default="3811913066/27"`, a cleared Workshop Mod List came back. On 2026-10-10 the operator reported that a second container, WARHOST2, hosting a base-game map kept writing the Red Dragon mod list and tags after both fields were cleared, and players without the pack could not join. An empty default lets a cleared field stay empty. A container added from the earlier template keeps the old `Default` in its saved `my-<Name>.xml`, so `none` is the opt-out that works there without recreating it. Hesse is a base-game 2v2 Conquest ID from Eugen's Map Base Id table in `README.md`, so a fresh install needs no mod and the preset player counts still fit. The warning does not stop the start because a conversion such as Galactic Divide can run on a base-game map. The 28 Red Dragon scenario IDs read on 2026-10-10 all start with `RDPort_`, so the pack does nothing for any other map.

## 2026-10-10 — Empty mod list only fits a base-game map

**Decision:** When Workshop Mod List is empty, the wrapper warns if Map is not one of the 102 base-game scenario IDs in the README, and still starts. Workshop scenario IDs that start with `_` are included in that warning. When Workshop Mod Tags is set and Workshop Mod List is empty, the wrapper prints a note that the tags are written and do not select modded content, and still writes the tags.

**Rationale:** An empty Workshop Mod List is the base-game preset, and only those maps run for players who have no workshop mod. Matching the README table, rather than every ID that starts with `_`, includes West Fulda, Highway to Oslo, Ramstein, Arsenal, and Helbe. The warning does not stop the start, matching the earlier mod-list warnings. The tags note is a disclaimer: the README already says those tags are browser icons and do not download mods.

## 2026-10-10 — Workshop Version read at container start

**Decision:** Workshop Mod List accepts a bare Workshop id, and the template example is `3811913066`. On each start, before `warno-server` launches, the wrapper turns every bare id into `id/Version` and writes that pair. A typed `id/version` is a pin and is written as typed. `warhost-workshop-versions.txt` in the settings folder caches `id time_updated Version`, and Steam's `time_updated` decides whether to read `Config.ini` again. That read is DepotDownloader 3.4.0, signed in anonymously, with a file list of `Config.ini` only, into a new directory in the settings folder that is removed before the next id. When the update check or the fetch fails and a cached `Version` exists, the wrapper writes it and warns. With no cached `Version` and no `Config.ini`, the start stops. The image installs DepotDownloader pinned by version and SHA-256, and no steamcmd.

**Rationale:** A client joins only when the number after the slash equals `Version` in the mod's `Config.ini`. Red Dragon went from 15 to 27 between 2026-10-09 and 2026-10-10, and the operator's server with the old number refused players while `warno-server` logged nothing. Steam's public item details have `time_updated` and `file_size` and no `Version`, so `Config.ini` has to be read. The server stands alone, so a Workshop folder mounted from a gaming PC was rejected. `steamcmd +workshop_download_item` has no file filter and would fetch Red Dragon's 9,059,324,422 bytes to read one line. DepotDownloader's `-filelist` filters the manifest before chunks are queued, and the measured read was 416 bytes plus a 419,989-byte manifest. Every mod names the file `Config.ini`, so ids are read one at a time and each directory is removed before the next. `ModGenVersion` is `201602` in all nine mods in the local Steam library, with the comment "ModGen revision, do not modify"; it identifies the mod generator, and `Version` is the number the client compares. One check per start keeps players in a running match, and a restart picks up a new `Version`. Anonymous access to app `1611600` Workshop manifests worked on 2026-10-10, so no Steam account is stored. A guessed number registers and then refuses every join without a log line, so a start with no `Version` stops and says why. DepotDownloader adds a 79 MB binary to the image; its GPL-2.0 license and source tag are in `README.md`.

## 2026-10-10 — A stale VERSION does not stop the release

**Decision:** A `VERSION` file below the latest git tag is ignored. The release workflow increments the latest tag, the same as when the file is absent or equal to that tag. A file higher than the latest tag is still the tag for that publish. The workflow still does not push a commit, and it still does not create a tag that already exists.

**Rationale:** The workflow reads `VERSION` and does not write it back. After a publish where the file matches the latest tag, the next tag is one minor higher and the file is unchanged. The following push to `main` then finds the file below the latest tag. On 2026-10-10 that stopped [Actions run 38097617043](https://github.com/suchamoneypit/WARHOST/actions/runs/38097617043): `VERSION` was `1.02` and the latest tag was `v1.03`, so `scripts/next_version.py` exited 1. Several agents publish without naming a new number, so the file stays behind whenever one of those pushes increments the tag. A lower file cannot rewind the number either way. Ignoring it keeps the next minor and lets that push finish.

## 2026-10-10 — Branch templates keep separate flash names

**Decision:** `scripts/print_template_fetch.sh --branch` rewrites the ref in `<TemplateURL>`. The ref already in that URL is saved as `my-<Name>.xml`. Any other branch is saved as `my-<Name>-<branch>.xml`. `/unraid-script` prints a separate paste for `main` and for `dev`, then a `--clean` paste for those two. `/first-unraid-install` is removed. `--clean` stops and removes containers named `<Name>` and `<Name>-dev`, drops an autostart line when its first field is one of those container names, removes `<Repository>` only when no container is still using that image, and deletes the two user-template files and the two private-template files. It removes `/mnt/user/appdata/warno/<port>/settings` for those containers: the template Settings Folder path, any path mounted at `/server/settings`, and any path saved in those template files. A folder still mounted by another container is left. It does not remove any other appdata path, and it does not remove a container whose name is not one of those two.

**Rationale:** One combined download installed every branch while a single branch was being tested. Separate flash names keep the dropdown entries distinct, and separate pastes keep an unused branch off the server. Apply still writes `my-<Name>.xml` from the Name field, so the clean-slate step has to remove that container and that file as well as the suffixed file. Previous Apps reads `templates-user`, and Unraid autostart reads `/var/lib/docker/unraid-autostart`. Leaving the image in place when another container uses it avoids deleting a second server's image. The settings folder holds the Eugen login and key, so a clean slate removes that folder for the containers being cleared and leaves a folder another container still mounts. The first-install walkthrough was for a setup that has already been done. The lobby page is a setting on `dev`, so there is no third template branch.

## 2026-10-11 — No session handoff paste

**Decision:** `/handoff` is removed. A new chat starts with the task. Continuity is the always-on rules, `docs/`, and `git status`. An unfinished goal is written to `docs/ROADMAP.md` during the work. `@Chats` or fork-chat is for when the thread itself has to carry over.

**Rationale:** The command spent a closing turn on a paste that was then loaded into the next chat. Git state, recorded fetches, and checks already live in the repo, and a pasted check result from the previous session is stale. The 2026-10-09 length cap does not apply anymore.

## 2026-10-10 — Lobby page stays beside the server

**Decision:** `WEB_UI` defaults to `false`. The page code lives in `webui/` on `dev`. `entrypoint-unraid.sh` gains one hook: when the variable is true and `webui/launch.sh` is executable, run it, ignore its exit, and still exec `/server/entrypoint2.sh`. A regular `variables.ini` that already exists is left in place; `login.ini` is still rewritten from the form. The page listens on the game port plus 1000, validates a save, and replaces `variables.ini`. It does not signal the game. Loading a save is an Unraid restart of that container. The Docker WebUI link is `http://[IP]:[PORT:11400]/`. A push of `dev` does not publish the page. It reaches `ghcr.io/suchamoneypit/warhost:latest` only when `dev` is merged to `main` and the image rebuild finishes.

**Rationale:** A page that is the parent of `warno-server`, or that restarts it, can take the match down when the page fails. The hook is fail-open so a missing launcher, a crash, or a taken page port only warns. Eugen's [variables.ini](https://hub.docker.com/r/eugensystems/warno) page, fetched 2026-10-10, is the key list the dropdowns write. Combat rule stays Destruction `1` and Conquest `2` from that page. The in-game labels for income and command and control are the ones recorded from the lobby screens.

## 2026-10-11 — The docker log says whether the lobby page is listening

**Decision:** With Lobby Page off, the wrapper prints `Lobby page is off. Nothing is listening on port N.` With it on, `webui/launch.sh` prints `Lobby page listening on port N.` only after a TCP connection to `127.0.0.1` succeeds and `/proc/net/tcp` shows that port listening on `0.0.0.0`. The server writes its own pid. The ready file is completed after the privilege drop is attempted. If the drop fails, the process stays root, the container log warns that it stayed root, and the page still serves. `WARHOST_WEBUI_DROP_FAIL` is a test seam, not a form field.

**Rationale:** On 2026-10-11 the operator opened the Docker WebUI button and Brave reported `10.0.1.105 refused to connect`. The docker log from that boot shows `warno-server` reaching matchmaking on `71.241.212.203:10400` and never mentions a lobby page. `ghcr.io/suchamoneypit/warhost:latest` was the image from [Actions run 38097617038](https://github.com/suchamoneypit/WARHOST/actions/runs/38097617038) for commit `9dfec47`. Its entrypoint layer does not contain `WEB_UI`. Host networking leaves `[PORT:11400]` as 11400 ([DockerClient.php](https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php) `getControlURL`, re-read 2026-10-11), so the button opens a port that image does not serve. The next image has to say that in the same log. A failed privilege drop must not close the port after the launcher has already returned.

## 2026-10-11 — The form field is WebUI, and a save does not add a workshop mod

**Decision:** The Show more field is named WebUI. `Target` stays `WEB_UI` and the default stays `false`. The docker log says `WebUI is off. Nothing is listening on port N.` and `WebUI is off. Port N is already in use.` With it on, `webui/launch.sh` prints `WebUI listening on port N.` The page heading is WARHOST WebUI. The map list shows base-game maps. Modded maps appear only when `ModList` already contains that pack's workshop id. A save keeps the existing `ModList` and `ModTagList`. A modded map whose pack id is absent is rejected. The page does not write the Unraid template.

**Rationale:** Unraid's Docker button is already called WebUI, and the old field name did not tell an operator that the button and the field are the same page. The page cannot edit the template on the Unraid flash. Writing a catalog `id/version` would pin a Version the wrapper does not refresh while WebUI is on, and it would drop a second workshop id joined with a hyphen. Workshop mod tags do not identify a pack.