ACTIVITY-WP-0020-T07: multi-cluster protection mechanism + cluster census

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

workplans/ACTIVITY-WP-0020-weekly-forgejo-package-prune.md

@@ -268,6 +268,23 @@ prune must aggregate live tags across **all** production clusters/contexts (or r
 where it sees them) before enable/apply. Enable/apply remains gated until every
 production cluster's live tags are protected in one dry-run.
 
+**Progress 2026-07-18:** multi-cluster mechanism landed
+(`railiance-platform@ca4e152`): repeatable `--live-images-file` merges
+image lists exported from other clusters (unit-tested; missing file =
+WARN). Cluster census: railiance01 k3s runs activity-core as a
+**locally-imported image** (`activity-core:railiance01-prod`) — no live
+workload pulls the forgejo `activity-core` packages at all, defusing the
+original fear; its live forgejo tag is `state-hub:main-1cf949b`. The
+coulombcore cluster's live forgejo tags: `issue-core:0.2.1`,
+`state-hub:f2e042a`, `vergabe-teilnahme:064d295`. Both clusters' exports
+staged (workstation scratchpad; coulombcore list also copied to
+`railiance01:~/.local/share/forgejo-prune/live-images-coulombcore.txt`).
+**Remaining (operator, ~5 min):** provide a Forgejo PAT
+(`/tmp/forgejo-tegwick-api-token`, chmod 600) and run
+`tools/cmd/forgejo-package-prune --live-images-file <railiance01 export>`
+— if all live tags land in protected/absent from would_delete, T07
+acceptance is met and T05 enable + T06 apply unblock.
+
 ---
 
 ### T06 — First apply run and backup impact evidence