Create CONTRIBUTING.md with contributor guidelines

[Copilot]

Description

Resolves #(issue)

Created comprehensive CONTRIBUTING.md consolidating contributor guidelines scattered across README.md. Removed duplicated content from README to maintain single source of truth.

Changes

• CONTRIBUTING.md (new): 338-line document covering:

  • Prerequisites: Java 25 installation via SDKMAN
  • Development workflow: build commands, test execution, CheckStyle enforcement
  • Code patterns: fluent interface, immutability, Lombok usage, validation
  • PR process: branching strategy, checklist, code review expectations
  • Project structure: monorepo modules and their purposes
  • Quality gates: CheckStyle, SonarCloud, CodeQL integration

• README.md: Removed 22 lines of duplicated content:

  • Java installation instructions → link to CONTRIBUTING.md
  • Code quality tools paragraph → moved to CONTRIBUTING.md
  • Contributing section → enhanced with structured references

Structure

CONTRIBUTING.md
├── Code of Conduct
├── Getting Started (Java 25 setup)
├── Development Workflow (build/test/style)
├── Making Changes (coding patterns, tests)
├── Submitting Changes (PR checklist, review)
├── Project Structure (modules overview)
└── Additional Resources (links)

Checklist:

• Public methods are documented
• Public methods are tested
• New and existing tests pass when run locally
• There are no new warnings or errors

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Chore]: Create a CONTRIBUTING.md document</issue_title>
<issue_description>### What

Draft a CONTRIBUTING.md document for the repository. Incorporate key usage/setup steps and coding style guidance from the README where relevant.

Duplicated information should be removed from the README.

Why

A clear contributing guide improves project maintainability and consistency for all contributors.

Notes

Include sections on code formatting, pull request process, and testing procedures as outlined or referenced in the README. Make sure example usages or build/run instructions from the README appear in appropriate places. Final draft should be reviewed by maintainers before merging.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Chore]: Create a CONTRIBUTING.md document #383

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull Request Overview

This PR creates a comprehensive CONTRIBUTING.md document that consolidates scattered contributor guidelines from README.md, establishing a single source of truth for development workflows and contribution processes.

Key Changes:

• Created detailed CONTRIBUTING.md (338 lines) covering prerequisites, development workflow, code patterns, PR process, project structure, and quality gates
• Streamlined README.md by removing 22 lines of duplicated content (Java installation, code quality tools) and replacing with references to CONTRIBUTING.md
• Enhanced the Contributing section in README.md with structured bullet points linking to specific CONTRIBUTING.md sections

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
CONTRIBUTING.md	New comprehensive contributor guide covering Java 25 setup, build/test procedures, code style enforcement (CheckStyle/Google Java Style Guide), PR workflow, project structure, and integration with SonarCloud/CodeQL
README.md	Removed duplicated Java installation instructions and code quality tool descriptions; replaced Contributing section with structured links to CONTRIBUTING.md sections

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud