/**
 * The manifest build reads ONE journal shard: the one describing its scope.
 *
 * This is a memory invariant expressed as a behavioural one. `listJournals()`
 * reads and parses every shard on the machine, and on a laptop holding a
 * personal vault plus several cloud companies that was the single largest line
 * item in the tail step's footprint — hundreds of megabytes spent parsing
 * ledgers whose rows were then dropped on the floor, repaid once per scope in
 * a fanout.
 *
 * A byte counter would be the obvious gate and the wrong one: it moves with
 * fixture size and tempts a future reader to widen it. The thing that must not
 * come back is the ENUMERATION, so the assertion counts journal files opened.
 * One is correct; anything above one means a caller has gone back to reading
 * the machine instead of the scope, no matter what the megabytes say.
 */
export {};
//# sourceMappingURL=ledger-shard-isolation.test.d.ts.map