Setup

Announce at start: "I'm using the humane:setup skill to diagnose this machine before changing anything."

Two jobs, in this order: find out what is actually wrong, then fix only what the user agrees to fix. Never the other way round — a setup flow that installs first and reports afterwards is one that installs things nobody wanted.

scripts/humane_setup.py doctor          # read-only: config + every check + the fix for each gap
scripts/humane_setup.py config          # show resolved configuration and where each value came from
scripts/humane_setup.py config --set language=ru [--scope project]
scripts/humane_setup.py settings        # what each setting means

doctor writes nothing, installs nothing, and never asks for a key. It exits 1 only on a genuinely blocking gap; missing optional pieces exit 0, because most of the cycle works without them.