feedback(meta-convert-dev): from convert-clojure-roc creation

## Feedback: meta-convert-dev

### Context
- **Task**: Creating `convert-clojure-roc` skill
- **Used for**: Understanding APTV workflow, type mapping strategies, idiom translation patterns

### What Worked Well

1. **APTV Workflow Structure**: The Analyze → Plan → Transform → Validate workflow provided excellent scaffolding for organizing the conversion skill. This made it clear how to structure the skill content.

2. **Type Mapping Examples**: The type mapping tables (primitives, collections, composites) in meta-convert-dev were excellent templates. They made it clear what level of detail was needed and how to document edge cases.

3. **Idiom Translation Philosophy**: The explanation of Literal → Semantic → Idiomatic → Redesign translation levels was extremely helpful for understanding when to preserve source patterns vs adopt target idioms.

4. **Reference to Existing Skills**: The explicit instruction to read existing convert-X-Y skills as references was crucial. Reading convert-elm-clojure provided concrete examples of depth and style.

5. **Clear Skill Structure Template**: The provided markdown template with all required sections made it impossible to miss major content areas.

### Suggested Improvements

- [ ] **Add Platform Ecosystem Section**: For conversions involving platform/runtime differences (JVM, .NET, BEAM, Native), add guidance on how to document these architectural shifts. The Clojure → Roc conversion required explaining the fundamental JVM process → platform/application separation, which wasn't covered in the meta-skill examples.

- [ ] **Expand Paradigm Translation Guidance**: While idiom translation is covered well, some conversions require documenting deeper paradigm shifts (REPL-driven → compile-time, dynamic → static). Consider adding a dedicated "Paradigm Translation" section template for conversions that cross major paradigm boundaries.

- [ ] **Numeric Type Mapping Edge Cases**: Add more guidance on handling numeric type differences, especially:
- Arbitrary precision (Python/Clojure BigInt) → fixed-size integers
- Automatic promotion vs explicit sizing
- Division behavior differences (integer/rational/float)
- Overflow/underflow handling

- [ ] **Lazy vs Strict Evaluation**: Some conversions (Haskell/Clojure → Roc/Rust) involve lazy → strict evaluation shifts. Consider adding this to the common patterns section.

- [ ] **State Management Translation**: The atom/ref pattern → platform state translation was significant for Clojure → Roc but not well-covered in meta-convert-dev. Consider adding a "State Management" section to the template for languages with different state models.

### Additional Notes

The meta-skill is excellent overall. The suggested improvements are primarily about expanding coverage for less common but important conversion patterns (platform ecosystems, paradigm shifts, state management models).

The 8 Pillars validation approach from the command was very helpful for identifying gaps and planning mitigations.

Relates to #205

---
Feedback from: `/create-lang-conversion-skill clojure roc`