Close out statehub-register bootstrap housekeeping (REIN-A-0001)

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

SCOPE.md

@@ -1,32 +1,52 @@
 # SCOPE
 
-> This file was generated by `statehub register`. Refine it as the repository
-> boundaries become clearer.
-
 ## One-liner
 
-Claude-Code-CLI-driven rein: governed, unattended/scheduled agent runtime
+Claude-Code-CLI-driven rein: governed, unattended/scheduled agent runtime.
+Formerly `agent-harness`; renamed per glas-harness ADR-001. Deployed live on
+Railiance for tenant `binky-control`.
 
 ## Core Idea
 
-rein-aharness exists to provide the capability described in INTENT.md.
+The single shared, multi-tenant runtime: consumes tasks (local JSON file or
+issue-core polling), loads a kaizen-agentic persona, runs a bounded Claude
+Code CLI session under a named tool profile allow-list, verifies a local
+commit, reports to State Hub and `.kaizen/metrics`. The harness is the only
+credential holder and only policy enforcement point for its sessions.
 
 ## In Scope
 
-- Maintain the repository's primary implementation.
-- Keep docs, tests, and operational metadata current.
+- Instance manifest resolution (`.kaizen/schedule.yml` extensions),
+  named tool profiles (`green-commit-only`, `blue-mail-triage`)
+- Task intake: local task-file (dev) and issue-core polling (production)
+- The agentic session itself (`adapter.py`/`runner.py`), including
+  per-tool-call audit streaming (`--stream-tool-events`,
+  `HARNESS-WP-0002-T03`)
+- kaizen metrics + State Hub progress/token reporting
+- Railiance packaging and deployment (`Containerfile`, `deploy/`)
+- Two non-Claude, non-agentic side paths: deterministic mailbox scan
+  (`mail-scan`) and llm-connect-JSON-driven mail-triage/daily-brief
 
 ## Out of Scope
 
-- Own unrelated adjacent systems.
-- Make irreversible operational decisions without human approval.
+- Scheduling and blueprint authoring — stay in `activity-core` and
+  `kaizen-agentic` respectively (this repo only consumes/loads them)
+- Being the glas-harness meta-framework itself — this repo is one
+  concrete rein under it, not the router
+  (`glas-harness/docs/adr/ADR-001-rein-harness-family.md`)
+- LLM provider abstraction — stays in `llm-connect`
 
 ## Current State
 
-- Status: active; implementation and stability should be verified by the repo agent.
+`HARNESS-WP-0001` (foundation) and `HARNESS-WP-0002` (rename + glas-harness
+alignment, including the live Railiance cutover) are both done. Live-proven
+through glas-harness's gateway with a real Claude Code session and a real
+verified commit. Deploy artifacts, CLI, and package are all under the
+`rein-aharness` name on the live Railiance deployment.
 
 ## Getting Oriented
 
-- Start with: INTENT.md
-- Agent instructions: AGENTS.md
-- Workplans: workplans/
+- Start with: `INTENT.md`
+- Deploy: `deploy/README.md`
+- Agent instructions: `AGENTS.md`
+- Workplans: `workplans/`