release: publish 1.0.0-beta.1 and complete distribution rollout #4

Purpose

Track the publication and cross-repository rollout that must happen after plugin PR #3 is reviewed and merged. SS-046 intentionally did not publish partial artifacts or open a registry PR with URLs that currently return 404.

Upstream prerequisites

• Merge Tabularis core PR TabularisDB/tabularis#688.
• Deploy its additive explain_parsers manifest schema to registry.tabularis.dev; verify npx @tabularium/cli validate .tabularium --registry https://registry.tabularis.dev --kind driver passes.
• Publish Tabularis v0.23.0 or later containing raw plugin EXPLAIN results and plugin parser-bundle loading.
• Publish @tabularis/explain 0.2.0 or later, containing the parser registry consumed by this package.
• Complete the real-desktop check from core PR #688: install this plugin archive in the released host, then connect, browse, query, and render both estimated SHOWPLAN_XML and runtime STATISTICS XML in Visual EXPLAIN.

Plugin and npm publication

• Merge plugin PR feat: complete the SQL Server plugin — protocol, packaging, explain #3 after all required checks pass.
• Resolve the bridge crate's missing standalone licence-file concern recorded in docs/dependencies.md, and decide/package any required third-party notices before distributing binaries.
• Push explain-v1.0.0-beta.1; verify the publish workflow releases @tabularis/explain-sqlserver@1.0.0-beta.1 publicly with peer dependency @tabularis/explain@^0.2.0.
• Inspect npm pack --dry-run: dist/index.js, dist/index.d.ts, dist/index.iife.js, README, licence, and package metadata are present, with no source fixtures or unrelated files.
• Push v1.0.0-beta.1; verify the release workflow publishes a prerelease and does not replace the stable Latest release.
• Verify all five archives exist: linux-x64, linux-arm64, darwin-x64, darwin-arm64, and win-x64.
• Inspect every archive for the platform binary, .tabularium, assets/, and explain/dist/index.iife.js; verify the standalone .tabularium release asset too.
• Confirm .tabularium version equals the tag and min_runtime_version still names the first released compatible host.
• HEAD-check the icon and all screenshot URLs at the tagged ref; update .tabularium away from mutable main URLs if the registry requires immutable release URLs.

Registry and site rollout

• HEAD-check every URL in docs/registry-entry.json; all five release assets must return success before opening a registry PR.
• Add the prepared entry to TabularisDB/tabularis/plugins/registry.json and open the registry PR only after those checks pass.
• Merge TabularisDB/explain-plan#2 using the published packages instead of temporary tarballs, deploy production, and verify SQL Server appears in the engine picker and parses the sample.
• Close Explain: let plugin drivers return raw explain output parsed by @tabularis/explain (SQL Server SHOWPLAN) #2 only after posting links to the merged core PR, published npm package, plugin release, and production site.