commitlisted

Create a git commit for the current changes using a concise Conventional Commits-style subject. ## Format `<type>(<scope>): <summary>` - `type` REQUIRED. Use `feat` for new features, `fix` for bug fixes. Other common types: `docs`, `refactor`, `chore`, `test`, `perf`,`ci`, `style`. - `scope` REQUIRED. Short noun in parentheses for the affected area (e.g., `api`, `parser`, `ui`). - `summary` REQUIRED. Short, imperative, <= 72 chars, no trailing period. ## Explanations fix: A bug fix. Correlates with PATCH in SemVer feat: A new feature. Correlates with MINOR in SemVer docs: Documentation only changes style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) refactor: A code change that neither fixes a bug nor adds a feature perf: A code change that improves performance test: Adding missing or correcting existing tests build: Changes that affect the build system or external dependencies (example scopes: pip, docker, npm) ci: Changes to CI configuration files and scripts (example scopes: GitLabCI) ## Notes - Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs. - Do NOT include breaking-change markers or footers. - Do NOT add sign-offs (no `Signed-off-by`). - **Never add AI attribution anywhere in commit metadata.** Do not write `Generated by ...`, `Co-authored-by: Claude`, `Co-authored-by: Opus`, `Co-authored-by: Sonnet`, or any other AI/model/agent attribution. - This ban applie