recursive-spine-bootstraplisted

# recursive-spine: bootstrap Stamp the convention onto the current repo. Read `${CLAUDE_PLUGIN_ROOT}/reference/principles.md` first. If the user hasn't seen the convention before, offer the `recursive-spine-method` skill before stamping. ## 1. Preflight (fail loud, not silent) - `gh auth status` — must be authenticated. - `gh repo view --json nameWithOwner` — must be a GitHub repo. - Board membership needs project scope: run `gh auth status` and check for `project` scope. If absent: DO NOT silently skip. Tell the user exactly what's missing (`gh auth refresh -s project`) and file a repo issue titled "spine: board membership pending (missing gh project scope)" so the gap is a record, not a memory. ## 2. Interview (one question at a time) 1. Which modules? Deferral is mandatory (offer alias naming, default `deferred`). Offer gap / debt / lane with one-line failure-mode pitches. If lane is chosen: ask the builder to NAME their own tiers — offering the tier names found in the repo's tokenomics playbook when one exists. Ship no default lane names — tokenomics' rule; the tiers are the builder's own words. 2. Dialect: what does this repo call a unit of work? Any existing label conventions to respect? 3. Board: add this repo to the user-level "Spine" Projects board? (Needs the scope from preflight.) 4. If the plumb-line plugin is installed (check for a `plumb-line-bootstrap` skill): offer it for epistemic enforcement — separate concern, their c