Remove composer; set up wp-env test environment

Co-authored-by: dd32 <767313+dd32@users.noreply.github.com>

Author: Copilot

.gitignore

@@ -0,0 +1,3 @@
+vendor/
+node_modules/
+.wp-env/

.wp-env.json

@@ -0,0 +1,6 @@
+{
+    "plugins": ["."],
+    "mappings": {
+        "wp-cli.yml": "./wp-cli.yml"
+    }
+}

composer.json

@@ -18,8 +18,5 @@
         ]
     },
     "minimum-stability": "dev",
-    "prefer-stable": true,
-    "require-dev": {
-        "wp-cli/cron-command": "^2.3"
-    }
+    "prefer-stable": true
 }

cron-concurrent.php

@@ -3,7 +3,8 @@
 /**
  * WP-CLI Cron Concurrent – entry point.
  *
- * Loaded automatically by WP-CLI when this package is installed.
+ * Loaded automatically by WP-CLI when this package is installed via Composer,
+ * or explicitly via `--require` / a `wp-cli.yml` require entry.
  * Registers the `wp cron-concurrent` command group.
  *
  * @package dd32/wpcli-cron-concurrent
@@ -13,9 +14,11 @@
 	return;
 }
 
-$autoloader = __DIR__ . '/vendor/autoload.php';
-if ( file_exists( $autoloader ) ) {
-	require_once $autoloader;
+// When installed as a Composer package the classmap autoloader already
+// handles this file; the direct require is only a safety-net for manual
+// --require usage (e.g. inside wp-env test containers).
+if ( ! class_exists( 'CronConcurrent' ) ) {
+	require_once __DIR__ . '/src/CronConcurrent.php';
 }
 
 WP_CLI::add_command( 'cron-concurrent', 'CronConcurrent' );