The accepted v1 contract is narrower than the architecture's long-term ambitions. Stilyagi is intentionally fixing a small, explicit day-one promise before broader syntax and locale work lands.
It does promise:
- one package-oriented installation story for v1;
- one in-process runtime boundary between Python orchestration and Rust extraction;
- no mandatory helper-binary management in normal use;
- a global
-V/--versionflag alongside theversionsubcommand; - a
--no-cacheoption forstilyagi check; - stable support for Markdown documents, Python docstrings, and Rust documentation comments; and
- English as the only formally supported v1 locale.[^1][^4]
It also promises that dump-ir and related debugging or fixture workflows will
use canonical JSON output, even though the in-process runtime may use a more
efficient transport internally.[^4]
It does not yet promise:
- the final end-user command set;
- full Markdown with JSX (MDX) support as part of the stable v1 syntax matrix;
- support for locales beyond English;
- the final release channels or installation instructions for each platform; or
- the exact debugging and diagnostic workflows, which land in later roadmap slices.[^3]