mecatequi

Overview ¶

Command mecatequi is a single-shot, headless mecatl runner for CI / batch use: it runs ONE prompt against an in-process engine assembled by internal/app, drives the run to a terminal state, and emits three artifacts — a working-tree git diff, a machine-readable run-summary JSON, and an optional durable JSONL event log — then maps the terminal stop reason to a process exit code.

It is deliberately small. Unlike mecated (a network daemon) it owns no listeners, TLS, auth, rate-limiting, or telemetry pipeline; unlike mecatui it has no UI. It shares the SAME engine/service assembly (app.Build) so its behaviour matches the daemon's.

Pipeline 1 scope: the untrusted-prompt fence is cmd-side ONLY — mecatequi builds the fenced prompt string with the canonical governance.FenceUntrusted helper and passes it as ordinary prompt text. Nothing in engine/agent, internal/app, or internal/adapter/server is modified for it.

DEVIATION FROM mecated (on purpose): --headless defaults to true. A single-shot CI tool has no human to answer a permission ask, so a CHILD subagent/member/branch permission ask is auto-denied / routed to the opt-in --subagent-ask-reviewer rather than parked until run-end. See flags.headless.

HEADLESS × POSTURE (the main-agent ask): the child auto-deny above covers CHILD asks only. A MAIN-engine ask still has nobody to answer it. With the default posture (strict), the main engine asks on every mutate — so a strict + headless run that reaches a mutate is CANCELLED on that ask (run.Cancel, drain-to-close) and exits 1 with an actionable "no approver" message naming the fix. The intended CI posture is therefore --permission-mode auto (allow-all, child injection-defense ON) or yolo, where the main engine does not ask. --timeout is the orthogonal wall-clock backstop. See run()'s cancel-on-ask path and flags.posture.