terminology: spawn → pour/wisp for molecules (gt-9uy0)

Molecules use chemistry verbs, not spawn:
- pour = create persistent mol (liquid)
- wisp = create ephemeral wisp (vapor)
- spawn = polecats only (workers)

Changes:
- Delete chemistry-design-changes.md (migration doc)
- Remove migration tables from sling-design.md
- Update bond tables: Spawn → Pour/Wisp
- Rename spawnMoleculeFromProto → pourMoleculeFromProto
- Rename spawnMoleculeOnIssue → runMoleculeOnIssue
- Update templates: bd mol spawn → bd wisp
- Update prime.go: commands and messages
- Clean all docs and comments

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

internal/templates/roles/refinery.md.tmpl

@@ -208,7 +208,7 @@ These consume minimal context. But complex rebases are different:
 1. Read `state.json` for `simple_merges` and `complex_merge`
 2. If `complex_merge == true` → hand off immediately
 3. If `simple_merges >= 20` → hand off
-4. Otherwise → continue patrol, spawn new wisp
+4. Otherwise → continue patrol, create new wisp
 
 **Rationale**: A clean rebase is a button-push. A conflict resolution fills context
 with diffs, decisions, and debugging. Fresh context handles the next conflict better.