Owner invitations

Steps

1. The Owner submits one invitation to an exact host. Read this device's invitations and current state. Process only the matching goal_id, host/config, run and world epoch; do not approve for the Owner or revive an old invitation.
2. The invitation's recipe_ref and installed provider's online guide_href define the task. Do not dispatch if the recipe is absent, changed or its input is invalid. The invitation does not expand World or host authority.
3. Receipt, host results and World actions are separate facts. A host ending does not prove task success; read observe and original action receipts for World changes. Stop new invitation work when cancelled or control/device generation changes, and reconcile uncertain outcomes using original requests.