docs: document CI workflow and SIMD runner setup (#85)

* docs: document CI workflow and SIMD runner setup

Clarify that PR CI falls back to scalar while AVX-512 benchmarks run on the self-hosted runner only.

* docs: move CI details under Contributing

Keep Requirements focused on runtime needs and link to Contributing from Performance.

Author: nnnkkk7

README.md

@@ -95,7 +95,7 @@ reader := csv.NewReaderWithOptions(r, csv.ReaderOptions{
 
 ## Performance
 
-Benchmarks on AMD EPYC 9R14 with AVX-512 (Go 1.26, `GOEXPERIMENT=simd`).
+Benchmarks on AMD EPYC 9R14 with AVX-512 (Go 1.26, `GOEXPERIMENT=simd`). See [Contributing](#contributing) for the CI setup.
 
 ### ReadAll Throughput
 
@@ -160,6 +160,19 @@ GOEXPERIMENT=simd go test -bench=. -benchmem
 
 Contributions are welcome! Please open issues or pull requests on GitHub.
 
+### CI
+
+This repository runs two GitHub Actions workflows:
+
+| Workflow | Trigger | Runner | SIMD acceleration |
+|----------|---------|--------|-------------------|
+| [`ci.yml`](.github/workflows/ci.yml) | Every pull request | GitHub-hosted `ubuntu-latest` | No (scalar fallback) |
+| [`ci-avx512.yml`](.github/workflows/ci-avx512.yml) | Manual only | Self-hosted (`avx512`) | Yes |
+
+Pull request checks use `ubuntu-latest`, which typically lacks AVX-512. Tests still pass because the library falls back to the scalar path when SIMD instructions are unavailable.
+
+AVX-512 benchmarks and SIMD validation run only on the self-hosted runner via **AVX-512 CI**. Trigger it manually from the Actions tab when you need real SIMD test and benchmark results.
+
 ## License
 
 MIT License - see [LICENSE](LICENSE) file for details.