/**
 * Counter / warehouse mix recipes under `agents insights`.
 *
 * These used to live as the top-level `agents trends` tree. That name was a
 * peer of `agents insights` with overlapping "analytics" meaning, so agents and
 * humans kept picking the wrong verb. The cheap counter path (sessions index +
 * usage.db) still exists — it is now `agents insights mix`. Latency stays on
 * `agents insights perf`; quota on `agents view`.
 *
 * One surface, not five: the board is `agents insights mix`, one section is
 * `agents insights mix <recipe>`, and `--list` names the recipe ids. The former
 * per-recipe shortcut commands (`harness-mix`, `model-mix`, …), the `recipes`
 * lister, and the `trends` alias were removed — `mix` already did all three.
 */
import type { Command } from 'commander';
export declare function parseMixDays(raw: string | undefined): number;
export declare function printMixSection(section: {
    id: string;
    title: string;
    rows: Array<Record<string, string | number | null>>;
}): void;
export declare function renderMixDashboard(days: number, asJson: boolean, bannerLabel?: string): void;
/**
 * Attach counter-mix subcommands to a parent (typically `insights`).
 *
 * Layout:
 *   <parent> mix                 multi-recipe board
 *   <parent> mix <recipe>        one baked recipe (harness-mix, model-mix, …)
 *   <parent> mix --list          list recipe ids
 *   <parent> query               raw usage.db rows
 */
export declare function registerMixCommands(parent: Command): void;
