Manage Relationship Action

Draft, approve, and record the outcome of ONE warm-introduction attempt.

A "relationship action" is a single attempt to reach a target person through a mutual connection rather than by contacting them directly: asking a colleague for an intro, checking whether a connector actually knows them, or requesting an entry into their company. find_warm_path discovers those routes and never writes; this tool is the only way to act on one.

Use this instead of the direct-outreach tools when the path runs through a person. manage_outreach and manage_messages send to the target themselves; manage_engagements handles reactions and comments on content. This tool messages the connector.

Nothing here auto-sends. Every attempt walks a state machine you drive one call at a time: draft creates it from a result_ref returned by find_warm_path, then transitions approve the exact message text, confirm that you sent it yourself outside Vruum, classify how the connector replied, record the final outcome, or cancel. The response's approval_required and next_actions fields tell you which transitions are legal right now — read them rather than guessing.

Two consistency rules the server enforces:

• draft is idempotent on client_request_id. Reuse the same value when retrying a draft; a new value creates a second attempt.
• Every transition needs expected_version. A stale version means someone else moved the attempt and yours is rejected rather than silently overwriting — re-read the attempt and retry.

A 409 route_stale on draft means the underlying relationship evidence changed since it was reviewed; re-run find_warm_path and draft from a fresh result_ref.