From a612bf72575c5c653425e3a335ce00be5d3cbfd1 Mon Sep 17 00:00:00 2001
From: Capri <caprimc@yahoo.com>
Date: Wed, 15 Jul 2026 14:56:15 +0000
Subject: [PATCH] Document safe public release workflow

---
 RELEASE_WORKFLOW.md | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 RELEASE_WORKFLOW.md

diff --git a/RELEASE_WORKFLOW.md b/RELEASE_WORKFLOW.md
new file mode 100644
index 0000000..bc5fa81
--- /dev/null
+++ b/RELEASE_WORKFLOW.md
@@ -0,0 +1,31 @@
+# Vexta Release Workflow
+
+## Repositories
+
+- Private development repository:
+  `~/Projects/vexta`
+
+  Contains the full development history.
+  Push is disabled for all remotes.
+
+- Public release repository:
+  `~/vexta-public`
+
+  Contains only clean public snapshots.
+  This is the only repository allowed to push to GitHub.
+
+## Future release process
+
+1. Finish and test changes in `~/Projects/vexta`.
+2. Create release binaries and checksums.
+3. Copy the current tracked source snapshot into `~/vexta-public`.
+4. Review the public diff carefully.
+5. Commit the public snapshot with a release-focused commit message.
+6. Create a version tag such as `v0.1.1`.
+7. Push only from `~/vexta-public`.
+8. Create the GitHub Release and attach binaries and checksum files.
+
+## Important
+
+Never push directly from `~/Projects/vexta`.
+Never push private phase tags or development branches to the public repository.