Roadmap to v15 (skeleton)

[luccahuguet]

Roadmap to v15 (skeleton)

This is intentionally provisional and explicitly post-v14.

It is not meant to compete with the current pre-v14 packaging/hardening roadmap. The goal is just to capture the major directions that already look likely once v14 lands.

Tentative pillars

1. Selective Rust rewrites

Not a blind whole-CLI rewrite. The likely direction is to start with the most structured, failure-prone core logic first, and only move deeper into launch/bootstrap orchestration later if the boundaries are clear enough.

Relevant issue:

• Rust rewrite with spec-driven feature development #461 Rust rewrite with spec-driven feature development

2. Cleaner architecture and sharper subsystem boundaries

This includes clarifying what belongs to the backend/runtime layer, what belongs to the workspace UX layer, and what a future Core-style boundary would honestly look like.

Relevant issues:

• Define the Yazelix backend contract before evaluating alternative runtime backends #538 Define the Yazelix backend contract before evaluating alternative runtime backends
• Define the runtime dependency contract and launch preflight checker scope #532 Define the runtime dependency contract and launch preflight checker scope
• Implement a shared runtime contract checker and reuse it across launch and doctor #533 Implement a shared runtime contract checker and reuse it across launch and doctor
• Extract a backend adapter boundary around env, run, refresh, and launch bootstrap #534 Extract a backend adapter boundary around env, run, refresh, and launch bootstrap
• Audit and classify yzx command families by backend coupling #535 Audit the yzx command surface into backend-required versus backend-agnostic commands
• Define the Yazelix Core edition boundary and support story #536 Define the Yazelix Core edition boundary and support story

3. Profile Yazelix top to bottom

Before rewriting too much, I want better evidence about where the real pain points are across startup, refresh, launch, config generation, and related flows.

Relevant issue:

• Profile Yazelix boot/initialization end-to-end #257 Profile Yazelix boot/initialization end-to-end

4. A much stronger website and presentation layer

I want Yazelix to be explained, presented, and demoed much better than it is today.

Relevant issues:

• Website launch at yazelix.com #408 Website launch at yazelix.com
• Create a GitHub social preview image for Yazelix #465 Create a GitHub social preview image for Yazelix

Current stance

I do think these themes are real. I do not think the detailed v15 sequence is ready to lock in publicly yet.

So this discussion is a skeleton, not a promise.