/**
 * daemon/issue-cli.ts — `aibroker issue`, the same verbs without an MCP reload.
 *
 * The MCP tool and this are the same handler; only the way in differs. That
 * matters for one reason: a new MCP tool does not appear in a session that is
 * already running, and making it appear needs a person at the keyboard. On the
 * afternoon this was written a session had a finding ready to post, the tool
 * had been published, and it could do nothing for want of a `/mcp` — while a
 * shell was sitting right there. A capability that waits on a human to become
 * reachable is not reachable.
 *
 * It goes through the daemon rather than calling the forge here, and that is
 * not ceremony. The permission check and the record of what was just written
 * both live in the daemon's memory; a CLI that talked to the forge directly
 * would bypass the first and be invisible to the second, so a session's own
 * comment would come back to it as news. The identity that decides permission
 * travels the same way it always does — the client reads `ITERM_SESSION_ID`
 * from the environment it was launched in, so running this in a pane is asking
 * as that pane, and there is no flag to claim otherwise.
 */
export declare function runIssue(args: string[]): Promise<void>;
//# sourceMappingURL=issue-cli.d.ts.map