/**
 * G2.2 — `agentsmarket pipeline bundle <dir> [--output <path>] [--json]`
 *
 * Bundle a local pipeline directory into a marketplace-ready zip:
 *
 *   - pipeline.yaml   (required; validated against schema)
 *   - README.md       (optional; max 8000 chars — warn if exceeded)
 *   - metadata.json   (auto-derived: name, version, author, sha256,
 *                      spec_hash, created_at, bundle format info)
 *
 * Output: `<slug>-<version>.zip` (default — cwd) or `--output <path>`
 * (custom). SHA-256 of the zip is printed to stdout; `--json` switches
 * to a single-line JSON envelope:
 *
 *   { "path": "/abs/.../style-review-1.0.0.zip", "sha256": "...", "size": 12345 }
 *
 * Idempotent: overwrites the existing zip if present (no prompt).
 *
 * Why this exists: `publish` uploads the spec to the server, but
 * offline / air-gapped environments + the `github-workflows` repo's
 * `pipelines/<slug>/` canonical home both need a local way to package
 * pipelines without going through the server.
 */
import { validatePipelineSpec } from '../../lib/pipeline-spec.js';
export interface BundleDeps {
    validatePipelineSpec?: typeof validatePipelineSpec;
    now?: () => Date;
    stderr?: (line: string) => void;
    stdout?: (line: string) => void;
    exit?: (code: number) => never;
}
export interface BundleResult {
    path: string;
    sha256: string;
    size: number;
    slug: string;
    version: string;
    has_readme: boolean;
    readme_truncated: boolean;
}
export declare function pipelineBundleCommand(dirArg: string, flags: {
    output?: string;
    json?: boolean;
}, depsOverrides?: BundleDeps): Promise<BundleResult | void>;