/**
 * Emission of the publish result document.
 *
 * The `publish-result-v3` contract, its counts, and its execution status are
 * owned by `@agentxm/workspace/publishing`; this module renders that outcome —
 * machine document or human view — and summarizes it for telemetry.
 */
import * as Effect from "effect/Effect";
import { type PublishResult } from "@agentxm/workspace/publishing";
import { type SuggestedAction } from "@agentxm/registry-protocol/unstable/suggested-action";
import { Screen } from "../../screen/index.js";
import { Verbosity } from "../../cli-flags/index.js";
import { type CommandOutcomeSummary } from "../../cli-runtime/index.js";
/**
 * Emit the publish result: the machine document, or the human view.
 *
 * @returns whether the outcome reached the person or program running the
 * command, so the caller ends with its exit code instead of a second report
 */
export declare const emitPublishResult: (result: PublishResult, options: {
    readonly exitCode: number;
    readonly elapsedMs?: number;
    readonly suggestions?: ReadonlyArray<SuggestedAction>;
    readonly withoutSuggestions?: boolean;
}) => Effect.Effect<boolean, never, Verbosity | Screen>;
/**
 * Convert a PublishResult to a CommandOutcomeSummary for telemetry.
 *
 * Outcome follows the same convention as executed plans: a run that touched
 * nothing is `no-op`, and any applied or failed work is `applied` even when
 * every item failed, so partial failures stay in one bucket.
 *
 * Unconfirmed work is not "touched nothing": an indeterminate upload joins the
 * failed bucket because its settlement is unproven and needs attention, and an
 * item that never left the process joins the blocked bucket. Either keeps the
 * run out of `no-op`. An interrupted run still reports `interrupted`.
 */
export declare const publishResultToSummary: (result: PublishResult) => CommandOutcomeSummary;
//# sourceMappingURL=result.d.ts.map