Adopt existing identities and review initialization actions

Edit adoption.tf.json to adopt the supplied existing marker identities at their requested addresses. api must bind original-api at terraform_data.adopted["api"] with input {name = "api", owner = "payments"}; worker must bind original-worker at terraform_data.adopted["worker"] with input {name = "worker", owner = "payments"}. Keep the existing terraform_data.audit binding owned-audit and input "security-log" unchanged. Declare exactly those three destinations. Each object ID may have only one address owner. The built-in terraform_data import starts with null input; the expected reviewed actions are adoption plus initialization updates to the approved payloads, rather than new creation, replacement or destruction. Do not add triggers_replace to force a replacement of an adopted identity. Direct import blocks use static to addresses and literal id strings. A distinct valid route uses a known literal for_each map of destination keys to IDs, to = terraform_data.adopted[each.key], and id = ${each.value}. The resource's literal for_each map supplies complete payloads with input = ${each.value}; the audit resource uses a literal input. Only built-in terraform_data declarations with input, optional literal triggers_replace and optional literal for_each, plus these bounded import forms, are supported. Arbitrary expressions, provider identity maps, modules and other resource schemas are outside this exercise. Inspect importMappings, bindings, duplicateObjectIds and actions after Run tests. Repair through normal edits without Reset.