Switch release workflow to manual dispatch with version input

[roborourke]

Summary

Replaces the release: created trigger in release.yml with a manual workflow_dispatch trigger that takes a version number input, mirroring the change we made to the hm-query-loop plugin.

Why

The previous workflow required creating a GitHub Release first (which creates the tag), then the workflow would substitute __VERSION__, build, retag with git tag -f, and git push --force to move the tag onto the version-bumped/built commit. Force-pushing tags is fragile and rewrites tag history.

What changed

• Trigger: release: created → workflow_dispatch with a required version string input (e.g. 1.2.3, no leading v).
• No force push: the workflow now creates the v{version} tag fresh from the version-bumped commit, so there's nothing to retag or force-push.
• Flow: checkout → npm i → substitute __VERSION__ with the input version → npm run build → commit + create/push v{version} tag → npm run plugin-zip → gh release create with hubspot-form-block.zip attached and auto-generated notes.
• Updated the Release workflow section in CLAUDE.md to document the new manual process.

How to release now

Run the Version and Release workflow from the Actions tab, entering the version number. The tag and GitHub Release are created by the workflow.

🤖 Generated with Claude Code

https://claude.ai/code/session_0195K19h2qMkAjp6iWVghaTc

---

Generated by Claude Code

[github-actions]

Playwright E2E Test Results (PHP 8.4, WP 6.9)

 13 passed
 1 flaky

Details

 14 tests across 4 suites
 2 minutes, 52 seconds
 be46d40

Flaky tests

chromium › persist-success.spec.js › HubSpot Form — persist success › should show full inline message including first-submission group on fresh success

[roborourke]

The test (8.4, 6.9) failure is a pre-existing flaky E2E test, not a regression from this PR.

• The only files changed here are .github/workflows/release.yml (a workflow_dispatch workflow that doesn't run on PRs) and CLAUDE.md — nothing that affects the block's frontend behaviour.
• The failing assertion is persist-success.spec.js:342 → expect(successParagraph).toBeAttached() timing out after 5s waiting for the HubSpot "Thank you!" success paragraph, on retry2 (Playwright had already retried twice).
• The exact same test passed on the test (8.4, latest) leg of this same run, where it was reported as flaky (passed on retry). lint, preview, and test (8.4, latest) are all green.

This is the live-HubSpot-SDK timing sensitivity called out in CLAUDE.md ("Allow time for hs-form-event:on-ready before asserting form elements exist"). Re-running the test (8.4, 6.9) job should clear it. Leaving it as-is since a docs + release-workflow change can't influence this test.

---

Generated by Claude Code