/**
 * Dev Sync Command
 *
 * DEV/TESTING ONLY - Syncs locally built infrastructure to remote servers
 * for testing beta features of @factiii/stack itself before releasing.
 *
 * SETUP:
 * In repositories you are testing with, add this to package.json:
 *   "devDependencies": {
 *     "@factiii/stack": "link:../infrastructure"
 *   }
 *
 * Then use dev-sync to SSH and copy/paste the current infrastructure folder
 * to staging/prod servers. This simulates pulling from npm without having
 * the package published to npm.
 *
 * PRODUCTION:
 * When @factiii/stack is published to npm, this command will be disabled.
 * Production deployments will use npm to install @factiii/stack normally,
 * so no infrastructure folder will exist on servers - npm handles it.
 *
 * This is NOT for testing app code - only for developing the infrastructure package.
 * Uses direct SCP to transfer infrastructure to servers (no GitHub releases/workflows).
 */
import type { DevSyncOptions } from '../types/index.js';
/**
 * Dev sync command - sync locally built infrastructure to servers
 */
export declare function devSync(options?: DevSyncOptions): Promise<void>;
//# sourceMappingURL=dev-sync.d.ts.map