docs: add CONTRIBUTING with git flow branching model

[andyne13]

Documents the git flow branching model the team is adopting: long-lived main (production/tags) and develop (integration), with feature/*, release/X.Y.Z, and hotfix/* short-lived branches.

Covers:

• Branch roles and the from/into table
• When to cut a release branch (version-complete, stabilize without freezing develop) and how it closes (merge to main + tag + back-merge to develop)
• Hotfix flow
• PR targeting rules (features → develop; main only for release/hotfix)
• Local pre-push checks (ruff, layer-import guard, unit tests)

Summary by CodeRabbit

• Documentation
  • Added contribution guidelines covering branching, releases, hotfixes, and pull request workflows.
  • Documented local validation steps to run before pushing changes, including formatting, tests, and import checks.

[coderabbitai]

Warning

Review limit reached

@Ahmath-Gadji, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7c587cb5-cac9-45ec-bc4a-6854638996b2

📥 Commits

Reviewing files that changed from the base of the PR and between f7d620d and dcf555b.

📒 Files selected for processing (1)

• CONTRIBUTING.md

📝 Walkthrough

Walkthrough

Adds CONTRIBUTING.md with Git Flow branching and release guidance, pull request rules, CI expectations, and local verification commands.

Changes

Contributor Workflow

Layer / File(s)	Summary
Branching and verification guidance CONTRIBUTING.md	Documents feature, release, and hotfix workflows; pull request targets and CI requirements; and uv, ruff, pytest, and layer-import-check commands.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the new CONTRIBUTING guide and its Git Flow branching model.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/contributing-branching-guide

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 18-22: Update the fenced block in the contributing documentation
to include a `text` or `console` language identifier immediately after the
opening fence, while preserving the existing diagram content.
- Line 54: Update the release-job condition in the build workflow so version-tag
push events are not blocked by github.event.base_ref, which is unset for tag
pushes. Preserve the intended main-branch release gating through an appropriate
trigger or condition, then update the tagging guidance in CONTRIBUTING.md to
match the working GA build flow.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8bd5334d-377e-4d80-be3e-2b4e5b9dfbca

📥 Commits

Reviewing files that changed from the base of the PR and between af74a5d and f7d620d.

📒 Files selected for processing (1)

• CONTRIBUTING.md

[Ahmath-Gadji]

Docs-only change (CONTRIBUTING.md, git flow branching model). Verified branch names, commands, and CI workflow references against the actual repo state — all accurate. CodeRabbit's two findings addressed: markdownlint MD040 fixed, and the base_ref/GA-build claim confirmed correct against real release history (v1.1.5–v2.0.0 all built successfully on tag push).