mix sv_ex.
Copy Markdown
Generates a stock Elixir or Phoenix project, adds the sv_ex dev
dependency, writes target.exs, and fetches and compiles dependencies.
mix sv_ex.new NAME --base otp|api|web --github-org ORG [--sv-ex-path PATH]Post-MVP continuation — verified working, deliberately NOT implemented
The four-step sequence that hands off to mix sv_ex.gen once it exists is
recorded verbatim, with the reason each step is load-bearing, in this
project's README.md under "Post-MVP continuation".
It is kept there rather than here because SvEx.BoundaryGuard
substring-scans this perimeter's lib/**/*.ex — documentation and comments
included — and two of those four calls are on its banned list. Prose naming a
banned API is indistinguishable from a call to it, which is the point: the
guard exists because a rule expressed only in prose rots.
Running that sequence today buys nothing — sv_ex.gen does not exist — and
deps.compile prunes every archive off the code path before it could.