Why: the recovery plan is the record for the remaining identity, rollback, and real-combo gaps.
Evidence: read-only queries on the 20261012T133921Z snapshots. No rows were moved.
Impact: adds r3.1. Earlier unapproved r3 text stays unapproved.
Refs: Dev feature/svc-d1-identity-flow
Why: the recovery plan is the record for the remaining identity, rollback, and real-combo gaps.
Evidence: read-only queries on the 20261012T133921Z snapshots. No rows were moved.
Impact: adds r3.1. Earlier unapproved r3 text stays unapproved.
Refs: Dev feature/svc-d1-identity-flow
Why: the 2026-10-12 batch-update failure still had identity, rollback, and real-combo gaps after Dev #474, Backend #180, and RDM #276. The recovery plan is the single record for that work, and the rdmcand data-ownership check needed a written result before any restore.
Evidence: read-only queries on runtime-backups/{dev,rdm1,rdmcand}/20261012T133921Z and the matching domain backups. No business rows were moved.
Impact: adds r3.1 sections D1/D2/D3 and the ownership finding that dev conversations predate rdmcand's use of dev/data, so no cross-instance restore is indicated. r3's earlier unapproved text stays unapproved.
Refs: Dev feature/svc-d1-identity-flow; Backend feature/d1-identity-open
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit 733f32c671 into main2026-10-12 15:07:07 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: the recovery plan is the record for the remaining identity, rollback, and real-combo gaps.
Evidence: read-only queries on the 20261012T133921Z snapshots. No rows were moved.
Impact: adds r3.1. Earlier unapproved r3 text stays unapproved.
Refs: Dev feature/svc-d1-identity-flow