Rename repo to rein-aharness per glas-harness ADR-001

Repo-identity rename only (directory, git remote, pyproject name,
self-referencing docs). CLI/package/deploy rename tracked separately
in REIN-A-WP-0002-T02 since it touches a live Railiance deployment.

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

README.md

@@ -1,4 +1,6 @@
-# agent-harness
+# rein-aharness
+
+(formerly `agent-harness`, renamed per glas-harness ADR-001 "rein" harness family)
 
 The single shared runtime for unattended agent instances in the Coulomb /
 Operational Knowledge ecosystem. Projects declare agents (manifest +
@@ -6,6 +8,18 @@ Operational Knowledge ecosystem. Projects declare agents (manifest +
 tasks via activity-core, compute via llm-connect, credentials via
 OpenBao/ops-warden, reporting to the Custodian State Hub.
 
+Within the glas-harness meta-framework, this repo is the **`rein-aharness`
+rein**: the Claude-Code-CLI-driven, unattended/scheduled harness for
+tenants that need governed cron-style agent runs. See
+[glas-harness ADR-001](../glas-harness/docs/adr/ADR-001-rein-harness-family.md)
+for how it relates to other reins (e.g. `rein-openweights`).
+
+The CLI command (`agent-harness`), Python package (`agent_harness`), and
+deploy artifacts (Docker image tag, k8s namespace, Railiance host paths)
+still use the old name — that rename is tracked separately in
+[workplans/REIN-A-WP-0002](workplans/REIN-A-WP-0002-rename-and-glas-harness-alignment.md)
+because it touches a live Railiance deployment.
+
 - Why and boundaries: [INTENT.md](INTENT.md)
 - Decision + architecture: [docs/adr/ADR-001](docs/adr/ADR-001-agent-harness-architecture.md),
   [docs/architecture.md](docs/architecture.md)