chore(ci): trigger initial CI checks for branch protection setup

[Alan-TheGentleman]

🔗 Linked Issue

Closes #54

---

🏷️ PR Type

• type:chore — Build, CI, or tooling changes

---

📝 Summary

• One-time dummy PR to trigger all 5 CI checks so GitHub registers them for branch protection rules

📂 Changes

File / Area	What Changed
CONTRIBUTING.md	Added version comment (trivial change to trigger CI)

---

🧪 Test Plan

• Unit tests pass (go test ./...)
• E2E tests pass (cd e2e && ./docker-test.sh)
• Manually tested locally

---

🤖 Automated Checks

Check	Status	Description
Check Issue Reference	⏳	PR body must contain Closes/Fixes/Resolves #N
Check Issue Has status:approved	⏳	Linked issue must have been approved before work began
Check PR Has type:* Label	⏳	Exactly one type:* label must be applied
Unit Tests	⏳	go test ./... must pass
E2E Tests	⏳	cd e2e && ./docker-test.sh must pass

---

✅ Contributor Checklist

• PR is linked to an issue with status:approved
• I have added the appropriate type:* label to this PR
• Unit tests pass (go test ./...)
• E2E tests pass (cd e2e && ./docker-test.sh)
• I have updated documentation if necessary
• My commits follow Conventional Commits format
• My commits do not include Co-Authored-By trailers

---

💬 Notes for Reviewers

This is a one-time dummy PR to trigger all CI workflows. Once checks are registered, set them as required status checks in branch protection for main. Merge and delete the branch after.

[Alan-TheGentleman]

Closing without merge — the CI checks are already registered and configured as required status checks on main. This dummy PR fulfilled its purpose without needing to land.