fix: correct concurrency resolution order in docs and comments

--parallel takes priority over VP_RUN_CONCURRENCY_LIMIT, not the
other way around. The code was correct; the docs and comments were
not.

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

Author: branchseer

crates/vite_task_plan/src/plan.rs

@@ -679,8 +679,8 @@ pub async fn plan_query_request(
     //
     // Priority (highest to lowest):
     // 1. `--concurrency-limit N` CLI flag
-    // 2. `VP_RUN_CONCURRENCY_LIMIT` env var
-    // 3. `--parallel` (without the above) → unlimited
+    // 2. `--parallel` (without the above) → unlimited
+    // 3. `VP_RUN_CONCURRENCY_LIMIT` env var
     // 4. `DEFAULT_CONCURRENCY_LIMIT` (4)
     let effective_concurrency = match plan_options.concurrency_limit {
         Some(n) => n,

docs/concurrency.md

@@ -54,6 +54,6 @@ Equivalent flags in other tools:
 The concurrency limit is resolved in this order (first match wins):
 
 1. `--concurrency-limit` CLI flag
-2. `VP_RUN_CONCURRENCY_LIMIT` env var
-3. `--parallel` without the above → unlimited
+2. `--parallel` without the above → unlimited
+3. `VP_RUN_CONCURRENCY_LIMIT` env var
 4. Default: 4