ci(pypi): add Trusted Publishing workflow

[cdeust]

Why

release.yml only builds a GitHub Release; PyPI uploads have always been by-hand from a maintainer's shell. v3.17.1 (the GHSA-gvpp-v77h-5w8g security fix) is sitting tagged + released on GitHub but unpublished on PyPI because the maintainer's PyPI token isn't visible to the Claude-Code subprocess shell that built it.

What

A new workflow .github/workflows/publish-pypi.yml that uses PEP 740 Trusted Publishing — GitHub Actions mints a short-lived OIDC token, PyPI verifies it against the trusted-publisher configuration on the project, and issues a one-shot upload token. No long-lived secret stored anywhere.

Triggers:

• push: tags: v* — every tag auto-publishes
• workflow_dispatch — manual re-publish for tags that pre-date this workflow (i.e. v3.17.1)

Setup required on PyPI side (one-time)

After this merges, do this once on pypi.org:

1. Log in to pypi.org as a maintainer of neuro-cortex-memory.
2. Go to https://pypi.org/manage/project/neuro-cortex-memory/settings/publishing/
3. Click Add a new publisher → GitHub.
4. Fill in:
   • Owner: cdeust
   • Repository name: Cortex
   • Workflow filename: publish-pypi.yml
   • Environment name: leave blank (or pypi if you also uncomment the environment: line in the workflow's publish job)
5. Save.

After PyPI is configured

I'll re-trigger this workflow against tag v3.17.1 via workflow_dispatch to actually ship the security fix. Subsequent tag pushes will auto-publish without any further action.

Why now, instead of next release

The security fix for GHSA-gvpp-v77h-5w8g (CVSS 7.8 HIGH) is currently advertised in the published GHSA and GitHub Release but cannot be installed via pip install --upgrade neuro-cortex-memory. Every hour that gap stays open is a maintainer-availability risk.

🤖 Generated with Claude Code

[cdeust]

Superseded: instead of a new publish-pypi.yml (which would need a fresh PyPI Trusted Publisher entry), the build+publish-pypi jobs were restored directly into release.yml in 9c9b659. That reuses the existing trusted-publisher entry (cdeust/Cortex, release.yml, env=pypi) from the <=3.14.7 era, so no PyPI reconfiguration is needed, and it's wired as a non-blocking deprecated channel per ADR-0050. Closing this PR.