Backport release/v6.7: Apply compiled KV repair files at a fixed height and generate them from digest inspect lists

[seidroid]

Backport of #4400 to release/v6.7.

[seidroid]

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

git fetch origin backport-4400-to-release/v6.7
git worktree add --checkout .worktree/backport-4400-to-release/v6.7 backport-4400-to-release/v6.7
cd .worktree/backport-4400-to-release/v6.7
git reset --hard HEAD^
git cherry-pick -x 792ff53715ca75e7ffb48b6400c53c4f3b964bd2
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 1, 2026, 4:32 PM

[codecov]

Codecov Report

❌ Patch coverage is 83.43816% with 79 lines in your changes missing coverage. Please review.
✅ Project coverage is 60.51%. Comparing base (8e7ba86) to head (a4ad665).

Files with missing lines	Patch %	Lines
...i-db/tools/cmd/seidb/operations/kvrepair_export.go	81.01%	22 Missing and 19 partials ⚠️
sei-db/common/kvrepair/repair.go	84.00%	14 Missing and 10 partials ⚠️
app/upgrades/kvrepair/kvrepair.go	86.74%	6 Missing and 5 partials ⚠️
...b/tools/cmd/seidb/operations/evm_logical_digest.go	33.33%	2 Missing ⚠️
sei-db/tools/cmd/seidb/main.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           release/v6.7    #4410      +/-   ##
================================================
- Coverage         61.40%   60.51%   -0.89%     
================================================
  Files              2163     2072      -91     
  Lines            189115   178582   -10533     
================================================
- Hits             116121   108067    -8054     
+ Misses            62261    60611    -1650     
+ Partials          10733     9904     -829     

Flag	Coverage Δ
sei-chain-pr	47.53% <83.43%> (?)
sei-db	70.02% <ø> (+0.21%)	⬆️
sei-db-state-db	?
sei-db-state-db-pr	69.87% <ø> (?)

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

Files with missing lines	Coverage Δ
app/app.go	71.73% <100.00%> (+0.01%)	⬆️
sei-db/common/kvrepair/values.go	100.00% <100.00%> (ø)
sei-db/tools/cmd/seidb/main.go	0.00% <0.00%> (ø)
...b/tools/cmd/seidb/operations/evm_logical_digest.go	41.40% <33.33%> (+7.04%)	⬆️
app/upgrades/kvrepair/kvrepair.go	86.74% <86.74%> (ø)
sei-db/common/kvrepair/repair.go	84.00% <84.00%> (ø)
...i-db/tools/cmd/seidb/operations/kvrepair_export.go	81.01% <81.01%> (ø)

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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-01T15:57:33.434726Z	73914e8	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cursor]

PR Summary

High Risk
Direct module-store mutations at consensus-defined heights can halt the chain on unexpected pre-state or cause consensus failure if repair data is wrong; operational risk is high though gated by old-value checks and review workflow.

Overview
Adds a kvrepair hard-fork path so reviewed EVM (and other module) store fixes ship as embedded JSON and run at a fixed chain ID + block height via HardForkManager.

The app wires kvrepair.Register at startup: it loads every repairs/*.json file, validates stores and duplicate keys, and registers one handler per repair. At target_repair_height, each handler sets or deletes listed keys, optionally checks the pre-repair old value (or old_absent), and always re-writes entries so correct and repaired nodes commit the same changeset. EVM comparisons treat all-zero slots/nonces/code hashes and empty code as absent where FlatKV and memiavl disagree.

Tooling: seidb kvrepair-export builds repair files from paired evm-logical-digest inspect lists (memiavl reserve vs composite/flatkv prod). Shared types and strict JSON parsing live in sei-db/common/kvrepair. Docs note --key-offset 4 for digest prefix filtering; a composite migration test checks repair-shaped writes survive EVM migration.

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

[seidroid]

This is a clean backport of #4400. It adds the kvrepair file format with strict parsing and validation, a hard-fork handler that applies embedded repair files at a fixed height, and a seidb kvrepair-export tool that builds repair files from digest inspect lists. With no .json repair files embedded, no handlers are registered, which matches the non-app-hash-breaking label; the referenced helpers exist on the base, and tests cover the parser, validator, handler and exporter, including an end-to-end export-and-apply run.

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

Blockers

• None at the file/PR level.

Non-blocking

• None at the file/PR level.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 73914e853c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Move the CLI walkthrough out of the GoDoc

KVRepairExportCmd has a multi-paragraph GoDoc containing an invocation workflow and command examples rather than a concise description of what the function returns. Move this material to the Cobra command's Long/Example text or package documentation and keep the function GoDoc to one or two descriptive sentences.

AGENTS.md reference: AGENTS.md:L61-L72

Useful? React with 👍 / 👎.