Durable multimodal records and inline CLI images

Keep images and files in conversations and Records without filling database rows with large base64 payloads or weakening tenant isolation.

Runtype now offloads large inbound media to internal, tenant-scoped storage before writes. The stored message carries a compact reference, while model execution and authenticated reads transparently receive the original content.

• Conversation writes, Record creates and updates, and Persona client-token chat use the same offload path.
• Internal assets are never served through public asset routes, and missing or foreign-tenant references degrade to an unavailable marker instead of exposing bytes.
• Hard-deleting a conversation or Record also cleans up its internal assets.
• runtype conversations get and runtype records get render images inline in iTerm2, WezTerm, Kitty, and Ghostty. Pipes, CI, unsupported formats, and --no-images keep compact text markers.

The storage change is transparent to agents and API readers, so existing multimodal flows continue to receive ordinary image and file content.