Sync hot-patch-6.15 into development (Phase 1 of 2)

.browserslistrc

@@ -0,0 +1 @@
+defaults and fully supports es6-module

.claude/CLAUDE.md

@@ -0,0 +1,200 @@
+# CLAUDE.md
+
+## Core Principles
+
+### Skills-First Workflow
+
+**EVERY user request follows this sequence:**
+
+Request → Load Skills → Gather Context → Execute
+
+Skills contain critical workflows and protocols not in base context.
+Loading them first prevents missing key instructions.
+
+### Planning
+
+When creating plans, always save them to: ./claude/plans/YYYY-MM-DD-<topic>.md
+Never use the default plan location. Use the ./claude/plans/ directory.
+
+### Context Management Strategy
+
+**Central AI should conserve context to extend pre-compaction capacity**:
+
+- Delegate file explorations and low-lift tasks to sub-agents
+- Reserve context for coordination, user communication, and strategic decisions
+- For straightforward tasks with clear scope: skip heavy orchestration, execute directly
+
+**Sub-agents should maximize context collection**:
+
+- Sub-agent context windows are temporary
+- After execution, unused capacity = wasted opportunity
+- Instruct sub-agents to read all relevant files, load skills, and gather examples
+
+### Routing Decision
+
+**Direct Execution**:
+
+- Simple/bounded task with clear scope
+- Single-component changes
+- Quick fixes and trivial modifications
+
+**Sub-Agent Delegation**:
+
+- Complex/multi-phase implementations
+- Tasks requiring specialized domain expertise
+- Work that benefits from isolated context
+
+**Master Orchestrator**:
+
+- Ambiguous requirements needing research
+- Architectural decisions with wide impact
+- Multi-day features requiring session management
+
+### Operational Protocols
+
+#### Agent Coordination
+
+**Parallel** (REQUIRED when applicable):
+
+- Multiple Task tool invocations in single message
+- Independent tasks execute simultaneously
+- Bash commands run in parallel
+
+**Sequential** (ENFORCE for dependencies):
+
+- Database → API → Frontend
+- Research → Planning → Implementation
+- Implementation → Testing → Security
+
+#### Quality Self-Checks
+
+Before finalizing code, verify:
+
+- All inputs have validation
+- Authentication/authorization checks exist
+- All external calls have error handling
+- Import paths verified against existing codebase examples
+
+### Coding Best Practices
+
+**Priority Order** (when trade-offs arise):
+Correctness > Maintainability > Performance > Brevity
+
+#### Task Complexity Assessment
+
+Before starting, classify:
+
+- **Trivial** (single file, obvious fix) → execute directly
+- **Moderate** (2-5 files, clear scope) → brief planning then execute
+- **Complex** (architectural impact, ambiguous requirements) → full research first
+
+Match effort to complexity. Don't over-engineer trivial tasks or under-plan complex ones.
+
+## Project Overview
+
+Gravity PDF is a WordPress plugin that generates PDF documents from Gravity Forms submissions. It has a PHP MVC backend and a React/Redux frontend for the admin UI.
+
+## Commands
+
+### JavaScript
+
+```bash
+yarn dev              # Start webpack dev server with hot reload
+yarn dev:build        # One-shot webpack build without watching
+yarn build            # Production webpack build
+yarn test:js          # Run Jest unit tests
+yarn test:js:watch    # Run Jest in watch mode
+yarn test:js -- tests/js-unit/react/sagas/fontManager.test.js  # Run single test file
+yarn test:js -- --testNamePattern="test name"                   # Run single test by name
+yarn lint:js          # ESLint check
+yarn lint:js --fix    # Auto-fix ESLint errors (e.g. JSDoc alignment)
+yarn lint:css         # Sass/CSS lint check
+yarn format           # Auto-fix JS/CSS/PHP formatting
+```
+
+### PHP
+
+```bash
+yarn test:php                           # Run PHPUnit in Docker (`yarn wp-env:integration start` required)
+yarn test:php -- --filter TestClassName # Run single test class
+yarn test:php -- --filter testMethod    # Run single test method
+yarn test:php:multisite                 # Run multisite PHPUnit tests
+composer lint                              # PHPCS check
+composer lint:fix                          # PHPCS auto-fix
+```
+
+PHP tests run inside a Docker container via `wp-env` — you cannot run PHPUnit directly. Start the environment first with `yarn wp-env:integration start`.
+
+### E2E Tests (Playwright)
+
+```bash
+yarn wp-env:e2e start    # Start dedicated E2E environment (port 8702)
+yarn test:e2e            # Run all Playwright tests (headless)
+yarn test:e2e:debug      # Open Playwright UI for interactive debugging
+```
+
+E2E tests live in `tests/playwright/` and run against a single wp-env instance on port 8702. Permalink mode is flipped per Playwright project group via `tools/playwright/global-setup.ts` (which shells out to `wp-env run cli wp option update permalink_structure`):
+- `core` project — runs `core/*` and `permalinks/*` tests under plain permalinks.
+- `core-with-permalinks` project — re-runs `permalinks/*` tests under `/%postname%/` permalinks. Depends on `core` so it runs serially after the plain-permalink pass completes.
+
+In CI, Playwright is sharded 4-ways via `--shard=N/4` (see `.github/workflows/playwright-e2e.yml`); each shard runs all setup projects against its own wp-env instance and executes its slice of the consumer projects' tests.
+
+Artifacts (screenshots, traces) are written to `tmp/artifacts/`.
+
+### Environment
+
+```bash
+yarn wp-env start                 # Start dev environment (port 8700)
+yarn wp-env:integration start     # Start PHP test environment (port 8701)
+yarn wp-env:e2e start             # Start E2E test environment (port 8702)
+yarn wp-env stop                  # Stop the default dev environment
+yarn start                        # Start dev environment + hot reload dev server
+```
+
+## Architecture
+
+### PHP Backend
+
+The plugin follows an MVC pattern bootstrapped by the `Router` class in `src/bootstrap.php`, which acts as the dependency injection container. Entry point is `pdf.php` → `src/bootstrap.php`.
+
+- **`src/Controller/`** — Request handlers (18+ controllers: forms, PDF generation, settings, fonts, templates, activation, etc.)
+- **`src/Model/`** — Business logic (PDF rendering via mPDF, settings management, merge tags, templates)
+- **`src/View/`** — Admin UI rendering; HTML templates live in `src/templates/`
+- **`src/Helper/`** — 47+ helpers including abstract base classes for options, fields, forms, logging, and fonts
+- **`vendor_prefixed/`** — Composer dependencies namespaced via `php-scoper` to avoid conflicts with other plugins
+
+Namespacing: all plugin code is under the `GFPDF\` namespace with PSR-4 autoloading.
+
+### JavaScript Frontend
+
+Three webpack bundles built from distinct entry points:
+
+| Bundle | Entry | Purpose |
+|--------|-------|---------|
+| `app.bundle.min.js` | `src/assets/js/react/gfpdf-main.js` | React app: font manager, template manager, core fonts UI |
+| `gfpdf-entries.min.js` | `src/assets/js/legacy/gfpdf-entries.js` | Legacy jQuery entry page UI |
+| `admin.min.js` | `src/assets/js/admin/bootstrap.js` | Admin settings page handlers |
+
+The React app uses Redux for state with Redux-Saga for all async side effects. Each feature area has its own reducers, sagas, actions, and API module under `src/assets/js/react/`.
+
+Legacy jQuery code coexists with the React app; they are separate bundles and do not share state.
+
+### Data Flow
+
+- **PDF generation**: Form submission → WordPress hooks → `Model_PDF` → mPDF → output file
+- **Admin settings**: Options stored in WP options table → REST API → React/Redux store → UI
+- **Sagas**: React components dispatch actions → sagas intercept → call `src/assets/js/react/api/` modules → WordPress REST endpoints → update Redux store
+
+### Testing
+
+- **PHP tests**: `tests/phpunit/` mirrors `src/` structure. Extends `WP_UnitTestCase`. Mock data in `tests/phpunit/unit-tests/Mocks/`.
+- **JS tests**: `tests/js-unit/` mirrors React source structure. Uses Jest + Enzyme. Coverage threshold: 75%.
+- **E2E tests (Playwright)**: `yarn test:e2e` — config at `tools/playwright/config.ts`. Use `yarn test:e2e:playwright` for the interactive UI mode.
+
+### Key Constraints
+
+- PRs must target the `development` branch (not `main`)
+- Each PR should contain a single commit
+- Minimum PHP 7.3 compatibility required
+- jQuery is an external (provided by WordPress); never bundle it
+- Run `composer prefix` after adding new Composer dependencies to namespace them via php-scoper

.env.example

@@ -1,4 +1,4 @@
-# Add a valid Gravity Forms license key. To run PHPUnit locally you will need an Elite License.
-GF_LICENSE=00000000000000000000000000000000
-WP_BASE_URL=http://localhost
-WP_ENV_TESTS_PORT=8889
+# Enable AI Translations
+# Usage:
+# composer run translate
+POTOMATIC_OPENAI_API_KEY=

.eslintignore

@@ -0,0 +1,4 @@
+.cache
+build
+node_modules
+vendor

.eslintrc.js

@@ -0,0 +1,47 @@
+module.exports = {
+	root: true,
+	extends: [
+		'plugin:@wordpress/eslint-plugin/recommended',
+		'plugin:jest/recommended',
+	],
+	globals: {
+		GFPDF: 'readonly',
+		Backbone: 'readonly',
+		jQuery: 'readonly',
+		gfpdf_migration_multisite_ids: 'readonly',
+		gf_vars: 'readonly',
+		tinyMCE: 'readonly',
+		gform: 'readonly',
+		ConditionalLogic: 'readonly',
+		GetFirstRuleField: 'readonly',
+		ToggleConditionalLogic: 'readonly',
+		GetRuleValuesDropDown: 'readonly',
+		QTags: 'readonly',
+		switchEditors: 'readonly',
+		getUserSetting: 'readonly',
+		wp: 'readonly',
+		gfMergeTagsObj: 'readonly',
+		form: 'readonly',
+		gform_initialize_tooltips: 'readonly',
+		_: 'readonly',
+		ClipboardJS: 'readonly',
+	},
+	rules: {
+		'no-alert': 'off',
+		'jest/no-done-callback': 'off',
+		'camelcase': 'off',
+		'jsdoc/empty-tags': ['off', { tags: ['package'] }],
+    '@typescript-eslint/no-unused-vars': 'off'
+	},
+  settings: {
+    jsdoc: {
+      mode: 'closure',
+    },
+    "import/resolver": {
+      node: {
+        extensions: ['.js', '.jsx', '.ts', '.tsx'],
+      },
+      "typescript": {}
+    }
+  },
+};

.gitattributes

@@ -1,16 +1,4 @@
-/.coveralls.yml	export-ignore
-/.eslintrc export-ignore
-/.gitattributes export-ignore
-/.gitignore export-ignore
 /.github export-ignore
-/.docker export-ignore
-/jest.config.js export-ignore
-/node_modules export-ignore
-/phpcs.xml.dist export-ignore
-/phpcompat.xml.dist export-ignore
-/phpunit.xml.dist export-ignore
-/.env.example export-ignore
 /tests export-ignore
-/tmp export-ignore
 
-*.sh eol=lf
+*.sh eol=lf

.github/README.md

@@ -3,7 +3,7 @@ Gravity PDF
 
 [![codecov](https://codecov.io/gh/GravityPDF/gravity-pdf/branch/development/graph/badge.svg)](https://codecov.io/gh/GravityPDF/gravity-pdf)
 
-Gravity PDF is a GPLv2-licensed WordPress plugin that allows you to automatically generate, email and download PDF documents using the popular form-builder plugin, [Gravity Forms](https://rocketgenius.pxf.io/c/1211356/445235/7938) (affiliate link). Find out more about Gravity PDF at [https://gravitypdf.com](https://gravitypdf.com/).
+Gravity PDF is a GPLv2-licensed WordPress plugin that allows you to automatically generate, email and download PDF documents using the popular form-builder plugin, [Gravity Forms](https://gpdf.us/gf) (affiliate link). Find out more about Gravity PDF at [https://gravitypdf.com](https://gravitypdf.com/).
 
 # About
 
@@ -25,11 +25,11 @@ The Docker setup will create a fully functional development environment preconfi
 
 1. Clone the repository using `git clone https://github.com/GravityPDF/gravity-pdf/` from the terminal
 2. Copy and rename `.env.example` to `.env`, then replace `00000000000000000000000000000000` with a valid Gravity Forms license key 
-3. Run `yarn && yarn build:production`
-4. Start Docker and then run `yarn env:install` to setup the local development environment
+3. Run `composer install`
+3. Run `yarn && yarn start`
 5. Access a local development site at `http://localhost:8888` with the login `admin` and `password`.
 
-If you shut down Docker and want to fire up the environment later, use `yarn wp-env start`. You can reset the database back to its original state with `yarn wp-env clean all`. When all else fails, delete everything and start again with `yarn wp-env destroy`.
+You can reset the database back to its original state with `yarn wp-env clean all`. When all else fails, delete everything and start again with `yarn wp-env destroy`.
 
 [See the WordPress Developer Handbook for more details about managing the docker environment](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-env/#wp-env-run-container-command).
 
@@ -39,26 +39,21 @@ X-Debug is enabled by default for step debugging and profiling. If you need to [
 
 ### Switch PHP Versions
 
-The default version that will be configured is PHP8.0. If you want to change this you can adjust the `phpVersion` value in the `.wp-env.json` file and then stop and start the environment with `yarn wp-env start`.
-
-## Setup without Docker
-
-If you would rather use your own development environment, you can build Gravity PDF using the following commands. 
-
-1. Clone the repository using `git clone https://github.com/GravityPDF/gravity-pdf/`
-1. Run `yarn && yarn build:production`
-1. Run `composer install`
-1. Run `composer run prefix`
+The default version that will be configured is PHP8.3. If you want to change this you can adjust the `phpVersion` value in the `.wp-env.json` file and then stop and start the environment with `yarn wp-env start`.
 
 ## Building JavaScript
 
-If you are making changes to any of the JavaScript or CSS, run `yarn build:dev` to ensure the files automatically gets built when you make changes on the file system.
+If you are making changes to any of the JavaScript or CSS, run `yarn dev` to ensure the files automatically gets built when you make changes on the file system.
 
 ## Linting
 
-To lint your JS code use `yarn lint:js`, and to try automatically fix it use `yarn lint:js:fix`.
+To lint your:
+
+1. JS code using `yarn lint:js`
+2. CSS code using `yarn lint:css`
+3. PHP code using `composer lint`
 
-To lint your PHP code, use `composer lint`, and to try automatically fix it use `composer lint:fix`.
+You can auto-fix many issues with `yarn format` and `composer lint:fix`.
 
 ## Automated Tests