Rezi is maintained as a determinism-first terminal UI framework with strict safety and module boundaries.
- Maintainers: review and merge pull requests, cut releases, own roadmap decisions.
- Contributors: propose changes via issues/PRs, improve tests/docs/widgets/backends.
Default approach:
- Open an issue (or PR) with a concrete proposal and examples.
- Prefer small, reviewable changes over broad refactors.
- If consensus isn’t reached, maintainers decide with project constraints as the rubric.
@rezi-ui/coreis the primary public API surface.- Binary protocols (drawlists and event batches) are versioned and must remain backward compatible within a major line.
- Behavior changes should be deterministic and documented.
Please follow SECURITY.md. For crashers, include:
- OS + terminal emulator
- Node version
- minimal reproduction
- any relevant binary dumps (drawlist/event batch) if available