/**
 *
 * Adds:
 *   peaks bee export --bee <id> --out <path.tar.gz>
 *   peaks bee import --in <path.tar.gz> [--as <bee-name>]
 *
 * The bee-side counterparts of the loop-side `peaks loop export /
 * import`. Same hard rules:
 *
 *   - source `shareable=false` blocks export at the CLI layer.
 *   - bundle lands as `candidate`; promotion to `stable` requires
 *     an `evolution_evaluation` row with an independent
 *     `evaluator_id` (see `peaks evolution evaluate`).
 *
 * The bee bundle captures the bee's inline manifest/segment/file/change
 * rows so the receiver can re-materialize the full bee + any
 * loop↔bee relations that referenced it + any evidence briefs that
 * touched it.
 *
 * The `peaks skill sediment export / import` alias lives in
 */
import type { Command } from 'commander';
import { type ProgramIO } from '../cli-helpers.js';
export declare function registerBeeCommands(program: Command, io: ProgramIO): void;