refactor

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, dimension positions, 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.topic_map` / `vocabulary.topic_map_plural` for MOC references
9   - Use `vocabulary.inbox` for the inbox folder name
10 
112. **`ops/config.yaml`** — current live configuration (the "after" state)
12 
133. **`ops/derivation.md`** — original derivation record (the "before" state)
14 
15If 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."
16 
17---
18 
19## EXECUTE NOW
20 
21**INVARIANT: /refactor never executes without approval.** The plan is always shown first.
22 
23**Target: $ARGUMENTS**
24 
25Parse immediately:
26- If target is empty: detect ALL config changes and plan restructuring
27- If target names a specific dimension (e.g., "granularity", "organization"): focus on that dimension only
28- If target is `--dry-run`: show plan without asking for approval
29 
30**Execute these phases:**
31 
321. Detect changes between config.yaml and derivation.md
332. Plan restructuring for each changed dimension
343. Show the plan with affected artifacts and risk assessment
354. Execute on approval (unless --dry-run)
365. Validate post-restructuring
37…