[Crunch] inconsistent find_or_create behavior in pipeline runner vs job
|Velocity based estimate||-|
The pipeline runner automatically adds a find_or_create = true field for jobs in the pipeline, if one does not exist. This inverts the documented default behavior at the job level (which is find_or_create = false).
Either we need to change the pipeline runner behavior, or we need to explicitly document this. It's very confusing to have a different default at different layers in our stack, though.