A Step node is one Gitea Actions step as it is (run, uses, with, env): inert in the browser, verbatim in the
export. Import now takes any Actions workflow file, not only one exported from here: its steps become a chain of
Step nodes and the rest of the file (on, permissions, concurrency, the job's runs-on and env) is kept as the
workflow's frame, so it exports back as it came in, with any Venice nodes spliced in as runner steps. A file
exported from a framed workflow re-reads each step's YAML from the file on import, so an edit made in the file wins.
Proof: .github/workflows/venture.yml imports as three Step nodes and exports back identical.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: open-workflows-venture-loop
teahubxyzandClaude
e6621649c3