ci: make publish workflow a valid manual-only stub

Author: HzaCode

.github/workflows/publish.yml

@@ -1,34 +1,33 @@
-# PyPI publish workflow - Currently disabled
-# Uncomment to enable automatic publishing on release
-
-# name: Publish to PyPI
-
-# on:
-#   release:
-#     types: [published]
-
-# jobs:
-#   deploy:
-#     runs-on: ubuntu-latest
-#     
-#     steps:
-#     - uses: actions/checkout@v4
-#     
-#     - name: Set up Python
-#       uses: actions/setup-python@v5
-#       with:
-#         python-version: '3.10'
-#     
-#     - name: Install dependencies
-#       run: |
-#         python -m pip install --upgrade pip
-#         pip install build twine
-#     
-#     - name: Build package
-#       run: python -m build
-#     
-#     - name: Publish to PyPI
-#       env:
-#         TWINE_USERNAME: __token__
-#         TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
-#       run: twine upload dist/*
+# PyPI publish workflow — manual trigger only.
+# Publishing is intentionally not automated; run this workflow by hand
+# from the Actions tab when a release should go to PyPI.
+
+name: Publish to PyPI
+
+on:
+  workflow_dispatch:
+
+jobs:
+  build-only:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: '3.12'
+
+    - name: Install build tooling
+      run: |
+        python -m pip install --upgrade pip
+        pip install build twine
+
+    - name: Build package
+      run: python -m build
+
+    - name: Check distribution metadata
+      run: twine check dist/*
+
+    # Publishing step intentionally omitted; upload manually with twine
+    # after verifying the built artifacts.