Remove stale ibc from v6.7 module version map

[masih]

Remove stale IBC from v6.7 module version map and apply minor cleanups
that are missed in previous IBC removal.

Remove obsolete relayer tests.

[cursor]

PR Summary

Medium Risk
The v6.7 upgrade path now mutates the module version map for IBC; incorrect handling could affect migrations or upgrade bookkeeping, though on-chain IBC stores stay mounted for compatibility.

Overview
Completes v6.7 IBC retirement cleanup by removing the stale ibc module version from the upgrade keeper’s version map on the v6.7 upgrade (alongside capability, feegrant, and transfer), with tests that seed and assert removal of storekeys.IBCStoreKey.

Documentation and operator guidance add an IBC core removal note to the changelog upgrade guide, link IBC retirement from the README, and document retained CosmWasm port metadata, unsupported IBC ops, and mounted stores in docs/ibc_retirement.md.

Miscellaneous cleanup deletes obsolete sei-wasmd/contrib/relayer-tests, reserves CosmWasm error code 16 without exporting ErrMaxIBCChannels, and clarifies in mod_test.go that github.com/cosmos/ibc-go is banned because IBC is retired rather than forked locally.

^{Reviewed by Cursor Bugbot for commit 0fad251. 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	Aug 26, 2026, 9:08 AM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.30%. Comparing base (9c5bb15) to head (0fad251).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4016      +/-   ##
==========================================
- Coverage   61.31%   60.30%   -1.01%     
==========================================
  Files        2158     2059      -99     
  Lines      188203   176609   -11594     
==========================================
- Hits       115395   106508    -8887     
+ Misses      62162    60394    -1768     
+ Partials    10646     9707     -939     

Flag	Coverage Δ
sei-chain-pr	58.20% <100.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 Δ
app/upgrades.go	46.29% <100.00%> (+1.01%)	⬆️
sei-wasmd/x/wasm/types/errors.go	0.00% <ø> (ø)

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

[seidroid]

Well-scoped cleanup: deleting the stale ibc module version at the v6.7 upgrade is correct and covered by a test, and the new IBC retirement doc's claims match the actual CosmWasm query/message behavior. Two non-blocking documentation/convention nits.

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

Blockers

• None at the file/PR level.

Non-blocking

• None at the file/PR level.
• 2 suggestion(s)/nit(s) flagged inline on specific lines.

[masih]

@seidroid review

[seidroid]

Correct, well-scoped follow-up: the stale ibc module version is deleted at the v6.7 upgrade with matching test coverage, wasm error code 16 is now reserved per the file's existing convention, and the removed relayer scripts/doc updates are consistent with the IBC retirement. One carry-over documentation inaccuracy remains in the CHANGELOG upgrade guide.

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

Blockers

• None at the file/PR level.

Non-blocking

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

[seidroid]

[suggestion] export-genesis is not a command in this repo. The CLI is seid export (sei-cosmos/server/export.go:41, registered via ExportCmd in sei-cosmos/server/util.go:369), backed by App.ExportAppStateAndValidators. The substance is correct — the retired modules are no longer in the module manager, so their state is not exported — but an operator following this upgrade guide will get an unknown-command error. The identical string was removed from docs/ibc_retirement.md; this copy was missed.