fix: update non-existent apps/frontend paths to apps/dashboard and align docs

[Deepthit-23]

Closes #160

Changes

• Updated Makefile to install frontend dependencies in apps/dashboard instead of the non-existent apps/frontend directory.
• Updated references from Next.js to React 19 + Vite in README.md and docs/ARCHITECTURE.md to align with the actual project structure and dependencies inside apps/dashboard.
• Replaced the Next.js badge in README.md with a React badge.

Summary by CodeRabbit

• Documentation

  • Updated frontend references throughout the README and architecture docs to reflect the current React-based dashboard and revised project structure.
  • Adjusted roadmap and tech stack descriptions to match the latest frontend setup.

• Chores

  • Updated the frontend install step so setup now targets the dashboard app location.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Makefile's install-frontend target is updated to install dependencies from apps/dashboard instead of apps/frontend. README.md and docs/ARCHITECTURE.md are updated to reflect the frontend framework switch from Next.js to React and the corrected directory path.

Changes

Frontend path and framework reference updates

Layer / File(s)	Summary
Fix install-frontend target path Makefile	The install-frontend target now runs npm install in apps/dashboard instead of the non-existent apps/frontend directory.
Update README frontend references README.md	Badge, architecture bullet, service breakdown table, tech stack table, and roadmap milestone are updated from Next.js 14 to React 19 (with Vite).
Update ARCHITECTURE.md frontend references docs/ARCHITECTURE.md	Overview text, component overview table, and data flow diagram are updated to reference the React dashboard in apps/dashboard.

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

Related issues: #160

Suggested labels: documentation, bug

Suggested reviewers: Devnil434

🐰 A hop from frontend to dashboard's door,
Next.js retires, React takes the floor,
The Makefile now finds its way just right,
Docs update their words, crisp and bright,
No more lost paths in the burrow tonight!

🚥 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 clearly summarizes the main fix: updating frontend paths and related docs.
Linked Issues check	✅ Passed	The Makefile and architecture docs now reference apps/dashboard as required, resolving the missing-path bug in #160.
Out of Scope Changes check	✅ Passed	The changes stay within the requested Makefile and documentation updates, with no unrelated code additions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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: 1

🤖 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 `@README.md`:
- Line 10: The repo still has consumer-facing references to the old frontend
path and framework in the issue templates, creating inconsistent guidance with
the updated README. Update the affected template text and any related
user-facing references so they point to apps/dashboard and React instead of
apps/frontend and Next.js, using the existing template strings and labels to
locate the stale references.

🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: be297a8f-1e9d-47a6-9714-0a3aaaafe132

📥 Commits

Reviewing files that changed from the base of the PR and between 147b2c0 and c97fc8f.

📒 Files selected for processing (3)

• Makefile
• README.md
• docs/ARCHITECTURE.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Update the remaining consumer-facing references too.

The README now points to apps/dashboard/React, but the issue templates still send contributors to apps/frontend and Next.js. That leaves the repo in a mixed state and keeps the old path alive in user-facing flows.

Also applies to: 81-81, 94-94, 109-109, 324-324

🤖 Prompt for 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.

In `@README.md` at line 10, The repo still has consumer-facing references to the
old frontend path and framework in the issue templates, creating inconsistent
guidance with the updated README. Update the affected template text and any
related user-facing references so they point to apps/dashboard and React instead
of apps/frontend and Next.js, using the existing template strings and labels to
locate the stale references.