[witbrock]

Merge decision: ready — this adds a working single-host pilot that turns a SAIL task assignment into a subscription-backed Codex run and a result or question delivered through Von.

User outcome

Michael can assign a native Von task to Codex DGX, share its originating conversation, and receive coding results or questions in Von while his Mac is offline. Tracked in JVNAUTOSCI-2740.

Material changes

Add an operator-configured polling script, its operational prompt and a runbook. The controller binds the worker/delegator/organisation, uses canonical Von services, keeps a worktree per task, starts one fresh Codex execution per non-empty check, and reconciles task/message effects with local checkpoints. Empty checks make no model request. Actor-addressed invitations provide source context without exposing owner-private conversation concepts. A host file lock prevents overlapping polls.

This is the trusted SAIL local-operator pilot: no new public authentication endpoint, distributed lease service or Vontology prompt authority. Task scope is fixed by the installed config; retrieved content cannot choose another acting identity or report recipient.

Evidence

• 15 targeted pytest cases pass; Ruff, Black and diff checks pass.
• Actual DGX ChatGPT-subscription login and Terra sandbox shell execution verified.
• Live labelled fixture: source transcript denied before sharing, invitation accepted, question delivered, reply consumed, code written and PDM checks passed. An independent process verified all three expected outputs; the required prefix came only from the source conversation and suffix only from the reply.
• Result and task state read back canonically; final result visibly present in the public Von Messages interface.
• Empty poll and overlapping poll verified. A real cron invocation returned idle before the schedule was changed to hourly.

Ship boundary

• Minimum ship criteria: dependable assigned-task → authorised context → isolated local code/test result → Von message, including question/reply continuation and honest interruption recovery. These pass on the pilot DGX.
• Stop-ship conditions: wrong actor/database, inaccessible transcript exposure, duplicate concurrent execution, or unsuccessful runs being marked complete.
• Non-blocking observations: the DGX GitHub account currently has read access only. Publication tasks remain blocked with local work retained. General Messages replies spanning several task threads may need a task comment to disambiguate. Host/database outages are recorded in the operator log; there is no separate outage alert.
• Non-goals: unrestricted agents, general inbox-to-task conversion, multi-host claiming, automatic web deployment, or Jira migration. The wider setup issue remains open for the publishing credential decision.