A job can hand back an answer

• A job can answer, not just report that it ran. A reviewed external job opts in with output: {format: json} and returns bounded structured JSON through job_status, kept for seven days and released only on an explicit read by the author who asked, in the conversation they asked in. Output that is missing, invalid or blocked erases neither the execution facts nor a valid gate, and a delivery that fails never reruns the job.
• A run leaves a record you can count. AGENT_WORK_EVENTS=1 — or agents.<name>.workEvents in chart 0.12.1 — emits bounded, versioned start and completion records from the scheduled and chat hosts alike, and a job report can carry typed artifact, subject-state, usage and health facts alongside them. Child diagnostics stay out of the host envelope, as do raw gate details, requester information and parameters.
• A verdict file has a size and a shape. Local verdict artifacts cap at 64 KiB and must be regular UTF-8 files rather than symlinks; an oversized or invalid report leaves its gate unproven instead of trusted.

Answers and work events are both opt-in, and no agent.yaml that works today needs a new field. Bring the gateway, dispatcher and worker images to the same release before turning structured answers on, and check JOB_OUTPUT_SCHEMA_VERSION or JOB_WORK_SCHEMA_VERSION before emitting a new artifact section — an older host rejects fields it doesn't know. Full notes are on the v0.4.1 release.