Automated Canvas CLI workflows can fail when pushing page content if the target page has existing auto-save data from edits in the Canvas UI. This is a problem for workflows such as when using GitHub Actions, where page content is pushed automatically from files. In these cases, the newly pushed content could later be overwritten when the existing auto-save data is published. However, that pushed content is typically recoverable because it exists locally or is version controlled. We need to support fully automated workflows, even when a user has in-progress auto-save data in Canvas. As an interim step, the content push endpoint should allow CLI pushes to proceed instead of failing because auto-save data exists. Canvas page conflict resolution is planned separately. Once available, users publishing auto-saved changes should be warned when conflicts exist and asked to resolve them.