The roadmap communicates direction, not delivery dates. Concrete work is tracked in GitHub Issues and milestones; breaking proposals begin in Discussions.
- Make onboarding, diagnostics, support, governance, and release evidence easy to discover.
- Keep the template, CLI, policy plugin, and showcase compatibility chain green across npm, pnpm, operating systems, and browsers.
- Reduce architecture-rule false positives without weakening default boundaries.
- Publish versioned documentation and direct rule diagnostics to stable repair guides.
- Add real-world recipes from adopter feedback.
- Establish a second reviewer/maintainer path and verified good-first-issue queue.
- Expand state-manager adapters only when another implementation has a real user.
- Add package and microfrontend tooling where independent ownership and deployment prove the need.
- Publish adopter stories and ecosystem integrations backed by public evidence.
JST will not add runtime telemetry, a proprietary feature tier, or architectural complexity solely to expand the roadmap.