Clone 'Program Steps' in Dynamic JO

Quick note on the AI angle, we're actually thinking about this at the whole program level, where AI can suggest and scaffold entire programs rather than individual steps, to build a new program.

1. Which step types matter most to you — Evaluate, Send Email/Survey, or all? Are there some you'd prioritize?
   1. From my POV, evaluate steps would offer admins the most consistency and allow more trust in building without having to put our eyes on every single evaluate step. In the first example below, we have a nine email JO with a week between each email. We made the choice to only evaluate whether the subscription was active ONCE because we’d have to rebuild the evaluate step each time. In the second example, we have a 1 year journey (1 month between each email, then a 6 month gap) -- we HAD to rebuild the evaluate step between each email, because otherwise someone may need to be routed out of the program.
   2. Whether a contact is active doesn’t change -- there are certain fields that will always be included with the same logical operators. Those operators increase the potential for error, and we’d need to audit any AI-created program to ensure it built the evaluate step the same way each time.
   3. There may be additional program-specific criteria added -- this is where pulling an evaluate step from a library and cloning it would be a HUGE admin QoL benefit.
   4. CTAs would also be valuable, but more from a cloning perspective in my mind.
2. If AI is scaffolding whole programs, would a step library still be valuable or does the program-level approach cover the need? ​@dayn.johnson 
   1. See above -- the step library would be hugely beneficial. It’d make things significantly easier when we need to onboard another admin (or AI) to help us build JO flows and queries.