git:20260430.b63f86a to git:20260708.6173c8e

- # Project

- Read @CLAUDE.md

-

- @CLAUDE.md contains the shared local development rules for both Claude Code and Codex contributors.

-

- # Commit Conventions

-

- The commit message SHALL be structured like this:

-

- ```

- <type>[optional scope]: <description>

-

- [optional body]

-

- [optional footer(s)]

- ```

-

- Use conventional commits types:

-

- - `feat:` for new features (correlates with MINOR in Semantic Versioning)

- - `fix:` for bug fixes (correlates with PATCH in Semantic Versioning)

- - `perf:` for performance improvements

- - `refactor:` for code restructuring

- - `test:` for test additions/changes

- - `docs:` for documentation

- - `spec:` for spec changes

- - `chore:` for maintenance tasks

-

- BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.