Great breakdown! This makes it so clear:.GitHub Actions handles the heavy lifting of deploying code to production, while job_runs steps in right at deployment time to handle those one-off configuration migrations or definition updates—acting almost like a DDL migration script right inside Databricks. Very useful feature.