recursive-spine-pollinatelisted

# recursive-spine: pollinate Two modes. **Capture** files a proven element into a hive; **pull** brings hive pollen into the current work. Ask which the user wants if the invocation doesn't say. Read `${CLAUDE_PLUGIN_ROOT}/pollen/README.md` for the record schema before writing any record. ## Hive configuration (both modes, first) Read the invoking repo's dialect note (`docs/tracking-dialect.md` or equivalent) for a `pollinate:` section listing hive repos and each hive's visibility. If absent, interview — never assume: 1. "Which repo is your hive (where pollen records live)?" Accept several; record each as `owner/repo (public|private)`. 2. If the builder works across public and private projects, recommend one hive per visibility scope (the two-hive model): private-proof pollen must never enter a hive whose readers can't see its source. 3. Write the answers to the dialect note before proceeding. No default hive ships with this skill — the hive is the builder's own answer. Degraded modes, always loud: no `gh` auth or not in a repo → draft the record locally, print it, and tell the builder exactly what to file where. Hive unreachable → report the error and stop; never guess. ## Capture mode 1. **Interview (brief — target under a minute):** - What worked? (one sentence) - What form is it? `snippet` / `pattern` / `skill-candidate` / `config` - Where's the proof? (repo + issue/PR — the `source:` field; the proof must exist, per the no-invented-pollen