rebar3 asobi check - the primary validation gate for an extension set.

rebar3 asobi check     # 0 and a summary, or 1 and a report naming both claimants

Add it to a host release's rebar.config:

{project_plugins, [{asobi, {git, "https://github.com/widgrensit/asobi.git", {tag, "v0.50.0"}}}]}.

This is the gate, not the backstop. asobi validates the same set again at boot, but a boot-time failure is raised from inside nova_sup:init/1 - Nova compiles the route table before asobi_app:start/2 runs - so it surfaces with Nova's crash context rather than a legible asobi error. Catching it in CI is the difference between "quests and clans both claim the Lua namespace \"quests\"" and a function_clause in somebody else's supervisor.

It runs asobi_extensions:check/0, the same function the boot backstop runs, so build time and boot cannot disagree about what is valid.

Core's reserved names come from the plugin's copy of asobi, which is the version in project_plugins. Pin it to the same tag as the dependency.