feat(async): stabilize Channel

[tomas-zijdemans]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.61%. Comparing base (a496da2) to head (f9cb22e).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7123   +/-   ##
=======================================
  Coverage   94.61%   94.61%           
=======================================
  Files         634      634           
  Lines       51801    51802    +1     
  Branches     9329     9329           
=======================================
+ Hits        49011    49012    +1     
  Misses       2216     2216           
  Partials      574      574           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[fibibot]

Mechanical stabilization is clean: unstable_channel.ts → channel.ts rename, @experimental tags dropped on all symbols, ./channel export added to async/deno.json and mod.ts, example imports updated consistently, no stale unstable-channel references left. Test file rename mirrors the source. CI fully green.

Calling out for your timing call: the last API change to Channel was #7106 (options-bag constructor, split per-operation options) on 2026-04-27, ~16 days ago. That's the kind of bake window you held #7115 (interleave) back for, so flagging it explicitly rather than deciding for you.

PR body is empty — adding a one-liner on why the API is ready (or linking to the prior issue/PR thread) would help future readers.

[fibibot]

CI is green now, promoting prior review to APPROVE.

[fibibot]

@bartlomieju this is ready to merge