Fix docs deployment from tag triggers by using workflow_dispatch

[laughingman7743]

Summary

• Add a new workflow (docs-trigger.yaml) that triggers the docs workflow via workflow_dispatch API when a tag is pushed
• Remove direct tag trigger from docs.yaml to ensure deployments always run in master context

Problem

When a tag (e.g., v3.23.0) triggers the docs workflow:

1. The workflow checks out the tag ref
2. sphinx-multiversion builds all versions correctly
3. The deployment "succeeds" but GitHub Pages doesn't actually update the content

This is because GitHub Pages is configured with source.branch: master, and deployments from tag refs are silently ignored.

Solution

Instead of triggering the docs workflow directly from tag pushes, use a separate workflow that:

1. Listens for tag pushes (on: push: tags: ['v*'])
2. Triggers the docs workflow via GitHub Actions API with ref: master
3. This ensures the docs workflow always runs in master context while still being triggered by tag releases

The actions: write permission is required to trigger workflows via the API.

Changes

• .github/workflows/docs-trigger.yaml - New workflow to trigger docs on tag push
• .github/workflows/docs.yaml - Removed tags: ['v*'] trigger

Test plan

• Create a new tag and verify docs workflow is triggered via workflow_dispatch
• Verify master push still deploys correctly
• Verify manual workflow_dispatch still works

🤖 Generated with Claude Code