Duplicate Configuration Files

[RUKAYAT-CODER]

Description

Overview
Multiple duplicate files exist in the project root causing confusion and clutter.

Background
Files like "package copy.json", "package-lock copy.json", "App copy.tsx", "global copy.css", "babel.config copy.js", "env.d copy.ts", ".gitignore copy", ".env copy.example", "README copy.md", "README.old.md", and "assets copy/" folder are duplicates of the original files. These create confusion about which file is the source of truth and can lead to editing the wrong file.

Specifications

• Remove all duplicate files with "copy" suffix
• Remove "assets copy/" folder
• Keep only original files

Tasks:

• Remove duplicate config files
• Remove duplicate source files
• Remove duplicate asset folders

Impacted Files:

• package copy.json
• package-lock copy.json
• App copy.tsx
• global copy.css
• babel.config copy.js
• env.d copy.ts
• .gitignore copy
• .env copy.example
• README copy.md
• README.old.md
• assets copy/

Labels: project-structure, technical-debt, priority-high

🙌Contribution Guidelines:
Assignment required before PR submission
Timeframe: 48-72 hours
PR description must include: Close #1
Star the repo⭐
For more context, please refer to the mobile README

[ayomideadeniran]

@ayomideadeniran has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I'm a full-stack developer and I'd like to take this issue.
I understand the requirements and will follow the existing project structure, keep the implementation clean, and include proper tests where applicable.

ETA: 1–3 days (depending on scope)
Portfolio: https://knightsdev-portfolio.vercel.app/

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayomideadeniran to this issue.

[drips-wave]

Congratulations, @ayomideadeniran! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @ayomideadeniran: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @ayomideadeniran as part of the Stellar Wave Program's 4th Wave 🥳

😎 @ayomideadeniran: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.