Make test-and-publish no-op on tag/version mismatch instead of failing

[Copilot]

test-and-publish was failing on historical/incorrect tag pushes because the release workflow exited non-zero when GITHUB_REF did not match package.json version. This change keeps strict version gating while preventing false-negative release failures.

• Version guard behavior

  • Converted the tag check into an output-producing guard step (id: version_guard).
  • On mismatch, the workflow now emits a warning and sets matched=false instead of failing the job.

• Release pipeline gating

  • Added if: steps.version_guard.outputs.matched == 'true' to all downstream release steps (npm ci, tests, smoke/cleanup, publish, registry verification, GitHub Release).
  • Result: matching tags continue full release flow; mismatched tags become an explicit no-op.

• Relevant workflow pattern

  - name: Check tag matches package.json version
    id: version_guard
    run: |
      TAG="${GITHUB_REF#refs/tags/}"
      V="v$(node -p "require('./package.json').version")"
      if [ "$TAG" != "$V" ]; then
        echo "::warning::tag ${TAG} does not match package.json version ${V} — skipping publish workflow"
        echo "matched=false" >> "$GITHUB_OUTPUT"
        exit 0
      fi
      echo "matched=true" >> "$GITHUB_OUTPUT"
  
  - name: Install dependencies
    if: steps.version_guard.outputs.matched == 'true'
    run: npm ci

[github-actions]

🚀 Preview deploy ready: http://localhost:8787/sample-site/preview-preview/

Deployed by deploy-cli on PR #2.