Install doc updates - #693

Description

The Official MCP Registry validates every server.json package entry against its upstream registry at the exact version being published. The registry-publish job added in #690 ran inside mcp-packaging - before the manual npm/PyPI wrapper publishes exist and racing the oci-publish job - so it fails for every fresh release (confirmed on the v0.10.559 dispatch).

This PR makes registry publication the explicit final step of a release:

• New standalone workflow_dispatch workflow .github/workflows/mcp-registry-publish.yml, dispatched after the npm/PyPI wrappers are live. Auth is GitHub Actions OIDC (the registry grants io.github.<repository_owner>/* to OIDC tokens from this repo), so no secret is stored. A preflight step checks npm, PyPI and Docker Hub for the target version and fails fast with a pointer to the missing release-process step.
• The mis-ordered registry-publish job is removed from mcp-packaging.yml.
• docs/stackql release process.md step 7 rewritten: strict one-way publish order (bundles/OCI -> wrappers -> registry entry last), 7c as a dispatch, manual PAT fallback retained with the gotchas hit during the v0.10.557/v0.10.559 releases.
• New workflow added to build.yml paths-ignore (both triggers).
• v0.10.559 wrapper version stamps (npm/package.json, pypi/pyproject.toml), matching the published packages.

Type of change

• Bug fix (non-breaking change to fix a bug).
• Feature (non-breaking change to add functionality).
• Breaking change.
• Other (eg: documentation change). Please explain. Release-process documentation updated to match the corrected publish ordering; no engine or query behaviour is touched.

Issues referenced.

None. The defect was introduced in #690 and observed on the v0.10.559 publish dispatch (see Evidence) before any issue was raised.

Evidence

• Failing run demonstrating the ordering defect: https://github.com/stackql/stackql/actions/runs/29893367438/job/88838670927 (registry rejects the publish because @stackql/mcp-server@0.10.559 / stackql-mcp-server 0.10.559 did not yet exist upstream).
• The exact sequence the new workflow encodes was executed manually end to end for v0.10.559 and succeeded, registry last:
  • npm: https://www.npmjs.com/package/@stackql/mcp-server/v/0.10.559
  • PyPI: https://pypi.org/project/stackql-mcp-server/0.10.559/
  • MCP Registry (0.10.559 active/latest): https://registry.modelcontextprotocol.io/v0/servers?search=io.github.stackql/stackql-mcp
• OIDC auth path, latest-CLI install and release-checksum rendering were each proven in CI by the failed run (all steps green up to the registry's version validation, which this PR re-orders around).

Checklist:

• A full round of testing has been completed, and there are no test failures as a result of these changes.
• The changes are covered with functional and/or integration robot testing.
• The changes work on all supported platforms.
• Unit tests pass locally, as per the developer guide.
• Robot tests pass locally, as per the developer guide.
• Linter passes locally, as per the developer guide.

Variations

The diff is CI workflow + documentation + wrapper version stamps only: no Go code, no query surface, no packaged artefact content. Unit/robot/lint runs exercise none of these paths, and the touched paths are all under build.yml paths-ignore, so the checklist items above are not applicable. Fitness for purpose is evidenced by the manual end-to-end execution of the encoded sequence for v0.10.559 (Evidence section). The new workflow's first CI execution will be the next release; the manual fallback in doc step 7c remains available if it misbehaves.

Tech Debt

No new technical debt. The npm and PyPI publishes remain manual - that is an inherent 2FA constraint of those registries, pre-existing and now accurately documented rather than papered over by CI jobs that could never succeed (three such jobs were removed in #690/this change). The registry step, which was the newly-introduced debt in #690, is resolved here by correct ordering.

🤖 Generated with Claude Code