fix: autobahn InitChain height and GetValidators panic (CON-249)

[wen-coding]

Summary

Fixes two bugs in autobahn's runExecute InitChain flow:

1. Height mismatch: After InitChain, runExecute called Commit which advanced the app to InitialHeight. The next FinalizeBlock at InitialHeight then failed with "invalid height: N; expected: N+1". Fix: remove the Commit after InitChain — the SDK expects the first FinalizeBlock at InitialHeight using the deliverState set up by InitChain.

2. GetValidators panic: Without Commit, the committed store is empty (staking params not persisted). GetValidators reading from committed store panics with "UnmarshalJSON cannot decode empty bytes". Fix: read committed store first (normal path), fall back to DeliverContext only when committed store returns no validators (autobahn-only genesis path).

Why the testApp Committed field was removed

The original testApp had a Committed bool field set by both InitChain and Commit, with FinalizeBlock checking if !state.Committed { error }. This conflated two states — "post-InitChain" and "post-Commit" — into one flag.

For autobahn's flow (InitChain → FinalizeBlock → Commit), InitChain set Committed=true. After the first FinalizeBlock set it to false, Commit correctly set it back to true. But if InitChain set Committed=true and then Commit was called (CometBFT flow), it would fail with "double commit" — not because there was actually a double commit, but because the flag was already true.

The real app guards against actual double commit structurally: Commit() sets deliverState = nil, so a second Commit() panics on nil pointer dereference. The testApp is too simple to replicate that mechanism and doesn't need to — it only tracks blocks and txs for test assertions.

Changes

• sei-tendermint/internal/p2p/giga_router.go: Remove Commit after InitChain; set next = InitialHeight (not +1)
• app/app.go: GetValidators() reads committed store first, falls back to DeliverContext only when empty (autobahn genesis path)
• sei-cosmos/baseapp/test_helpers.go: Add DeliverContext() accessor for reading uncommitted state
• sei-tendermint/internal/p2p/giga_router_test.go: Remove Committed field from testApp; add TestInitChainCommitThenFinalize test

Test plan

• TestInitChainCommitThenFinalize passes — verifies InitChain → FinalizeBlock → Commit flow
• TestGigaRouter_FinalizeBlocks — pre-broken on main (times out, caused by Made autobahn producer use TxMempool #3224), not affected by this change
• Docker integration test with AUTOBAHN=true cluster

🤖 Generated with Claude Code

[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	Apr 15, 2026, 5:34 AM

[codecov]

Codecov Report

❌ Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.26%. Comparing base (9795d18) to head (5982d5f).

Files with missing lines	Patch %	Lines
sei-cosmos/baseapp/test_helpers.go	0.00%	4 Missing ⚠️
app/app.go	0.00%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3243      +/-   ##
==========================================
- Coverage   59.26%   59.26%   -0.01%     
==========================================
  Files        2070     2070              
  Lines      169788   169791       +3     
==========================================
  Hits       100631   100631              
- Misses      60358    60362       +4     
+ Partials     8799     8798       -1     

Flag	Coverage Δ
sei-chain-pr	60.97% <0.00%> (?)
sei-db	70.41% <ø> (ø)

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

Files with missing lines	Coverage Δ
sei-tendermint/internal/p2p/giga_router.go	68.75% <ø> (+1.67%)	⬆️
app/app.go	68.90% <0.00%> (-0.14%)	⬇️
sei-cosmos/baseapp/test_helpers.go	66.66% <0.00%> (-10.26%)	⬇️

🚀 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.

[pompon0]

this pr seems to be a noop, no?

[wen-coding]

this pr seems to be a noop, no?

Sorry, still working on it, Claude pushed before it's ready. I'll ping you when it's ready for review.