docs: add root project README

[poyrazK]

Summary

• add a root-level README.md describing the CloudMedia backend scope and current service layout
• document local development setup (prerequisites, make dev-up/dev-down/dev-reset, and service run command)
• link API contract and implementation planning docs for onboarding

Verification

• docs-only change; validation will run in CI (docs-and-contracts)

Summary by CodeRabbit

• Documentation
  • Added comprehensive README documenting the CloudMedia backend platform, including setup prerequisites, local development workflows, microservice information, and infrastructure management commands.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new README.md file is added to the repository root, documenting the CloudMedia backend platform, including project overview, implemented microservices, setup prerequisites, development workflows with make commands, and repository structure guidance.

Changes

Cohort / File(s)	Summary
Documentation README.md	New top-level README introducing CloudMedia backend platform, detailing Java microservices, prerequisites (Java 21+, Maven 3.9+, Docker), local development workflows using make commands, and repository layout with docs/ reference locations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A README hops into place,
Guiding devs through backend space—
Microservices, ports, and make commands bright,
Docker Compose and infrastructure in sight!
Welcome, friend, to CloudMedia's might! 🚀

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: add root project README' directly and specifically describes the main change - adding a root-level README file to the repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/add-root-readme

---

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 and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

README.md (1)

75-77: Make doc references clickable for faster navigation.

Consider replacing inline code paths with markdown links so readers can jump directly from the README.

Suggested doc-link refinement

-- REST API contract: `docs/contracts/rest-api-v1.md`
-- MVP backend plan: `docs/mvp-backend-implementation-plan.md`
-- Modular rollout roadmap: `docs/modular-implementation-roadmap.md`
+- REST API contract: [docs/contracts/rest-api-v1.md](docs/contracts/rest-api-v1.md)
+- MVP backend plan: [docs/mvp-backend-implementation-plan.md](docs/mvp-backend-implementation-plan.md)
+- Modular rollout roadmap: [docs/modular-implementation-roadmap.md](docs/modular-implementation-roadmap.md)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 75 - 77, The README currently shows plain inline code
paths for documents; change those to markdown links so they are clickable by
replacing occurrences like `docs/contracts/rest-api-v1.md`,
`docs/mvp-backend-implementation-plan.md`, and
`docs/modular-implementation-roadmap.md` with markdown link syntax (e.g. [REST
API contract](docs/contracts/rest-api-v1.md)) and similar descriptive link text
for the other two entries; update the list items in README.md to use these link
labels so readers can jump directly to the docs.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@README.md`:
- Around line 75-77: The README currently shows plain inline code paths for
documents; change those to markdown links so they are clickable by replacing
occurrences like `docs/contracts/rest-api-v1.md`,
`docs/mvp-backend-implementation-plan.md`, and
`docs/modular-implementation-roadmap.md` with markdown link syntax (e.g. [REST
API contract](docs/contracts/rest-api-v1.md)) and similar descriptive link text
for the other two entries; update the list items in README.md to use these link
labels so readers can jump directly to the docs.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ee9eb0fd-8142-4118-b63a-22ded112b524

📥 Commits

Reviewing files that changed from the base of the PR and between 66dea9e and 9e237d0.

📒 Files selected for processing (1)

• README.md