From 17550628237b7c9883c1432a96355a4443a847ae Mon Sep 17 00:00:00 2001
From: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Date: Mon, 7 Sep 2026 11:22:47 -0700
Subject: [PATCH] Update enforcement start to exact deployment timestamp

Issue template enforcement must use the precise moment the workflow deployed, not midnight, so issues created before that moment aren't retroactively flagged.
---
 .github/scripts/issue-template-compliance.mjs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/scripts/issue-template-compliance.mjs b/.github/scripts/issue-template-compliance.mjs
index a9452d25339..adaceb2c3b0 100644
--- a/.github/scripts/issue-template-compliance.mjs
+++ b/.github/scripts/issue-template-compliance.mjs
@@ -87,9 +87,9 @@ function hasComplianceLabel(issue) {
   )
 }
 
-// Why hardcoded: the day this workflow shipped. Issues filed earlier were written
+// Why hardcoded: the moment this workflow landed. Issues filed earlier were written
 // before the forms were mandatory, so editing one must not retroactively flag it.
-export const ENFORCEMENT_START = '2026-09-07T00:00:00Z'
+export const ENFORCEMENT_START = '2026-09-07T16:27:44Z'
 
 // Why created_at, not label presence: `cancel-in-progress` can kill the `opened`
 // run mid-flight, leaving a brand-new non-compliant issue unlabeled.