chore(sdks): update Somnia abitype metadata

[foredstudio]

Summary

• add the latest known abitype version (1.3.0)
• add its 2026-07-16 release date
• add maintainer (wevm) and MIT license metadata

Verification

• verified current package metadata against the npm registry
• ran the repository json-tools validation flow locally: validate_csv.py, csv_to_json.py, validate.py — all passed

Rewards address (Ethereum Mainnet): 0x71585c4C945f3D326f1B0d7102cdDbDFDf3C32C6

[USS-Supervisor]

Verdict: COMMENT
Risk: LOW
Summary: The exact required validation check is passing and I do not see a blocking data-integrity issue in the visible diff. CSV widths remain stable, touched listing !offer: references resolve where applicable, and the changes are scoped to the PR's stated data/schema cleanup.

Findings:

• No blocking data finding from the visible diff. I am leaving this as a non-approval review because the required current-cycle link-check gate did not produce a run within the five-minute label window after check-links was added. The label was removed before this review, and approval is blocked until a current-cycle link-check completes successfully.

Confidence: HIGH

[eugene17kotov]

Thanks for the update. The abitype offer itself can remain, but the newly populated SDK metadata fields need to be reverted.

In references/offers/sdks.csv → abitype, please clear:

• latestKnownVersion
• latestKnownReleaseDate
• maintainer
• license

The current SDK documentation explicitly reserves these four fields for Chain.Love automation and states that they cannot be modified manually.

Some of the supplied values, such as version 1.3.0 and the MIT license, are supported upstream, but they still should not be hardcoded in the canonical CSV.

[github-actions]

Summary

Status	Count
🔍 Total	2
🔗 Unique	2
✅ Successful	2
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[foredstudio]

Requested metadata cleanup is now applied in 9fc9db166c5d9143da92cadaa2c7788ea7098e7b: the four automation-managed abitype fields are blank again, with the repository validation scripts passing locally. The two workflows created for this head are currently action_required, so could a maintainer please approve the workflow runs and re-review when convenient? No further content changes are pending from my side.