fix: remove private deployment metadata and retain release licenses

2026-10-18 16:14:56 +08:00
parent 4e9eccd809
commit 038b858eb7
9 changed files with 66 additions and 26 deletions
@@ -20,3 +20,17 @@ Publishing requires scanning all refs, removing private historic files, pruning
 unreachable remote Git objects and archiving/removing historical Actions logs.
 A private original mirror is retained outside the repository. Existing clones must
 reclone after the privacy history rewrite; do not merge the original history back.
+
+## Private deployment inputs
+
+Do not publish host addresses, workstation paths, disk UUIDs, photo-library counts,
+or deployment receipts. Keep receipts and recovery bundles outside the repository
+in an owner-only directory. A privacy history rewrite changes existing commit IDs;
+existing clones must be replaced instead of merging old history back.
+
+`server-release.py` reads `FRAME_FLOW_ROOT` (default `/srv/frameflow`), requires
+`FRAME_FLOW_MOUNT_UUID` and `FRAME_FLOW_ORIGIN`, and retains the mount-identity
+check before release actions. Supply verified values privately to the sudo process;
+existing installations must set their existing root explicitly. Do not use the
+generic default to migrate a deployment. The script still requires the existing
+mount guard and does not change host mounts, services, or storage automatically.