ci(remote-cache): guard temporary deployment button URLs

Co-authored-by: GPT-6 Codex <codex@openai.com>

Author: fengmk2

.github/workflows/ci.yml

@@ -7,7 +7,7 @@ permissions:
 on:
   workflow_dispatch:
   pull_request:
-    types: [opened, synchronize]
+    types: [opened, synchronize, ready_for_review, converted_to_draft]
   push:
     branches:
       - main
@@ -23,6 +23,35 @@ defaults:
     shell: bash
 
 jobs:
+  deploy-button-links:
+    name: Deploy button links
+    runs-on: namespace-profile-linux-x64-default
+    steps:
+      - uses: taiki-e/checkout-action@7d1e50e93dc4fb3bba58f85018fadf77898aee8b # v1.4.2
+      - uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8
+        with:
+          script: |
+            const { readFile } = require('node:fs/promises');
+            const main = 'https://github.com/voidzero-dev/vite-task/tree/main/packages/remote-cache';
+            const pr = context.payload.pull_request;
+            const temporary = pr?.draft
+              ? `https://github.com/${pr.head.repo.full_name}/tree/${pr.head.ref}/packages/remote-cache`
+              : undefined;
+            for (const file of ['README.md', 'packages/remote-cache/README.md', 'packages/remote-cache/docs/self-hosting.md']) {
+              const content = await readFile(file, 'utf8');
+              const buttons = [...content.matchAll(/\]\((https:\/\/deploy\.workers\.cloudflare\.com\/\?url=[^)]+)\)/g)];
+              if (!buttons.length) core.setFailed(`${file}: Deploy to Cloudflare button is missing.`);
+              for (const [, button] of buttons) {
+                const source = new URL(button).searchParams.get('url');
+                if (source === main) continue;
+                if (temporary && source === temporary) {
+                  core.warning(`${file}: Temporary PR branch URL. Restore the button to main before marking this PR ready for review.`);
+                } else {
+                  core.setFailed(`${file}: Restore the Deploy to Cloudflare source URL to ${main} before merge.`);
+                }
+              }
+            }
+
   detect-changes:
     runs-on: namespace-profile-linux-x64-default
     permissions:
@@ -396,6 +425,7 @@ jobs:
     runs-on: namespace-profile-linux-x64-default
     if: always()
     needs:
+      - deploy-button-links
       - clippy
       - test
       - test-musl

README.md

@@ -15,7 +15,7 @@ vp run --cache build      # run with caching enabled
 
 ## Remote cache service
 
-[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https%3A%2F%2Fgithub.com%2Fvoidzero-dev%2Fvite-task%2Ftree%2Fmain%2Fpackages%2Fremote-cache)
+[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https%3A%2F%2Fgithub.com%2Fvoidzero-dev%2Fvite-task%2Ftree%2Ffeat%2Fpublic-remote-cache%2Fpackages%2Fremote-cache)
 
 To deploy the public remote cache service in your own Cloudflare account and bind it to a GitHub repository, follow the [self-hosting guide](packages/remote-cache/docs/self-hosting.md). The service is available in this source tree; the `vp run` remote-cache client adapter is not yet implemented here.
 

packages/remote-cache/README.md

@@ -4,7 +4,7 @@ This package implements the server in the [remote cache RFC](rfcs/0001-remote-ca
 
 The package contains no `vp run` client adapter. Cache keys, values, and blobs remain opaque. A successful lookup does not prove that a result is reusable; a client must validate its inputs and output archive.
 
-[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https%3A%2F%2Fgithub.com%2Fvoidzero-dev%2Fvite-task%2Ftree%2Fmain%2Fpackages%2Fremote-cache)
+[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https%3A%2F%2Fgithub.com%2Fvoidzero-dev%2Fvite-task%2Ftree%2Ffeat%2Fpublic-remote-cache%2Fpackages%2Fremote-cache)
 
 **Start here:** [Deploy the service and bind your repository](docs/self-hosting.md#quick-start-deploy-to-cloudflare). The button creates a standalone repository and provisions storage. Set `CACHE_REPOSITORY` to your public GitHub repository and keep the default `free` profile. The guide covers build-token permissions, deployment checks, custom domains, and the current client-integration limitation.
 

packages/remote-cache/docs/self-hosting.md

@@ -6,7 +6,7 @@ This guide deploys the service in your Cloudflare account and gives your reposit
 
 ## Quick start: Deploy to Cloudflare
 
-[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https%3A%2F%2Fgithub.com%2Fvoidzero-dev%2Fvite-task%2Ftree%2Fmain%2Fpackages%2Fremote-cache)
+[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https%3A%2F%2Fgithub.com%2Fvoidzero-dev%2Fvite-task%2Ftree%2Ffeat%2Fpublic-remote-cache%2Fpackages%2Fremote-cache)
 
 The button copies this package into a new GitHub repository in your account and connects it to Workers Builds. It provisions a Worker, a D1 database, and an R2 bucket. You do not need a local checkout or GitHub Actions secrets. The repository that hosts the Worker can differ from the application repository that uses its cache. See [Cloudflare's deployment-button guide](https://developers.cloudflare.com/workers/platform/deploy-buttons/).
 
@@ -38,7 +38,7 @@ Keep the generated D1 ID and R2 name in `wrangler.jsonc`. Each build reconstruct
 
 The automatic checks verify the new deployment ID, disabled HTTP caching, rejected anonymous uploads, invalid requests, and cache misses. They do not upload data or prove authorized GitHub OIDC writes. The [e2e plan](e2e-plan.md#deploy-to-cloudflare-button) covers the full acceptance checks.
 
-The button targets the package on `main`. Before this change is merged, test the flow by supplying the package URL at the reviewed PR commit to Cloudflare's deployment page.
+The button temporarily targets `feat/public-remote-cache` for PR #718's live e2e test. Before marking the PR ready for review, restore the buttons in the root README, package README, and this guide to `main`, and remove this note. The CI button check rejects temporary branch URLs on a PR that is ready for review.
 
 ## CLI deployment