Move scheduled jobs from Trigger.dev, Inngest, Modal, Google Cloud Run and AWS Batch

Change one import, or run one command, and the jobs run on Runtime unchanged, with their schedules, sizes, timeouts and retries. withruntime/trigger runs Trigger.dev schedules.task and task definitions, and withruntime/inngest runs Inngest functions with cron or event triggers; runtime jobs deploy builds the project and creates one job per task. python -m withruntime.modal deploy app.py creates a job for each Modal Function with a schedule (modal.Cron or modal.Period). runtime jobs import reads a Cloud Run job's YAML with its Cloud Scheduler job, or an AWS Batch job definition (API JSON, describe-job-definitions output or a CloudFormation template) with its EventBridge schedule or rule, and creates the jobs. Settings with no equivalent, such as a GPU, parallel tasks or a mounted bucket, are listed with the reason. The plan is also available as POST /v1/job-imports, jobs.importPlan in every SDK and the runtime_jobs_import MCP tool. Requires SDK 0.36.0 (Python 0.34.0). See Move jobs from another platform.