@productlobster/plob 0.1.6 → 0.1.8

package/dist/index.d.ts

@@ -33,6 +33,7 @@ declare const EXIT_CODES: {
     readonly versionRevoked: 17;
     readonly serviceUnavailable: 18;
     readonly allotmentExhausted: 19;
+    readonly notAvailable: 20;
     readonly network: 70;
 };
 type CliExitCode = (typeof EXIT_CODES)[keyof typeof EXIT_CODES];
@@ -86,13 +87,31 @@ interface CommandRunnerDeps {
     mcpClientFactory: McpClientFactory;
     openUrl: (url: string) => Promise<void> | void;
 }
+/**
+ * One more tool call on the command's open connection, with the first call's
+ * parsing and failure handling: the success envelope is unwrapped and parsed
+ * with `outputSchema`, and a failed call throws a {@link CliOperationalError}
+ * carrying the mapped code (`not_available` when the server does not offer the
+ * tool), which the runner renders like a failed first call.
+ */
+type FollowUpToolCall = <TResponse>(toolName: string, toolArguments: Record<string, unknown>, outputSchema: {
+    parse(input: unknown): TResponse;
+}) => Promise<TResponse>;
 interface CommandPostProcessContext {
     bearerToken: string;
+    /** A follow-up call on the same connection (PRO-4141, `analysis-pull`). */
+    callTool: FollowUpToolCall;
     endpoint: string;
     globalOptions: RunnerGlobalOptions;
     io: CliIO;
 }
 interface CommandSpec<TParsedResponse, TRenderedResponse = TParsedResponse> {
+    /**
+     * Render with `renderHuman` even when stdout is piped, and failures as human
+     * text on stderr (`analysis-pull --body-only`, whose stdout is the Markdown
+     * itself or nothing). `--json` still wins.
+     */
+    humanWhenPiped?: boolean;
     outputSchema?: {
         parse(input: unknown): TParsedResponse;
     };