ci: auto-publish on Version Packages PR merge via pull_request trigger (

#14)

Merging the Changesets "Version Packages" PR never auto-published: its commits
are authored by github-actions[bot], and GitHub suppresses push-triggered
workflows from bot-authored pushes (anti-recursion under the default
GITHUB_TOKEN). So the bumped versions landed on main but nothing shipped to npm.

Add a `pull_request: closed` trigger (gated to the merged `changeset-release/main`
PR from this repo) to both the Release and Publish VS Code Extension workflows.
Merging a PR is a human action, so that event fires regardless of merge method —
no PAT or GitHub App token required. The publish jobs check out `main` (post-merge
tip) and remain idempotent, and workflow_dispatch stays as a manual fallback.

Update RELEASING.md: any merge method now works; drop the merge-commit-not-squash
requirement.

ci: add workflow_dispatch to Release as a publish escape hatch (#8)

The changesets "Version Packages" PR merges as a github-actions[bot]-authored
commit, and GitHub does not trigger workflows from bot-authored pushes. So the
publish step does not auto-run after merging the version PR. Add
workflow_dispatch so the release can be triggered manually; changeset publish
is idempotent (only publishes versions not already on npm).

Merge pull request #3 from AlemTuzlak/changeset-release/main

ci: version packages

Merge pull request #2 from AlemTuzlak/feat/rebrand-kiira

feat: rebrand Typedown to Kiira + add documentation site

Kiira GitHub Action v1.0.0

Kiira GitHub Action v1 (moving major)