A goroutine runs a function concurrently with its caller. Starting one does not mean it has finished by the time the next line executes. A useful concurrent function therefore needs a completion boundary: receive a result, wait on a WaitGroup or close a channel after its producers finish. Sleeping is not that boundary. The browser uses Go's single-threaded WebAssembly scheduler, so concurrency works without promising parallel CPU execution. These exercises launch small independent jobs and collect their outputs deterministically. Keep result order separate from completion order when the caller needs the original ordering. Empty input must complete immediately, and every goroutine you start must have a way to finish. The checks compare results rather than demanding one particular scheduling order.
Receive the completed result.