Keep one rollback tag derived from original release

docs/deployment/GITEA_CD.md

@@ -367,7 +367,7 @@ complete audit succeeded.
 ### Production image retention
 
 After a deployment passes verification and its success journal is saved, Frame Flow
-removes obsolete `release-<commit>-<owner>` and `rollback-<owner>` images from the
+removes obsolete release and rollback images from the
 configured production image repository. It retains the running version and the
 previous deployment baseline for one-step rollback. Images referenced by any
 container (including stopped containers), images with unrelated tags, and CI
@@ -376,3 +376,7 @@ Failed deployments do not run retention; cleanup failure produces a warning and
 never rolls back a successfully verified deployment. Historical deployment
 journals remain available for audit, but only the latest rollback image is
 retained locally; older releases require rebuilding before use.
+
+The rollback image keeps one tag: its original `release-<commit>-<owner>`
+tag with `-rollback` appended. Duplicate release/legacy rollback tags are removed
+only after the rollback alias exists, and container-referenced tags remain protected.