Publish drevops/vortex-tooling 2.0 and switch constraint from ^2.0@alpha to ^2.0

[AlexSkrypnyk]

Context

During 2.x pre-release development, the root composer.json requires drevops/vortex-tooling as ^2.0@alpha, with the path repository pinned to 2.0.0-alpha1 so the in-tree copy resolves locally and in CI (introduced in #2652 / #2666).

No 2.0 release of drevops/vortex-tooling is published to Packagist yet - only the 2.x-dev branch and the old 1.x tags. As a result, sites scaffolded from 2.x cannot resolve the tooling from Packagist (the installer strips the in-tree path repository). This is acceptable during pre-release development but must be resolved before go-live.

Pre-release activity (before 2.0 go-live)

1. Publish a 2.0 release of drevops/vortex-tooling to Packagist. The 2.x branch is mirrored to the standalone drevops/vortex-tooling repository by the vortex-publish-tooling workflow; tag and release 2.0.0 from there.
2. Switch the root composer.json constraint from ^2.0@alpha to a plain ^2.0.
3. Update the path repository version pin from 2.0.0-alpha1 to the released 2.0 version in all three places: root composer.json, scripts/vortex-tooling.sh, and .vortex/tests/phpunit/Traits/SutTrait.php.
4. Update the .vortex/CLAUDE.md Publishing note to drop the pre-release caveat.
5. Verify that a fresh scaffolded site resolves drevops/vortex-tooling from Packagist on the 2.0 line.

Acceptance criteria

• drevops/vortex-tooling 2.0 is published and installable from Packagist.
• The 2.x template and scaffolded sites require ^2.0 (no @alpha, no inline alias).
• A fresh composer install on a scaffolded site resolves the tooling from Packagist on the 2.0 line.

Constraints

• This change lives on 2.x only.

[coderabbitai]

🔗 Related PRs

#2541 - Enhanced 'vortex-tooling' package docs and relocated its maintenance guide. [merged]
#2585 - Update PHP - All packages except core - Minor and patch [merged]
#2604 - Added '*.x' version branch CI support behind VORTEX_DEV fences. [merged]
#2624 - Updated deps. [merged]
#2653 - Added '2.x' to the tooling publish workflow trigger. [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!