hedgehog-landing-looplisted

# Hedgehog Landing Loop The operating loop for a bootstrapped `landing-page` project: `hedgehog claim --owner <owner> --count <n>` emits the packet for one ready phase (this core's chain is linear, so `--count N` always returns 1), run it through its owning agent, `hedgehog verify` gates and commits it. The build graph (`.hedgehog/hedgehog.db`) is the live list — query it via `hedgehog status`/`hedgehog ready`, never re-derive state from prose. The five compiled phases (`src/golden-cores/landing-page/core.yaml`, already the source of truth) are the degenerate one-module case of the layer graph: one task per phase, each depending on the one before it. This is the **Chain Method**: a pipeline where every visual choice traces back to a reason. No agent may introduce a choice that doesn't originate in the previous agent's output — that discipline is what this skill enforces mechanically, the same role Nx module boundaries play for `full-stack-app`. ## Planning intake (Phase 0, before any build phase) Run once, before `bootstrap` scaffolds the workspace. Opens with `hedgehog-planning-intake`'s Phase 0 — the same vendored BMAD-METHOD shelf `full-stack-app` runs, in the same full sequence, archived to the same `.hedgehog/BMAD/` layout. After that Phase 0 completes, this section does its own mining — a one-paragraph subject statement, the landing-page counterpart to `hedgehog-planning-intake`'s own Phase 1 (domain modules and an Add-ons decision on full-stack-app). That mined dra