Design a Rust learning plan.

My programming experience: {{experience}}
My goal: {{goal}} (systems, web, embedded, cli, curiosity)
Daily time: {{daily_time}}

Return:
1. The mental model — why Rust feels different and what it's really protecting you from
2. Ownership, borrowing, lifetimes — explained in the right order
3. Pattern matching and the type system (enums and Option/Result done right)
4. Traits and generics — Rust's way of doing polymorphism
5. Error handling: Result, ? operator, error types
6. Cargo and the ecosystem
7. Async Rust — when to learn it (and when to delay it)
8. The borrow checker fight — what to do instead of fighting it
9. 3 projects in escalating difficulty
10. The honest truth: where Rust is worth the cost vs. where Go/Python is fine