Pattern creator: use createRoot for React 18/19 forward compatibility

AGENTS.md

@@ -0,0 +1,57 @@
+# AGENTS.md
+
+## What this is
+
+The codebase for **wordpress.org/patterns** — the WordPress.org Block Pattern Directory site. It is a meta-environment monorepo: WordPress core, third-party plugins, and shared WordPress.org themes/mu-plugins are pulled in via Composer, while the project's own code lives in three npm workspaces under `public_html/wp-content/`.
+
+## Setup & environment
+
+Requires Docker, Node/npm, and Composer.
+
+- `npm run create` — full first-time bootstrap (`bin/index.sh`): runs `composer update`, `npm install`, builds all workspaces, starts wp-env, activates plugins/theme, sets permalinks, and imports seed pattern content. Site comes up at `localhost:8888`.
+- `npm run wp-env start` / `npm run wp-env stop` — bring the environment up/down. **Always run from the repo root** (where `.wp-env.json` lives), or wp-env spins up a stray instance in a sub-project.
+- `npm run wp-env run cli "<wp-cli command>"` — run WP-CLI against the site, e.g. `npm run wp-env run cli "plugin list"`.
+- The local environment runs **WordPress trunk on PHP 8.1** (`.wp-env.json`); Composer's `platform.php` is pinned to 7.4 for dependency resolution, so PHP code must stay 7.4-compatible.
+
+## Build, lint, test
+
+These are npm-workspace commands — most run per-workspace via `--workspaces` or `--workspace=<name>`.
+
+- **Build:** `npm run build --workspaces` (all), or the convenience scripts `npm run build:creator` / `build:directory` / `build:theme`.
+- **Watch:** `npm start --workspace=<name>` — one workspace at a time. Convenience: `npm run start:creator` etc.
+- **Lint JS/CSS:** `npm run lint:js --workspaces` and `npm run lint:css --workspaces`.
+- **Lint/format PHP:** `npm run lint:php` (= `composer run lint` = `phpcs`), `npm run format:php` (= `phpcbf`). Config in `phpcs.xml.dist` (WordPress coding standards).
+- **PHP tests:** `npm run test:php` — runs PHPUnit inside the `tests-cli` container as **multisite** (`WP_TESTS_MULTISITE=1`). Suite config: `public_html/wp-content/tests/phpunit/phpunit.xml`; tests live in `public_html/wp-content/plugins/pattern-directory/tests/phpunit/` (files suffixed `-test.php`).
+- **JS tests:** `npm run test:unit --workspace=wporg-pattern-creator` (Jest via wp-scripts). The directory plugin and theme have no JS tests.
+- Run a single PHP test: `npm run wp-env run tests-cli --env-cwd=/var/www/html/ ./vendor/bin/phpunit -c wp-content/tests/phpunit/phpunit.xml --filter <TestNameOrMethod>`.
+
+CI (`.github/workflows/`) runs linters on every PR and PHP+JS unit tests on changes under `public_html/`. The default branch is **`trunk`**.
+
+## Workspaces & architecture
+
+Three workspaces, each a standard `@wordpress/scripts` project extending the root `eslint.config.js` / `.stylelintrc` / `.prettierrc.js`:
+
+| Workspace | Path | Role |
+|---|---|---|
+| `wporg-pattern-directory` | `plugins/pattern-directory` | Core data layer (PHP-heavy) |
+| `wporg-pattern-creator` | `plugins/pattern-creator` | Front-end pattern editor (React/JS-heavy) |
+| `wporg-pattern-directory-2024-theme` | `themes/wporg-pattern-directory-2024` | Block theme for the site |
+
+(`plugins/pattern-translations` is a fourth plugin, not a JS workspace.)
+
+**pattern-directory** is the backbone. Entry point `bootstrap.php` wires up everything via `includes/`: the `wporg-pattern` custom post type and `wporg-pattern-flag` post type, pattern validation, search, favorites, stats, badges, notifications, admin screens, and two REST controllers (`class-rest-flags-controller.php`, `class-rest-favorite-controller.php`). The single JS bundle (`src/pattern-post-type.js`) augments the block-editor admin experience for patterns.
+
+**pattern-creator** is a front-end SPA-style block editor (`pattern-creator.php` enqueues the build of `src/index.js`) letting logged-in users create/edit patterns on the site front end. It uses a `@wordpress/data` store (`src/store`), an `api-middleware` layer, React components, and hooks — a substantial subset of Gutenberg editor packages as dependencies.
+
+**pattern-translations** imports pattern strings into GlotPress and serves translated patterns. It depends on the directory plugin's `POST_TYPE` constant and runs scheduled cron + WP-CLI commands. The `i18n.yml` workflow regenerates translation strings twice daily and commits them to `trunk`.
+
+### How the pieces fit
+
+The directory plugin owns the pattern data model and APIs; the creator plugin is a front-end client that writes patterns through those APIs; the theme renders the public directory; the translations plugin localizes pattern content. All four share the `WordPressdotorg\Pattern_Directory\*` PHP namespaces and the `wporg-patterns` text domain.
+
+Composer pulls shared WordPress.org infrastructure (`wporg-mu-plugins`, `wporg-parent-2021` parent theme, `wporg-internal-notes`, the `wporg` meta theme/mu-plugin from meta SVN) plus Gutenberg, Stream, and the WordPress Importer. Composer's `installer-paths` place these into `public_html/wp-content/{plugins,themes,mu-plugins}/`.
+
+## Conventions
+
+- WordPress PHP coding standards (`phpcs.xml.dist`); keep PHP 7.4-compatible.
+- Per-project `.editorconfig` and the shared root JS/CSS lint configs govern style — run the linters before pushing; CI enforces them.

CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

composer.json

@@ -67,7 +67,7 @@
 	],
 	"require": {
 		"composer/installers": "~1.0",
-		"wpackagist-plugin/gutenberg": "*",
+		"wpackagist-plugin/gutenberg": "23.3.0",
 		"wpackagist-plugin/stream": "*",
 		"wpackagist-plugin/wordpress-importer": "*",
 		"wordpress-meta/wporg": "1",

eslint.config.js

@@ -0,0 +1,16 @@
+/**
+ * External dependencies
+ */
+const wpScriptsConfig = require( '@wordpress/scripts/config/eslint.config.cjs' );
+
+module.exports = [
+	...wpScriptsConfig,
+	{
+		rules: {
+			'@wordpress/i18n-text-domain': [
+				'error',
+				{ allowedTextDomain: [ 'wporg-patterns' ] },
+			],
+		},
+	},
+];