Why: The approved r1 migration rule conflicts with the current candidate because legacy rows lack trustworthy per-key write times.
Evidence: Backend migration implementation and the r0.2 interface record specify explicit source selection and fail-closed project settings authorization.
Impact: Adds a clearly unapproved r1.1 review candidate without rewriting the approved r1 scope or claiming formal acceptance.
Refs: Dev feature/rdm-settings-completion Stage 4
weichen
62c2e2347e