/**
 * Current-code invariants asserted (2026-04-21, ses_006 Phase 3):
 *
 *   - `ManagedRegistry` extends `Registry` with a component-named
 *     logger + two optional id-extraction strategies: `idField` or
 *     `computeId`. `computeId` takes precedence when both are set.
 *   - `register(id, item)` (2-arg): throws when `item` is missing;
 *     warn-logs + overwrites on duplicate id (no typed error).
 *   - `register(item)` (1-arg): extracts id via computeId/idField;
 *     throws when neither is configured.
 *   - `register(items[])`: batch-registers (recursively calls the
 *     single-arg path for each). Any failure in a single register
 *     throws and aborts the batch (no partial-success semantics).
 *   - `getOrThrow(id)`: returns the item; throws
 *     `new Error("Not found: <id>. Available: <csv of known ids>")`
 *     — a plain `Error`, NOT a typed `XYZNotFoundError` (Codex #1).
 *   - No start / stop lifecycle exists (design §2.3 claim was
 *     fictional).
 */
export {};
//# sourceMappingURL=ManagedRegistry.test.d.ts.map