ddflow_resolve
Settle a contested item by choosing which duplicate definition or lease to keep; the losing claim is released, and losing definitions can be re-added under new ids.
Instructions
Settle a CONTESTED item: two clones each added the same id with different content, or each claimed it, and a merge brought both in. ddflow_doctor names every contested item, ddflow_show lists the rival definitions (event id, agent, title, body) and claims, and ddflow_next will not offer one until it is settled. keep names the definition (event id or agent) and/or the lease holder to keep; the losing claim is released in the same transaction. A losing DEFINITION is returned in lost -- re-add it under a new id with refile_as, or it exists only in the log. Refused (exit 3) on an item that is not contested. Settle what the operator decides, not by guess.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The contested item. | |
| keep | Yes | Event id (or a 6+ character prefix), agent, or lease holder to keep. | |
| as_agent | No | Subagent sharing the parent's connection: your own stable name, for this call only (see ddflow_identify). | |
| refile_as | No | Comma-separated new ids, one per definition NOT kept, in `show` order: each is re-added under its new id in the same transaction. |