railiance-platform/workplans/RPF-WP-0031-workplan-identity-collision.md

id	type	title	domain	repo	status	owner	created	updated
RPF-WP-0031	workplan	Separate duplicated apps-pg and Core Hub workplan identities	financials	railiance-platform	blocked	codex	2026-09-05	2026-09-05

Separate duplicated workplan identities

Diagnose and prepare the exact repair

id: RPF-WP-0031-T01
status: done
priority: high

The supported rmgr sync --path . --push path reached the verified primary railiance01 projection in 5.8 seconds, but refused six duplicate identities. Both the May apps-pg archive and August Core Hub onboarding use RPF-WP-0021, the same workplan UUID, and the same first five task UUIDs. No projection rows were created, changed, or retired by the refused reconciliation.

docs/evidence/RPF-WP-0021-collision-repair-proposal.json fixes the proposed choice: retain the older archive and reidentify the newer onboarding record as RPF-WP-0030, with six Repo Manager-derived UUIDs and four evidence-reference updates. Existing source UUIDs have not been changed.

Apply the identity repair and reconcile

id: RPF-WP-0031-T02
status: wait
priority: high

Requires a one-time user exception to AGENTS.md's prohibition on editing managed UUID fields. The existing Repo Manager migration command considers only live workplans and unfinished tasks, so it does not repair these finished records. After approval, apply the exact proposal, preserve the archived identity and all completion evidence, check uniqueness across root and archived workplans, commit/push, and run rmgr sync. Inspect any retirement refusal before proceeding; never blanket-acknowledge unrelated retirements.