Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a Go CLI that does genuinely concurrent work — e.g. a parallel URL/health checker, a directory word-counter, or a batch file processor. Launch goroutines, coordinate them with a sync.WaitGroup (or collect results over a channel), parse flags with the flag package, and handle errors as values (if err != nil). It must produce correct, deterministic output and clean up after itself.
Goroutines coordinated correctly with WaitGroup/channels; no leaked goroutines; deterministic results.
gofmt-clean; errors handled as values (no ignored err); capitalized exports where appropriate.
Flags/args parsed sensibly; usage on bad input; non-zero exit on failure.
Right output; edge cases (empty input, a failing item) don't crash the whole run.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A concurrent command-line tool ## Goal Build a Go CLI that does genuinely concurrent work — e.g. a parallel URL/health checker, a directory word-counter, or a batch file processor. Launch goroutines, coordinate them with a sync.WaitGroup (or collect results over a channel), parse flags with the flag package, and handle errors as values (if err != nil). It must produce correct, deterministic output and clean up after itself. ## Acceptance criteria - [ ] Concurrency: Goroutines coordinated correctly with WaitGroup/channels; no leaked goroutines; deterministic results. - [ ] Idiomatic Go: gofmt-clean; errors handled as values (no ignored err); capitalized exports where appropriate. - [ ] CLI: Flags/args parsed sensibly; usage on bad input; non-zero exit on failure. - [ ] Correctness: Right output; edge cases (empty input, a failing item) don't crash the whole run. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.