Closes #1250: Fix publish_mcp_abilities workflow after CI migration

[remyperona]

🤖 AI-generated — created by an automated pipeline. Review before acting on this.

Description

Fixes #1250

The Publish MCP Abilities to ARD Service workflow failed on every tag push because its Dump Imagify abilities catalog (WP latest, PHP 8.2) job still called bin/install-wp-tests.sh, a script deleted in #1229 during the CI migration to the wp-media/workflows composite actions. publish_mcp_abilities.yml was missed in that migration, so the abilities catalog was never published on release. Users are not directly impacted, but the release pipeline was broken.

Type of change

• Bug fix (non-breaking change which fixes an issue).

Detailed scenario

What was tested

• Automated: Validated the workflow YAML parses cleanly.
• Manual (static): Diffed the changed job structure against the already-migrated, CI-passing test.yml and test_legacy.yml to confirm it uses the same composite actions, composer-options: '', mysql service container, and problem matchers.
• The end-to-end run was not exercised: the workflow only triggers on a tag push, and publishing a tag during development is out of scope for this fix. First real validation will be the next tag publish after merge.

How to test

• Confirm .github/workflows/publish_mcp_abilities.yml no longer references bin/install-wp-tests.sh and that the removed script is not needed elsewhere.
• Compare the Dump Imagify abilities catalog job against test.yml / test_legacy.yml — setup should be the setup-php-composer@main + setup-wp-tests@main composite actions plus the mysql service container.
• After merge, on the next tag push, verify the Dump Imagify abilities catalog (WP latest, PHP 8.2) job installs the WP test suite and proceeds to dump and upload the abilities catalog without exit code 127.

Affected Features & Quality Assurance Scope

• CI/CD only: the publish_mcp_abilities.yml release workflow.
• No plugin code, features, or user-facing behavior are changed.

Technical description

Documentation

publish_mcp_abilities.yml was aligned with the workflows migrated in #1229. The obsolete manual setup steps — Install SVN, Start mysql service, composer cache directory steps, Install Strauss, Install dependencies, Install tests, and the Mysql8 auth plugin workaround — were removed and replaced with the shared composite actions:

• wp-media/workflows/.github/actions/setup-php-composer@main (with composer-options: '' so the Strauss post-install script runs)
• wp-media/workflows/.github/actions/setup-wp-tests@main (wp-version: latest)

A mysql:8.0 service container was added, matching test.yml, since setup-wp-tests expects the DB to be available (the old manual mysql start / auth workaround are no longer needed).

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.

Unticked items justification

This is a CI-workflow YAML change with no PHP code:

• Acceptance Criteria / triggering changed lines: the workflow only runs on a tag push, which is deliberately not performed during development; validation was done statically against the equivalent, CI-passing test workflows.
• Built-in tests: not applicable to a GitHub Actions workflow definition.
• Entry points / output messages: no runtime code, inputs, or user-facing messages are involved.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage ∅ diff coverage

Metric	Results
Coverage variation	Report missing for cd27ae41
Diff coverage	✅ ∅ diff coverage (50.00%)

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (cd27ae4)	Report Missing	Report Missing	Report Missing
Head commit (22ba39c)	20475	1613	7.88%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#1252)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

¹ Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}