fix(client): resolve page corruption and restore stable Dashboard, Login and Register implementations

[AasthaOswal]

Summary

This PR fixes multiple frontend pages that contained corrupted/incorrectly merged JSX code resulting in build failures and broken UI rendering.

Changes Made

• Restored Dashboard page to a clean working version.
• Restored Login page to a clean working version.
• Restored Register page to a clean working version.
• Removed duplicated and incorrectly merged JSX blocks
• Verified that all restored pages compile successfully.

Root Cause

During investigation, several frontend pages were found to contain corrupted code caused by incorrectly merged implementations. In particular, Dashboard contained multiple dashboard layouts merged into a single component, resulting in invalid JSX and build failures.

The stable versions were recovered from earlier working commits and used as the baseline for restoration.

Testing

• Dashboard page renders correctly.
• Login page renders correctly.
• Register page renders correctly.

Issue

Closes #309

[vercel]

@AasthaOswal is attempting to deploy a commit to the souma9830's projects Team on Vercel.

A member of the Team first needs to authorize it.

[AasthaOswal]

Hi @souma9830,

I would like to request a reconsideration of the issue level from Level 2 to Level 3.

The fix required investigating multiple affected pages (Register, Login, and Dashboard), reviewing historical commits, identifying the last stable implementations, and restoring the correct code after merge/corruption issues across files.

Thank you for considering the re-evaluation.

[AasthaOswal]

Hi @souma9830,

The frontend page corruption has been resolved, and the code now compiles cleanly.

Could you please review the following when you have a moment?

1. Update the PR tag to Level 3 : As noted in the linked issue, resolving this required extensive troubleshooting—including investigating multiple affected pages (Register, Login, and Dashboard), tracing historical commits to find the last stable baselines, and clean-merging the fixes.
2. Merge the PR: If everything looks good on your end, it's ready to go.

Thank you for your time and guidance!

[AasthaOswal]

Hi @souma9830,

I updated this PR with the latest master branch and resolved the merge conflicts.

While investigating the failing client CI check, I found that the failure appears to be unrelated to the Dashboard/Login/Register restoration changes in this PR.

The current lint job fails because ESLint cannot find a configuration file:

"ESLint couldn't find a configuration file."

I verified that the repository contains ESLint dependencies and a lint script, but no tracked ESLint configuration file (eslint.config.js or .eslintrc.*).

I also tested locally by adding a temporary ESLint configuration to understand the failure. ESLint then ran successfully but reported a large number of existing repository-wide lint issues, indicating that the current CI failure is not specific to the changes in this PR.

Could you please take a look at the lint configuration/CI setup when you have a chance?

Thank you.

[souma9830]

Nsoc ????

[AasthaOswal]

@souma9830 Yes, I am contributing from NSOC