docs(claude): add workflow rules (#3293)

* fix(home): handle GitHub API failures gracefully in releases/changelogs (#3291)

Wrap GitHub API calls in try/catch and return empty array on failure.
Prevents 422 errors when rate-limited or repos are unreachable.

* fix(home): align error tests with graceful GitHub API fallback

Tests now expect 200 with empty data when GitHub API fails, matching
the service's catch-and-return-empty-array behavior.

* docs(claude): add workflow rules — PRs required, thresholds, module audit

Author: PierreBrisorgueil

CLAUDE.md

@@ -67,6 +67,13 @@ Node / Express / Mongoose / JWT stack from Devkit. Standalone backend or fullsta
 - PRs: always use `/pull-request` — never open manually
 - After user correction, evaluate if the pattern belongs in `ERRORS.md`
 
+## Workflow rules
+
+- **Never push directly to master/main.** Always create a branch, push, create a PR, wait for CI green + review, then merge.
+- **Never lower coverage thresholds** in `jest.config.js`. If coverage drops after adding code, write tests for the new project modules to bring it back above thresholds.
+- **Audit existing modules before implementing.** Before creating new storage, file handling, or utility code, check `modules/` for existing solutions (e.g., `uploads` module for file storage via GridFS).
+- **Always run `/verify` after any code change** before declaring done. CI must be green.
+
 ## Skills
 
 | Skill | Description |