/**
 * Headless, machine-readable `monomind init --json` (issue #358, capability
 * `init-json`). Coder workspaces (mono-agent) call this to turn an arbitrary
 * folder into a ready-to-use monomind/Claude Code workspace without a human
 * at the terminal: one JSON document on stdout, human output suppressed.
 *
 * Contract: doc/agent-exec-protocol.md §11.
 *
 * @module @monomind/cli/commands/init-workspace
 */
import type { CommandContext, CommandResult } from '../types.js';
/**
 * The directory name the Claude Code CLI/Agent SDK uses under
 * `~/.claude/projects/` for a given absolute project path: every path
 * separator becomes `-` (e.g. `/home/user/app` -> `-home-user-app`).
 * Verified empirically (see doc/agent-exec-protocol.md §11) — the CLI itself
 * is a closed-source binary, so this is an observed convention, not a
 * documented API; it covers POSIX paths, which is monomind's primary target.
 */
export declare function claudeProjectSlug(targetDir: string): string;
/** Absolute path to this project's Claude Code session-history directory. */
export declare function claudeProjectDir(targetDir: string, home?: string): string;
/**
 * `monomind init --json` (and `--project`/`--if-missing`/`--no-graph`/
 * `--register-claude-project`, all of which also work without `--json`).
 * No spinner, no boxes, no prompts — a single JSON document on stdout.
 */
export declare function runInitWorkspace(ctx: CommandContext, cwd: string): Promise<CommandResult>;
//# sourceMappingURL=init-workspace.d.ts.map