/**
 * The stream's defaults when the tuning flags are not given. Caller-side, not a
 * property of the loop: `streamWorkflowUpdates` takes all three as required
 * options and never falls back. Single-sourced because only `workflow monitor`
 * can hand them to oclif — `workflow start --monitor` has to apply them itself
 * (see `gatedMonitorStreamFlags`), and a literal repeated on that side would
 * drift the moment one of these changes.
 */
export declare const MONITOR_DEFAULTS: {
    readonly interval: 2500;
    readonly color: true;
    readonly includePayloads: false;
};
/** For a command that always monitors, where oclif can apply the defaults itself. */
export declare function monitorStreamFlags(): {
    'include-payloads': import("@oclif/core/interfaces").BooleanFlag<boolean>;
    interval: import("@oclif/core/interfaces").OptionFlag<number, import("@oclif/core/interfaces").CustomOptions>;
    color: import("@oclif/core/interfaces").BooleanFlag<boolean>;
};
/**
 * For a command where monitoring is opt-in (`workflow start --monitor`).
 *
 * These carry no oclif `default` on purpose: a defaulted flag counts as present
 * (`validateFlags` runs a relationship check whenever the parsed value is not
 * `undefined`, and `validateDependsOn` has no `setFromDefault` exemption the way
 * `validateExclusive` does), which triggers its own `dependsOn` check and fails
 * every invocation that omits `--monitor` — including a plain `workflow start`.
 * The caller applies the defaults in `run()`, so the interval's default is
 * spelled out in the help text rather than rendered by oclif.
 */
export declare function gatedMonitorStreamFlags(gatedBy: string): {
    'include-payloads': import("@oclif/core/interfaces").BooleanFlag<boolean>;
    interval: import("@oclif/core/interfaces").OptionFlag<number | undefined, import("@oclif/core/interfaces").CustomOptions>;
    color: import("@oclif/core/interfaces").BooleanFlag<boolean>;
};