upgrade

## Runtime Configuration (Step 0 — before any processing) Read these files to configure domain-specific behavior: 1. **`ops/derivation-manifest.md`** — vocabulary mapping, platform hints - Use `vocabulary.notes` for the notes folder name - Use `vocabulary.note` / `vocabulary.note_plural` for note type references - Use `vocabulary.reduce` for the extraction verb - Use `vocabulary.reflect` for the connection-finding verb - Use `vocabulary.reweave` for the backward-pass verb - Use `vocabulary.verify` for the verification verb - Use `vocabulary.rethink` for the meta-cognitive verb - Use `vocabulary.topic_map` for MOC references 2. **`ops/config.yaml`** — processing depth, domain context 3. **`ops/derivation.md`** — derivation state and engine version If these files don't exist, use universal defaults. ## EXECUTE NOW **Target: $ARGUMENTS** Parse immediately: - If target contains a specific skill name (e.g., "upgrade reduce"): check only that skill - If target contains "--all": check all generated skills - If target is empty: check all generated skills (same as --all) **START NOW.** Reference below defines the upgrade process. --- ## Why Consultation, Not Hashing Skills 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?" A skill could be un...