Drop redundant -- before bare wp-env-test subcommands

Use `npm run wp-env-test start` (etc.) to match the existing
`npm run wp-env start` convention, keeping `--` only where a flag is
passed through to wp-env (e.g. `start -- --xdebug=coverage`,
`run cli -- --env-cwd=...`).

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

Author: westonruter

.github/workflows/copilot-setup-steps.yml

@@ -65,4 +65,4 @@ jobs:
       - name: Install WordPress and start environments
         run: |
           npm run wp-env start
-          npm run wp-env-test -- start
+          npm run wp-env-test start

.github/workflows/e2e-test.yml

@@ -57,7 +57,7 @@ jobs:
         run: npx playwright install chromium --with-deps
 
       - name: Install WordPress
-        run: npm run wp-env-test -- start
+        run: npm run wp-env-test start
 
       - name: Run tests
         env:

.github/workflows/php-test-plugins.yml

@@ -85,12 +85,12 @@ jobs:
       - name: Install WordPress
         run: |
           if [ "${{ matrix.coverage }}" == "true" ]; then
-            npm run wp-env-test -- start --xdebug=coverage
+            npm run wp-env-test start -- --xdebug=coverage
           else
-            npm run wp-env-test -- start
+            npm run wp-env-test start
           fi
       - name: Composer Install
-        run: npm run wp-env-test -- run cli --env-cwd="wp-content/plugins/$(basename $(pwd))" composer install --no-interaction --no-progress
+        run: npm run wp-env-test run cli -- --env-cwd="wp-content/plugins/$(basename $(pwd))" composer install --no-interaction --no-progress
       - name: Update Composer Dependencies
         run: composer update --with-all-dependencies --no-interaction --no-progress
       - name: Install PHPUnit

AGENTS.md

@@ -46,12 +46,12 @@ each defined by its own config file and running as fully isolated containers:
 
 The `wp-env-test` script is shorthand for `wp-env --config=.wp-env.test.json`.
 
-* Check if the environments are running: `npm run wp-env status` / `npm run wp-env-test -- status`
-* Start the environments: `npm run wp-env start` / `npm run wp-env-test -- start`
-* Stop the environments: `npm run wp-env stop` / `npm run wp-env-test -- stop`
+* Check if the environments are running: `npm run wp-env status` / `npm run wp-env-test status`
+* Start the environments: `npm run wp-env start` / `npm run wp-env-test start`
+* Stop the environments: `npm run wp-env stop` / `npm run wp-env-test stop`
 
 The `test-php*` and `test-e2e*` scripts run against the tests environment, so
-start it with `npm run wp-env-test -- start` before running them.
+start it with `npm run wp-env-test start` before running them.
 
 Each environment can be overridden locally (these files are git-ignored):
 `.wp-env.override.json` for development and `.wp-env.test.override.json` for tests.