@withpica/mcp-server/dist/tools/my-reported-issues.d.ts

MCP Server for withPICA — enables AI assistants to interact with your withPICA music catalog

/**
 * My-Reported-Issues Tool — ADR-196 Phase 4a.
 *
 * Closes the agent-to-agent loop on the resolution side. An agent that
 * fired `pica_report_issue` previously can poll this tool to see if
 * operators have resolved the issue, what the resolution_note says, and
 * whether other orgs have been affected since.
 *
 * Org-scoped — only returns issues whose `impacted_org_ids` includes the
 * authenticated org. Customers cannot see the cross-org queue (that lives
 * on the operator-only `team_platform_inspect { sections: ['issues'] }`
 * surface).
 *
 * The same closure also fires opportunistically via the
 * `discovery_events` row written by `opsIssuesService.updateStatus`
 * when an issue resolves — `pica_dashboard_briefing` and
 * `pica_dashboard_attention` will surface it on the agent's next call.
 * This tool is the explicit-poll counterpart for "the user just asked me
 * about that issue I reported last week."
 */
import { PicaClient } from "@withpica/mcp-sdk";
import { ToolDefinition, ToolExecutor } from "./index.js";
export declare class MyReportedIssuesTools {
    private pica;
    constructor(pica: PicaClient);
    getTools(): Array<{
        definition: ToolDefinition;
        executor: ToolExecutor;
    }>;
    private listMine;
}
//# sourceMappingURL=my-reported-issues.d.ts.map