Adopting an agent's transcript now hard-links the file, copying only when linking is impossible.
What's wrong with this entry?
On 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.
- The fallback copy verifies the inode, refuses on
ADOPT_IDENTITY_MISMATCH, and preserves timestamps. - If the transcript step throws, the metadata file write is rolled back.
- A new
tengu_adopt_linkevent records the kind, the method used and any fallback code, reportingadopt_link_fallback_copywhen a copy was needed.
tengu_adopt_link
Strings lifted out of the shipped bundle, so the claim above can be checked against them.