test: prepare real local rein acceptance with artifact verification

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0726e-5232-73f2-aaca-2c05ceb62efb

docs/local-profile-acceptance.md

@@ -123,3 +123,39 @@ retarget existing consumers or enable production schedules.
 
 The open-weight profile remains blocked until its own route and real-rein
 proof pass. Keep that portion of `GLAS-IN-0002` live after this workplan closes.
+
+## Prepared acceptance runner
+
+After the owner requirements and candidate review pass, run:
+
+```bash
+.venv/bin/python scripts/prove-local-profile.py \
+  --harness-profile harness.agent-dev-local@1.1.0
+```
+
+Use `--profile-dir <reviewed-directory>` if the versioned candidate is staged
+outside the packaged catalog. The runner requires an explicit version, the
+local Claude route, nonempty credential route references, and bounded token/time
+limits. It preserves catalog readiness and refuses blocked profiles before
+creating even the disposable fixture. There is no force or readiness override.
+
+The fixture wraps the catalog-built `ReinAharness` to observe its result and
+cleanup, while delegating actual session setup and agent dispatch. It checks
+the committed and working-tree file contents, direct parent commit, changed
+paths, clean tree (including ignored files), source absence, exact child
+identity, and task mode inside owner execution. Task removal is checked before
+destroy; host source integrity and workspace absence are checked afterward.
+
+Output includes configuration references, requested model, commit id, and
+boolean checks. It excludes raw model/provider output, task text, and exception
+messages. Exit zero means this real-run artifact/lifecycle acceptance passed;
+`readiness_review_required` remains true. The owner runtime/deployment pins,
+credential-delivery proof, enforced egress and negative-route checks remain
+separate prerequisites for T02/T05. The runner does not update the catalog or
+publish artifacts.
+
+Validation of the runner itself: its focused tests use local disposable Git
+repositories and mocked adapter boundaries, covering extra commits, extra
+paths, bad content, untracked/ignored artifacts, source visibility, file mode,
+strict boolean inspection results, redacted failures, and profile refusal.
+These tests do not count as the pending real-rein acceptance run.