docs: align execution handoff with Glas

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