OTP Application callback for :mutagen_ex.
Boots the MutagenEx.Supervisor one-for-one root supervisor with a single
initial child: a named Task.Supervisor registered as MutagenEx.TaskSup.
Why this exists
Per .spec/decisions/supervision_tree.md:
- F25 closure — library callers depending on
:mutagen_exget a supervision tree on application start without writing any new public-API surface. Themix mutagenCLI path also benefits: the application boots as a side effect of the Mix task, soMutagenEx.TaskSupis available whenMutagenEx.MutationRunner.run/1enters its task body. - F2-arch foundation —
MutagenEx.TaskSupis the documentedTask.Supervisorwhoseterminate_child/2recursively kills the per-site task's link tree on a:timeoutoutcome. The swap fromTask.async+Task.shutdown(:brutal_kill)toTask.Supervisor.async_nolink/2+Task.Supervisor.terminate_child/2lands in S2; this S1 ticket only plants the supervisor. - F26 singleton-ownership contract —
MutagenEx.TaskSupis the named owner of:cover_serverandExUnit.Serverduring a MutagenEx mutation cycle. The rejection message inMutagenEx.CoverageRunner.run/1cites this module by name; the supervisor must exist at runtime for the contract to be enforceable.
Topology
MutagenEx.Supervisor (one-for-one, named)
└── MutagenEx.TaskSup (Task.Supervisor, named)No other children are added in S1. .30 (parallelism) will eventually
introduce sibling workers, but this is the minimum tree that closes F25
and gives S2 / S3 the named supervisor they reference.
Smoke check
From a fresh iex -S mix:
Process.whereis(MutagenEx.Supervisor) |> is_pid() # true
Process.whereis(MutagenEx.TaskSup) |> is_pid() # true