Great post. Would also like to consider the following points:

Guardrails: schema evolution is powerful — it can also accidentally add garbage columns if upstream sends unexpected fields.
Recommendation: validate/allowlist schema changes in higher environments before promoting to prod (especially for critical tables).
Observability: log schema diffs when evolution occurs (e.g., compare batch_df.schema with table schema).

This increases trust and helps teams adopt it confidently.