In tendermint/tendermint SocketPV.SignProposal and SocketPV.SignVote do not mitigate accidental double-signing (e.g., validator node crash before committing to WAL). Is it correct to assume that responsibility will be left to the CKMS/signer implementation?

If that's the case, will rpc::Request expose the vote's or the proposal's HRS as member variable(s) before launch? And will session::Session::sign support similar mitigation logic to FilePV.signProposal or FilePV.signVote in tendermint/tendermint?

I'm trying to get a sense of direction to follow.