A Shared Run Shows Its Product, Not Its Parts
You make a story video for a child, you send the link to their grandmother, and she opens a page that lists an audio player, then a picture, then the video, then three blocks of text — one of which begins "a brave little…
You make a story video for a child, you send the link to their grandmother, and she opens a page that lists an audio player, then a picture, then the video, then three blocks of text — one of which begins "a brave little fox…" and another of which reads "3d-render".
That is the run's inventory. It is not the thing that was made.
The video is the thing
A shared run now leads with its product. If there is a video, that is the share: the illustration that was generated along the way becomes the video's poster frame rather than a second item, and the narration is not listed separately because it is inside the video you are about to play. If there is no video but there is a song, the share is the song with its cover art. A run that only made pictures still shows every picture, because there the pictures are the product.
Text has to earn its place. The main piece — the story, the report — stays. Short fragments do not, which is what removes the prompt echoes: they were never content, they were the inputs, and they had been sitting under the story looking like part of it.
Old shares repair themselves
A share is a snapshot, frozen when it was made, which is what makes a shared link stable. That also means the shares already out there were frozen in the old shape and would have stayed that way.
Rather than a migration, a share in the old shape is recognised on its first public read and rebuilt once, screened as any content is. Nobody needs to re-share anything, and a link someone sent last week opens the new way.
The same snapshot feeds the link preview card and the tour, so both now show the video where they used to show whatever came first.