cue doctor already tells users to run cue toolkit install <tool> when a dependency is missing, and doctor fix --all runs that exact command, but there is no cue toolkit command defined in cmd/ yet. The doctor workflow therefore points to a non-existent CLI entrypoint.
Building a cmd/toolkit.go (or similar) that hooks into internal/toolkit.Registry and exposes at least list, install, and upgrade subcommands would make the doctor's fixes actionable. Contributors can reuse the existing toolkit engine to print tool metadata, call toolkit.Install, and wire the new command into rootCmd. With that in place, the doctor's user guidance and automation become meaningful.
cue doctoralready tells users to runcue toolkit install <tool>when a dependency is missing, anddoctor fix --allruns that exact command, but there is nocue toolkitcommand defined incmd/yet. The doctor workflow therefore points to a non-existent CLI entrypoint.Building a
cmd/toolkit.go(or similar) that hooks intointernal/toolkit.Registryand exposes at leastlist,install, andupgradesubcommands would make the doctor's fixes actionable. Contributors can reuse the existing toolkit engine to print tool metadata, calltoolkit.Install, and wire the new command intorootCmd. With that in place, the doctor's user guidance and automation become meaningful.