harnessloop-initlisted

# Harnessloop Init Initialize Harnessloop in the target project and prepare the project for the full `$harnessloop-loop` protocol. Treat `harnessloop:init` as an invocation phrase for this skill; skill names cannot contain `:`, so the installed skill name is `harnessloop-init`. ## Input Contract Accept a target project path, optional intake slug, and optional mode: - `target-project`: defaults to the current working directory. - `intake-slug`: optional; use when initialization is for taking over an existing agent session. - `dry-run`: optional; preview files without writing. - `force`: optional; overwrite generated files only after explicit user confirmation. Accept an explicit skill invocation such as `$harnessloop-init this repo` or `$harnessloop-init --project C:\repo --intake task-slug`. Treat `harnessloop:init` as a natural-language alias only; `$harnessloop:init` is not a valid skill invocation. ## Processing Contract Resolve the target project, check whether `.harnessloop/` already exists, then prefer the bundled initializer from `harnessloop-loop/scripts/init_project.py`. If the initializer is unavailable, create only the minimal protocol skeleton. Do not infer project facts, credentials, goals, data sources, or validation results. ## Output Contract Return the target project path, whether initialization was created, skipped, previewed, or blocked, and the files/directories created or expected. If intake was requested, return the transfer packet path and tell