docs: rename workflows for clarity

Before (industry jargon):
- ci.yml → name: CI (what does CI mean?)
- cd.yml → name: CD (what does CD mean?)

After (descriptive verbs):
- validate.yml → name: Validate (validates code quality)
- release.yml → name: Release (publishes releases)

New developer experience:
- See 'validate.yml' → understands: this validates something
- See 'release.yml' → understands: this releases something
- No need to know CI/CD terminology

Comments also explain:
- What triggers each workflow
- What each workflow does
- Expected behavior

Author: tracer-mohist

.github/workflows/cd.yml .github/workflows/release.yml.github/workflows/cd.yml renamed to .github/workflows/release.yml

@@ -1,11 +1,17 @@
-# .github/workflows/cd.yml
+# .github/workflows/release.yml
 #
-# Continuous Delivery
-# Triggers on push to main
-# Publishes release if semantic-release detects changes
+# Publishes new releases automatically
+# Uses semantic-release to calculate version from commit messages
+#
+# Triggers:
+# - Push to main (after validation passes)
+#
+# Behavior:
+# - If commits follow Conventional Commits: creates new release
+# - If no release-worthy commits: skips silently
 #
 
-name: CD
+name: Release
 
 on:
   push:

.github/workflows/ci.yml .github/workflows/validate.yml.github/workflows/ci.yml renamed to .github/workflows/validate.yml

@@ -1,11 +1,14 @@
-# .github/workflows/ci.yml
+# .github/workflows/validate.yml
 #
-# Continuous Integration
-# Runs on PR and push to main
-# Validates: test, lint, commit message, documentation
+# Validates code quality on every change
+# Runs: tests, linting, commit message format, documentation checks
+#
+# Triggers:
+# - Pull requests to main
+# - Direct pushes to main (safety net)
 #
 
-name: CI
+name: Validate
 
 on:
   push: