release_tagging

Katz 0.121

Deployment is tag-driven rather than commit-driven for every publishable channel.
Tags are created automatically by deployment_flow, not manually.
Site deployments are triggered by Git tags matching `site/v*` via site_distribution.
VS Code extension publishing is triggered by Azure DevOps tags matching `ext/v*` via extension_distribution and openvsx_registry.
npm publishing is triggered by Git tags matching `language/v*`, `analytical/v*`, `cli/v*`, or `mcp/v*` via npm_distribution.
Platform native packages ride `analytical/v*` ( same version as `@reqlan/analytical` ); they are not a separate tag prefix.
The tag suffix after the channel prefix ( `site/v`, `ext/v`, `language/v`, `analytical/v`, `cli/v`, `mcp/v` ) equals the package. json version at that tag.

Interactive page: release_tagging