hedgehog-adoptlisted

# Hedgehog Adopt Brings Hedgehog's discipline to a repo that already exists, without bootstrapping a workspace. On every other core, bootstrap generates or copies a workspace before any build step runs. Here there is nothing to generate — the workspace already exists, built by whoever wrote this repo — so this skill replaces bootstrap entirely rather than extending it. It writes `.hedgehog/` and nothing else, ever. ## What this is, precisely Hedgehog on an existing repo is a **permanent discipline for how change lands**, not an authority over what exists. The build graph covers new work only. Pre-existing code is context to read and respect, never a node in the graph — no task is ever created to "build" something that's already there, and no artifact record, commit, or task ever claims Hedgehog wrote code it didn't. `adoption.md`'s "Repo shape" section (Step 4) is a separate thing: a dated, prose snapshot of what Step 1 observed, refreshable by re-running this skill — never build-graph state, never authoritative past the date it was read, and never a substitute for reading the actual code. This is what makes adoption safe to run on a real, live codebase: - **The build graph never models pre-existing architecture.** Module boundaries, conventions, and shape live in `adoption.md`'s prose as a dated read, not as `core.yaml` state or task history — nothing about the existing repo is ever treated as something Hedgehog built or verified. - **No completion backfill.** I