docs: align execution handoff with Glas

docs/integrations/activity-core-handoff-wp0006.md

@@ -1,15 +1,18 @@
 # activity-core Handoff — Scheduled Agent Execution (WP-0006)
 
 > **Historical supplier handoff, completed for the initial resolver/pilot path.**
-> The current production composition is activity-core durable `ops_run` work
-> claimed by rein-aharness through its generic `agent-session` approach. The
-> resolver and preparation contracts below remain compatible inputs.
+> The initial production composition used activity-core durable `ops_run` work
+> claimed by rein-aharness through its generic `agent-session` approach. Glas
+> contract 1.0 now defines the rein-neutral execution boundary: new blueprint
+> and agent-instance handoffs should carry a versioned `harness_profile_ref`.
+> The resolver and preparation contracts below remain compatible inputs.
 
 Coordination checklist for the **activity-core** team to enable kaizen scheduled
 agent runs. kaizen-agentic owns the schedule contract, the prepare CLI, and the
 ActivityDefinition **drafts**; activity-core owns the resolver, schedule firing,
-and durable work creation (repo boundary, ADR-005); rein-aharness owns governed
-execution.
+and durable work creation (repo boundary, ADR-005). Task intake remains
+rein-local where implemented; glas-harness owns explicit execution-profile
+resolution and normalized evidence.
 
 Open this as an activity-core issue/PR titled *"Enable kaizen scheduled agent
 execution (WP-0006)"* and track the boxes there.
@@ -74,9 +77,9 @@ kaizen-agentic schedule prepare coach   # non-empty orientation bundle
 
 Then in activity-core: run the resolver (dry-run) and confirm one
 `scheduled_run` per enabled `(repo, agent)` with a correct `prepare_command`.
-For unattended operation, confirm the resulting `ops_run` is claimable and the
-rein-aharness worker selects the `agent-session` approach before enabling the
-schedule broadly.
+For unattended operation, confirm the resulting `ops_run` is claimable, the
+blueprint/instance provides an approved `harness_profile_ref`, and Glas resolves
+it without a hidden rein/model fallback before enabling the schedule broadly.
 
 ## Pilot roster
 

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.