chore(sdk-outpost): update artifact registry for Ethereum 0.3.0 + Solana 0.3.1 artifact suite

[joshglogau]

Summary

• register the exact SDK Outpost artifact pair validated by the current Sandbox: Ethereum 0.3.0 plus Solana 0.3.1
• advance only @wireio/outpost-solana-artifacts from 0.3.0 to 0.3.1
• retain @wireio/outpost-ethereum-artifacts at 0.3.0 because its source and artifact-set identity are unchanged
• update the lockfile, exact producer-identity assertions, package documentation, and repository guidance

Naming and scope

Sandbox is the reusable deployment class. The current validation chain may be described as Sandbox (Bearbox) when its individual provenance matters. Bearbox is not an SDK environment key, endpoint catalog entry, or runtime selector.

SDK Outpost continues to select its compile-time artifact suite from authenticated deployment-profile ABI/IDL identities and then verifies exact live runtime identity. Any sandbox or other deployment with the same compatible profile identities uses this artifact pair without environment-specific SDK code.

Why this is required

The current Sandbox deployment uses the same Ethereum artifact set already published as 0.3.0, but it deploys the updated Solana artifact set published as 0.3.1. Consumers locked to the earlier SDK suite fail closed on the Solana IDL identity:

• previous registered Solana IDL: 82fc1d9f54f1247e312eb217b703a26d8fe165d7853212687f348d3f0bc651e4
• current Sandbox Solana IDL: 2283ffe0674c01d1895a0f564a9268f2af53045f351067a4f6499b6cc4564099

This change registers that producer pair without adding a runtime registry, deployment-profile download, endpoint ownership, or environment-specific branch.

Current Sandbox provenance (Bearbox descriptor)

• Wire chain ID: 4b1db236931a8a0cbc5bf1e24c39958fc65656123fe05fe16a744b7d4da47a4e
• immutable handoff SHA-256: eccfeecd15f6614e248d70055944a9f17cf6556cd0370e7e979e0b9298f10ba6
• Solana source revision: 9d49cbe92419606667f6a4684714aa742ac5c40b
• wire-sysio source revision: 33e86e8f9c134391f1910c815fb4ffc85b84edd3
• Solana IDL SHA-256: 2283ffe0674c01d1895a0f564a9268f2af53045f351067a4f6499b6cc4564099
• deployed Solana program SHA-256: 9ad39d30c062205190589aa99acea48dd706d5501b5853e550fc6aa651ccda2a
• Solana package integrity: sha512-gRq36L2fxS+J47qsjMprIXP5StZiK3xuQ0WUyhC6LZKZEdQkntiHg/4VDV3WVc8iewXPY1K75aTkChvNnhE+RA==
• immutable handoff
• successful Solana artifact publication

Validation

• corepack pnpm --dir packages/sdk-outpost run build
• SDK Outpost: 12/12 suites and 65/65 tests
• repository ESLint: clean
• repository: 88/88 suites and 955/955 tests
• Hub connected read-only native quote canary: 6/6 directions
• Hub connected read-only full route set: 28/28 routes
• Hub exact compatibility test intentionally fails with the previously installed Solana 0.3.0 suite and identifies the expected 0.3.1 IDL hash

Consumer follow-up

After merge, publish SDK Outpost through the repository release workflow. Consumers such as Hub then update @wireio/sdk-outpost and their lockfiles; no Bearbox-specific SDK configuration is required. A same-code Sandbox respin needs a new deployment profile, not another producer artifact or SDK release.

Sandbox-specific runtime note

This specific Sandbox currently runs Solana validator/runtime 4.0.3 because 4.2.0 crashes liqsol_core in that environment. The trusted Sandbox publication path records that observed-versus-source-declared difference; the package manifest still identifies the source declaration 4.2.0. This PR does not generalize that exception beyond trusted Sandbox handoffs.