/**
 * The completeness claim an enumerating step ends its reply with (wicked-crew#721).
 *
 * wicked-garden's `core/refs/inventory-report.md` codebook asks a step that lists things a later
 * step acts on (issues, PRs, files) to end with one fenced `wicked-inventory` JSON block per source:
 * where it listed from, whether the source answered fully, how many it has, the total the source
 * reported, and what it could not read. crew#648 is why: two triage runs reported success, one
 * inventory was six items short, and nothing on the wire told them apart.
 *
 * Pure: text in, claims out. Deny-dominates on the claim itself: a block that does not parse, or
 * has a required field missing or misshapen, reads `unknown`, never `full`; a `full` that its own
 * numbers contradict (something unread, or a count unlike the source's total) reads `partial`, with
 * the contradiction added to `unread`. Only the blocks that end the reply are the report.
 */
import type { InventoryAnswered, InventoryClaim } from 'wicked-crew-api-types';
export type { InventoryAnswered, InventoryClaim };
/**
 * The report's claims: the `wicked-inventory` blocks that END the reply, as the codebook asks
 * ("one block per source, nothing after them"). Parsed line by line with fence tracking, so:
 * - a block quoted inside another fence (an example in a code sample) is not a claim;
 * - a block followed by more prose is not the report (an example earlier in the reply);
 * - an inventory opener that never closes (a truncated reply) is an `unknown` claim.
 * Empty when the reply makes no report.
 */
export declare function parseInventoryClaims(text: string): InventoryClaim[];
/** Whether a set of claims says the inventory is complete: at least one claim, every one `full`. */
export declare function inventoryComplete(claims: InventoryClaim[]): boolean;
//# sourceMappingURL=inventory-claim.d.ts.map