/**
 * Leaf partition-chunk primitives for the flat-monorepo strategies
 * (`flat-monorepo-strategy.ts`).
 *
 * Hoisted out of `flat-monorepo-strategy.ts` (originally so the ADR-0045
 * community-partition prototype could reuse `chunkByCount` cycle-free; the
 * prototype was discarded by measurement, but the extraction is a harmless
 * leaf and any future partition strategy reuses it the same way).
 * Behavior-preserving move — `flat-monorepo-strategy.test.ts` is the
 * refactor canary.
 */
/**
 * Synthetic partition — the unit that gets handed to a child process in
 * the flat-large fan-out. `id` is suitable as a display label and a
 * cache-key segment; `files` are absolute paths.
 */
export interface SyntheticPartition {
    readonly id: string;
    readonly files: readonly string[];
}
/**
 * Default chunk size for `file-count-chunks` and `hybrid` sub-partitioning.
 * Chosen at 2000 to stay well below the 2500-file heap-elevation threshold —
 * each partition runs in a child process with a default V8 heap (no
 * elevation needed at this size).
 */
export declare const DEFAULT_CHUNK_SIZE = 2000;
/**
 * Sort `files` lexicographically (stable) and split into chunks of
 * `chunkSize`. Partition ids follow the `chunk-N` contract (`chunk-0`,
 * `chunk-1`, …) that `hybrid` sub-partition ids (`<parent>.chunk-N`)
 * concatenate onto — the id scheme is load-bearing for fragment-cache
 * keys, so it must not drift.
 */
export declare function chunkByCount(files: readonly string[], chunkSize: number): readonly SyntheticPartition[];
//# sourceMappingURL=partition-chunk.d.ts.map