conventional-commitslisted

# Conventional Commits Format all commit messages according to the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. This enables automated changelog generation, semantic versioning, and better commit history. ## Format Structure ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` ## Commit Types ### SemVer-Mapped Core Types Use these types when they match the change; they are the only types with implicit SemVer meaning in the specification: - **`feat:`** - A new feature (correlates with MINOR in Semantic Versioning) - **`fix:`** - A bug fix (correlates with PATCH in Semantic Versioning) ### Common Additional Types - **`docs:`** - Documentation only changes - **`style:`** - Code style changes (formatting, missing semicolons, etc.) - **`refactor:`** - Code refactoring without bug fixes or new features - **`perf:`** - Performance improvements - **`test:`** - Adding or updating tests - **`build:`** - Build system or external dependencies changes - **`ci:`** - CI/CD configuration changes - **`chore:`** - Other changes that don't modify src or test files - **`revert:`** - Reverts a previous commit ## Scope An optional scope provides additional contextual information about the section of the codebase: ``` feat(parser): add ability to parse arrays fix(auth): resolve token expiration issue docs(readme): update installation instructions ``` ## Description - Must immediately follow the colon and space af