/**
 * olam memory start — bring up the agent-memory service.
 *
 * Phase B substrate: delegates to `MemoryServiceContainerController` so the
 * service runs as a Docker container managed by the same lifecycle as
 * kg-service / auth-service / mcp-auth-service. The legacy Phase A host-process
 * model (spawning the `agentmemory` npm bin + writing `~/.olam/memory.pid`)
 * is retired; legacy on-disk state is migrated away on first new-substrate
 * invocation via `migrateFromHostProcess()`.
 *
 * Operator-facing surface unchanged:
 *   - `olam memory start` still produces a running service on :3111.
 *   - `bootstrap.ts:429` `runOlam(['memory', 'start'])` call site untouched.
 *   - `--skip-memory` / `OLAM_BOOTSTRAP_SKIP_MEMORY=1` still skip.
 *
 * Phase C deletes the host-process helpers from `_paths.ts` + drops the
 * `@agentmemory/agentmemory` PUBLISH_DEPS entry. Until then, the host-process
 * code paths are unreachable but present (clean-revert insurance).
 *
 * Plan reference: docs/plans/memory-service-as-docker-peripheral/phase-b-tasks.md B1
 */
import type { Command } from 'commander';
export declare function runMemoryStart(): Promise<number>;
export declare function registerMemoryStart(cmd: Command): void;
//# sourceMappingURL=start.d.ts.map