VersionControl:PRs/maybelle-config/247

maybelle-config#247: hunter: agency-<name> becomes emergent-<name>; homes move whole

State	🟣 merged 2026-11-01 03:12:32
Worked on by	magent, justin
Moods	#emergence
Deploy	redeploy hunter
Branch	emergent-containers → production, by magent-cryptograss
Opened · last pushed	2026-10-31 20:33:47 · 2026-10-31 20:33:35

Justin picked `emergent-<name>` as the containers' name in #emergence (31 Oct). This is the last open piece of the Agent → Emergent rename.

**What happens on the next hunter deploy**
1. `retired: [agency, agency-re, agency-blu]`: the playbook runs `docker compose down` for agency-re and agency-blu and renames their compose files `docker-compose.retired.yml`. Everything else under `/opt/magenta/agency-*` stays on disk.
2. `emergent-re` and `emergent-blu` are made with `home_from: agency-re` / `agency-blu`. `agent_homes.py` moves each home over whole with `os.rename` on the same filesystem, so sessions, poller state and clones all come along. The paths inside are `/home/<agent>` in either container, so nothing in a home needs changing.
3. Later deploys find each home in place and move nothing (test covers it).

**Also**
- `mood: emergent` replaces `mood: agency`. For an agent's container, `MOOD_SLUG` is only checked as plain words; it is never passed to the poller (`start_agent_poller`), so the value is cosmetic.
- Comments in the compose template, user-instance tasks, Caddyfile and `container_startup.py`, plus `hunter/CONTAINERS.md`.
- New test `test_agency_re_becomes_emergent_re_its_home_whole`. `scripts/test_agent_homes.py` and `test_container_startup.py`: 37 pass.
- magenta has no references to `agency` (checked with `git grep` on origin/main).

**Expect:** re and blu go down for the length of one container start. A turn running at that moment is cut off. Ansible isn't installed in my container, so I didn't run `render_diff.py` locally; CI runs it on this PR.

Deploy: redeploy hunter
Worked on by: magent, Justin, in #emergence