[Adi-ty]

What this PR does

Releases each Composer package on its own tag, so wp-phpstan can go to 2.0.0 without wp-phpcs getting an empty 2.0.0. Until now any v* tag split and tagged both mirrors at the same version.

Closes

N/A

Changes

• release-php.yml triggers on rtcamp/<package>@<version> tags (for example rtcamp/wp-phpstan@2.0.0). It splits only that package and tags its mirror v<version>, so Packagist sees the same tag format as before. The other mirror is not touched.
• The tag must match a splitsh.json subtree and the package's composer.json name, or the run fails before pushing anything. A bare v* tag no longer triggers a release.
• workflow_dispatch takes the same tag form in test_tag (default rtcamp/wp-phpstan@0.0.0-test), so a smoke test or resync_branch run acts on one mirror.
• AGENTS.md, the split-npm-packages.yml header and the monorepo-builder.php comment now describe per-package tags.

How I verified

• actionlint passes on every workflow, including ci(npm): publish workspaces to npm from main with trusted publishing #71's publish-npm-packages.yml.
• I ran the tag-parsing step locally against the real splitsh.json:

'rtcamp/wp-phpstan@2.0.0'      OK  tag=v2.0.0       ["wp-phpstan:composer-packages/phpstan:SPLIT_KEY_PHPSTAN"]
'rtcamp/wp-phpcs@1.1.0'        OK  tag=v1.1.0       ["wp-phpcs:composer-packages/phpcs:SPLIT_KEY_PHPCS"]
'rtcamp/wp-phpstan@0.0.0-test' OK  tag=v0.0.0-test  ["wp-phpstan:composer-packages/phpstan:SPLIT_KEY_PHPSTAN"]
'v2.0.0'                       FAIL Refusing tag 'v2.0.0': a release tag must look like <vendor>/<package>@<version>
'main'                         FAIL Refusing tag 'main': ...
'rtcamp/wp-foo@1.0.0'          FAIL 'splitsh.json' has no subtree named 'wp-foo'
'acme/wp-phpstan@2.0.0'        FAIL Tag names acme/wp-phpstan, but composer-packages/phpstan/composer.json is named 'rtcamp/wp-phpstan'
'@rtcamp/eslint-config@1.1.0'  FAIL Refusing tag ...

Reviewer notes

• Stacked on ci(npm): publish workspaces to npm from main with trusted publishing #71 (base v1.0.0/task/npm-publish). Merge ci(npm): publish workspaces to npm from main with trusted publishing #71 first; this PR then retargets to main.
• A follow-up PR adds release-please, which creates its tags in this same rtcamp/<package>@<version> form.
• The push side is unchanged: the same split, deploy keys, fast-forward rule and resync mode.
• monorepo-builder release is lockstep by design and was not used for v1.0.0 or v1.0.1 (both were hand-made tags).

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.