source: repo-manager reason: deterministic projection registration Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
1.7 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | state_hub_workstream_id |
|---|---|---|---|---|---|---|---|---|---|---|
| RMGR-WP-ADHOC-2026-09-11 | workplan | Preserve seven bound historical Railiance task labels during routine sync | infotech | repo-manager | finished | codex | infotech | 2026-09-11 | 2026-09-11 | c0eb5694-b35c-5c14-ae69-2d11be879175 |
Preserve closed historical item labels without identity migration
id: RMGR-WP-ADHOC-2026-09-11-T01
status: done
priority: medium
state_hub_task_id: "4fbbe0d9-8731-5010-8867-9fab956eae71"
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.