fix: Use PYPI_API_TOKEN for PyPI publishing (v2.2.2)

Trusted Publisher was not configured on PyPI.org. Reverted to using
API token authentication which is already set up as a GitHub secret.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: 2 people

.github/workflows/release.yml

@@ -75,9 +75,10 @@ jobs:
           --notes-file RELEASE_NOTES.md \
           --verify-tag
 
-    - name: Publish to PyPI (Trusted Publisher)
+    - name: Publish to PyPI
       if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/')
-      uses: pypa/gh-action-pypi-publish@release/v1
-      with:
-        verbose: true
-        print-hash: true
+      env:
+        TWINE_USERNAME: __token__
+        TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+      run: |
+        twine upload dist/* --verbose

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "empathy-framework"
-version = "2.2.1"
+version = "2.2.2"
 description = "AI collaboration framework with persistent memory, anticipatory intelligence, and multi-agent orchestration"
 readme = {file = "README.md", content-type = "text/markdown"}
 requires-python = ">=3.10"