docs: add conventional commit guidelines and fix CI workflows

.github/COMMIT_CONVENTION.md

@@ -0,0 +1,41 @@
+# Commit Message Convention
+
+This project follows the [Conventional Commits](https://www.conventionalcommits.org/) specification.
+
+## Format
+
+```
+type(scope): subject
+
+body
+
+footer
+```
+
+## Types
+
+- `feat`: A new feature
+- `fix`: A bug fix
+- `docs`: Documentation changes
+- `style`: Code style changes (formatting, missing semi-colons, etc.)
+- `refactor`: Code refactoring
+- `perf`: Performance improvements
+- `test`: Adding or updating tests
+- `build`: Changes to build system or dependencies
+- `ci`: Changes to CI configuration
+- `chore`: Other changes that don't modify src or test files
+
+## Examples
+
+```
+docs(readme): add installation instructions
+
+feat(auth): implement JWT authentication
+
+fix(api): resolve null pointer exception in user endpoint
+```
+
+## Validation
+
+All commits are validated using commitlint with the conventional config.
+See `commitlint.config.js` for configuration details.

.github/COMMIT_HISTORY_NOTE.md

@@ -0,0 +1,17 @@
+# Commit History Note
+
+## Commit 5827b78
+
+The commit `5827b78a46e74d34111955ec815b84c5a31fa34f` with message:
+"Enhance README with project details and structure"
+
+Should have followed conventional commit format as:
+```
+docs(readme): add comprehensive project documentation
+
+Added detailed sections covering project overview, vision, goals, features,
+tech stack, architecture, testing guidelines, and contribution workflow.
+```
+
+This note documents the correct format for reference. Future commits will follow
+the conventional commit specification as enforced by commitlint.