Releasing And Deploying Tilebox Workflows

Use this skill to initialize workflow projects, turn workflow code changes into immutable releases, and deploy those releases to one or more Tilebox clusters. Use writing-tilebox-workflows for task code and this skill for project scaffold, config, publish, deploy, and runner iteration.

Agent Release Loop

For routine iteration, do the smallest safe loop:

1. For a new project, initialize once with tilebox workflow init --json or tilebox workflow init --name "Scene QA" --json.
2. Edit workflow code and ensure changed files are covered by [build].include and not excluded.
3. Optional local verification: tilebox workflow build-release --debug --json.
4. Publish: tilebox workflow publish-release --json.
5. Deploy the new release to a target or cluster.
6. If testing locally, use a testing cluster, deploy the release to that, and run a dynamic runner for that cluster and submit a job.

Prefer a specific release ID for production-like targets; use --latest for dev iteration only when that is acceptable.

For failed existing jobs caused by a compatible task bug, prefer deploying the fixed release and retrying the failed job over submitting a fresh job from scratch.