Product direction with the current line kept clear.
This roadmap is meant to be read plainly: what the current product baseline supports, where the next layer of depth is heading, and what still belongs in clearly future-looking language.
Build diagnosis, project reads, and clearly bounded workflows
The active baseline is strongest when Build Doctor leads, then expands into project intelligence, multi-surface access, and review-first workflow control.
Current baseline
This is the dependable baseline: current capability, current posture, and current product shape.
Everything on the roadmap has to earn its way in.
The roadmap stays disciplined: active baseline first, bounded next depth second, and later bridge work only where it still belongs.
Planning rule
Trust posture first
Roadmap depth only counts if review posture, clear boundaries, and operator control remain intact while the product grows.
The roadmap stays useful because the boundaries stay clear.
Active surfaces
Keep CLI, MCP, VSCode, and CI aligned around one shared operating model and one visible trust posture.
Workflow depth
Broaden useful follow-through while keeping review, preflight, and gating clear to operators.
Editor-native bridge depth
Reserve richer editor-side workflows for the phase where that boundary is ready to carry the same product discipline.