savesAndLoadsLeaderForTerm

The round trip §3.10 sender-authentication rests on: RaftEngine restores this record on start-up and refuses a TimeoutNow from anyone but the LeaderForTerm.leaderId it names, so both halves must come back exactly as written.

The term half is the one an adapter is most likely to lose, and losing it is worse than losing the whole record: the engine decides relevance by comparing the stored term to its own, so a term that comes back wrong either hides a live pin (the honest transfer target refuses its own leader) or exposes a stale one (an identity from an older term is admitted as this term's authority).