/** * Grep-safe output support for the media generation tools. * * Agents routinely pipe gsk stdout through `grep | head` to save context. * With indent-2 JSON the URL values sit on their own lines, so such * filters keep the `"image_urls": [` key line and silently drop the URLs * — the agent then reconstructs (fabricates) them from memory, which is * the prod broken-card incident behind PR #41690. Two defenses: * * 1. `mediaItemsKeyFor` marks these tools for compact (single-line) * stdout — any line filter then keeps the whole payload. * 2. `mediaSummaryLines` produces stderr `[INFO]` lines carrying the * fields the render card needs (task_id / status / first URL), so * even a stdout-swallowing pipeline still surfaces them via 2>&1. * * `mediaProgressLines` is the same stderr contract for the server's * mid-stream progress frame: a paid render's task ids, printed the moment * the render is submitted, so a wait that is cut later (shell timeout, a * killed process) still leaves the id in the log for * `gsk video_generation --task_id` to collect instead of a resubmit. */ export declare function mediaItemsKeyFor(toolName: string): string | undefined; /** The submit-time progress frame's task ids as one line; [] otherwise. */ export declare function mediaProgressLines(toolName: string, msg: { [key: string]: unknown; }): string[]; /** One summary line per generated item; [] when not a media result. */ export declare function mediaSummaryLines(toolName: string, result: { status?: string; data?: unknown; }): string[]; //# sourceMappingURL=mediaSummary.d.ts.map