From d18e77c16fc7a0d12170b940e556e1d13a3c962f Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 18:51:22 +0000
Subject: [PATCH 1/5] Initial plan


From 718acafed092da30539bb244b9aa9248e59d2c1c Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 15 Jan 2026 18:53:51 +0000
Subject: [PATCH 2/5] Add GitHub Copilot instructions file

Co-authored-by: westonruter <134745+westonruter@users.noreply.github.com>
---
 .github/copilot-instructions.md | 89 +++++++++++++++++++++++++++++++++
 1 file changed, 89 insertions(+)
 create mode 100644 .github/copilot-instructions.md

diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 0000000000..3df0fdce70
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,89 @@
+# Copilot Instructions for Performance Lab
+
+This repository is a monorepo for the WordPress Performance Team, containing a collection of standalone performance feature plugins. When contributing to this project, follow these guidelines:
+
+## Project Structure
+
+- `/plugins/*` - Individual WordPress plugin folders
+- `/plugins/*/tests` - PHPUnit tests for each plugin
+- `/bin` - Custom CLI commands and scripts
+- `/tools` - Setup and configuration files for linting and testing
+
+## Code Style Standards
+
+### PHP
+- Follow [WordPress PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
+- Use procedural programming patterns (classes play a supporting role)
+- Do NOT use namespaces (following WordPress core conventions)
+- Use the most specific PHP type hints compatible with PHP 7.2+
+- For filter functions, accept `mixed` union types and validate at runtime
+- Use PHPStan's PHPDoc Types (level 10 compliance)
+- Never render `<script>` tags directly in HTML; use WordPress script APIs (`wp_enqueue_script()`, `wp_enqueue_script_module()`, etc.)
+- Favor script modules over classic scripts
+
+### JavaScript
+- Follow [WordPress JavaScript Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/)
+- Use ES modules (runnable without build step)
+- Write plain JavaScript, not TypeScript
+- Use JSDoc comments with [TypeScript types](https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html)
+- Format with Prettier using `wp-prettier` with `--paren-spacing` option
+
+### HTML
+- Follow [WordPress HTML Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/html/)
+- Do NOT self-close void tags (use `<br>` not `<br />`)
+
+### Documentation
+- Use `@since n.e.x.t` for new code (replaced at release time)
+- Every file, function, class, method, constant, and global variable needs a docblock with `@since` tag
+- Follow [WordPress inline documentation standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/)
+
+### Formatting
+- Use tabs for indentation (see `.editorconfig`)
+
+## Development Commands
+
+### Setup
+```bash
+npm install
+composer install
+npm run build
+```
+
+### Building
+- Build JS/CSS assets: `npm run build`
+- Build all plugins: `npm run build-plugins`
+- Build specific plugin: `npm run build:plugin:<plugin-slug>`
+- Build ZIP files: `npm run build-plugins:zip`
+
+### Linting & Static Analysis
+- Lint JavaScript: `npm run lint-js`
+- Lint PHP: `npm run lint-php`
+- Format JavaScript: `npm run format-js`
+- Format PHP: `npm run format-php`
+- PHPStan: `npm run phpstan`
+- TypeScript checking: `npm run tsc`
+
+### Testing
+- PHPUnit tests: `npm run test-php`
+- PHPUnit multisite: `npm run test-php-multisite`
+- E2E tests: `npm run test-e2e`
+
+### Local Environment
+- Uses `@wordpress/env` (default: http://localhost:8888)
+- Start: `npm run wp-env start`
+- Stop: `npm run wp-env stop`
+- Check status: `npm run wp-env status`
+
+## Key Requirements
+
+- Minimum WordPress version: 6.5
+- Minimum PHP version: 7.2
+- All contributions released under GPLv2+ license
+- Disclose AI tool usage in pull requests
+
+## Additional Resources
+
+For comprehensive documentation, see:
+- [AGENTS.md](../AGENTS.md) - Detailed project documentation for AI agents
+- [Performance Lab Handbook](https://make.wordpress.org/performance/handbook/performance-lab/)
+- [CONTRIBUTING.md](../CONTRIBUTING.md)

From 1ea1a5b6d3d27dd0f707e17eb6e758e34e67e18f Mon Sep 17 00:00:00 2001
From: Weston Ruter <weston@ruter.net>
Date: Sun, 1 Feb 2026 16:18:51 -0800
Subject: [PATCH 3/5] Refer to AGENTS.md

---
 .github/copilot-instructions.md | 90 +--------------------------------
 1 file changed, 1 insertion(+), 89 deletions(-)

diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
index 3df0fdce70..d6f4afe9eb 100644
--- a/.github/copilot-instructions.md
+++ b/.github/copilot-instructions.md
@@ -1,89 +1 @@
-# Copilot Instructions for Performance Lab
-
-This repository is a monorepo for the WordPress Performance Team, containing a collection of standalone performance feature plugins. When contributing to this project, follow these guidelines:
-
-## Project Structure
-
-- `/plugins/*` - Individual WordPress plugin folders
-- `/plugins/*/tests` - PHPUnit tests for each plugin
-- `/bin` - Custom CLI commands and scripts
-- `/tools` - Setup and configuration files for linting and testing
-
-## Code Style Standards
-
-### PHP
-- Follow [WordPress PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
-- Use procedural programming patterns (classes play a supporting role)
-- Do NOT use namespaces (following WordPress core conventions)
-- Use the most specific PHP type hints compatible with PHP 7.2+
-- For filter functions, accept `mixed` union types and validate at runtime
-- Use PHPStan's PHPDoc Types (level 10 compliance)
-- Never render `<script>` tags directly in HTML; use WordPress script APIs (`wp_enqueue_script()`, `wp_enqueue_script_module()`, etc.)
-- Favor script modules over classic scripts
-
-### JavaScript
-- Follow [WordPress JavaScript Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/)
-- Use ES modules (runnable without build step)
-- Write plain JavaScript, not TypeScript
-- Use JSDoc comments with [TypeScript types](https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html)
-- Format with Prettier using `wp-prettier` with `--paren-spacing` option
-
-### HTML
-- Follow [WordPress HTML Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/html/)
-- Do NOT self-close void tags (use `<br>` not `<br />`)
-
-### Documentation
-- Use `@since n.e.x.t` for new code (replaced at release time)
-- Every file, function, class, method, constant, and global variable needs a docblock with `@since` tag
-- Follow [WordPress inline documentation standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/)
-
-### Formatting
-- Use tabs for indentation (see `.editorconfig`)
-
-## Development Commands
-
-### Setup
-```bash
-npm install
-composer install
-npm run build
-```
-
-### Building
-- Build JS/CSS assets: `npm run build`
-- Build all plugins: `npm run build-plugins`
-- Build specific plugin: `npm run build:plugin:<plugin-slug>`
-- Build ZIP files: `npm run build-plugins:zip`
-
-### Linting & Static Analysis
-- Lint JavaScript: `npm run lint-js`
-- Lint PHP: `npm run lint-php`
-- Format JavaScript: `npm run format-js`
-- Format PHP: `npm run format-php`
-- PHPStan: `npm run phpstan`
-- TypeScript checking: `npm run tsc`
-
-### Testing
-- PHPUnit tests: `npm run test-php`
-- PHPUnit multisite: `npm run test-php-multisite`
-- E2E tests: `npm run test-e2e`
-
-### Local Environment
-- Uses `@wordpress/env` (default: http://localhost:8888)
-- Start: `npm run wp-env start`
-- Stop: `npm run wp-env stop`
-- Check status: `npm run wp-env status`
-
-## Key Requirements
-
-- Minimum WordPress version: 6.5
-- Minimum PHP version: 7.2
-- All contributions released under GPLv2+ license
-- Disclose AI tool usage in pull requests
-
-## Additional Resources
-
-For comprehensive documentation, see:
-- [AGENTS.md](../AGENTS.md) - Detailed project documentation for AI agents
-- [Performance Lab Handbook](https://make.wordpress.org/performance/handbook/performance-lab/)
-- [CONTRIBUTING.md](../CONTRIBUTING.md)
+Please see [AGENTS.md](../AGENTS.md).

From bbb0f56048dbf8b792602bf43033230ce0d38dea Mon Sep 17 00:00:00 2001
From: Weston Ruter <weston@ruter.net>
Date: Sun, 1 Feb 2026 16:28:36 -0800
Subject: [PATCH 4/5] Copy copilot-setup-steps.yml from GitHub docs

See https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment#preinstalling-tools-or-dependencies-in-copilots-environment
---
 .github/workflows/copilot-setup-steps.yml | 38 +++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 .github/workflows/copilot-setup-steps.yml

diff --git a/.github/workflows/copilot-setup-steps.yml b/.github/workflows/copilot-setup-steps.yml
new file mode 100644
index 0000000000..7b5d87787a
--- /dev/null
+++ b/.github/workflows/copilot-setup-steps.yml
@@ -0,0 +1,38 @@
+name: "Copilot Setup Steps"
+
+# Automatically run the setup steps when they are changed to allow for easy validation, and
+# allow manual testing through the repository's "Actions" tab
+on:
+  workflow_dispatch:
+  push:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+  pull_request:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+
+jobs:
+  # The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.
+  copilot-setup-steps:
+    runs-on: ubuntu-latest
+
+    # Set the permissions to the lowest permissions possible needed for your steps.
+    # Copilot will be given its own token for its operations.
+    permissions:
+      # If you want to clone the repository as part of your setup steps, for example to install dependencies, you'll need the `contents: read` permission. If you don't clone the repository in your setup steps, Copilot will do this for you automatically after the steps complete.
+      contents: read
+
+    # You can define any steps you want, and they will run before the agent starts.
+    # If you do not check out your code, Copilot will do this for you.
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: "npm"
+
+      - name: Install JavaScript dependencies
+        run: npm ci

From f057022df945667b80be914cde242c9f7b0d0a1a Mon Sep 17 00:00:00 2001
From: Weston Ruter <weston@ruter.net>
Date: Sun, 1 Feb 2026 16:36:31 -0800
Subject: [PATCH 5/5] Customize copilot-setup-steps.yml

---
 .github/workflows/copilot-setup-steps.yml | 37 ++++++++++++++++++-----
 1 file changed, 30 insertions(+), 7 deletions(-)

diff --git a/.github/workflows/copilot-setup-steps.yml b/.github/workflows/copilot-setup-steps.yml
index 7b5d87787a..4a79b98aab 100644
--- a/.github/workflows/copilot-setup-steps.yml
+++ b/.github/workflows/copilot-setup-steps.yml
@@ -1,4 +1,4 @@
-name: "Copilot Setup Steps"
+name: 'Copilot Setup Steps'
 
 # Automatically run the setup steps when they are changed to allow for easy validation, and
 # allow manual testing through the repository's "Actions" tab
@@ -22,17 +22,40 @@ jobs:
       # If you want to clone the repository as part of your setup steps, for example to install dependencies, you'll need the `contents: read` permission. If you don't clone the repository in your setup steps, Copilot will do this for you automatically after the steps complete.
       contents: read
 
-    # You can define any steps you want, and they will run before the agent starts.
-    # If you do not check out your code, Copilot will do this for you.
     steps:
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Set up Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
         with:
-          node-version: "20"
-          cache: "npm"
+          node-version-file: '.nvmrc'
+          cache: npm
+
+      - name: Install pre-commit hook
+        run: npx husky
 
       - name: Install JavaScript dependencies
         run: npm ci
+
+      - uses: shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1 # 2.36.0
+        with:
+          php-version: latest
+
+      - name: Get Composer Cache Directory
+        id: composer-cache
+        run: |
+          echo "dir=$(composer config cache-files-dir)" >> $GITHUB_OUTPUT
+
+      - uses: actions/cache@9255dc7a253b0ccc959486e2bca901246202afeb # v5.0.1
+        with:
+          path: ${{ steps.composer-cache.outputs.dir }}
+          key: ${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}
+          restore-keys: |
+            ${{ runner.os }}-composer-
+
+      - name: Build assets
+        run: npm run build
+
+      - name: Install and start WordPress
+        run: npx wp-env start