Under the hood
Artifact type descriptions can now be resolved from a separate type_file reference instead of inline content
What
A new function handles describing an Artifact's type when that type's data lives in a separate type_file reference rather than being written inline. It can show either a placeholder for content that hasn't been read yet, or a preview of the actual content. The calling code also now checks a new read_of_type_link flag to decide whether to prefix the type's title before showing its description.
Why
This lets Artifact type information be stored in and pulled from a separate file rather than always being embedded directly, with appropriate handling for cases where that file hasn't been read yet.