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>

docs/vision.md

@@ -162,9 +162,9 @@ source formulas). Bond adapts to its operands:
 
 | bond | Proto | Mol | Wisp |
 |------|-------|-----|------|
-| **Proto** | Compound Proto | Spawn + attach | Spawn wisp + attach |
-| **Mol** | Spawn + attach | Link | Link |
-| **Wisp** | Spawn + attach | Link | Link |
+| **Proto** | Compound Proto | Pour + attach | Wisp + attach |
+| **Mol** | Pour + attach | Link | Link |
+| **Wisp** | Wisp + attach | Link | Link |
 
 This enables patterns like:
 - Patrol wisp discovers issue → bonds new work mol
@@ -240,7 +240,7 @@ Patrol agents run ephemeral wisps for their cycles:
 - Wisp starts at cycle begin
 - Steps complete as work progresses
 - Wisp squashes to digest at cycle end
-- New wisp spawns for next cycle
+- New wisp created for next cycle
 
 This prevents accumulation: patrol work is vapor that condenses to minimal
 digests, not liquid that pools forever.