MisakaNet Release Checklist

Standard release process. Do not skip steps.

Pre-release

Run gate tests

python -m pytest tests/test_intake_redaction.py tests/test_demand_board_model.py tests/test_intake_classify.py
python -m pytest

Run site-health (issue #783 — also run it after any Worker / frontend change)
```
python3 scripts/site_health_check.py --write --strict
```
Writes docs/maintainer/site-health-YYYY-MM-DD.md and exits non-zero if any endpoint or frontend entry point is not OK. Commit the snapshot with the release.
Update version
- pyproject.toml: version = "X.Y.Z"
- server.json: "version": "X.Y.Z" (both occurrences)
Update CHANGELOG.md
- Add new version section with highlights, new files, data stats
Update stale docs
- Scan for old lesson/node counts: grep -rn "235\+\|244\|旧数字" --include="*.md" --include="*.html" --include="*.json"
- Update: README.md, docs/index.html, docs/search/index.html, docs/mcp-quickstart.md, hub/README.md, STATUS.md, server.json description

Commit and tag

git add -A
git commit -m "release: vX.Y.Z - Title"
git tag -a vX.Y.Z -m "vX.Y.Z — Title"
git push && git push origin vX.Y.Z

Publish to PyPI

python -m build
python -m twine upload dist/misakanet-X.Y.Z*

Create GitHub Release

gh release create vX.Y.Z --title "vX.Y.Z — Title" --notes '...'

Wait for Glama auto-sync — no manual action needed
MCP Registry — best-effort only
- Requires mcp-publisher.exe login github (device code flow)
- Requires direct HTTPS to registry.modelcontextprotocol.io:443
- Unreliable in restricted networks (proxy, firewall)
- Do not delay release for MCP Registry
- Retry manually when network is available:
```
.\mcp-publisher.exe login github
.\mcp-publisher.exe publish
```

PyPI → GitHub Release → CHANGELOG/docs → site-health → Glama wait → MCP Registry (best-effort)

MCP Registry is last and non-blocking. Never let it delay the release.