hedgehog-contributinglisted

# Contributing to Hedgehog Walks a user from "I want to fix/build this in Hedgehog itself" to an open pull request against `skyf0xx/hedgehog`. This is for changes to the **discipline** — `src/agents/`, `src/skills/`, `src/templates/`, `bin/cli.mjs`, `README.md` — never for changes to the user's own project, which is a different repo with different rules. ## When this runs - The user names a specific gap (a bug they hit, a `ROADMAP.md` item) and wants to fix it in Hedgehog rather than work around it locally. - `tweaker` offered this at the end of a build and the user said yes. If the user hasn't picked a target yet, read `ROADMAP.md` at the Hedgehog repo root with them and let them choose an item — prefer the "Small items" tier for a first contribution, since each entry there is scoped to one file or one narrow addition. ## Before starting Confirm where the Hedgehog source actually lives on this machine. A project that ran `npx @skyf0xx/hedgehog init` has a *copy* of the payload (`.claude/agents/`, `.claude/skills/`), not the Hedgehog repo itself — editing those files changes nothing upstream. Ask the user: - If they already have a local clone of `skyf0xx/hedgehog`, use it. - If not, offer to clone it: `gh repo fork skyf0xx/hedgehog --clone` (forks under their account and clones the fork), or `git clone https://github.com/skyf0xx/hedgehog` if they'd rather push directly to a branch on a repo they already have write access to. Do this in a separate directory fro