docs: align execution handoff with Glas

docs/adr/ADR-005-scheduled-agent-execution.md

@@ -55,18 +55,22 @@ specific durable implementation:
 activity-core Temporal schedule/event
   → rule evaluation and eligibility
   → unique, idempotent ops_run with lease/retry state
-  → rein-aharness claim loop
-  → agent-session approach and governed runtime/profile resolution
+  → rein-local intake or caller receives bounded work
   → kaizen-agentic schedule prepare <agent>
-  → bounded coding-agent session
+  → Glas ExecutionRequest(harness_profile_ref=...)
+  → versioned profile resolves rein + model + sandbox + tool policy + limits
+  → bounded session and normalized execution evidence
   → ops_run result + State Hub progress + .kaizen metrics/artifact evidence
 ```
 
-`activity-core` owns schedule and durable work state. `rein-aharness` owns
-claiming, execution policy, credential routing, runtime selection, and bounded
-session operation. Kaizen Agentic continues to own declaration, agent craft,
-preparation, and improvement evidence. A human-started coding-agent session
-remains a supported execution mode and reference smoke path.
+`activity-core` owns schedule and durable work state. Task intake stays with
+the caller or rein where already implemented. A Kaizen blueprint or agent
+instance supplies an explicit, versioned `harness_profile_ref`; glas-harness
+resolves the concrete execution constellation and normalizes evidence; the
+selected rein owns its inner loop, backend policy, and credential use. Kaizen
+Agentic continues to own declaration, agent craft, preparation, and improvement
+evidence. A human-started coding-agent session remains a supported execution
+mode and reference smoke path.
 
 ### 1. Schedule manifest — `.kaizen/schedule.yml`
 
@@ -149,9 +153,11 @@ kaizen-agentic schedule prepare <agent> [--target PATH] [--format markdown|json]
   rule evaluation, and `ops_run` state belong to activity-core; the roster query
   belongs to State Hub.
 - **No LLM invocation.** `prepare` produces a runner-agnostic bundle; a human or
-  rein-aharness-governed coding-agent session executes it.
-- **No runtime authority or credentials.** Those remain with rein-aharness and
-  the ecosystem credential/authorization owners.
+  Glas-selected rein executes it.
+- **No concrete rein/model selection.** Kaizen carries a versioned
+  `harness_profile_ref`; glas-harness resolves it without a hidden default.
+- **No runtime authority or credentials.** Those remain with Glas, the selected
+  rein, and the ecosystem credential/authorization owners.
 - **State-hub schema changes** (roster opt-in flag) are designed here but
   implemented in `the-custodian` (repo boundary).
 

docs/adr/ADR-007-forward-deployed-engagement-convention.md

@@ -132,16 +132,17 @@ should amend this ADR (or a successor), not re-open DEC-FDA-001 silently.
   `railiance-infra`; transfer requires explicit receiver acceptance before the
   supplier copy is removed or reduced to a pointer.
 - Manual preparation remains supported. Unattended host duties require an
-  engagement-specific activity-core definition and a rein-aharness execution
-  profile in addition to the generic `ops_run`/`agent-session` path.
+  engagement-specific activity-core definition and an approved versioned Glas
+  `harness_profile_ref` in addition to the generic `ops_run` intake path.
 - Kai is not a payment processor; EUR path remains future work
 
 ### Follow-ups
 
 - Complete the proposed pilot transfer to the client-owned `railiance-infra`
   evidence path and record its accepted commit
-- Register engagement-specific activity-core definitions and rein-aharness
-  profile for daily host-operator preparation when unattended operation is desired
+- Register engagement-specific activity-core definitions and a Glas execution
+  profile reference for daily host-operator preparation when unattended
+  operation is desired
 - EUR commercial FX after 2–3 engagement calibration cycles
 
 ## Pilot evidence