Files feed: document parent for images hotlinked into chats

[jeremy]

GET /files.json wraps rich-text attachments in a recording envelope whose parent identifies the recording the attachment hangs from. For most attachments that is the document or message they live in — but an image hotlinked into a chat is recorded under an autolinked-image wrapper, so that wrapper is the parent: its title is the image's source URL, and its url and app_url point at the surrounding chat line.

This documents that case. (Requests for pages surfacing such attachments previously returned an error; they now render, with the parent shape described here.)

Synced from bc3 doc/api/ by script/api/sync_to_bc3_api — not a hand-edit.

[Copilot]

Pull request overview

Documents how GET /files.json reports the parent recording for rich-text attachments when the attachment is an image hotlinked into a chat (where the parent is an autolinked-image wrapper rather than the surrounding document/message).

Changes:

• Clarifies that parent identifies the recording an attachment hangs from, which may be the containing doc/message or (for hotlinked chat images) an autolinked-image wrapper whose url/app_url point at the chat line.

Tip

If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.