X_REGISTRAR_CONFLICT
Means
two different registrars are loaded for one primitive kind
Typical cause
two copies of the kind's owning package in the dependency tree (task → @ultimat3/jobs, mutator → @ultimat3/action, route → @ultimat3/render), each with its own registry, so half the primitives register where nothing reads them. bun pm why <owning package> names the dependents when ranges genuinely disagree
Fix
bun update <owning package> — the error's own fix: names it