[ayushcmd]

Summary

Organizes the CloudMonitor documentation into a dedicated docs/ folder and keeps the repository root clean.

Structure

• README.md (root): short GitHub landing page linking to the documentation folder.
• docs/README.md: full project overview, live demo warning, problem statement, technology stack, architecture diagram, local installation, endpoint summary and team.
• docs/PROJECT_BUILD_AND_ARCHITECTURE.md: in-depth design, frontend/backend, API routes, agent telemetry flow, PostgreSQL, Prometheus, Node Exporter, Grafana, cAdvisor, Alertmanager, local setup and limitations.
• docs/AWS_DEPLOYMENT_AND_OPERATIONS.md: EC2/Compose deployment, networking, environment configuration, monitoring, CI/CD status, planned Systems Manager migration, PostgreSQL backup/restore, rollback, cost considerations and troubleshooting.

Accuracy and safety notes

• Distinguishes local Compose from the production Compose stack.
• Records the current demo URL as HTTP, and warns against sending real credentials or agent keys over it.
• Notes that Grafana and cAdvisor are in local Compose but not in the current production Compose stack; cAdvisor is not a current Prometheus scrape target.
• Notes that Alertmanager webhook receiver lists are empty, so external notification delivery is not claimed as working.
• Preserves PostgreSQL volume safety requirements and records Systems Manager migration as future work.
• Lists Sarnendu Das, Parveen Kumar and Ayush Raj equally without assigning unconfirmed individual roles.
• Fixes the stale clone URL that pointed to a different repository and updates links for the new docs/ locations.

Validation

• Fetched the three documentation files from the branch after writing them.
• Moved the two detailed guides and full project README into docs/, then verified their contents are present there.
• Removed the duplicate full-length guide files from the repository root.
• No application code, Compose files, workflows, AWS resources or production data were modified.

Review caution

This PR is not merged. Merging into main may trigger the existing production CD workflow; recent SSH connectivity failures remain unresolved, so review the workflow behavior before merging.