release

# Release & PR Workflow > **REVISED 2026-09-04 (docs/workflows/DESIGN.md section 5).** The PUBLISH > half of this file (steps 4-7 below: local build, `twine upload`, `git tag`, > `gh release create`, `mcp-publisher`) is SUPERSEDED by `release.yml`, > dispatched per `docs/cicd/RUNBOOK.md` section 1; the `/release` command > prepares the release PR and stops. Those steps stay here as the record of > the retired path and for RUNBOOK section 1a's hand-finish while PyPI > persists no publisher (C-15). The PR-workflow and CLA halves are current. > This copy is TRACKED in this repo; the suite copy under `C:\MCPs\.claude` > serves jdoc and jdata. ⚠⚠ **THIS FILE MIXES TWO AUDIENCES AND THE SPLIT IS LOAD-BEARING.** Almost every command below is run BY THE AGENT through the Bash tool (Git Bash), so bash syntax is correct for them: `PYTHONPATH=src python ...`, `GITHUB_TOKEN="" gh ...`, `BR=$(...)`. **Inline env-var prefixes and `$(...)` do NOT exist in cmd.exe or PowerShell**, which is what jjg is at when he types. **Step 7 is the ONE command a HUMAN types interactively**, and on 2026-08-13 it failed mid-release because it had silently inherited bash path syntax from its neighbours (`~\mcp-publisher.exe` -> "The system cannot find the path specified"). **The dev platform is Windows.** Any line added here that a human will type must be given in cmd.exe AND PowerShell form, with no `~`, no inline `VAR=x cmd` prefix, and no `$(...)`. Mark the shell explicitly. ## Publishing a release ⚠...