agent-conveyor 0.1.23 → 0.1.24

package/README.md

@@ -194,7 +194,12 @@ worker have visible app-thread send receipts, fresh app heartbeats, durable
 received/accepted acknowledgements, and an `app-smoke status` result with
 `real_work_allowed=true`. The plain CLI records and evaluates receipts; the
 Codex app skill/operator layer must perform live `send_message_to_thread`
-delivery and record `sent`, `blocked`, or skipped/advisory evidence.
+delivery and record `sent`, `blocked`, or skipped/advisory evidence. After
+required smoke passes, pair and worker-set skills start `app-autopilot` before
+real work so the just-proved sessions keep polling. A setup is autonomous only
+when the emitted heartbeat automation specs have been applied, or explicitly
+deferred as `manual-poll only`; smoke-passed by itself only proves connection
+plumbing at that moment.
 When the manager is itself running in the Codex app and
 thread tools are available, the skill should first call `create_thread` for a
 fresh same-project worker, name it with `set_thread_title`, pass the returned
@@ -560,7 +565,9 @@ stay out of receipts.
   same blockers without blocking, and skip mode records an explicit bypass. The
   CLI does not call Codex app thread tools; use the
   `conveyor-smoke-app-connections` plugin skill from a Codex app operator
-  session for live `send_message_to_thread` delivery.
+  session for live `send_message_to_thread` delivery. A smoke-passed operator
+  flow should immediately run `app-autopilot start` and handle the emitted
+  automation specs before sending real task prompts.
 - `app-worker-rotation-plan TASK --old-worker-thread-id ID [--require-handoff]
   [--reason TEXT] [--json]` — Prepare a Codex app fresh-worker rotation. The
   CLI verifies that `ID` exactly matches the active bound worker session before
@@ -845,7 +852,8 @@ stay out of receipts.
   either received, accepted, or blocked on it. `received` requires delivery;
   `accepted` and `blocked` require consumption. Use this after visible Codex app
   sessions print `CONVEYOR RECEIVED`; do not use direct app-thread text as the
-  durable receipt.
+  durable receipt. `--from-stdin` expects a JSON object, for example
+  `printf '%s\n' '{"summary":"accepted","evidence":["consumed notification"],"blockers":[]}' | conveyor inbox-ack ... --from-stdin`.
 
 ### Actuation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-conveyor",
-  "version": "0.1.23",
+  "version": "0.1.24",
   "description": "Local agent manager/worker conveyor control plane for Codex sessions.",
   "license": "MIT",
   "type": "module",

package/plugin/agent-conveyor/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-conveyor",
-  "version": "0.1.23",
+  "version": "0.1.24",
   "description": "Codex operator skills for Agent Conveyor manager-worker setup.",
   "skills": [
     "conveyor-app-wake-relay",

package/plugin/agent-conveyor/skills/conveyor-create-pair/SKILL.md

@@ -28,6 +28,14 @@ tranche.
   `conveyor-smoke-app-connections` skill in required mode. If smoke fails, do
   not send the real task prompt; return the exact smoke blockers and repair
   action.
+- After required smoke passes, start app-autopilot before sending real work:
+  `conveyor app-autopilot start "$TASK" --dispatcher-id dispatch-local --path "$LEDGER" --json`.
+  Apply the emitted Codex app automation specs when automation tools are
+  available. If they are unavailable, report the pair as `manual-poll only`
+  and include the manager/worker heartbeat prompts.
+- Do not report a created pair as autonomous unless required smoke passed,
+  `app-autopilot start` succeeded, and automation specs were either applied or
+  explicitly deferred by the operator.
 - Tell the operator to use `conveyor-app-wake-relay` for stale app threads;
   direct app-thread prompts are wake prompts only, not durable task truth.
 
@@ -45,7 +53,14 @@ LEDGER="$PWD/.codex-workers/workerctl.db"
 3. Run `conveyor create-disposable-binding` with the created thread ids and:
    `--path "$PWD/.codex-workers/workerctl.db" --json`.
 4. Run `conveyor-smoke-app-connections` for the created task. Required smoke
-   must pass before the real task starts.
-5. Return the manager thread title/id, worker thread title/id, ledger path,
+   must pass before the real task starts, and the smoke skill must start
+   app-autopilot before returning `real_work_allowed=true` as actionable.
+5. If automation tools are available, create the manager and worker heartbeat
+   automations from the `app-autopilot start` output. If automation tools are
+   not available, return the automation specs and mark the setup
+   `manual-poll only`.
+6. Return the manager thread title/id, worker thread title/id, ledger path,
    task name, and exact status command:
    `TASK="example-task"; conveyor app-loop-status "$TASK" --path "$PWD/.codex-workers/workerctl.db" --json`.
+   Include `app-autopilot status` and whether heartbeat automation specs were
+   applied, deferred, or blocked.

package/plugin/agent-conveyor/skills/conveyor-create-worker-set/SKILL.md

@@ -22,6 +22,14 @@ not run a campaign, Ralph loop, ship-it loop, or tmux workflow.
   set passes only when every required worker smoke passes. If any smoke fails,
   do not send real task prompts to any worker; return exact blockers and repair
   actions.
+- After each worker task's required smoke passes, start app-autopilot for that
+  task before sending real work:
+  `conveyor app-autopilot start "$TASK" --dispatcher-id dispatch-local --path "$LEDGER" --json`.
+  Apply emitted Codex app automation specs when automation tools are available,
+  or report that shard as `manual-poll only`.
+- Do not report a worker set as autonomous unless every worker task has passed
+  smoke, started app-autopilot, and had automation specs applied or explicitly
+  deferred by the operator.
 - Tell the operator to use `conveyor-app-wake-relay` for stale app threads;
   only Dispatch inboxes and Conveyor receipts are durable task truth.
 
@@ -60,6 +68,8 @@ conveyor create-disposable-binding "$TASK" \
 
 5. Run `conveyor-smoke-app-connections` once per worker task. Aggregate the
    resulting `app-smoke status` receipts. Required smoke must pass for every
-   worker before the real task starts.
+   worker before the real task starts. Each shard must also start
+   app-autopilot before it is treated as autonomous.
 6. Return a setup receipt listing every task, worker role, thread id/title,
-   manager thread id/title, ledger path, smoke id/status, and status command.
+   manager thread id/title, ledger path, smoke id/status, autopilot status,
+   automation spec state, and status command.

package/plugin/agent-conveyor/skills/conveyor-smoke-app-connections/SKILL.md

@@ -35,6 +35,9 @@ only.
   `app-smoke status`.
 - If `conveyor app-smoke status` reports `real_work_allowed=false`, do not send
   the real task prompt.
+- Prompts that ask a manager or worker to use `--from-stdin` must include an
+  explicit JSON stdin example. Do not rely on the target session to infer the
+  payload format.
 
 ## Default Ledger
 
@@ -109,9 +112,12 @@ Then poll for the worker smoke report:
 conveyor manager-inbox '<TASK>' --consume-next --wait --timeout 60 --path '<LEDGER>' --json
 
 If you consume a manager inbox item for smoke <NONCE>, record:
-conveyor inbox-ack '<TASK>' --notification-id '<consumed.id>' --role manager --status received --from-stdin --path '<LEDGER>' --json
-conveyor inbox-ack '<TASK>' --notification-id '<consumed.id>' --role manager --status accepted --from-stdin --path '<LEDGER>' --json
-conveyor app-smoke record '<TASK>' --smoke-id '<SMOKE_ID>' --nonce '<NONCE>' --role manager --status accepted --thread-id '<MANAGER_THREAD_ID>' --notification-id '<consumed.id>' --from-stdin --path '<LEDGER>' --json
+printf '%s\n' '{"summary":"manager received worker smoke report","evidence":["consumed manager inbox item for smoke <NONCE>"],"blockers":[]}' \
+  | conveyor inbox-ack '<TASK>' --notification-id '<consumed.id>' --role manager --status received --from-stdin --path '<LEDGER>' --json
+printf '%s\n' '{"summary":"manager accepted worker smoke report","evidence":["worker report nonce matched <NONCE>"],"blockers":[]}' \
+  | conveyor inbox-ack '<TASK>' --notification-id '<consumed.id>' --role manager --status accepted --from-stdin --path '<LEDGER>' --json
+printf '%s\n' '{"summary":"manager accepted app smoke","evidence":["fresh manager heartbeat","worker smoke report consumed","worker nonce matched <NONCE>"],"blockers":[]}' \
+  | conveyor app-smoke record '<TASK>' --smoke-id '<SMOKE_ID>' --nonce '<NONCE>' --role manager --status accepted --thread-id '<MANAGER_THREAD_ID>' --notification-id '<consumed.id>' --from-stdin --path '<LEDGER>' --json
 
 If blocked, record app-smoke blocked with the exact blocker.
 Stop after the smoke receipt. Do not start real work.
@@ -152,12 +158,16 @@ conveyor app-heartbeat '<TASK>' --role worker --path '<LEDGER>' --json
 conveyor worker-inbox '<TASK>' --consume-next --wait --timeout 60 --path '<LEDGER>' --json
 
 For the consumed smoke item, record:
-conveyor inbox-ack '<TASK>' --notification-id '<consumed.id>' --role worker --status received --from-stdin --path '<LEDGER>' --json
-conveyor app-smoke record '<TASK>' --smoke-id '<SMOKE_ID>' --nonce '<NONCE>' --role worker --status received --thread-id '<WORKER_THREAD_ID>' --notification-id '<consumed.id>' --from-stdin --path '<LEDGER>' --json
+printf '%s\n' '{"summary":"worker received smoke item","evidence":["consumed worker inbox item for smoke <NONCE>"],"blockers":[]}' \
+  | conveyor inbox-ack '<TASK>' --notification-id '<consumed.id>' --role worker --status received --from-stdin --path '<LEDGER>' --json
+printf '%s\n' '{"summary":"worker received app smoke","evidence":["fresh worker heartbeat","worker inbox item consumed","nonce matched <NONCE>"],"blockers":[]}' \
+  | conveyor app-smoke record '<TASK>' --smoke-id '<SMOKE_ID>' --nonce '<NONCE>' --role worker --status received --thread-id '<WORKER_THREAD_ID>' --notification-id '<consumed.id>' --from-stdin --path '<LEDGER>' --json
 
 Then record accepted:
-conveyor inbox-ack '<TASK>' --notification-id '<consumed.id>' --role worker --status accepted --from-stdin --path '<LEDGER>' --json
-conveyor app-smoke record '<TASK>' --smoke-id '<SMOKE_ID>' --nonce '<NONCE>' --role worker --status accepted --thread-id '<WORKER_THREAD_ID>' --notification-id '<consumed.id>' --from-stdin --path '<LEDGER>' --json
+printf '%s\n' '{"summary":"worker accepted smoke item","evidence":["smoke instructions understood","no product work started"],"blockers":[]}' \
+  | conveyor inbox-ack '<TASK>' --notification-id '<consumed.id>' --role worker --status accepted --from-stdin --path '<LEDGER>' --json
+printf '%s\n' '{"summary":"worker accepted app smoke","evidence":["smoke item accepted","nonce matched <NONCE>"],"blockers":[]}' \
+  | conveyor app-smoke record '<TASK>' --smoke-id '<SMOKE_ID>' --nonce '<NONCE>' --role worker --status accepted --thread-id '<WORKER_THREAD_ID>' --notification-id '<consumed.id>' --from-stdin --path '<LEDGER>' --json
 
 Finally notify the manager:
 conveyor enqueue-notify-manager '<TASK>' --message 'CONVEYOR SMOKE <NONCE>: worker accepted smoke.' --correlation-id '<SMOKE_ID>-worker-report' --path '<LEDGER>' --json
@@ -189,6 +199,33 @@ conveyor app-smoke status "$TASK" --smoke-id "$SMOKE_ID" --path "$LEDGER" --json
 If `real_work_allowed=true`, the setup may send the real work prompt. If
 `real_work_allowed=false`, report exact blockers and stop.
 
+8. Start app-autopilot immediately after required smoke passes and before
+   sending real work:
+
+```bash
+conveyor app-autopilot start "$TASK" \
+  --dispatcher-id dispatch-local \
+  --path "$LEDGER" \
+  --json
+```
+
+The operator or manager must apply the emitted Codex app automation specs with
+Codex app automation tools. If automation tools are unavailable, report the
+task as `manual-poll only` and include the manager and worker heartbeat prompts
+from the autopilot output. Do not report the pair as autonomous until autopilot
+is started and its automation specs are either applied or explicitly deferred.
+
+9. After autopilot start, run:
+
+```bash
+conveyor app-autopilot status "$TASK" --path "$LEDGER" --json
+conveyor app-loop-status "$TASK" --path "$LEDGER" --json
+```
+
+If `app-loop-status` reports stale manager or worker immediately after
+autopilot setup, wake the stale role or report the exact blocker before sending
+real work.
+
 ## Worker Set Flow
 
 For worker sets, run the pair flow once per bound worker task. Treat each worker
@@ -214,7 +251,10 @@ End with:
 - `blocked_roles`
 - `status_after`
 - `real_work_allowed`
+- `autopilot_status`
+- `automation_specs_applied_or_deferred`
 - `next_action`
 
 If any role is blocked, name the exact blocker and do not report the smoke as
-passed.
+passed. If smoke passed but autopilot was not started or automation specs were
+not applied/deferred, report the pair as smoke-passed but not autonomous.