/**
 * Writer tests for the query-before-derive sensor (mmnto-ai/totem#2510).
 *
 * The induced-failure blocks follow the ADR-115 § 2 three-pack convention used
 * by `mail-degraded-e4.test.ts`:
 *   1. per-item accounting fires — the specific failing item is NAMED in the
 *      warnings channel;
 *   2. the loud backstop throws — for this MUTATING path that is a literal
 *      throw from `recordDeriveAction`, and the ledger is left in prior-good
 *      state (the derive row present, simply uncorrelated) rather than
 *      "presenting as success while partial";
 *   3. a recovery / control assertion — with the fault removed the same call
 *      returns to green, and a healthy control never warns.
 *
 * **The two ADR-115 § 2 packs** induce their failures with real errnos (a file
 * where a directory belongs) or real on-disk state (a hand-written pointer),
 * never by mocking the module under test — that is what makes them evidence
 * rather than assertion.
 *
 * Other tests in this file DO stamp errnos onto `fs` via `vi.spyOn` (EACCES,
 * ENOSPC). That is deliberate and scoped: ENOSPC is not inducible on a real
 * filesystem, and those tests cover accounting branches rather than the
 * degraded-path contract. The blanket "never by mocking" claim used to sit at
 * file level and overstated what four of these tests do.
 */
export {};
//# sourceMappingURL=record.test.d.ts.map