Flow generator

Read an Adapty flow's builder config, transform it, check the result, and write it back. Transforming a config that exists is the default, and the safer path: everything you emit is then grounded in a document that already works.

Authoring a new flow is also in scope, and two things — and only these two — genuinely cannot be synthesized:

• An image you have no readable FILE for. Given a path you can now upload it — flows media upload (media.md). An image you can only see — pasted or attached into the conversation — is not one you have: ask for a path. With no file there is nothing to upload, so it stays an empty values map, never a made-up URL (trap 5). SVG uploads fail, so a monochrome glyph is authored inline in _meta.icons; a graphic no element can express, you draw and rasterize (media.md). An icon is not in this list: python3 references/icons.py --search <word> resolves any phosphor glyph, and an invented name draws blank however good your markup is (trap 23).
• Real store prices. They come from the store, not from Adapty; products create has no price flag.