- All user-facing CLI output, prompts, help text, warnings, and error messages must be written in English only.
After modifying any .zig file, always run zig build run -- list to verify the changes work correctly.
- Run tests, review commands, and other side-effecting tooling from an isolated directory under
/tmp/<task-name>withHOME=/tmp/<task-name>.
- When updating and pushing a release version, always follow docs/release.md.
- Do not add low-level technical implementation details to
README.md. Put implementation-specific behavior indocs/*.mdorAGENTS.mdinstead.
- Do not guess Zig APIs from memory or from examples targeting other Zig versions.
- Before using or changing a Zig API, run
zig envandzig versionto confirm the local toolchain and source layout. - Use the paths reported by
zig envas the source of truth, especiallystd_dirfor the standard library andlib_dirfor other bundled Zig libraries. - Prefer evidence from local sources: symbol definitions, nearby tests, and existing call sites in this repository.
- If the needed behavior is not clear from
std_dir, inspect other Zig sources and tests under the locallib_dirtree as needed.