fix(registry): write command-not-found diagnostic to stderr
The registry's Exec returned an error wrapping ExitStatus(127) when a
command wasn't registered, but never wrote the diagnostic anywhere.
Callers like time and env that dispatch through the runner saw status
127 with no message, so users got a silent failure (and the matching
tests failed expecting "command not found" on stderr).
Assisted-by: Claude Opus 4.7 via Claude Code
Signed-off-by: Xe Iaso <me@xeiaso.net>