feat(release): add Studio dev preview channel

[MuncleUscles]

Delivery context

No cross-repository code dependency. The CLI RC-prep PR will depend on this PR and pin its exact published commit.

Problem and outcome

The Consensus v0.6 / Studio v0.123 candidate needs an explicit preview network without silently moving stable Studionet. The existing npm workflow also published every tag to latest, which made prereleases unsafe.

This adds studioDevnet for the canonical Studio-dev RPC and makes prerelease publication select a validated npm channel and GitHub prerelease state. Stable studionet remains chain 61999 at studio.genlayer.com.

Implementation and validation

• Export studioDevnet with chain ID 61997 and https://studio-dev.genlayer.com/api.
• Reuse the deployed Studio consensus addresses while keeping the preview chain identity separate.
• Add the preview network to wallet connection and public network types/docs.
• Resolve release channels in a directly tested script.
• Publish 2.0.0-rc.1 under npm dist-tag rc, never latest.
• Mark prerelease GitHub releases explicitly and reject mismatched or unsafe tags.

Validated locally:

• full unit suite: 191/191
• production build
• focused chain and release-channel regression tests
• git diff --check

Planned prerelease after merge: v2.0.0-rc.1 from v2-dev.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 86dc6276-3913-44c0-9923-c6e15a222c16

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[MuncleUscles]

/merge

Queue this dependency-free RC-prep change after its native landing gates are green. No full cross-stack E2E is requested for network metadata and release-channel policy.

[ci-core-e2e-runner]

/merge was not queued.

The App could not find a current E2E Merge Train check for this exact PR head (d09b781d0cd8).
Run /run-e2e and wait for the full E2E result. A green exact-snapshot run should create the merge action; if E2E is already green, follow the E2E workflow because its landing proof did not reconcile successfully.