Add a project-structure map to the README

[Otaiki1]

Context

README.md has a tree listing around line 339, but it is partial and mixes documentation files with
source directories. A newcomer cannot tell from it which directory owns the circuit, which owns the
prover, or where the browser code that generates proofs actually lives.

Every issue in this backlog names its files; the README should make those names meaningful.

Where to build it

• README.md — the existing structure section around line 339.
• docs/architecture.md — the detailed version links from here.

What to do

• One table: directory, what it is, its language/toolchain, how to run its tests, and the label used for its issues (frontend, sdk, contracts, circuits).
• Cover app/, packages/client/, contracts/, circuits/, scripts/, docs/, judges/, test-vectors/.
• Fix the duplicated demo-video line at README lines 51–52 while you are in there — the same link line appears twice with different trailing links.
• Link each row to that directory's own README.

Acceptance criteria

• A newcomer can pick a directory to work in from the README alone.
• The duplicate line at lines 51–52 is gone.

[graceshaba93]

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

Hello Maintainer, I can fix this issue.
Please assign me.

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

[ibochielizabeth-spec]

@ibochielizabeth-spec has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hello maintainer i would like to fix this issues quicky....

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

[drips-wave]

Congratulations, @graceshaba93! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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