{"version":"2.1.228","anchor":"adopted-agent-transcripts-are-relinked-by-hard-link-with-a-v","canonical_anchor":"adopted-agent-transcripts-are-relinked-by-hard-link-with-a-v","heading":"Adopted agent transcripts are relinked by hard link with a verified copy fallback","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/adopted-agent-transcripts-are-relinked-by-hard-link-with-a-v","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Adopted agent transcripts are relinked by hard link with a verified copy fallback\n\nAdopting an agent's transcript now hard-links the file, copying only when linking is impossible.\n\n**What**\n\nOn the v5 transcript storage backend, adopting an agent now places its transcript and metadata file under the expected name using a hard link, falling back to a streaming copy when linking is not possible. The older relink path still runs on other backends.\n\n**Details**\n\n- The fallback copy verifies the inode, refuses on `ADOPT_IDENTITY_MISMATCH`, and preserves timestamps.\n- If the transcript step throws, the metadata file write is rolled back.\n- A new `tengu_adopt_link` event records the kind, the method used and any fallback code, reporting `adopt_link_fallback_copy` when a copy was needed.\n\n**Evidence**\n\n`tengu_adopt_link`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}