chore(sdks): update Somnia Data Streams SDK metadata

[foredstudio]

Summary

• update Somnia Data Streams SDK version to 0.12.2
• set maintainer to Somnia Foundation
• set license to MIT

Verification

Verified directly against the official somnia-chain/somnia-data-streams-sdk repository package.json and LICENSE. Chain.Love's local git-hooks/pre-commit.py validation completed successfully; unrelated auto-sorting side effects were discarded before this PR.

Validation checklist

• I followed the Style Guide and Column Definitions.
• I personally verified the source used for every changed value.
• Somnia support is already represented by the existing listings/specific-networks/somnia/sdks.csv entry.
• This is not a blind AI-generated submission; each changed value was independently checked against the official upstream repository.

Optional

• Rewards address (for data patching rewards): 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 upstream values are verifiable, but these fields should not be populated manually.

In references/offers/sdks.csv → somnia-data-streams-sdk, please clear:

• latestKnownVersion
• maintainer
• license

The current SDK documentation explicitly reserves latestKnownVersion, latestKnownReleaseDate, maintainer, and license for Chain.Love automation and states that they cannot be modified manually.

The SDK itself can remain; only the manually populated automation-managed fields need to be reverted.

[foredstudio]

Requested metadata cleanup is now applied in 39166a626045a3b1bfe10f4af273d37d85184e18: the manually populated automation-managed somnia-data-streams-sdk 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.