docs: consolidate agent execution and custody

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

@@ -127,16 +127,21 @@ should amend this ADR (or a successor), not re-open DEC-FDA-001 silently.
 
 ### Negative / trade-offs
 
-- Pilot vault currently sits in the supplier repo (`engagements/pilots/`) — must
-  still be treated as client confidential; export to client repo is recommended
-  before multi-tenant growth
-- activity-core automation for host duties is optional Phase 3 (manual prepare OK)
+- Pilot vault currently sits in the supplier repo (`engagements/pilots/`) under
+  transitional custody. The Railiance01 receiving authority is
+  `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.
 - Kai is not a payment processor; EUR path remains future work
 
 ### Follow-ups
 
-- Export pilot vault to client-owned path when railiance ops repo is ready
-- Optional activity-core ActivityDefinitions for daily host-operator prepare
+- 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
 - EUR commercial FX after 2–3 engagement calibration cycles
 
 ## Pilot evidence