Clarify source-bound release identity

Author: Manablaq

docs/ENVIRONMENT.md

@@ -74,7 +74,11 @@ application release. It is not the current source-bound coordinator.
 
 ## Current source-bound deployment
 
-Repository HEAD: `6fe34484acb4bb21afd8f438ecac00e7780042e1`
+Source-binding release commit: `6fe34484acb4bb21afd8f438ecac00e7780042e1`
+
+The current `main` branch may contain later documentation and verification-only
+commits; the source-binding commit above is the exact code revision that
+introduced the certified frontend anchor.
 
 Base GitHub main before publication:
 

docs/LIVE_STUDIO_NEXT_LIFECYCLE_2026-09-16.md

@@ -8,7 +8,7 @@ transactions settled.
 ## Release identity
 
 - Repository: `https://github.com/Manablaq/commit-protocol`
-- Repository HEAD: `6fe34484acb4bb21afd8f438ecac00e7780042e1`
+- Source-binding release commit: `6fe34484acb4bb21afd8f438ecac00e7780042e1`
 - Coordinator source: `contracts/commit.py`
 - Coordinator source: 19,873 bytes
 - Coordinator SHA-256: `e235731ac223ee136b06b8cfc332065927a03553a3b1f5531571cd4d5da119c6`