ci

No overt malware is present in the workflow YAML itself; however, the workflow materially increases supply-chain and CI compromise impact by (1) checking out a user-supplied branch without visible validation, (2) weakening dependency pinning via `pnpm install --frozen-lockfile=false`, and (3) executing repository-defined publish scripts with `GITHUB_TOKEN`/`NPM_TOKEN` under broad write permissions. This workflow should be hardened by enforcing lockfile pinning, restricting/allowlisting branch triggers, tightening permissions to the minimum needed, and reviewing/attesting the `pnpm ci:snapshot`/`pnpm ci:prerelease` implementations and dependency lifecycle behavior.