Add modern wp-build DataForm route for AI settings page

.distignore

@@ -4,8 +4,10 @@
 /.wordpress-org
 /docs
 /node_modules
+/routes
 /src
 /tests
+/tools
 
 # Files
 .*

.github/workflows/plugin-check.yml

@@ -69,5 +69,6 @@ jobs:
                       plugin_header_unsupported_plugin_name
                   exclude-directories: |
                       .github
+                      build
                       docs
                       tests

.gitignore

@@ -19,6 +19,7 @@ Thumbs.db
 # Build output
 build/
 build-module/
+build-scripts/
 build-types/
 
 # Environment

ai.php

@@ -29,6 +29,8 @@
 /**
  * Shortcut constant to the path of this file.
  */
-define( 'WPAI_DIR', plugin_dir_path( __FILE__ ) );
+if ( ! defined( 'WPAI_DIR' ) ) {
+	define( 'WPAI_DIR', plugin_dir_path( __FILE__ ) );
+}
 
 require_once WPAI_DIR . 'includes/bootstrap.php';

docs/ARCHITECTURE_OVERVIEW.md

@@ -6,7 +6,8 @@ The plugin follows a modular, experiment-based architecture:
 ```
 ai/
 ├── ai.php                            # Plugin bootstrap
-├── build/                            # Built assets
+├── build/                            # wp-build route assets
+├── build-scripts/                    # wp-scripts built assets
 ├── docs/                             # Documentation
 │   ├── experiments/                  # Experiment specific documentation
 │   ├── ARCHITECTURE_OVERVIEW.md      # Architecture Overview

docs/DEVELOPER_GUIDE.md

@@ -242,7 +242,7 @@ The plugin also includes the following action hooks:
 
 ### Asset Loading
 
-The plugin provides a utility class for loading assets. This uses `wp-scripts` to build assets which are expected to live within the `src/` directory. They will then be built into the `build/` directory, where the asset loader will look for the files, pulling in the proper dependencies and versioning.
+The plugin provides a utility class for loading assets. This uses `wp-scripts` to build assets which are expected to live within the `src/` directory. They will then be built into the `build-scripts/` directory, where the asset loader will look for the files, pulling in the proper dependencies and versioning.
 
 ```php
 use WordPress\AI\Asset_Loader;
@@ -252,7 +252,7 @@ use WordPress\AI\Asset_Loader;
  *
  * First argument is the script handle.
  * The second argument is the script file name.
- * This script file name should be in the build/ directory.
+ * This script file name should be in the build-scripts/ directory.
  * The source script files should be in the src/ directory. If needed,
  * you can add the entry point to the webpack.config.js file.
  */
@@ -263,7 +263,7 @@ Asset_Loader::enqueue_script( 'my-experiment', 'experiments/my-experiment' );
  *
  * First argument is the style handle.
  * The second argument is the style file name.
- * This style file name should be in the build/ directory.
+ * This style file name should be in the build-scripts/ directory.
  * The source style files should be in the src/ directory. If needed,
  * you can add the entry point to the webpack.config.js file.
  */

includes/Abstracts/Abstract_Feature.php

@@ -216,27 +216,11 @@ public function register_settings(): void {
 		// Child classes can override to register custom settings.
 	}
 
-	/**
-	 * Renders feature-specific settings fields.
-	 *
-	 * Override this method in child classes to render custom settings UI
-	 * that will appear within the feature's card on the settings page.
-	 * This is called after the feature's main toggle control.
-	 *
-	 * @since 0.6.0
-	 *
-	 * @return void
-	 */
-	public function render_settings_fields(): void {
-		// Default implementation does nothing.
-		// Child classes can override to render custom settings UI.
-	}
-
 	/**
 	 * Gets the option name for a custom feature setting field.
 	 *
 	 * Generates a properly namespaced option name for feature-specific settings.
-	 * Use this when registering and rendering custom settings fields to ensure
+	 * Use this when registering and storing custom settings fields to ensure
 	 * consistent naming across the plugin.
 	 *
 	 * @since 0.6.0

includes/Asset_Loader.php

@@ -37,8 +37,8 @@ class Asset_Loader {
 	 * @param array<string, mixed>|null $asset_data Optional asset metadata (dependencies and version).
 	 */
 	public static function enqueue_script( string $handle, string $file_name, ?array $asset_data = null ): void {
-		$script_path       = WPAI_PLUGIN_DIR . 'build/' . $file_name . '.js';
-		$script_url        = WPAI_PLUGIN_URL . 'build/' . $file_name . '.js';
+		$script_path       = WPAI_PLUGIN_DIR . 'build-scripts/' . $file_name . '.js';
+		$script_url        = WPAI_PLUGIN_URL . 'build-scripts/' . $file_name . '.js';
 		$script_asset_path = substr( $script_path, 0, -3 ) . '.asset.php';
 
 		// If the file doesn't exist, don't try to enqueue it.
@@ -82,8 +82,8 @@ public static function enqueue_script( string $handle, string $file_name, ?array
 	 * @param array<string, mixed>|null $asset_data Optional asset metadata (dependencies and version).
 	 */
 	public static function enqueue_style( string $handle, string $file_name, ?array $asset_data = null ): void {
-		$style_path       = WPAI_PLUGIN_DIR . 'build/' . $file_name . '.css';
-		$style_url        = WPAI_PLUGIN_URL . 'build/' . $file_name . '.css';
+		$style_path       = WPAI_PLUGIN_DIR . 'build-scripts/' . $file_name . '.css';
+		$style_url        = WPAI_PLUGIN_URL . 'build-scripts/' . $file_name . '.css';
 		$style_asset_path = substr( $style_path, 0, -4 ) . '.asset.php';
 		$handle           = 'ai_' . $handle;