Remove interchain swagger API and protos

[masih]

Now that interchain accounts is deleted, remove the proto and swagger APIs. This breaking change in proto + APIs is expected since in and out bound IBC is disabled.

[cursor]

PR Summary

Medium Risk
Breaking change to public gRPC/REST and proto contracts; low runtime risk on-chain if ICA is already gone, but integrators and codegen that still reference ICA paths will break.

Overview
Follow-up cleanup after interchain accounts (ICA) was removed from the chain: this PR deletes the remaining ICA protobuf definitions under sei-ibc-go/proto/ibc/applications/interchain_accounts/ (controller, host, shared account/genesis/metadata/packet types and gRPC query services) and strips matching OpenAPI surface from docs/swagger-ui/swagger.yml (e.g. host Params query path and related schema types).

This is an intentional breaking API/proto change aligned with disabled inbound/outbound IBC ICA behavior—clients must not rely on these REST or proto endpoints anymore.

^{Reviewed by Cursor Bugbot for commit 062f942. 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 7, 2026, 6:06 PM

[seidroid]

Clean, complete removal of the ICS-27 interchain accounts protos and swagger entries — no dangling references, no orphaned generated code, and the buf breaking rules in use (WIRE/WIRE_JSON) permit the deletion. Two non-blocking follow-ups: the served swagger bundle (docs/swagger/statik.go) wasn't regenerated, and sei-ibc-go/README.md still lists ICS 27.

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

Blockers

• None at the file/PR level.

Non-blocking

• sei-ibc-go/README.md:54 still lists "2.2 [ICS 27 Interchain Accounts]" in its module index. Now that the protos are gone alongside the already-deleted module, that entry is stale and worth dropping in this PR.
• Heads-up on tooling, not this PR's fault: scripts/update-swagger-ui-statik.sh uses sed -i '', which is BSD/macOS-only and fails on GNU sed (Linux). Anyone regenerating the statik bundle on Linux will need sed -i without the empty-argument form.
• The Cursor second-opinion pass produced no output (cursor-review.md is empty). Codex reported no material findings. This review is therefore effectively a single-reviewer pass plus my own verification.
• Verified for the record, so it doesn't get re-flagged: repo-wide grep on the merged tree finds no remaining interchain_accounts references outside the README, no orphaned *.pb.go, and no proto still importing the deleted files — so buf build won't break on missing imports. Root buf.yaml scopes sei-ibc-go/proto under breaking: use: [WIRE, WIRE_JSON], which permits deletions (the *_NO_DELETE rules are in the FILE/PACKAGE categories), and proto-registry.yml only pushes proto/** while sei-ibc-go/proto has no module name — so no published buf module is affected.
• 1 suggestion(s)/nit(s) flagged inline on specific lines.

[seidroid]

[suggestion] Editing this file alone doesn't change what a node actually serves. docs/swagger/statik.go is the statik-embedded copy of docs/swagger-ui/ (I confirmed the bundle contains a swagger.yml entry), and it's what app/app.go:2772 RegisterSwaggerAPI mounts at /swagger/ via fs.NewWithNamespace("swagger"). Since statik.go is unchanged in this PR, the running node's swagger UI will still advertise /ibc/apps/interchain_accounts/host/v1/params for an endpoint that no longer exists.

Re-running scripts/update-swagger-ui-statik.sh to regenerate docs/swagger/statik.go would make the change reach the served docs. Non-blocking — docs-only, no runtime or consensus impact — and note the embedded copy may already have been drifting from this file before this PR, in which case this is pre-existing rather than newly introduced. Either way, the removal doesn't propagate without the regen.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.75%. Comparing base (0278f2c) to head (062f942).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3881      +/-   ##
==========================================
- Coverage   61.61%   60.75%   -0.87%     
==========================================
  Files        2348     2254      -94     
  Lines      200842   190346   -10496     
==========================================
- Hits       123751   115646    -8105     
+ Misses      66033    64479    -1554     
+ Partials    11058    10221     -837     

Flag	Coverage Δ
sei-db	70.41% <ø> (ø)
sei-db-state-db	?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 94 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.