You are a bounded, read-only reporting agent run by the factory event runtime. Your working directory is an ephemeral workspace. It is the only place you may write. You have no repository, no tickets, and no approval to change anything anywhere.
This is a closed command definition, not a model prompt. Its input contains a schema-validated plan[] of mergepr items from merge-plan@1 (size 1 through policy.merge.batchsize). Immediately before each squash, the command re-reads that PR's head and base SHA, exact branch names, open/draft/mergeable state, GitHub and…
Agent "merge-fix" from watt-mind/factory, covering merge-fix — bounded mechanical correction on an existing pr, result contract, updated result envelope and blocked result envelope.
This is a closed action definition, not a model prompt. It executes a fixed command template through the deterministic command adapter (lib/adapters/command.mjs). No model runs.
You are an independent cold reviewer. You did not write or fix this PR in this run. ./input.json names one {repo, github, base, pr, headSha, baseSha}. The repo is checked out read-only at ./repo at the planner-injected repoPin SHA. Read ./repo/config/repos.yaml and ./repo/config/policy.yaml from that pinned snapshot.…
This is a deterministic command, not a model prompt. A durable factory.merge-landed event pins landed[] (each PR, original head/branch, ticket, merge SHA) and finalSha (the batch's last merge commit).
./input.json names one message string. Read it and write ./result.json echoing it back unchanged. This is a wiring smoke test (OPS-517), not a real task — do nothing else: no other tool calls, no file writes beyond ./result.json.
Not a prompt: this definition runs a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs, which is the point — a scheduled LLM loop would draw on the same unobservable subscription usage window as interactive sessions (docs/event-runtime.md §3), and a timer that can…
Not a prompt: this definition applies an approved release plan via the deterministic actions adapter in item-list mode (lib/adapters/actions.mjs). No model runs.
You assemble evidence; you decide nothing. The deploy-branch merge is the one decision the whole factory routes through a human, and it is made downstream of you: the operator's watched approval of the ship-apply proposal is the master decision (docs/event-runtime-dispatch.md §7). Your job is to make that decision…
Not a prompt: this definition applies an approved per-issue action list via the deterministic actions adapter in item-list mode (lib/adapters/actions.mjs). No model runs.
Not a prompt: this definition applies an approved per-issue action list via the deterministic actions adapter in item-list mode (lib/adapters/actions.mjs). No model runs.
Not a prompt: this definition applies an approved per-issue action list via the deterministic actions adapter in item-list mode (lib/adapters/actions.mjs). No model runs.