conditional deactivation of consensus timeout overrides in config

[pompon0]

In 6.6 release we want to disable the overrides support.
Overrides can only be disabled AFTER onchain params are updated via government proposal.
Govenment proposal needs to wait for changes deployed in 6.6.
Disabling overrides needs to be synchronized across the network.
We need ability to reenable overrides for disaster recovery (chain halt).

To achieve that we:

• add a unsafeOverridesEnabled flag
• unsafeOverridesEnabled defaults to true BEFORE the government proposal goes through, and to false AFTERWARDS

[cursor]

PR Summary

High Risk
Changes how every node computes propose/vote/commit timeouts and commit bypass, which directly affects consensus liveness and must stay synchronized with on-chain param migration and operator config.

Overview
Adds unsafe-overrides-enabled on consensus config and centralizes effective timeout selection in ConsensusConfig.ResolveTimeouts, so operators can stop applying local Unsafe*TimeoutOverride values once on-chain params are fixed while still re-enabling overrides for recovery.

When overrides are disabled, config overrides are ignored unless on-chain timeouts still match the hard-coded badParams snapshot (legacy pacific-1 values); in that case override behavior is preserved until a gov proposal updates chain params. BypassCommitTimeout remains a special case: only a non-nil pointer override replaces the resolved value.

Consensus proposeTimeout, voteTimeout, commitTime, and bypassCommitTimeout now call ResolveTimeouts instead of duplicating override logic. TimeoutParams.TimeoutParamsOrDefaults is replaced by TimeoutParams.Or, which also merges BypassCommitTimeout via cmp.Or. RPC consensus-params loading uses the same Or helper for defaults.

^{Reviewed by Cursor Bugbot for commit ab5f001. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Jun 22, 2026, 2:09 PM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.18%. Comparing base (4cf4ede) to head (ab5f001).
⚠️ Report is 17 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3601      +/-   ##
==========================================
- Coverage   58.96%   58.18%   -0.78%     
==========================================
  Files        2208     2134      -74     
  Lines      181757   173832    -7925     
==========================================
- Hits       107164   101152    -6012     
+ Misses      64976    63713    -1263     
+ Partials     9617     8967     -650     

Flag	Coverage Δ
sei-chain-pr	73.69% <100.00%> (?)
sei-db	70.41% <ø> (ø)
sei-db-state-db	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
sei-tendermint/config/config.go	74.27% <100.00%> (+0.76%)	⬆️
sei-tendermint/internal/consensus/state.go	76.28% <100.00%> (+3.37%)	⬆️
sei-tendermint/internal/rpc/core/consensus.go	38.94% <100.00%> (ø)
sei-tendermint/types/params.go	80.06% <100.00%> (+1.03%)	⬆️

... and 76 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[wen-coding]

Is this the same as DefaultTimeoutParams?

[pompon0]

huh, indeed. Perhaps timeouts are currently not set at all.

[masih]

hm..

[wen-coding]

Our gov proposal will always override all params at the same time right? It would be a headache if proposal updates some args while override updates some.

[pompon0]

proposal updates everything atomically, yes. It wouldn't make sense otherwise.

[philipsu522]

correct, all happens within a block

[masih]

hm..