[WIP] Resolve upstream merge conflict on autopilot

[Codex]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

---

This section details on the original issue you should resolve

<issue_title>Resolve upstream merge conflict on autopilot</issue_title>
<issue_description>The daily sync from trunk (upstream WordPress) cannot fast-forward into autopilot.

Agent work on autopilot has diverged from upstream.

Task

1. Merge trunk into autopilot resolving any conflicts
2. Prefer upstream changes unless agent work is clearly intentional
3. Ensure all tests pass after resolution
4. Open a PR targeting autopilot with the merge</issue_description>

Comments on the Issue (you are @codex[agent] in this section)

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @codex.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[nopilots-dalton]

Dalton (Security):

The diff primarily involves changes to documentation files and a pull request template, which do not introduce any executable code or alter application behavior. As such, there are no direct security concerns arising from this specific change. However, it's worth noting that the presence of AI tools in the development process (as disclosed in the README) could introduce indirect risks if not properly monitored, but this is outside the scope of the current diff.

The changes reflect a focus on contributing guidelines and AI tool usage rather than any code that could be exploited. Therefore, I find no exploitable vulnerabilities in this pull request.

INPUT_SANITIZATION: N/A — No user input handling in this diff.
OUTPUT_ESCAPING: N/A — No output generation or display in this diff.
SQL_PREPARATION: N/A — No database interactions in this diff.
CAPABILITY_CHECKS: N/A — No capability checks present in this diff.
NONCE_VERIFICATION: N/A — No nonce usage in this diff.
ATTACK_SURFACE: N/A — No attack surface introduced in this diff.

[nopilots-doc]

Doc (Code Quality):

1. The changes to the .github/pull_request_template.md file introduce unnecessary verbosity in the comments. The original comments were concise and to the point. For example, the line <!-- What does this PR do? Why? --> has been replaced with a lengthy block of text that may overwhelm contributors. This can lead to confusion about what information is essential versus what is supplementary. Keep comments succinct to enhance clarity (lines 3-5).

2. In the README.md, the removal of the initial section about "No Pilots" seems to strip away context that could be important for understanding the specific fork's purpose. While the new content is informative, it lacks a clear transition from the previous context, which can disorient new contributors. A brief note explaining the transition would improve readability (lines 1-10).

3. The use of lists in the new README.md section is inconsistent. For instance, the transition from bullet points to numbered steps in the "Getting Started" section could confuse readers. Consistent formatting is crucial for maintaining a clear structure (lines 11-183).

4. The phrase "you must disclose what tooling you are using and to what extent a pull request has been authored by AI" in the AI disclosure section is ambiguous. It could be clearer on what constitutes adequate disclosure. Ambiguity can lead to inconsistent practices among contributors, which might result in compliance issues (lines 36-40).

READABILITY: FAIL — The changes introduce verbosity and inconsistency that may confuse readers.
PHPDOC: N/A — No PHP documentation changes were made.
COMPLEXITY: N/A — No complex logic was introduced or modified.
TESTS: N/A — No tests were added or modified.
STYLE: FAIL — Inconsistent formatting and ambiguous language detract from clarity.

[nopilots-pat]

Pat (Compatibility + Decision):

The test status shows a failure, which means the PR is not ready for review regardless of the code quality or security concerns raised. Without passing tests, we cannot proceed with any changes, even if they are limited to documentation.

TESTS: FAIL — were PHPUnit and Coding Standards green at review time?
FUNCTION_SIGNATURES: N/A — no changes to public functions
HOOK_COMPATIBILITY: N/A — no changes to hooks
RETURN_TYPES: N/A — no changes to return types
DEPRECATION_PATH: N/A — no deprecated features
DECISION: REQUEST_CHANGES
RATIONALE: The PR fails the test suite and must pass before further review.

DECISION: REQUEST_CHANGES

[nopilots-pat]

Pat (Compatibility + Decision):

The test status shows a failure, which means the PR is not ready for review regardless of the code quality or security concerns raised. Without passing tests, we cannot proceed with any changes, even if they are limited to documentation.

TESTS: FAIL — were PHPUnit and Coding Standards green at review time?
FUNCTION_SIGNATURES: N/A — no changes to public functions
HOOK_COMPATIBILITY: N/A — no changes to hooks
RETURN_TYPES: N/A — no changes to return types
DEPRECATION_PATH: N/A — no deprecated features
DECISION: REQUEST_CHANGES
RATIONALE: The PR fails the test suite and must pass before further review.

DECISION: REQUEST_CHANGES

[josephfusco]

Merge conflict resolved on autopilot directly. No longer needed.