hedgehog-bootstrap-authored-corelisted

# Hedgehog Bootstrap — authored core Lands the workspace for a project whose core `hedgehog-core-design` designed. `hedgehog init` never scaffolds anything core-specific until a core is actually chosen, so nothing needs clearing here — this skill is the first thing that writes a workspace for this project. The stack varies per project (`hedgehog-core-design`'s Step 2 stack table), so it's generated live from the ecosystem's own tooling and verified before it's committed. ## Steps ### 1. Confirm this hasn't already run Check for a `feat(<project>): workspace` commit matching `.hedgehog/core.yaml`'s `id` (`git log --oneline --grep="^feat("`), or the presence of a root config file the stack in `core-design.md` would produce (e.g. `wxt.config.ts` for a WXT browser extension, `pyproject.toml` for a Python CLI). Either means this already ran — stop there. A workspace that looks wrong is a Correction Protocol case against the specific file. ### 2. Fill in `CLAUDE.md`'s core section Root `CLAUDE.md` was landed by `init` as a shell with its `{{CORE_SECTION}}` placeholder still unfilled (no core was known yet). Read `src/templates/CLAUDE.core.authored.md` from the installed Hedgehog package and write its contents in place of the placeholder — every other line in root `CLAUDE.md`, including the `{{PROJECT_NAME}}`/ `{{PROJECT_SUMMARY}}` values `planner` already filled at planning intake, stays untouched. If the placeholder is already filled (a project that ran `init` with an expli