/** * Seed a new worktree's index from a sibling checkout * (change: seed-worktree-index-from-sibling-checkout). * * `.openlore/` is gitignored, so a new git worktree starts with no index, and its first call * could only say "a build has started". The main checkout next door usually holds a current * index of nearly the same code. This copies that index in, verified, so the first call * answers; a background rebuild then reuses the copied per-file memo in `call-graph.db`. * * What makes a copy safe to serve: * - The sibling shares this checkout's git common directory, so it is the same repository. * - No build owns the sibling, and its generation manifest is a published one. * - Only known artifact names are copied, never a symlink or a special file, and never the * sibling's runtime state (locks, stamps, progress), which lives outside the analysis dir. * - The COPY is verified, not the source: its digests match the manifest and its edge store * reconciles `healthy` against its attestation. The source is re-checked after the copy, * so a writer that moved underneath it voids the seed. * - The verified set is published by one directory rename, so a reader never sees a part. * * Any refusal leaves this checkout untouched, and the caller starts the ordinary cold build. */ export type SeedResult = { state: 'seeded'; source: string; generationId: string; } | { state: 'not-seeded'; reason: string; }; /** * Seed `directory`'s index from a sibling checkout of the same repository, when it has none. * * The caller applies the auto-init opt-outs first. Never throws: every refusal is a * `not-seeded` result, and the caller then starts the ordinary cold build. */ export declare function seedFromSiblingCheckout(directory: string): Promise; /** * Is `directory` still serving the generation it was seeded with? True from the seed until * the rebuild publishes its own generation. */ export declare function servingSeededIndex(directory: string): Promise; //# sourceMappingURL=seed-from-sibling.d.ts.map