Backport release/v6.7: Initialize app from last header when a frozen node restarts

[seidroid]

Backport of #4447 to release/v6.7.

[seidroid]

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-4447-to-release/v6.7
git worktree add --checkout .worktree/backport-4447-to-release/v6.7 backport-4447-to-release/v6.7
cd .worktree/backport-4447-to-release/v6.7
git reset --hard HEAD^
git cherry-pick -x d4853e532b878fe34033ff63495521c782baf0fb
git push --force-with-lease

[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	Oct 12, 2026, 3:33 PM

[codecov]

Codecov Report

❌ Patch coverage is 60.00000% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 60.80%. Comparing base (455235e) to head (43e3831).

Files with missing lines	Patch %	Lines
sei-tendermint/node/node.go	60.00%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           release/v6.7    #4507      +/-   ##
================================================
- Coverage         61.84%   60.80%   -1.04%     
================================================
  Files              2168     2068     -100     
  Lines            188739   176784   -11955     
================================================
- Hits             116724   107494    -9230     
+ Misses            61159    59406    -1753     
+ Partials          10856     9884     -972     

Flag	Coverage Δ
sei-chain-pr	64.51% <60.00%> (?)
sei-db	69.80% <ø> (ø)
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/node/node.go	66.52% <60.00%> (-0.07%)	⬇️

... and 100 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.

[cursor]

PR Summary

Medium Risk
Touches node startup and app initialization for freeze-mode operators; behavior is narrow (only when freezeHeight > 0 and chain state exists) but affects RPC availability after restarts.

Overview
Frozen nodes now re-initialize the application from the last persisted block header on startup, so query paths (including EVM RPC) work after restart even though no new blocks are committed.

In node.OnStart, after the handshake reloads state, freeze mode calls App.InitLastHeader with the header from blockStore at state.LastBlockHeight, and fails startup if that block meta is missing.

Coverage adds a unit test that asserts the header passed to InitLastHeader matches the block store, and a Docker integration test that restarts seid in a frozen container and checks eth_getBlockByNumber still succeeds at the frozen height.

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

[seidroid]

The node.go change backports cleanly. However, sei-tendermint/node/freeze_test.go was committed with unresolved merge-conflict markers, so the node test package won't compile.

Findings: 1 blocking | 0 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.
• 1 blocking issue(s) flagged inline on specific lines.

Non-blocking

• None at the file/PR level.

Inline comments (could not post inline; listed here)

• sei-tendermint/node/freeze_test.go:15 (RIGHT) -- [blocker] The import block still has merge-conflict markers (<<<<<<< HEAD / ======= / >>>>>>>), so the file won't parse. That breaks compilation of the whole sei-tendermint/node test package and blocks CI. Resolve it by keeping both sides: the existing test still uses tcp.TestReserveAddr() (line 89), and the new test needs libs/utils, libs/utils/require and tmproto. Then run gofmt and goimports on the file.