Contributing

Kirn is built in public. The best contributions are focused, reproducible, and honest about what the compiler currently supports.

Code contributions

1. Read the repository's contributing guide.
2. Build the project and run the relevant example or test.
3. Keep a change focused and explain the behavior it verifies.
4. Open a pull request with reproduction and verification notes.

Documentation contributions

Documentation examples should run with the current toolchain. If a claim compares Kirn with another language or promises a future feature, include a source or benchmark and label roadmap work clearly.

The docs site lives in docs-site/ and is deployed by GitHub Actions. Run npm install and npm run docs:build there before opening a docs pull request.