/**
 * Command dispatch for the JAM CLI, separated from the bin so other entry
 * points (notably @jam-mcp/bootstrap) can forward to exactly these commands
 * instead of reimplementing them.
 */
export declare const USAGE = "jam - Jira Agent MCP\n\nLifecycle (the same words ASC uses)\n  jam setup [--project KEY] [--shared] [--migrate] [--non-interactive]\n                          Wire up this project and verify it. Binds it to you\n                          alone, writing nothing to the repository; --shared\n                          adopts JAM for the team (project.yaml, .mcp.json)\n  jam status              What is configured, what works, what is blocked\n  jam update              Move this machine's registration to the published release\n  jam refresh             Keep the version; re-register what this build owns\n  jam uninstall           Remove JAM's registrations; your bindings and credentials stay\n  jam runtime             Show which JAM build this machine runs\n  jam runtime use package | development <path>\n                          Change it (writes ~/.jam/config.yaml only, never a project)\n\nJira\n  jam jira search <jql> [--scope preview|complete]\n  jam jira context <KEY> [KEY...]\n  jam jira full <KEY> [KEY...]\n                          Read Jira from the shell - the same reads the MCP\n                          tools do, for a session that cannot see them yet\n  jam jira write-plan --operation <op> [--key KEY] --input '<json>'\n  jam jira write-apply <planId>\n                          Write the same way the tools do: plan first, then\n                          apply that plan by id. Nothing is written until\n                          write-apply, and it takes no payload of its own\n\nAuthentication\n  jam auth status [--json]  Whether Jira credentials are configured (never their value)\n  jam auth login            Store them in this user's OS secret store\n  jam auth logout           Remove them again\n\nFor coding agents and scripts (stdout is JSON only, never prompts):\n  jam setup --agent       One shot: detect, plan, apply what is safe, verify\n  jam setup plan --json   Report what setup would change, changing nothing\n  jam setup apply --non-interactive --json\n                          Execute the plan\n  jam status --json       Health check as structured output\n  jam update check|plan [--json]\n  jam refresh check|plan [--json]\n  jam uninstall plan [--json]\n\nHost runtime\n  jam serve               Run the MCP server over stdio - this is what Claude\n                          Code and Codex launch. Not a command a person types.\n\nEnvironment:\n  JIRA_BASE_URL     https://your-site.atlassian.net\n  JIRA_EMAIL        Atlassian account email\n  JIRA_API_TOKEN    Atlassian API token\n  JAM_PROJECT_KEY   Jira project key, used by `jam setup`/`jam serve` when no\n                     .jira-agent/project.yaml exists yet\n\nCredentials and JAM_PROJECT_KEY are read from the current shell's environment\nfirst, then (on Windows) from the User environment - so a value set with\n`setx` works without opening a new terminal.\n";
export declare function runJamCommand(argv: string[]): Promise<number>;