harnessloop-setuplisted

# Harnessloop Setup Walk the user through completing the Harnessloop project setup skeleton that `$harnessloop-init` creates empty. This skill is a conversation-driven wizard backed by a machine-readable completeness check (`check_setup.py`); it does not execute business work, does not accept a round, and does not replace `$harnessloop-goal`, `$harnessloop-loop`, or `$harnessloop-continue`. ## Input Contract Accept an explicit skill invocation such as `$harnessloop-setup`, or natural language asking to complete, check, or resume Harnessloop setup. Treat `harnessloop:setup` and `harnessloop setup` as natural-language aliases only; `$harnessloop:setup` is not a valid skill invocation. Useful input includes: - `target-project`: defaults to the current working directory. - Optional request to run a single step only (e.g., "just the control-contract step"). - Optional profile preference for S4 (`lite`, `standard`, or `strict`). If `.harnessloop/` is missing, stop and suggest `$harnessloop-init`. If imported intake work is pending and has not passed the intake gate, route to `$harnessloop-intake` before running this wizard. ## Completeness Check (`check_setup.py`) Run this before asking the user anything, every time this skill is invoked: ```bash python3 -B <plugin-root>/skills/harnessloop-loop/scripts/check_setup.py --project <target-project> --json ``` The `-B` flag (or `PYTHONDONTWRITEBYTECODE=1`) guarantees no `__pycache__` bytecode is written, so this check stays rea