refactor

## Runtime Configuration (Step 0 — before any processing) Read these files to configure domain-specific behavior: 1. **`ops/derivation-manifest.md`** — vocabulary mapping, dimension positions, platform hints - Use `vocabulary.notes` for the notes folder name - Use `vocabulary.note` / `vocabulary.note_plural` for note type references - Use `vocabulary.topic_map` / `vocabulary.topic_map_plural` for MOC references - Use `vocabulary.inbox` for the inbox folder name 2. **`ops/config.yaml`** — current live configuration (the "after" state) 3. **`ops/derivation.md`** — original derivation record (the "before" state) If these files don't exist, report error: "Cannot refactor without both ops/config.yaml and ops/derivation.md. These files establish the baseline and current configuration." --- ## EXECUTE NOW **INVARIANT: /refactor never executes without approval.** The plan is always shown first. **Target: $ARGUMENTS** Parse immediately: - If target is empty: detect ALL config changes and plan restructuring - If target names a specific dimension (e.g., "granularity", "organization"): focus on that dimension only - If target is `--dry-run`: show plan without asking for approval **Execute these phases:** 1. Detect changes between config.yaml and derivation.md 2. Plan restructuring for each changed dimension 3. Show the plan with affected artifacts and risk assessment 4. Execute on approval (unless --dry-run) 5. Validate post-restructuring **START NOW.** Reference...