agent-conveyor 0.1.19 → 0.1.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-conveyor",
-  "version": "0.1.19",
+  "version": "0.1.21",
   "description": "Local agent manager/worker conveyor control plane for Codex sessions.",
   "license": "MIT",
   "type": "module",
@@ -24,6 +24,7 @@
     "dist/",
     "scripts/capture-static-html-screenshot.mjs",
     "skills/**/*",
+    "plugin/**/*",
     "scripts/serve-landing-page.mjs",
     "README.md",
     "docs/landing-page.html",

package/plugin/agent-conveyor/plugin.json

@@ -0,0 +1,16 @@
+{
+  "name": "agent-conveyor",
+  "version": "0.1.21",
+  "description": "Codex operator skills for Agent Conveyor manager-worker setup.",
+  "skills": [
+    "conveyor-create-pair",
+    "conveyor-create-worker-set",
+    "conveyor-check-status",
+    "conveyor-whats-next-nudger"
+  ],
+  "requires": {
+    "npmPackage": "agent-conveyor",
+    "sessionKind": "codex_app",
+    "ledger": "per_project"
+  }
+}

package/plugin/agent-conveyor/skills/conveyor-check-status/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: conveyor-check-status
+description: Check Agent Conveyor manager/worker or worker-set status from the current project's per-project ledger.
+---
+
+# Conveyor Check Status
+
+Use this skill when the operator asks for the status of an Agent Conveyor pair
+or worker set from any project.
+
+## Rules
+
+- Operator-facing only.
+- Codex app native sessions only.
+- Use `.codex-workers/workerctl.db` under the current project unless the
+  operator explicitly provides another path.
+- Do not inspect product code or private content.
+- Treat ledger claims as claims unless backed by durable receipts.
+- Prefer compact status receipts with exact next action.
+
+## Commands
+
+For a known task:
+
+```bash
+TASK="example-task"
+conveyor app-loop-status "$TASK" --path "$PWD/.codex-workers/workerctl.db" --json
+conveyor app-autopilot status "$TASK" --path "$PWD/.codex-workers/workerctl.db" --json
+```
+
+For an unknown task, list candidate records first:
+
+```bash
+conveyor tasks --path "$PWD/.codex-workers/workerctl.db" --json
+```
+
+Report manager and worker thread ids/titles, stale roles, inbox backlog,
+heartbeat/autopilot state, dispatch health, and the exact next action.

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

@@ -0,0 +1,43 @@
+---
+name: conveyor-create-pair
+description: Create one visible Codex app manager and one visible Codex app worker for the current project using the globally installed Agent Conveyor CLI.
+---
+
+# Conveyor Create Pair
+
+Use this skill when the operator wants a Codex-app-only manager/worker pair
+from any target project. This skill is operator-facing. Do not use tmux in this
+tranche.
+
+## Rules
+
+- Treat the current working directory as the target project.
+- Use `.codex-workers/workerctl.db` under the target project unless the
+  operator explicitly gives another path.
+- Verify `conveyor` is available before setup:
+  `command -v conveyor && conveyor plugin-status --json`.
+- If `conveyor` is missing or the plugin is stale, tell the operator:
+  `npm install -g agent-conveyor && conveyor install-plugin`.
+- Use native Codex app thread tools when available to create visible manager
+  and worker threads.
+- Do not inspect product code as part of pair setup.
+- Generated manager and worker prompts must require visible session sections:
+  `CONVEYOR POLL`, `CONVEYOR RECEIVED`, `WORK`, `CONVEYOR SEND`, and
+  `DISPATCH`.
+
+## Default Ledger
+
+```bash
+mkdir -p .codex-workers
+LEDGER="$PWD/.codex-workers/workerctl.db"
+```
+
+## Operator Flow
+
+1. Clarify the bounded task name only if the operator has not provided one.
+2. Create one manager Codex app thread and one worker Codex app thread.
+3. Run `conveyor create-disposable-binding` with the created thread ids and:
+   `--path "$PWD/.codex-workers/workerctl.db" --json`.
+4. 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`.

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

@@ -0,0 +1,55 @@
+---
+name: conveyor-create-worker-set
+description: Create one visible Codex app manager and multiple visible Codex app workers for the current project using Agent Conveyor.
+---
+
+# Conveyor Create Worker Set
+
+Use this skill when the operator wants one Codex app manager supervising
+multiple Codex app workers. This skill creates the set and bindings; it does
+not run a campaign, Ralph loop, ship-it loop, or tmux workflow.
+
+## Rules
+
+- Operator-facing only.
+- Codex app native sessions only.
+- Use the current working directory as the target project.
+- Use `.codex-workers/workerctl.db` under the target project by default.
+- Create concise worker role names when the operator does not provide them.
+- Do not inspect product code during setup.
+
+## Default Ledger
+
+```bash
+mkdir -p .codex-workers
+LEDGER="$PWD/.codex-workers/workerctl.db"
+```
+
+## Operator Flow
+
+1. Determine worker count and role labels.
+2. Create one manager Codex app thread.
+3. Create one worker Codex app thread per role.
+4. For each worker role, create one Conveyor task and app-session binding:
+
+```bash
+TASK="example-worker-role-task"
+WORKER_NAME="example-worker-role"
+WORKER_THREAD_ID="created-worker-thread-id"
+WORKER_THREAD_TITLE="Created Worker Thread"
+MANAGER_NAME="example-manager"
+MANAGER_THREAD_ID="created-manager-thread-id"
+MANAGER_THREAD_TITLE="Created Manager Thread"
+conveyor create-disposable-binding "$TASK" \
+  --worker "$WORKER_NAME" \
+  --manager "$MANAGER_NAME" \
+  --worker-codex-app-thread-id "$WORKER_THREAD_ID" \
+  --worker-codex-app-thread-title "$WORKER_THREAD_TITLE" \
+  --manager-codex-app-thread-id "$MANAGER_THREAD_ID" \
+  --manager-codex-app-thread-title "$MANAGER_THREAD_TITLE" \
+  --path "$LEDGER" \
+  --json
+```
+
+5. Return a setup receipt listing every task, worker role, thread id/title,
+   manager thread id/title, ledger path, and status command.

package/plugin/agent-conveyor/skills/conveyor-whats-next-nudger/SKILL.md

@@ -0,0 +1,116 @@
+---
+name: conveyor-whats-next-nudger
+description: Run a bounded Agent Conveyor "what's next?" nudger loop for an existing Codex app manager/worker pair or worker set.
+---
+
+# Conveyor What's Next Nudger
+
+Use this skill when the operator wants an existing Agent Conveyor Codex app
+manager/worker pair or worker set to continue through a bounded number of
+manager-approved follow-up passes. This skill does not create sessions, publish,
+schedule, push, open PRs, merge, or archive workers unless the operator
+explicitly grants that separate authority.
+
+## Rules
+
+- Operator-facing only.
+- Codex app native sessions only.
+- Use `.codex-workers/workerctl.db` under the current project unless the
+  operator explicitly gives another path.
+- Require a bounded loop count before continuing; default to 1 extra pass if
+  the operator says "one more" and 2 passes if the operator gives no count.
+- Treat worker "done" and "what's next" suggestions as claims until the
+  manager verifies receipts.
+- Continue only when the manager records concrete evidence and the proposed
+  next slice is in scope, reversible, and consistent with current authority.
+- Keep manager closeout/control-plane proof out of worker acceptance criteria;
+  use it in the manager final report instead.
+- Do not inspect private content, publish externally, or perform repo shipping
+  actions unless the existing task policy explicitly permits the narrow action.
+- Keep visible Codex session sections for consumed work:
+  `CONVEYOR POLL`, `CONVEYOR RECEIVED`, `WORK`, `CONVEYOR SEND`, `DISPATCH`.
+
+## Default Ledger
+
+```bash
+mkdir -p .codex-workers
+LEDGER="$PWD/.codex-workers/workerctl.db"
+```
+
+## Operator Flow
+
+1. Identify the task or campaign. If the task is unknown, list candidates:
+
+```bash
+conveyor tasks --path "$LEDGER" --json
+```
+
+2. Inspect current status before nudging:
+
+```bash
+TASK="example-task"
+conveyor app-loop-status "$TASK" --path "$LEDGER" --json
+conveyor loop-status "$TASK" --path "$LEDGER" --json
+```
+
+3. Ask the manager, not the worker directly, to evaluate the completed pass and
+   choose one of:
+   - stop with verified evidence;
+   - request a narrow revision;
+   - ask the worker "what's next?" and continue for one bounded pass.
+
+Use the manager's inbox or visible app wake path for the existing setup. If the
+setup exposes `app-wakeup-plan` or `app-wakeup-dispatch`, prefer that prepared
+wake path over ad hoc direct prompts:
+
+```bash
+conveyor app-wakeup-plan "$TASK" --path "$LEDGER" --json
+```
+
+4. When the manager approves another pass, queue exactly one continuation or
+   worker nudge with a narrow instruction and an iteration budget. Prefer loop
+   continuation for Ralph-loop tasks:
+
+```bash
+RUN="loop-run-id-from-loop-status"
+NEXT_ITERATION="2"
+conveyor enqueue-continue-iteration "$TASK" \
+  --loop-run "$RUN" \
+  --requested-iteration "$NEXT_ITERATION" \
+  --message "Manager approved one more pass. Before acting, print visible CONVEYOR sections, summarize the verified prior evidence, propose the next narrow slice, do the work only if in scope, then notify the manager with receipts." \
+  --path "$LEDGER" \
+  --json
+conveyor dispatch --watch --watch-iterations 1 --interval 2 \
+  --dispatcher-id dispatch-local \
+  --path "$LEDGER" \
+  --json
+```
+
+If the task is not a Ralph loop, use the existing setup's generated
+`enqueue-nudge-worker` or manager-approved assignment command instead. Do not
+invent new shipping authority.
+
+5. After each worker pass, require all of:
+   - durable worker-to-manager notification receipt;
+   - one Dispatch receipt routing that notification;
+   - manager verification of artifacts, tests, screenshots, dashboard records,
+     or other task-specific evidence;
+   - explicit manager decision: continue, revise, stop, or block.
+
+6. Stop when the bounded pass count is exhausted, evidence is insufficient, the
+   next proposed slice is out of scope, or the manager recommends stopping.
+   Report a compact receipt with task, ledger, passes used, manager decision,
+   evidence checked, blockers, and the exact next action.
+
+## Final Receipt
+
+End with:
+
+- `task`
+- `ledger`
+- `passes_requested`
+- `passes_completed`
+- `manager_decision`
+- `evidence_checked`
+- `blockers`
+- `next_action`