diff --git a/docs/forgejo-migration-inventory.md b/docs/forgejo-migration-inventory.md
index ecb41df..98ec9eb 100644
--- a/docs/forgejo-migration-inventory.md
+++ b/docs/forgejo-migration-inventory.md
@@ -321,7 +321,22 @@ Examples not yet on Forgejo: `llm-connect`, `the-custodian`, `flex-auth`,
 
 All Forgejo-hosted registered repos now point at `forgejo-remote` (12 hub
 remotes including tier-2.5 stack, tier-3 services, `ops-warden`). Remaining
-52 registered repos still use `gitea-remote`.
+51 registered repos still use `gitea-remote`.
+
+### Wave 2 promotion queue (T10/T11)
+
+Hub-registered repos on Gitea only (**29**). Suggested order (operator approval
+for tier 3):
+
+| Tier | Repo | Notes |
+| ---: | --- | --- |
+| 1 | `ihp-railiance-probe` | Integration probe; promote before tier-3 wave |
+| 2 | `artifact-store`, `ops-bridge`, `open-reuse`, … | Non-production / tooling |
+| 3 | `llm-connect`, `the-custodian`, `user-engine`, `flex-auth`, `vergabe-teilnahme`, `railiance-fabric` | Production-adjacent; gated |
+
+Per-repo procedure: `railiance-enablement/tools/promote-repo-to-forgejo.sh`,
+then `patch-forgejo-remote-urls.sh <slug>`, then `statehub fix-consistency --repo <slug>`.
+See `the-custodian/docs/forgejo-tier3-remote-url-sweep-playbook.md`.
 
 ## Addendum (2026-07-04) — migration ladder and new repos
 
diff --git a/tools/forgejo-restore-drill.sh b/tools/forgejo-restore-drill.sh
index e0ae028..f892625 100755
--- a/tools/forgejo-restore-drill.sh
+++ b/tools/forgejo-restore-drill.sh
@@ -26,7 +26,7 @@ copy_backup_to_pod() {
   step "Chunked copy (${size} bytes) to pod"
   chunk_dir="$(mktemp -d)"
   trap 'rm -rf "${chunk_dir}"' RETURN
-  split -b 48m -a 3 "${src}" "${chunk_dir}/part-"
+  split -b 16m -a 3 "${src}" "${chunk_dir}/part-"
   for part in "${chunk_dir}"/part-*; do
     kubectl cp "${part}" "${dest_ns}/${dest_pod}:/backup/$(basename "${part}")" -c "${container}"
   done
diff --git a/workplans/RAIL-HO-WP-0005-forgejo-production-migration.md b/workplans/RAIL-HO-WP-0005-forgejo-production-migration.md
index eabb377..6f5af3b 100644
--- a/workplans/RAIL-HO-WP-0005-forgejo-production-migration.md
+++ b/workplans/RAIL-HO-WP-0005-forgejo-production-migration.md
@@ -596,10 +596,11 @@ T05+T08 ──► T10 migration ladder ──► T11 production cutover ──
 T03 isolated probe: CANCELLED (superseded by T05 + in-production pilots)
 ```
 
-**Current focus (2026-07-08):** T05/T06/T07/T08 **done**; T09 **restore drill from
-offsite backup passed**; backup 7-day gate counting. T10 tiers 0–2.5 complete.
-Next: complete 7-day backup gate, tier-3 promotions with operator approval
-(T10/T11). `ops-warden` hub patch pending approval.
+**Current focus (2026-07-08):** T05/T06/T07/T08 **done**; T09 restore drill **passed**;
+backup 7-day gate **1/7** (chunked `forgejo-backup` fix in `railiance-platform`;
+intermittent kubelet 502 on manual rerun). T10: `ihp-railiance-probe` promoted
+tier-1 + hub `remote_url` patched; wave-2 queue in inventory (29 hub-registered
+Gitea-only repos). Next: backup gate, tier-3 wave with operator approval.
 
 **Absorbed by `CUST-WP-0054-T04`:** forge + CI on railiance01; workstation
 build retirement; staged repo promotion before State Hub primary move (T05).