Preserve closed Railiance item bindings during routine sync

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc

workplans/ADHOC-2026-09-11.md

@@ -0,0 +1,39 @@
+---
+id: RMGR-WP-ADHOC-2026-09-11
+type: workplan
+title: "Preserve seven bound historical Railiance task labels during routine sync"
+domain: infotech
+repo: repo-manager
+status: finished
+owner: codex
+topic_slug: infotech
+created: "2026-09-11"
+updated: "2026-09-11"
+---
+
+## Preserve closed historical item labels without identity migration
+
+```task
+id: RMGR-WP-ADHOC-2026-09-11-T01
+status: done
+priority: medium
+```
+
+Routine Railiance Apps sync stopped on seven completed, UUID-bound historical
+RAILIANCE-WP-0004-I01..I07 tasks while publishing the invited Vergabe pilot
+contract. Extend the existing historical-binding preservation path for exactly
+this closed parent and these labels. Conformance reporting remains strict;
+active/unfinished tasks, unbound or invalid UUIDs, other parents and I labels
+outside the observed set still refuse. Preserve existing source IDs, UUIDs,
+statuses and historical references. New records continue to require canonical
+IDs. No Hub identity mutation or sealed UUID migration is involved.
+
+The attempted label-only normalization was withdrawn before commit/projection:
+ordinary sync does not rename nonblank task record IDs, and changing the UUIDs
+would enlarge the task without improving the pilot. This explicit historical
+preservation resolves the routine sync blocker. Canonical migration remains the
+existing RMGR-WP-0005 programme, not a new pilot prerequisite.
+
+Validation: targeted historical/identity regression suite and Ruff, plus an
+actual Railiance Apps dry run preserving all seven bindings without assigning
+new UUIDs to them. Parent return is RAPPS-WP-0014 and HFACT-WP-0001.