[Repo Assist] Fix ofAsyncEnum deadlock on single-threaded runtimes (Blazor WASM)

[github-actions]

🤖 Repo Assist here — I'm an automated AI assistant for this repository.

Closes #152

Root Cause

AsyncSeq.ofAsyncEnum registers an IDisposable cleanup to call DisposeAsync() on the underlying IAsyncEnumerator. The previous implementation waited for disposal synchronously:

e.DisposeAsync().AsTask() |> Async.AwaitTask |> Async.RunSynchronously

On single-threaded runtimes such as Blazor WASM, Async.RunSynchronously blocks the only available thread. The DisposeAsync task then needs that same thread to complete — causing a deadlock.

Fix

Replace the blocking call with a fire-and-forget:

e.DisposeAsync() |> ignore

ValueTask starts execution immediately; ignoring the return value simply means we do not wait for it. For synchronous enumerators (the common case) the ValueTask is already complete when returned, so there is no observable difference. For asynchronous enumerators the cleanup still happens — we just do not block waiting for it, which is consistent with how IDisposable.Dispose() behaves throughout the rest of the library.

Test Status

• Build passes
• All 190 tests pass (dotnet test)

Generated by Repo Assist

To install this workflow, run gh aw add githubnext/agentics/workflows/repo-assist.md@b0296681ad309e6455276244363810b1e7d98335. View source at https://github.com/githubnext/agentics/tree/b0296681ad309e6455276244363810b1e7d98335/workflows/repo-assist.md.