Rename package, CLI, and deploy artifacts to rein-aharness (HARNESS-WP-0002-T02)

agent_harness -> rein_aharness (package + all imports), CLI command
agent-harness -> rein-aharness, Docker image tag, k8s namespace/labels/
names, Makefile targets, deploy script env var/paths. In-repo identity
strings (hub event source, metrics harness field, default assignee,
argparse prog name, commit author identity) updated to match.

Historical documents left untouched on purpose: docs/adr/ADR-001-agent-harness-architecture.md,
docs/architecture.md (dated v0.1 snapshot), workplans/HARNESS-WP-0001
(completed under the old name), and the SSH host alias
"forgejo-agent-harness" (external ~/.ssh/config entry, not owned here).

Verified: 47/47 tests pass, CLI runs correctly from a fresh venv,
`make image` builds and the resulting container runs correctly.

deploy/README.md gained an explicit rename cutover checklist for what
this session cannot safely do unattended -- moving the host-side
secrets dir and checkout on railiance01, and not deleting the old k8s
namespace until the new one is confirmed working. The actual live
cutover (running that checklist against the real Railiance deployment)
is not attempted here -- real production surgery on binky-control's
live automation, needs the operator present.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md

@@ -33,19 +33,48 @@ state_hub_task_id: "bf04ed50-cbe2-4f8f-9876-d06c579d19e6"
 
 Rename the parts of this repo that a mechanical identity rename would
 otherwise silently break, because they touch a *live* Railiance
-deployment: the `agent-harness` CLI command (`pyproject.toml
-[project.scripts]`, `agent_harness/cli.py` entry point), the
-`agent_harness` Python package directory, the Docker image tag
-(`agent-harness:railiance01`), the k8s namespace/labels/ConfigMap names
-(`deploy/k8s/railiance/*.yaml`), the Railiance host directory
-(`~/agent-harness/deploy/...`), and `deploy/scripts/railiance-smoke.sh`'s
-`AGENT_HARNESS_ROOT` env var and SSH remote alias. Do this as one
-reviewed change with a Railiance re-deploy and smoke-test run
-immediately after, not as incidental cleanup.
+deployment: the `agent-harness` CLI command, the `agent_harness` Python
+package directory, the Docker image tag, the k8s namespace/labels/
+ConfigMap names, the Railiance host directory, and
+`deploy/scripts/railiance-smoke.sh`'s env var and paths.
+
+**Code/config side done (2026-07-26):**
+- `agent_harness/` → `rein_aharness/` (`git mv` + all internal imports)
+- `pyproject.toml`: `[project.scripts]` → `rein-aharness =
+  "rein_aharness.cli:main"`; wheel package name
+- `Containerfile`: `COPY rein_aharness`, `ENTRYPOINT ["rein-aharness"]`
+- `Makefile`: `IMAGE`/`TAR` → `rein-aharness:railiance01` /
+  `rein-aharness-railiance01.tar`; `deploy-rsync` target path
+- `deploy/k8s/railiance/*.yaml`: namespace/labels/names/image all
+  `rein-aharness`
+- `deploy/scripts/railiance-smoke.sh`: `AGENT_HARNESS_ROOT` →
+  `REIN_AHARNESS_ROOT`, default checkout path, AppRole env source path
+  (SSH host alias for Forgejo left untouched — that's an external
+  `~/.ssh/config` entry, not owned by this repo)
+- In-repo identity strings updated too: `hub.py`'s `source` field,
+  `metrics.py`'s `harness` field default, `intake.py`'s
+  `DEFAULT_ASSIGNEE`, `cli.py`'s `argparse` prog name, commit
+  author identity in `smoke.py`/`tenant_onboard_runs.py`
+- Verified: 47/47 tests pass, `rein-aharness` CLI runs correctly from a
+  fresh venv, `docker build` succeeds and the built image runs
+  (`ENTRYPOINT`/`CMD` dispatch correctly)
+- `deploy/README.md` gained an explicit **rename cutover checklist**
+  for the parts this session cannot safely do unattended: moving the
+  host-side secrets dir (`~/.local/agent-harness` → `~/.local/rein-aharness`)
+  and checkout (`~/agent-harness` → `~/rein-aharness`) on railiance01
+  itself, and not deleting the old k8s namespace until the new one is
+  confirmed working
+
+**Still open — the actual live cutover:** running the checklist on
+railiance01, rebuilding+importing the image there, applying the renamed
+k8s manifests, and running the host smoke script against the live
+deployment. Not attempted from this session — real production surgery
+on `binky-control`'s live automation, needs the operator present for
+the actual host-side moves and a confirmed rollback point.
 
 ```task
 id: HARNESS-WP-0002-T02
-status: todo
+status: progress
 priority: medium
 state_hub_task_id: "7c5d23cd-d7fd-4c79-8847-448b83feb673"
 ```