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/beads/christmas_ornament_test.go

@@ -8,7 +8,7 @@ import (
 )
 
 // TestChristmasOrnamentPattern tests the dynamic bonding pattern used by mol-witness-patrol.
-// This pattern allows a parent molecule step to dynamically spawn child molecules
+// This pattern allows a parent molecule step to dynamically create child molecules
 // at runtime, with a fanout gate (WaitsFor: all-children) for aggregation.
 func TestChristmasOrnamentPattern(t *testing.T) {
 	if testing.Short() {

internal/beads/molecules_patrol.go

@@ -234,7 +234,7 @@ completion, verify clean git state before kills, and escalate stuck workers.
 
 **You do NOT do implementation work.** Your job is oversight, not coding.
 
-This molecule uses dynamic bonding to spawn mol-polecat-arm for each worker,
+This molecule uses dynamic bonding to create mol-polecat-arm for each worker,
 enabling parallel inspection with a fanout gate for aggregation.
 
 ## The Christmas Ornament Shape