OTP application for :taskweft.
When :taskweft is used as a library dependency (or under mix test /
mix run) this starts an empty supervision tree — no behaviour change for
consumers. When the app boots as the standalone Burrito binary from issue
#53, it starts a single Task that runs Taskweft.CLI.main/0, turning the
binary into a CLI: subcommands that produce output print and halt, and
mcp keeps the VM alive.
The CLI is only auto-run when the app is running as a Burrito-wrapped
standalone binary (Burrito.Util.running_standalone?/0, i.e. the __BURRITO
runtime marker is set), so starting :taskweft as one dependency among many
in another project's release does nothing. Set TASKWEFT_CLI=0 to suppress
it even in the standalone binary.