harness-bootstraplisted

# Super Bootstrap — Development Pipeline for Any Repo Set up (or sync) the development pipeline in a project. Installs harness — workflow rules, doc-sync gate, skeleton docs, core plugin pins — in one scaffold session. The doc-sync gate at every later commit grows the skeleton docs over time, so there's no deferred deep-scan stage. Designed for a solo developer working across multiple Claude Code sessions and cloud Claude Code. ## Phase 1: Quick Scan (lightweight, parallel reads) Gather just enough to scaffold — skim manifests for stack/version, note structure shape, stop. Check contributor count (`git shortlog -sn --all | head -5`). If >1 active contributor, surface as info — don't block: > "FYI: detected multiple contributors. The pipeline's CLAUDE.md assumes solo dev (simple branching, no PRs for self-review). You can edit those sections after bootstrap if your team's workflow differs." ### Sampling Discipline (applies to all source-file reads) Throughout this skill — Phase 1 detection, anywhere Claude reads source files — **paraphrase structure into committed docs; never paste raw file contents.** Skip files whose names suggest secrets (e.g. `.env*`, `*.key`, `*.pem`, `id_*`, `*credential*`, `*secret*`, `.npmrc`, `.netrc`, `*.p12` / `*.pfx`, `*.keystore`, `kubeconfig` — illustrative, judge by name). When skipping, surface to user: `⊘ skipped <path> (likely secret)`. Reason: reading alone isn't the breach — Claude's context isn't shared. The breach is **quoting ra