When a CLI wraps an external tool with necessary adjustments (path resolution, default flags, multi-step workflows), onboarding documentation must point users to the wrapper command, not the raw tool. In this case, the GoodTurn onboarding page showed harbor run -p tasks/my-task -a oracle (raw harbor) instead of goodturn env check tasks/my-task (the wrapper). The wrapper resolves relative paths to absolute (harbor silently fails on relative -p), passes required flags (--yes, -k 1, -n 1, --jobs-dir), runs lint before the container build, and executes both oracle and nop legs. Two known harbor pitfalls (relative paths, bare task names) were already solved in the CLI wrapper but users bypassed it because the onboarding page pointed elsewhere.