- This is not currently not used in production.
- This is broken storage side [1]
- And finally, this is temporary as this will soon go away with T2310 [2]
[1] origin-visit-add does not deal correctly with metadata
(origin-visit-status-add does it well though). And it so happens there is no
test around it... So unfortunately it only got detected by @douardda's run with
the backfiller or something. It's good it got detected though ¯\_(ツ)_/¯
[2] we are currently phasing out multiple origin-visit fields including this
one