/**
 * Tests: stale todo_update revision handling after durable recovery.
 *
 * A stale todo_update revision is now recovered INTERNALLY and
 * DETERMINISTICALLY: the engine reads the current state, rebases the
 * non-conflicting intent exactly once, and applies it. A stale revision is
 * NEVER a run-terminal condition and NEVER requires the model to manually
 * issue todo_read merely to satisfy an internal concurrency protocol.
 *
 * The prior false-positive behavior (REQUIRE_READ + REPEATED_TODO_UPDATE_LOOP
 * run termination) is gone; this file documents the corrected behavior.
 */
export {};
//# sourceMappingURL=todo-stale-error-classification.test.d.ts.map