# `mix mob.regen_plugin_manifest`
[🔗](https://github.com/genericjam/mob_dev/blob/master/lib/mix/tasks/mob.regen_plugin_manifest.ex#L1)

Regenerates `priv/generated/mob_plugins.exs` — the host's **runtime plugin
manifest** — from the activated plugins' tier-3/4 manifest sections.

    mix mob.regen_plugin_manifest          # regenerate the file
    mix mob.regen_plugin_manifest --check  # verify on-disk matches, non-zero on drift

Tiers 3 (multi-screen) and 4 (sub-app) are pure-Elixir and runtime-wired: the
on-device `Mob.Plugins` module reads this file at boot to learn which screens,
lifecycle hooks, settings, and notification handlers the activated plugins
declared (`MobDev.Plugin.activated/0` is compile-time only). Spec-v2
`:screens_generator`s run here, under the host-config audit.

Like `mix mob.regen_driver_tab`, the output is committed so reviewers see the
runtime surface, and the file is regenerated whenever `config :mob, :plugins`
changes. `mob.doctor` runs `--check` to report drift.

---

*Consult [api-reference.md](api-reference.md) for complete listing*