/**
 * log10x_set_gitops_repo — write the gitops.repo field on an env entry
 * in ~/.log10x/envs.json so configure_engine can author cap-CSV PRs.
 *
 * configure_engine requires gitops_repo (owner/name) to know which
 * GitHub repo to open the PR against. The value can come from three
 * places:
 *   1. Passed directly as `gitops_repo` to configure_engine.
 *   2. The LOG10X_GH_REPO environment variable on the MCP server.
 *   3. The `gitops.repo` field in the env entry in ~/.log10x/envs.json.
 *
 * This tool handles option 3 — writing the field to envs.json. After
 * writing, the MCP server must restart to pick up the change (the file
 * is read once at boot by environments.ts). Use log10x_dev_restart to
 * trigger the restart, or restart the MCP server process manually.
 *
 * Why not log10x_configure_env?
 * configure_env runs a live-backend validation before writing — it
 * requires metricsBackend credentials and refuses to persist without
 * them. Setting gitops.repo is orthogonal to backend validation: the
 * user may already have a working env and just needs to add the gitops
 * field. Adding this as a separate targeted tool avoids forcing the user
 * to re-supply backend credentials for an unrelated field update.
 */
import { z } from 'zod';
import { type StructuredOutput } from '../lib/output-types.js';
export declare const setGitopsRepoSchema: {
    gitops_repo: z.ZodString;
    environment: z.ZodOptional<z.ZodString>;
    gitops_lookup_path: z.ZodOptional<z.ZodString>;
    confirm: z.ZodLiteral<"set-now">;
};
interface SetGitopsRepoArgs {
    gitops_repo: string;
    environment?: string;
    gitops_lookup_path?: string;
    confirm: 'set-now';
}
export declare function executeSetGitopsRepo(args: SetGitopsRepoArgs): Promise<string | StructuredOutput>;
export {};