fix: explicitly dispatch docs deployment from create-tag.yml

[97gamjak]

Summary

• Root cause of "docs stopped deploying entirely": create-tag.yml pushes the release tag using the default GITHUB_TOKEN. GitHub explicitly blocks events triggered by GITHUB_TOKEN from starting other workflow runs (anti-recursion protection), so docs.yml's on.push.tags trigger never actually fired for any release tag (confirmed via gh run list — no run exists for the 0.1.3 tag push at all).
• Fix: create-tag.yml now explicitly dispatches the Docs workflow via gh workflow run docs.yml --ref "$version" right after pushing the tag (needs actions: write permission, added).
• docs.yml's deploy condition now also accepts workflow_dispatch regardless of ref (not just tag pushes), so a missed/broken release's docs can be redeployed manually without cutting a new version.

Test plan

• Confirmed via gh run list --workflow=docs.yml that no run was ever triggered by a tag push (root cause)
• YAML-validated both modified workflow files with yaml.safe_load
• Next release cut through create-tag.yml should show a Docs run triggered by workflow_dispatch pinned to the new tag, followed by a successful deploy

🤖 Generated with Claude Code

https://claude.ai/code/session_0126spNDGtqDKMoYtuPT7JfW