Thanks for putting this together 
I’m on board with the solution, phasing, and layering. Once we iterate to something more programmable, it’ll feel like an ejection to the user, but all we’ll end up doing is allowing them to drill down a layer and get to the engine primitives that make this possible.
Another example you might want to include as a reference is Ona and their automations, which I believe embrace a .yaml format:
tasks:
install:
name: Install dependencies
command: npm ci
triggeredBy:
- postDevcontainerStart
I’d keep an eye on how this space (agentic automation) evolves, because I believe we’ll see some patterns emerging around how to codify automation that includes non-deterministic agentic steps. I also think this primitive has the potential to be shareable by the community as our platform has more capabilities (e.g. we expose more data and signals)