EEx-template assigns, native-tree template/static roots, dep resolution, and Pythonx wiring for mix mob.adopt.

Duplicated from MobNew.ProjectGenerator (mob_new, the project generator archive). Only the transitive closure mix mob.adopt exercises was copied — the full mix mob.new generation pipeline (generate/3, liveview_generate/3, the mix phx.new shell-out, the config/router patchers) stays in mob_new. Phase 5 of build_system_migration.md reunifies the two copies behind a single Igniter-based path; until then both repos carry their own copy (mob_new can't depend on mob_dev — it's a self-contained Mix archive; see ArchiveSelfContainedTest).

Native templates come from the installed mob_new archive

The Android/iOS native trees mob.adopt emits are rendered from mob_new's priv/templates/mob.new/ and priv/static/mob.new/. Those template files belong to the generator and are deliberately NOT duplicated here. By design, mix mob.adopt --android/--ios requires the mob_new archive installed (mix archive.install hex mob_new) in addition to mob_dev as a project dep — mob_new stays the single source of native templates, so the two can't drift. Mix puts an installed archive on the code path, so :code.priv_dir(:mob_new) resolves its bundled priv at runtime — the same way mob_new's own mix mob.new loads them. templates_root/1 / static_root/1 prefer that, then fall back to a local checkout via $MOB_NEW_DIR / ~/code/mob_new for development. See decisions/2026-06-19-mob-adopt-lives-in-mob_dev.md.

Compile-time regex

Compiles regexes at runtime via Regex.compile!/1, never ~r// literals (OTP 28.0 dropped :re.import/1). See mob AGENTS.md rule #9.