Stop building AI workflows your team is afraid to touch

The pattern I keep seeing: someone builds a 40-node workflow, it works, everyone's happy. Six months later that person is on vacation or has moved on, and nobody on the team will touch the thing. Sections of the flow get referred to by color, not function. Nobody can fully explain what happens when a step fails. The client calls and the agency either freezes changes or rebuilds from scratch, both of which erode trust. This isn't purely a tooling problem, but the right practices around tooling buy you time. Draft-versus-publish versioning means someone can experiment on a copy without breaking what's live. Node-by-node test runs let the next person actually see what each step does before they change it. Neither solves the knowledge transfer problem entirely, but they give whoever picks it up a fighting chance to understand the flow before touching it. The deeper issue is that the gap between a working prototype and something you'd put in front of a paying client's customers is where most agent builds fall apart. You ship the demo, then spend weeks patching edge cases that only surface in production traffic. If the person who built it is also the only person who understands those patches, you've got a bus factor of one on every client engagement. Curious what people are actually doing about this. Documentation helps but nobody writes it. Pair building helps but clients won't pay for two people on the build. How are teams solving the handoff problem on multi-step agent workflows?