upgrade

1## Runtime Configuration (Step 0 — before any processing)
2 
3Read these files to configure domain-specific behavior:
4 
51. **`ops/derivation-manifest.md`** — vocabulary mapping, platform hints
6   - Use `vocabulary.notes` for the notes folder name
7   - Use `vocabulary.note` / `vocabulary.note_plural` for note type references
8   - Use `vocabulary.reduce` for the extraction verb
9   - Use `vocabulary.reflect` for the connection-finding verb
10   - Use `vocabulary.reweave` for the backward-pass verb
11   - Use `vocabulary.verify` for the verification verb
12   - Use `vocabulary.rethink` for the meta-cognitive verb
13   - Use `vocabulary.topic_map` for MOC references
14 
152. **`ops/config.yaml`** — processing depth, domain context
16 
173. **`ops/derivation.md`** — derivation state and engine version
18 
19If these files don't exist, use universal defaults.
20 
21## EXECUTE NOW
22 
23**Target: $ARGUMENTS**
24 
25Parse immediately:
26- If target contains a specific skill name (e.g., "upgrade reduce"): check only that skill
27- If target contains "--all": check all generated skills
28- If target is empty: check all generated skills (same as --all)
29 
30**START NOW.** Reference below defines the upgrade process.
31 
32---
33 
34## Why Consultation, Not Hashing
35 
36Skills do not upgrade through hash comparison against a generation manifest. Hash comparison answers a narrow question: "Has this file changed?" Meta-skill consultation answers the right question: "Is this skill's approach still the best approach given what we know?"
37…