feat(p2p): carry the accept-interval key through the legacy config mapping

[bdchatham]

Companion to sei-protocol/sei-chain#3899, which adds a p2p accept-interval key so the router's inbound accept rate can be configured instead of being pinned to its compiled-in default of 1 accept/second.

Why this repo has to change too

WriteConfigToDir regenerates config.toml wholesale from the legacy structs:

tm := cfg.toLegacyTendermint()
if err := atomicWriteTOML(configPath, tm); err != nil { ... }

A key with no corresponding field on legacyP2P is therefore silently dropped on the next write — not preserved, not rejected. Without this change, seictl and sei-k8s-controller would strip accept-interval from any node config they write, reverting that node to 1 accept/s with no diagnostic. The sei-chain change alone does not survive contact with a fleet managed by this library.

Change

Five sites, following DialInterval exactly, per the contract in CLAUDE.md:

Site	Field
config.go — unified P2PConfig	AcceptInterval Duration \toml:"accept_interval"``
legacy.go — legacyP2P	AcceptInterval Duration \toml:"accept-interval"``
defaults.go — baseDefaults()	Dur(10 * time.Millisecond)
legacy.go — toLegacyTendermint()	mapping
legacy.go — fromLegacy()	mapping

Note the deliberate tag asymmetry, matching every neighbouring key: underscore in the unified schema (accept_interval), hyphen in the legacy file (accept-interval).

The default matches the one sei-chain#3899 sets, so a node written by this library and a node relying on seid's own defaults agree rather than silently diverging.

No enrichments.go entry — DialInterval has none either, so that layer is curated rather than exhaustive. Happy to add one if you'd rather it be surfaced in the field registry.

Tests

Extended TestWriteReadRoundTrip per CLAUDE.md ("Every new field should be exercised in at least one round-trip test"), using the testing package only, per the repo's no-assertion-library rule.

Verified it discriminates rather than merely passing — with the toLegacyTendermint mapping removed it fails as:

--- FAIL: TestWriteReadRoundTrip (0.04s)
    config_test.go:365: p2p.accept_interval: got 0s, want 25ms

which is precisely the silent-drop failure mode this guards. Full suite green with the mapping in place:

go test ./... -count=1
ok  	github.com/sei-protocol/sei-config	0.629s

make vet is clean. make lint reports 6 pre-existing lll violations (config_test.go:38/55/93/118/126, migrate.go:189) that reproduce identically on unmodified origin/main; none are lines this PR adds.

Sequencing

This should land before anything starts writing accept-interval into node configs, otherwise the key is written and then stripped on the next reconcile. Consumers (seid, seictl, sei-k8s-controller) pick it up on the next release + dependency bump; I have not touched version.json, since releases here appear to be their own chore: release commits.

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Schema and mapping-only change with a round-trip test; affects P2P tuning defaults but no auth, data, or security-sensitive logic.

Overview
Adds P2P accept_interval so inbound accept rate can flow through this library’s config model and into config.toml as accept-interval, aligned with sei-chain’s new knob (companion to sei-chain#3899).

The field is wired like DialInterval: unified P2PConfig, legacyP2P, toLegacyTendermint / fromLegacy, and baseDefaults() set to 10ms so defaults match seid. Without the legacy mapping, WriteConfigToDir would regenerate config.toml and drop the key, pushing nodes back toward a 1 accept/s effective rate.

TestWriteReadRoundTrip now asserts a non-default 25ms survives write/read, guarding that silent-drop behavior.

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