[Atmostone]

The name now matches what the thing does: this is an evaluation harness, not a spawner.

What changed

217 occurrences across 73 files, in three casings handled separately: spawnhive to evalhive (178), SpawnHive to EvalHive (40), SPAWNHIVE_ to EVALHIVE_ (34).

The SPA- ticket prefix is deliberately untouched — 83 references in the CHANGELOG alone. It is the Linear team key, and changing it would invalidate every commit subject and cross-reference in the project history.

Beyond text

Most of these are not prose. The rename also covers the identity of live infrastructure:

Volumes	spawnhive_* to evalhive_* — copied, not recreated
Database + role	spawnhive to evalhive
MinIO bucket	spawnhive to evalhive
Network, containers	evalhive-*
Images	rebuilt, including the derived Toolathlon agent
Repository	Atmostone/SpawnHive to Atmostone/EvalHive

COMPOSE_PROJECT_NAME=evalhive is pinned in .env (not in this diff — the file is ignored). Without it the volume prefix follows the directory name, so renaming the checkout would silently create a second, empty set of volumes.

One benchmark fixture changed

_rag/spawnhive-internal-runbook.md is renamed along with the eight capability cases that reference it. Flagging it rather than burying it: that is an edit to a frozen dataset, not cosmetics, and runs recorded against the old filename belong to the prior version of those cases.

Verification

The migration was verified rather than assumed:

• volumes compared file by file — pgdata 2543 = 2543, miniodata 17724 = 17724, zero differences. A size check had suggested pgdata lost 2.7 MB; that turned out to be directory-entry overhead, not data, and only the per-file diff could say so.
• 521 experiment_runs, 208 quality records and 7 annotations intact after the database and role rename;
• blobs read back from the renamed bucket (3/3 sampled);
• 718 unit tests pass against the renamed stack;
• an agent spawns from evalhive-agent:latest and the API answers 200.

One defect this surfaced

Toolathlon cells run on a derived image, evalhive-agent-toolathlon:latest, which rebuilding the base image does not produce. Two cells started on the plain image before this was caught — they would have been recorded as agent failures when the cause was the rename. Caught from a mismatch between running cells and running containers: the experiment was paused, the derived image built, and the affected containers removed. Worth remembering — after any image rename, the derived images need rebuilding too.

Not included

The working directory is still SpawnHive — that is a host path, and renaming it breaks open terminals and IDE sessions. It is now safe to rename at any time, since the compose project name no longer depends on it.