feat: add developer verification readiness gate to release checklist

Expanded the README developer-verification section with specific
install-impact notes for users in Brazil, Indonesia, Thailand, and
Singapore (the September 2026 pilot regions).

Added a release-front-door check that fails if the "reassess Q3 2026"
tag is still present after 2026-09-01, ensuring the guidance cannot
go stale through a release cycle without review.

Author: SysAdminDoc

README.md

@@ -116,12 +116,18 @@ including, in the rolled-out form, sideloaded APKs. F-Droid has published an
 **Current posture (reassess Q3 2026):** SwiftFloris does **not** plan to
 pre-register under this scheme. The F-Droid track remains the primary
 privacy-first distribution channel and F-Droid's own response will shape what,
-if anything, packagers must do. GitHub/Obtainium sideloading is unaffected in
-regions and on devices where enforcement has not yet landed. This is a
-reversible default: if enforcement begins blocking installs for users in the
-pilot regions ahead of a viable F-Droid path, registration will be
-reconsidered then. Maintainers can override this stance at any time — it is a
-recommendation, not a binding commitment.
+if anything, packagers must do.
+
+**If you are in a pilot region** (Brazil, Indonesia, Thailand, Singapore): after
+September 2026, certified Android devices in your region may begin warning or
+blocking sideloaded APKs from unregistered developers. Until then, GitHub and
+Obtainium installs work normally. If blocking begins and no F-Droid workaround
+exists, the project will reassess registration. Watch the release notes for
+updates.
+
+This is a reversible default: maintainers can override this stance at any time.
+The release-front-door script checks that this section has been reviewed within
+the current quarter; stale guidance blocks the release.
 
 ### Enable as Default Keyboard
 

scripts/check-release-front-door.sh

@@ -122,6 +122,20 @@ else
   echo "GitHub Release: SKIPPED (gh CLI not available)"
 fi
 
+# --- 5. Developer verification guidance freshness ---
+# After Q3 2026, the developer-verification README section must have been
+# reviewed. The "(reassess Q3 2026)" tag triggers a warning if the current
+# date is past 2026-09-01 and the tag is still present — it means the
+# guidance was not updated for the enforcement window.
+if grep -q "reassess Q3 2026" README.md 2>/dev/null; then
+  current_date="$(date -u +%Y%m%d 2>/dev/null || echo 20260101)"
+  if [ "$current_date" -ge "20260901" ]; then
+    fail "README.md developer-verification section still says 'reassess Q3 2026' but we are past that date — update the guidance"
+  else
+    echo "developer-verification: OK (reassessment date not yet reached)"
+  fi
+fi
+
 # --- Summary ---
 if [ "$errors" -gt 0 ]; then
   echo "release-front-door: FAIL ($errors error(s), $warnings warning(s))"