address review: fix trailing commas in workflows and docs precision

- Use conditional expressions in qsvmcp/qsvlite build steps to avoid
  trailing commas when addl-qsvlite-features is empty
- Move MALLOC_CONF from "always included" to jemalloc-specific in env
  vars docs to match the actual code behavior
- Narrow jemalloc unsupported target note to just Windows (not arm)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: jqnatividad

.github/workflows/publish-nightly.yml

@@ -101,7 +101,7 @@ jobs:
         command: build
         use-cross: false
         toolchain: ${{ matrix.rust }}
-        args: --profile release-nightly --bin qsvmcp -Z build-std=std --features=qsvmcp,nightly,${{ matrix.job.addl-qsvlite-features }} --target ${{ matrix.job.target }} ${{ matrix.job.default-features }}
+        args: --profile release-nightly --bin qsvmcp -Z build-std=std ${{ matrix.job.addl-qsvlite-features != '' && format('--features=qsvmcp,nightly,{0}', matrix.job.addl-qsvlite-features) || '--features=qsvmcp,nightly' }} --target ${{ matrix.job.target }} ${{ matrix.job.default-features }}
     # TODO: Add qsvdp-nightly build back in after v5.0.3, be sure to copy qsvdp binaries below
     # - name: Build qsvdp-nightly
     #   env:

.github/workflows/publish-portable.yml

@@ -193,7 +193,7 @@ jobs:
         command: build
         use-cross: ${{ matrix.job.use-cross }}
         toolchain: ${{ matrix.rust }}
-        args: --release --locked --bin qsvmcp --features=qsvmcp,${{ matrix.job.addl-qsvlite-features }} --target ${{ matrix.job.target }} ${{ matrix.job.default-features }}
+        args: --release --locked --bin qsvmcp ${{ matrix.job.addl-qsvlite-features != '' && format('--features=qsvmcp,{0}', matrix.job.addl-qsvlite-features) || '--features=qsvmcp' }} --target ${{ matrix.job.target }} ${{ matrix.job.default-features }}
     - name: Copy binaries to working dir
       shell: bash
       run: |

.github/workflows/publish.yml

@@ -208,7 +208,7 @@ jobs:
         command: build
         use-cross: ${{ matrix.job.use-cross }}
         toolchain: ${{ matrix.rust }}
-        args: --release --locked --bin qsvmcp --features=qsvmcp,${{ matrix.job.addl-qsvlite-features }} --target ${{ matrix.job.target }} ${{ matrix.job.default-features }}
+        args: --release --locked --bin qsvmcp ${{ matrix.job.addl-qsvlite-features != '' && format('--features=qsvmcp,{0}', matrix.job.addl-qsvlite-features) || '--features=qsvmcp' }} --target ${{ matrix.job.target }} ${{ matrix.job.default-features }}
     - name: Copy binaries to working dir
       shell: bash
       run: |

.github/workflows/test-publish-nightly.yml

@@ -89,7 +89,7 @@ jobs:
         command: build
         use-cross: false
         toolchain: ${{ matrix.rust }}
-        args: --profile release-nightly --bin qsvlite -Z build-std=std,panic_abort -Z build-std-features=panic_immediate_abort --features=lite,self_update,${{ matrix.job.addl-qsvlite-features }} --target ${{ matrix.job.target }} ${{ matrix.job.default-features }}
+        args: --profile release-nightly --bin qsvlite -Z build-std=std,panic_abort -Z build-std-features=panic_immediate_abort ${{ matrix.job.addl-qsvlite-features != '' && format('--features=lite,self_update,{0}', matrix.job.addl-qsvlite-features) || '--features=lite,self_update' }} --target ${{ matrix.job.target }} ${{ matrix.job.default-features }}
     - name: Build qsvdp-nightly
       env:
         RUSTFLAGS: --emit=asm

docs/ENVIRONMENT_VARIABLES.md

@@ -78,7 +78,7 @@ Several dependencies also have environment variables that influence qsv's perfor
   * `POLARS_BACKTRACE_IN_ERR` - if set to 1, includes backtrace in polars-related error messages.
 
 > ℹ️ **NOTE:** To get a list of all active qsv-relevant environment variables, run `qsv --envlist`.
-Relevant env vars always include anything that starts with `QSV_`, `MALLOC_CONF` & the proxy variables listed above. Allocator-specific env vars are build-dependent: `MIMALLOC_` vars are included when qsv is built with mimalloc support, and `JEMALLOC_` vars are included when qsv is built with jemalloc support.
+Relevant env vars always include anything that starts with `QSV_` & the proxy variables listed above. Allocator-specific env vars are build-dependent: `MIMALLOC_` vars are included when qsv is built with mimalloc support, and `JEMALLOC_` & `MALLOC_CONF` vars are included when qsv is built with jemalloc support.
 
 ## MCP Server Environment Variables
 

docs/PERFORMANCE.md

@@ -129,7 +129,7 @@ or
 cargo build --release --no-default-features --features all_features
 ```
 
-To find out what memory allocator qsv is using, run `qsv --version`. After the qsv version number, the allocator used is displayed ("`standard`", "`mimalloc`" or "`jemalloc`"). Note that jemalloc is not supported on Windows and `arm` targets, and you'll need to use the "mimalloc" or "standard" allocator on those platforms.
+To find out what memory allocator qsv is using, run `qsv --version`. After the qsv version number, the allocator used is displayed ("`standard`", "`mimalloc`" or "`jemalloc`"). Note that jemalloc is not supported on Windows targets, and you'll need to use the "mimalloc" or "standard" allocator on those platforms.
 
 ### Out-of-Memory (OOM) Prevention
 Most qsv commands use a "streaming" approach to processing CSVs - "streaming" in the input record-by-record while processing it. This allows it to process arbitrarily large CSVs with constant memory.