logEntryTerm_roundTripsAtZero

The lower edge of the term half of RaftEngine.checkedRestoredEntries — term = 0 is admitted, and an adapter treating 0 as "unset" (a nullable column, a sentinel) corrupts it.

The index half is deliberately not probed at 0: the engine's own contiguity check requires the restored log to begin at snapshotIndex + 1, which is >= 1 because lastIncludedIndex >= 0, and the restore reads entries(snapshotIndex + 1) — so an entry at index 0 is never written by the engine and never visible to it. Requiring an adapter to store one would test past faithfulness.