Add CODEOWNERS and designate @WordPress/interactivity-api as the code owners of the wp-interactivity-api skill

[luisherranz]

What

Adds a .github/CODEOWNERS file.

It initially designates @WordPress/interactivity-api team as the code owners of the skills/wp-interactivity-api/ directory.

/skills/wp-interactivity-api/ @WordPress/interactivity-api 

Why

The Interactivity API was authored and is actively maintained by the @WordPress/interactivity-api team. Assigning code ownership for that skill ensures:

• @WordPress/interactivity-api is automatically added as a required reviewer on any PR that modifies files inside skills/wp-interactivity-api/.
• Changes to the skill go through the person with the deepest domain knowledge, keeping the skill accurate and up-to-date as the API evolves.
• Other skills in the repository are unaffected — ownership is intentionally scoped only to this single skill directory.

How

A single .github/CODEOWNERS file is created with one ownership rule scoped to /skills/wp-interactivity-api/. No other files or skills are touched.

[luisherranz]

@WordPress/interactivity-api, just so you know, once this is merged you will receive pings every time there is a PR that modifies the Interactivity API skill 🙂

[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: @Copilot.

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

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

Unlinked contributors: Copilot.

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

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