/**
 * The "you are on a stale main" text. ONE consumer today:
 *
 *   - read-stale-guard        blocks the Read tool     → {@link StaleMainMessage.forReads}
 *
 * It had a second consumer, `forBash`, for the days when stale-main-bash-guard blocked CONTENT reads
 * on a stale main. That guard judges the SAME state again today (rows 6/7 — `main`, known behind), but
 * its verdict shape is different: default-deny plus the row 4 skip list rather than a per-file call,
 * and its cure is the branch form alone because a Bash session cannot be cured by staying put. So it
 * carries its own message and this variant was deleted rather than left as a second spelling.
 *
 * One source of truth on purpose (same reason as MergedBranchMessage): the cure is an instruction the
 * AI follows literally, so two drifting copies mean two behaviours for one repo state.
 *
 * Cure 1 is `--ff-only` deliberately. A plain `git pull` on a stale main can start a MERGE, which is
 * the one thing redirect-how-to-merge-main exists to keep an AI away from; `--ff-only` either
 * fast-forwards or fails loudly without touching anything. It used to be the ONLY cure printed, on the
 * strength of "the block only fires when the tree is clean and behind" — which stopped being true when
 * the dirty valve was deleted, and was the reason that valve existed. Cure 2 (`git checkout -b`) is
 * what makes the message correct on a dirty tree, so both are printed and each is labelled.
 */
export declare class StaleMainMessage {
    private readonly treeRoot;
    /**
     * `treeRoot` is the tree the guard JUDGED (which is NOT the shell's cwd when the command carried
     * a leading `cd`). Pass it and the cure is rendered as `cd <treeRoot> && git pull …`, naming the
     * directory outright.
     *
     * WHY that matters here specifically: in the field this guard told an agent working in a worktree
     * to `git pull` — which, run from wherever the next tool call happened to start, meant pulling the
     * PRIMARY CLONE, a tree that agent had been explicitly instructed not to touch. A remedy must
     * never mutate a tree other than the one the command targeted, and naming it is how you ensure it.
     */
    constructor(treeRoot?: string);
    /**
     * The diagnosis + BOTH cures.
     *
     * Two cures rather than one, and that is what let the dirty valve be deleted. The guard used to
     * fail open on a dirty tree because the only cure it printed was `git pull --ff-only`, which is
     * not a clean fast-forward when there are local modifications — so the block was suppressed to
     * avoid prescribing something that could not run.
     *
     * The row always had a second cure (`git checkout -b <new> origin/main`), and that one works
     * DIRTY: it carries uncommitted changes onto the new branch and lands you on current code, which
     * is the whole objective. Printing it unconditionally means the message is correct in both tree
     * states, so nothing has to detect dirtiness — no extra `git status --porcelain` on the block
     * path, and no state in which the printed cure is unrunnable.
     */
    private common;
    forReads(behindCount: string): string;
}