hermes - 💡(How to fix) Fix Docs: CONTRIBUTING.md missing PR submission workflow (fork → branch → PR)

Summary

CONTRIBUTING.md covers dev environment setup well but is missing the PR submission workflow entirely — the guide stops at "clone and run tests" without explaining how to actually contribute code back.

What's Missing

The typical open-source contribution flow is:

fork → clone → branch → code → push → open PR → review → merge

CONTRIBUTING.md jumps straight to git clone https://github.com/NousResearch/hermes-agent.git, skipping both the fork step and the PR submission step. New contributors may not know they need to fork first to push a branch.

Bonus: Fine-Grained Token Gotcha

If the fork step is documented, it's worth adding a note: GitHub fine-grained personal access tokens cannot fork repositories the user doesn't own. Attempting to fork NousResearch/hermes-agent with a fine-grained token returns 403 regardless of configured permissions. The workaround is OAuth authentication:

gh auth login --web -p https

This is a GitHub platform limitation, not a Hermes bug, but worth mentioning so contributors don't waste time debugging token permissions.

Suggested Change

Add a "Submitting Changes" section to CONTRIBUTING.md covering:

1. Fork the repo (with the fine-grained token note)
2. Create a feature branch
3. Make changes + run tests
4. Push and open a PR
5. Link to any PR template or review guidelines

Environment

• GitHub fine-grained PAT: fork API → 403 (by design)
• GitHub OAuth via gh auth login: works correctly