commit-authorlisted

# Git Commit Standards ## 1. Format * **Structure:** `<type>(<optional scope>): <subject>` ## 2. Allowed Types Full Conventional Commits v1.0.0 type set (Angular convention): | Type | When to use | |---|---| | `feat` | New feature for the user (MINOR in SemVer) | | `fix` | Bug fix for the user (PATCH in SemVer) | | `refactor` | Code change that neither fixes a bug nor adds a feature | | `perf` | Code change that improves performance | | `docs` | Documentation-only changes | | `style` | Formatting, whitespace, semicolons — no code-meaning change | | `test` | Adding or correcting tests; no production code change | | `build` | Build system or external dependency changes (e.g. npm, go.mod, Dockerfile) | | `ci` | CI configuration changes (GitHub Actions, pipelines) | | `chore` | Maintenance tasks that don't fit elsewhere (no src/test changes) | | `revert` | Reverts a previous commit; body must reference the reverted SHA | ## 3. Subject Line * **Rules:** Use imperative mood (e.g., `add`, not `added`), maximum 50 characters, lowercase start, and no trailing period. ## 4. Body * **Content:** Explain *why* the change was made, not *what* changed. Do not write line-by-line file summaries. * **Formatting:** Hard wrap lines at 72 characters. ## 5. Footers * **Breaking Changes:** Must begin with `BREAKING CHANGE:` followed by a migration path. Applies to any type and forces a MAJOR version bump. * **References:** Append related issues at the bottom (e.g., `Resolves #12`). ## 6. At