A job's body may be a prompt, so a coworker can do light scheduled work only its brain can do.

A job's body may be a prompt. A jobs[] entry declares one body: run for a process in its own pod, or prompt for a brain turn in the gateway — so reading one channel at 18:00, summarizing it, and posting to another needs no clock outside the coworker, where its kill switch and doctor can't see it.
The prompt is a reviewed page, named not pasted. prompt takes a short inline string or { skill: <name> } from the bundle's own skills/, read at load and refused there. No channel text can start one of these turns or edit its prompt.
An external worker deploys on managed Kubernetes again. The 1.34 floor read v1.34.9-eks-… as a prerelease and refused every cluster it was meant to admit. Chart 0.13.1; the runtime is untouched.

Chart 0.14.0 pairs with this release in one direction only — a 0.5.0 gateway refuses a manifest declaring a prompt job, so mirroring one in values must take imageRef to 0.5.1 in the same pass. Full notes are on the v0.5.1 release.

A scheduled job that can think