[jeffpaul]

This pull request updates project documentation to clarify maintainer responsibilities, the process for merging and closing pull requests, and how contributors can become maintainers. It also lists the current maintainers and provides guidance for contributor engagement.

Maintainer and Contribution Process Updates:

• Added a new "Merging PRs" section to CONTRIBUTING.md outlining who can merge PRs, the process for non-maintainers to request merges, and the importance of assigning release milestones.
• Introduced a "Joining the php-ai-client-maintainers team" section in CONTRIBUTING.md, explaining the criteria and process for becoming a maintainer.
• Added a "Closing PRs" section to CONTRIBUTING.md with best practices and a template for communicating PR closures to contributors.

Documentation and Maintainer Listing:

• Updated README.md to explicitly list the current maintainers and provide a link to contact them via the php-ai-client-maintainers team.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>

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

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.