/**
 * What the `agency workflow` commands print. Every piece of text that came
 * from a file goes through `stripControlCharacters`, so a docstring or a
 * workflow description cannot move the cursor or recolor the terminal.
 *
 * Each formatter takes the color function as its last argument. The default,
 * `ttyColor`, colors on a terminal and prints plain text when the output is
 * piped. Text that goes into `--json` output passes `plainColor`. Text is
 * cleaned before it is colored, since cleaning would strip the color codes.
 */
import type { CatalogEntry } from "../../stdlib/workflow/catalog.js";
import type { StepEffects } from "../../stdlib/workflow/effects.js";
import type { Problem } from "../../stdlib/workflow/types.js";
import { type ColorFunction } from "../../utils/termcolors.js";
/** A heading per module, then each tool's signature, `(handoff)` for an
 *  agent, its description's first paragraph, and what it raises. */
export declare function formatCatalog(entries: CatalogEntry[], paint?: ColorFunction): string;
/** `<label> has <n> problem(s):`, then one line each. */
export declare function formatProblems(label: string, problems: Problem[], paint?: ColorFunction): string;
/** One step that raises an effect: the step's id and the tool it calls. */
export type RaisingStep = {
    step: string;
    tool: string;
};
/** One effect and the steps that raise it. */
export type EffectSteps = {
    effect: string;
    steps: RaisingStep[];
};
/** Each effect the steps raise, in the order it is first raised, with the
 *  steps that raise it. */
export declare function effectSteps(steps: StepEffects[]): EffectSteps[];
/** A table with a heading row, then one row for each step that raises each
 *  effect:
 *
 *    Effect         Step      Tool
 *    std::weather   weather   weather
 *
 *  The widths are worked out on the plain text, before anything is colored. */
export declare function effectTable(list: EffectSteps[], paint?: ColorFunction): string[];
/** `<label>: no problems`, then the warnings and what the workflow can
 *  raise, each under its own heading with a blank line before it. A warning
 *  is printed like a problem, with its step in front but not its field: the
 *  field of an untyped-return warning is always `tool`, which the message
 *  already names. */
export declare function formatChecked(label: string, warnings: Problem[], steps: StepEffects[], paint?: ColorFunction): string;
/** The part of a saved workflow `list` prints. */
export type ListedWorkflow = {
    name: string;
    workflow: {
        inputs: string;
        description: string;
    };
};
/**
 * A workflow's inputs type written as a parameter list, so a saved workflow
 * reads like a function call: `{ zip: string; units: string }` becomes
 * `zip: string, units: string`. The printer puts each top-level property on
 * its own line ending in `;`, and a nested object type on one line, so the
 * line ends are where the commas go. Text that does not parse is returned
 * as it is.
 */
export declare function inputsAsParams(inputs: string): string;
/** Each workflow as a call, `name(input: type, ...)`, then its description,
 *  with a blank line between workflows. */
export declare function formatList(dir: string, entries: ListedWorkflow[], paint?: ColorFunction): string;
/** A run's value: a string as itself, anything else as indented JSON. */
export declare function formatRunValue(value: unknown): string;
/** The effects a person's policy does not cover, before the run asks. */
export declare function formatUncovered(list: EffectSteps[], paint?: ColorFunction): string;
/** What `run` says when it has no terminal to ask in. */
export declare const NO_TERMINAL = "Run this in a terminal to approve them, or cover them with --policy, --approve, or --reject.";