Forthcoming Capabilities
Design-stage write-ups of capabilities that are specified in Netsuke's design documents and RFCs but have not shipped. Each page says what is designed, what is implemented on a branch, and which release the preview is targeted at. Names, flags, and file formats here may change before they land.
Netsukefile Linter
Deterministic manifest linting under netsuke check, inspired by mbake. A stable rule catalogue covering
style, correctness, and portability; per-rule severity policy; an explainable rule reference; and
findings that share the compiler's own diagnostics envelope. Findings never mutate the manifest.
Netsukefile Testing Framework
Manifest-time tests under netsuke test that run through the same compiler as the build. A YAML test dialect
beside the manifest, mock and fixture engines so a test never touches the real host, and assertions over the
expanded manifest, the build graph, and the generated Ninja.
How to read a preview
- Designed means the behaviour is specified in an RFC, ADR, or design document in the Netsuke repository, and the page links to it.
- Implemented on a branch means code exists against the design but has not been merged and released. Treat it as evidence the design is buildable, not as a contract.
- Preview targeted at names the release in which the capability is planned to appear behind a preview label. The roadmap tracks the current sequence, and the task-level roadmap the detail.