From 9c124ceb46c8d0796f2c0f2591ca393af4112372 Mon Sep 17 00:00:00 2001
From: not-compromised <94505409+not-compromised@users.noreply.github.com>
Date: Tue, 13 Oct 2026 19:05:33 -0500
Subject: [PATCH] chore(fork): dispatch the nightly from the owner's server

GitHub's cron for fork-nightly.yml was silently disabled until Oct 12 and
fired 7h40m late on Oct 13, shipping mid-day. The owner's server now
dispatches it once a night, or by day after the owner approves; remove the
schedule so a late GitHub run cannot ship without that approval.

Closes #12
---
 .github/workflows/fork-nightly.yml |  8 ++------
 FORK.md                            | 13 ++++++++-----
 2 files changed, 10 insertions(+), 11 deletions(-)

diff --git a/.github/workflows/fork-nightly.yml b/.github/workflows/fork-nightly.yml
index 0a0e4d3d829f0..46e850df0d9d1 100644
--- a/.github/workflows/fork-nightly.yml
+++ b/.github/workflows/fork-nightly.yml
@@ -4,13 +4,9 @@
 # installed apps, servers and the version-skew check all see one number.
 name: Fork nightly
 
+# No schedule: the owner's server dispatches this once a night, or by day after
+# the owner approves. GitHub's cron dropped runs and fired hours late (#12).
 on:
-  schedule:
-    # Finishes before the owner's 08:30 UTC digest scan, which reports a fork
-    # still behind upstream; servers install the release within 30 minutes.
-    # GitHub drops a public repo's schedules after 60 days without activity
-    # and revives them only when a person commits a change to this line.
-    - cron: "35 7 * * *"
   workflow_dispatch:
     inputs:
       target_tag:
diff --git a/FORK.md b/FORK.md
index 0a9a72d5258be..c1deb7fd511b9 100644
--- a/FORK.md
+++ b/FORK.md
@@ -123,11 +123,13 @@ otherwise.
 ### Fork pipeline
 
 - **Commits:** `chore(fork): nightly rolling rebase and release pipeline`,
-  `fix(fork): revive the nightly schedule GitHub dropped`
+  `fix(fork): revive the nightly schedule GitHub dropped`,
+  `chore(fork): dispatch the nightly from the owner's server`
 - **Must still be true:**
-  - Daily at 07:35 UTC and on demand, the newest upstream nightly gets
-    `custom` replayed onto it, checked and built; it ships only when every
-    step is green.
+  - On each dispatch, the newest upstream nightly gets `custom` replayed onto
+    it, checked and built; it ships only when every step is green. GitHub
+    never starts it on a schedule: the owner's server dispatches it once a
+    night, or by day after the owner approves.
   - A changed `ORCHESTRATION_PROTOCOL_VERSION` never ships without
     `allow_protocol_change`.
   - A release carries the upstream version unchanged, and fork builds update
@@ -143,7 +145,8 @@ otherwise.
 - **Tests:** `node --test .github/fork/*.test.cjs` (Check job), one test per
   promise above that can be checked without running Actions.
 - **Detail:** this file and `.github/workflows/fork-nightly.yml`;
-  not-compromised/t3code#6 (nightly schedule revival).
+  not-compromised/t3code#6 (nightly schedule revival),
+  not-compromised/t3code#12 (dispatch from the owner's server).
 - **Retire when:** never.
 
 ### Dependency security fixes