[Docs] frontend/README.md is stale - documents built features (Zustand, ui/ component library, Jest/Playwright tests, localized routes) as 'planned' and lists wrong scripts/structure

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

frontend/README.md describes the app as aspirational. It says State Management is React hooks + Context API (planned) though the app ships Zustand stores; Wallet Integration is Stellar Wallet Kit (planned) though package.json depends on @stellar/freighter-api; Button/Card/Modal/Input are listed under Planned Components though they exist in frontend/src/app/components/ui/; Testing is Planned though Jest, Playwright and frontend/e2e/ exist. Available Scripts omits test/test:e2e/typecheck/format/audit:a11y and claims npm run lint runs ESLint when package.json defines it as prettier --check. Project Structure lists a tailwind.config.ts that does not exist.

Acceptance criteria

• Rewrite README sections (Tech Stack, State Management, Wallet Integration, Component Library, Testing, Routing, Available Scripts, Project Structure) to reflect the shipped implementation
• List all real npm scripts and correct the lint description (prettier, not ESLint)
• Remove the nonexistent tailwind.config.ts reference and document the Tailwind 4 / globals.css token setup
• Replace the / and /404 Current Routes list with the real localized /[locale]/* routes

Files to touch

• frontend/README.md
• frontend/package.json
• frontend/src/app/components/ui
• frontend/src/app/globals.css

Out of scope

• Backend README
• Adding new features

[jammajo]

Hi! I would love to claim this issue. I have read the description and the acceptance criteria thoroughly. I can update the frontend/README.md right away to accurately reflect the current state of the project, including updating the tech stack (Zustand, Freighter API), correcting the npm scripts from package.json, updating the Tailwind v4 structure, and documenting the localized routes. Since there are no comments yet, I'm ready to be assigned and start working on it immediately. Thanks!

[OpadijoIdris]

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

I have read and understood the acceptance criteria. i can deliver

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

[CyberXpert607]

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

Hey team,

I'll take #1245.

I'll rewrite the frontend README to reflect what's actually shipped, Zustand stores, Freighter wallet integration, existing UI components, Jest/Playwright tests, localized routes, and all real npm scripts (test, test:e2e, typecheck, format, audit:a11y). Fix the npm run lint description to prettier --check, remove the nonexistent tailwind.config.ts reference, and document Tailwind 4 / globals.css token setup.

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

[iyanumajekodunmi756]

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

I would love to work on this issue

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

[amosleoamadi]

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

Can I work on this issue please?

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

[MethelyDev]

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

Hi maintainer, i would like to work on this issue, kindly assign me

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

[grantfox-oss]

🦊 GrantFox — @MethelyDev has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1245)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @MethelyDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @MethelyDev: 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 🌊