/**
 * Shared accumulator for cascade-mode skip tracking in `DefinitionCreateOperation`.
 *
 * When `--method full` orchestrates multiple input builders (record-type, outcome),
 * per-object "skipping" warnings would be false: the object survives the run with
 * other variants. The cascade caller allocates this accumulator and passes it down
 * to the empty-result branches of each builder. Builders push the skipped object's
 * name into the relevant bucket instead of pushing a per-object warning. The cascade
 * caller then emits at most one aggregated summary warning after both builders run.
 *
 * Standalone callers (`--method recordtype`, `--method outcome`) pass nothing — per-object
 * warning behavior is unchanged at line 910 (RT) and line 1021 (outcome) of their
 * respective files.
 *
 * Presence/absence of the accumulator IS the caller-context signal — no enum needed.
 *
 * CLI-3611: `noOutcomeField` bucket removed. In `--method full`, outcome support is
 * limited to Opportunity/Case/Lead by Salesforce platform design. Silently skipping
 * objects without outcome fields is expected behavior — emitting a warning implies
 * something went wrong, which is misleading.
 */
export type CascadeSkipAccumulator = {
    /** Object names where `RecordTypeService` returned zero record types (empty-result branch). */
    noRecordTypes: string[];
};