What one creation flow holds besides its files, for as long as it is in
progress: the share sheet's quick-promotion controller (the editor's
publication burst and the "New reel" screen's batch are one owner in the app,
split across two screens here) and the running user flows the screens started
and will end by value. Both die with the flow: keyed by its id in the
process's state, freed when the flow closes on any path.
What one creation flow holds besides its files, for as long as it is in progress: the share sheet's quick-promotion controller (the editor's publication burst and the "New reel" screen's batch are one owner in the app, split across two screens here) and the running user flows the screens started and will end by value. Both die with the flow: keyed by its id in the process's state, freed when the flow closes on any path.