ci(publish): update workflow to require release_tag input

AGENTS.md

@@ -35,11 +35,12 @@ repository's user or organization (not necessarily the npm scope `warkypublic`).
 2. Run `pnpm exec changeset version` to apply pending changesets. Review and commit
    the updated version, changelog, and consumed changesets with the release changes.
 3. Create and push a matching tag to the Gitea remote, for example `v1.1.0` for
-   package version `1.1.0`. To dispatch manually, select that existing matching tag
-   as the workflow run ref in the Actions UI; the workflow rejects branch refs and
-   tags that do not exactly match the package version. It runs the tests and
-   bundle checks, then publishes using pnpm so the `publishConfig` overrides point
-   consumers to the built JavaScript and declarations.
+   package version `1.1.0`. To publish manually, run the workflow from the Actions
+   UI and set its required `release_tag` input to the matching tag. Checkout and
+   validation use that tag; the workflow rejects tags that do not exactly match the
+   package version. It then runs tests and bundle checks before publishing with
+   pnpm, which applies the `publishConfig` entries for built JavaScript and
+   declarations.
 
 Stable versions receive the `latest` dist-tag; prereleases receive `next`.
 Existing package versions cannot be overwritten; release a new version instead.