docs: align execution handoff with Glas

docs/integrations/forward-deployed-engagement-playbook.md

@@ -90,7 +90,7 @@ kaizen-agentic engagement close-session eng-... \
 - Enable entries in engagement `schedule.yml`; they declare intent but do not
   activate unattended work by themselves
 - Continue manual prepare until an engagement-specific activity-core definition
-  and rein-aharness profile have passed a bounded smoke test
+  and versioned Glas execution profile have passed a bounded smoke test
 - Daily: health + load; weekly: OS/security pass (privileged changes still gated)
 
 ### 8. Ramp-down (when ending)
@@ -161,9 +161,12 @@ Not required for operate. When ready:
 
 1. Customer or engagement repo owns the ActivityDefinition that identifies the
    engagement and emits idempotent, claimable `ops_run` work in activity-core.
-2. The run carries `agent-session` approach metadata and a compatible
-   rein-aharness profile reference; it does not carry secrets or raw prompts.
-3. rein-aharness claims the run, resolves credentials and policy, and executes
+2. The run or bound agent instance carries organizational references and an
+   approved versioned `harness_profile_ref`; it does not carry secrets or raw
+   provider prompts.
+3. Rein-local intake or another caller claims/receives the work and constructs
+   the Glas `ExecutionRequest`. Glas resolves the concrete rein, model, sandbox,
+   tool policy, and limits; the selected rein executes
    `kaizen-agentic engagement prepare <id>` inside the bounded session.
 4. Completion links the `ops_run`, engagement report, metrics, and State Hub
    progress without duplicating confidential content into coordination records.