docs: update commit convention to match branch naming — full words, no scopes

Author: RandomCrocodile

CONTRIBUTING.md

@@ -129,20 +129,43 @@ dotnet test Tests/Confuser.CLI.Test/Confuser.CLI.Test.csproj -c Release --collec
 
 Every PR receives an automatic coverage comment showing per-assembly line and branch coverage. The full HTML drill-down report is downloadable as the `coverage-report` artifact from the test workflow.
 
-## Commit Conventions
-
-We use [Conventional Commits](https://www.conventionalcommits.org/):
+## Commit Format
 
 ```
-feat(scope): add new feature
-fix(scope): fix a bug
-test(scope): add or update tests
-refactor(scope): code change that doesn't fix a bug or add a feature
-chore(scope): build, CI, dependency updates
-docs(scope): documentation changes
+<type>: <short description>
+
+[optional body — what changed and why]
 ```
 
-Always reference the issue number: `fix(renamer): handle FnPtr types (#6)`
+**Types** — full words, matching branch naming:
+
+| Type | When to use |
+|------|-------------|
+| `feature` | New feature or capability added |
+| `fix` | Bug fix |
+| `test` | Adding or updating tests |
+| `refactor` | Code change that neither fixes a bug nor adds a feature |
+| `chore` | Build config, dependencies, tooling, project setup |
+| `docs` | Documentation only changes |
+| `hotfix` | Urgent fix applied directly to main |
+| `experiment` | Exploratory or throwaway work |
+
+**Rules:**
+- Full words only — no abbreviations (`feature` not `feat`)
+- No parenthesized scopes — the description should be clear enough
+- Reference issue number at end when applicable: `(#42)`
+- Lowercase first word after colon
+
+**Examples:**
+
+```
+feature: add symbol server support (#54)
+fix: handle locked file exception on folder scan (#42)
+test: add cross-framework integration tests
+chore: update dependencies
+docs: add plugin development guide
+refactor: extract base repository to reduce duplication
+```
 
 ## Pull Request Process