From b03fb252d8a94aea4d8b10df51188ed5dbc42ada Mon Sep 17 00:00:00 2001
From: Waters Church <info@waterschurch.org>
Date: Thu, 24 Sep 2026 15:50:35 -0400
Subject: [PATCH] Note in index.html how a change here reaches the web and the
 apps

This directory feeds both targets by different routes, and the difference is the
thing people get wrong: the website serves it directly, while the apps carry a
copy frozen at build time. Someone editing here reasonably assumes a deploy is
enough, and for the website it is.

Written at the top of the file rather than in a README because this is where the
assumption gets made.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 server/public/index.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/server/public/index.html b/server/public/index.html
index 5a1cd84..a1a7963 100644
--- a/server/public/index.html
+++ b/server/public/index.html
@@ -1,4 +1,12 @@
 <!DOCTYPE html>
+<!-- This directory is the source of truth for both the website and the apps. The website
+     serves it directly; mobile/scripts/sync-web.js copies it into the iOS and Android
+     bundles at build time, so the apps carry a FROZEN copy taken when they were last built.
+
+     A change here therefore reaches the two in different ways: pushing to main redeploys
+     the website within a minute, and separately rebuilds both apps on the ingest Mac and
+     emails that they are behind — but nothing reaches a phone until someone runs
+     ./release.sh --ios --android and the stores approve it. -->
 <html lang="en">
 <head>
     <meta charset="UTF-8">