2026.3.2 (container 2026.3.2-azure, Azure SQL): three issues found upgrading from 2026.2.5

I just upgraded my installation from 2.5 to 3.2 and tested everything I have in it.
Running in Linux container in Azure App Services using the images provided.

1. Removed schedules keep running as orphaned Hangfire jobs. Removing three schedules from schedules.ps1, in the same sync that removed their scripts, deleted them from the admin console. Their recurring jobs kept firing every minute and survived a restart, each run logging Failed to execute job with schedule <name> / System.Exception: Schedule <name> not found. Nothing was visible in the UI. Workaround: re-add the schedules with -Paused under the same names, sync, then remove them.

1. Invoke-PSUScript -Integrated now authorizes the caller. This isn't in the release notes or the cmdlet help. From an app handler it now fails with "Permission denied. The role specified does not have access to this resource." for users without script permissions, where 2026.2.5 allowed it. Also, a scheduled script with no execution role can still start another script with -Integrated, but the same script with -ExecutionRole Execute or -ExecutionRole Administrator is refused. Is that intended, and what is the supported way for an app to start a job on a user's behalf without granting the user script permissions?

1. $EventData from form controls arrives JSON-encoded. In New-UDSelect -OnChange and New-UDTextbox -OnChange, $EventData is now "value", with the quotes, where 2026.2.5 gave value.