Remove retired chat placeholder and stale deployment documentation

1 files changed, 3 insertions, 4 deletions

diff --git a/docs/GIT-HISTORY.txt b/docs/GIT-HISTORY.txt
index 2dfc335..410b53b 100644
--- a/docs/GIT-HISTORY.txt
+++ b/docs/GIT-HISTORY.txt
@@ -20,15 +20,15 @@ GIT IDENTITY AND SIGNATURE REWRITE
     RSA-2048 key 3346AA3150F8F16828BB0D14F8C66DF77AFECEA6.
 
     Ten historical author identities and their corresponding committer identities
-    were corrected. All 27 commits reachable from main and feature/private-chat
+    were corrected. All 27 commits reachable from the two published branches
     at the time of the rewrite were recreated and signed because rewritten
     parents change descendant commit IDs. Every new signature was verified.
 
     Every corresponding tree, message, original author timestamp/time zone, and
     original committer timestamp/time zone was preserved. Merge topology was
     preserved. Signature creation times reflect the new signing operation.
-    main's file tree is unchanged. Configuration/chat development stays on
-    feature/private-chat; rewriting metadata does not deploy that code to main.
+    At the time, main's file tree was unchanged and chat development was separate.
+    Chat has since been merged into main; the temporary feature branch was deleted.
 
     Remote updates use an atomic push and exact force-with-lease expectations
     for both branches, preventing overwrite of an unexpected remote update.
@@ -48,7 +48,6 @@ EXISTING CLONES
         git switch main
         git reset --keep origin/main
 
-    For a feature checkout, use feature/private-chat in the final two commands.
     --keep refuses updates that would overwrite conflicting working changes.
     Do not blindly reset a clone with independent local work; use the mapping
     below to identify the corresponding rewritten base before rebasing that work.