fix(release): soft-warn instead of fail on missing samples.yml run

The v1.0.0-beta.0 release workflow failed at the "Confirm samples
workflow green for this commit" step. Two root causes:

1. The query hard-coded --branch=main, but the tag was on develop.
2. samples.yml only triggers on pull_request and push-to-main, not
   on tag pushes. There is never a tag-commit samples.yml run to
   wait for. The maintainer cutting the tag is responsible for
   verifying the green PR run on the tag commit; CI can't enforce
   that cross-workflow.

The step is now informational only. It queries the API by commit
SHA (no branch filter), reports the conclusion as a ::notice or
::warning, and never fails the release. release.yml proceeds to
publish the GitHub release using the CHANGELOG section as the body.

CHANGELOG.md adds a [1.0.0-beta.1] section recording the workflow
fix. No skill content, README, MAINTENANCE, CLAUDE.md, or sample
changes since v1.0.0-beta.0.

Conformance: scripts/verify-all.sh passes 8/8.
scripts/check-changelog.sh v1.0.0-beta.1 passes.

Author: kittisakLS

.github/workflows/release.yml

@@ -35,24 +35,34 @@ jobs:
       - name: Run verify-all.sh (conformance)
         run: scripts/verify-all.sh
 
-      - name: Confirm samples workflow green for this commit
+      - name: Report samples workflow status for this commit (informational)
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           GIT_SHA: ${{ github.sha }}
         run: |
-          # Best-effort: query GitHub API for the samples workflow runs
-          # against this commit. Fail if the latest samples run is not
-          # green. (When the API is unavailable, fall back to a manual
-          # confirmation note in the release body.)
+          # Informational only. samples.yml triggers on pull_request and
+          # push-to-main, not on tag pushes, so a tag commit may have no
+          # samples.yml run associated with it. The maintainer cutting
+          # the tag is responsible for ensuring samples were green on
+          # the commit (typically via a green PR before tagging). This
+          # step queries the API for visibility but does NOT fail the
+          # release on a missing or non-success conclusion.
           if ! command -v gh >/dev/null 2>&1; then
-            echo "::warning ::gh CLI unavailable; manual confirm required"
+            echo "::notice ::gh CLI unavailable; cannot look up samples run"
             exit 0
           fi
-          conclusion="$(gh run list --workflow=samples.yml --branch=main --commit "$GIT_SHA" --limit 1 --json conclusion --jq '.[0].conclusion' 2>/dev/null || echo 'unknown')"
-          if [[ "$conclusion" != "success" ]]; then
-            echo "::error ::samples workflow conclusion for $GIT_SHA is '$conclusion' (expected 'success')"
-            exit 1
-          fi
+          conclusion="$(gh run list --workflow=samples.yml --commit "$GIT_SHA" --limit 1 --json conclusion --jq '.[0].conclusion // "none"' 2>/dev/null || echo 'unknown')"
+          case "$conclusion" in
+            success)
+              echo "::notice ::samples workflow for $GIT_SHA: success"
+              ;;
+            none|null|"")
+              echo "::warning ::no samples workflow run found for $GIT_SHA. Tag pushes do not trigger samples.yml; the green PR for this commit is the gate. Proceeding."
+              ;;
+            *)
+              echo "::warning ::samples workflow for $GIT_SHA: $conclusion (expected 'success' for a stable release). Proceeding because this is informational."
+              ;;
+          esac
 
       - name: Create GitHub release
         env:

CHANGELOG.md

@@ -19,7 +19,33 @@ range under a **Validated against** line.
 
 ## [Unreleased]
 
-(No changes yet since v1.0.0-beta.0.)
+(No changes yet since v1.0.0-beta.1.)
+
+## [1.0.0-beta.1] - 2026-05-14
+
+Patch on top of `v1.0.0-beta.0` to fix the release workflow.
+
+**Validated against**: `@react-pdf-kit/viewer` `>=1.0.0 <2.0.0`
+
+### Fixed
+
+- `.github/workflows/release.yml`: the "Confirm samples workflow
+  green for this commit" step incorrectly assumed `samples.yml` had
+  run against the tag commit on `main`, but `samples.yml` only
+  triggers on `pull_request` and `push to main`, never on tag
+  pushes. The query also hard-coded `--branch=main` even when the
+  tag was on `develop`, so it returned `'unknown'` and failed the
+  release on `v1.0.0-beta.0`. The step is now informational only:
+  it reports the samples run conclusion as a notice/warning and no
+  longer fails the release. The maintainer cutting the tag remains
+  responsible for ensuring the green PR for the tagged commit
+  exists.
+
+### Catalog content
+
+(No skill or content changes since `v1.0.0-beta.0`. All eight
+skills, README, MAINTENANCE, CLAUDE.md, conformance scripts, and
+the rest of the CI surface ship unchanged.)
 
 ## [1.0.0-beta.0] - 2026-05-14