/**
 * 024 — `agentsmarket pipeline deprecate` / `un-deprecate`.
 *
 * ## Why this is a separate command and not `pipeline publish --deprecate`
 *
 * The flag was tried first and is wrong. `pipeline publish` decides for itself
 * whether the run produces a NEW row or a no-op, and the deprecation has to
 * land on the row the author already published. Against the flag:
 *
 *   - same version, same hash → server answers ALREADY_PUBLISHED and creates
 *     nothing. A deprecation carried in the POST body is silently dropped, and
 *     the author is told it applied.
 *   - same version, changed content → 409, then an automatic version bump. The
 *     NEW row is created and deprecated while the OLD one — the one people are
 *     actually buying — stays live and listed. The author asked to retire a
 *     pipeline and instead published a retired copy of it next to the original.
 *
 * Both outcomes are silent successes, which is the failure mode this project
 * keeps paying for elsewhere. So deprecation is its own verb with its own
 * resolution, and it is idempotent: running it twice deprecates one row.
 *
 * ## Semantics it relies on (server side, migration 024)
 *
 *   deprecated  → hidden from GET /v1/pipelines by default, 410 DEPRECATED on
 *                 a new install (`?force=true` escapes it), still invokable by
 *                 existing buyers, who additionally get the reason back.
 *   NOT the same as is_private — private hides the bundle from people who
 *   already paid for it. Deprecating never takes a bundle away.
 */
export declare function pipelineDeprecateCommand(slug: string, message: string | undefined): Promise<void>;
export declare function pipelineUnDeprecateCommand(slug: string): Promise<void>;