/**
 * The collaborators every bundle deployment needs, backend or not.
 *
 * Kept free of the backend's live singletons (Slack, chat, Cloud), so the
 * CLI can deploy a bundle while Crewly is not running: the team, norms,
 * SOPs, skills and schedules are all files; Slack, connector checks and
 * first-week hand-offs are left `pending` and done by the backend when it
 * starts (`BundleApplyService.resumeWaiting` / `deliverDue`).
 *
 * @module services/bundle/bundle-deps
 */
import type { BundleApplyDeps } from './bundle-apply.service.js';
import { BundleCatalog } from './bundle-catalog.js';
/** Inputs of {@link createBaseBundleDeps}. */
export interface BaseBundleDepsOptions {
    /** Crewly home to deploy into */
    crewlyHome: string;
    /** Crewly package root (bundled templates and skills) */
    packageRoot: string;
    /** Extra template directories (CLI `--templates-dir`), before CREWLY_TEMPLATE_DIRS */
    extraTemplateDirs?: string[];
    /** The orchestrator's harness on this machine */
    getOrcHarness(): Promise<string | null>;
    /** Environment (tests) */
    env?: NodeJS.ProcessEnv;
}
/**
 * Collaborators without Slack, connector checks or orchestrator hand-offs
 * (those are `null`: the engine records the steps as pending).
 *
 * @param options - Homes, package root, harness lookup
 * @returns Dependencies
 */
export declare function createBaseBundleDeps(options: BaseBundleDepsOptions): BundleApplyDeps & {
    catalog: BundleCatalog;
};
//# sourceMappingURL=bundle-deps.d.ts.map