grok-implementlisted

# Implement via `grok` (Grok Build) A paid-pool write leg, tier peer of `codex-implement` and `agy-implement`. Its output is **Grok-family** work: the review gate for anything it writes must come from a different model family — that is the suite's headline cross-family rule, and it is the main reason to spend this pool on implementation at all (it frees the GPT/Gemini/Claude legs to review). ## Before the first run of a session Read **[`references/grok-runtime.md`](../grok-adversarial-review/references/grok-runtime.md)**. The items that bite the write role hardest: the machine's `config.toml` may carry a global always-approve default (state the posture explicitly, never inherit it), the sandbox is kernel-gated and silently unenforced on old kernels, and the family has **zero calibration-journal rows** — first dispatches are calibration runs, verified accordingly. ## Worktree, snapshot, then dispatch Every write leg gets its own worktree, without exception — same rule, same helpers, same reasons as the other families: ```bash RUN_DIR=$(mktemp -d "${TMPDIR:-/tmp}/grok-implement.XXXXXX") # FIRST — the snapshot lands here BASE=$(git rev-parse HEAD) # from a clean checkout, recorded before anything WORKTREE=../<repo>-grok-<short-task-slug> git worktree add -b grok/<short-task-slug> "$WORKTREE" "$BASE" # The helper lives in the SUITE's tree, cwd is the TARGET repo — a bare # `scripts/…` resolves against the target and exits 127. DEV_LEAD=${DEV_LEAD_ROOT:-$(ls -d "$HOME"/.